Overview

Providers are global carrier trunks or external services used by routing profiles, inbound DIDs, SMS,SMS delivery, and billing.cost handling. Use Admin > Providers to create SIP, PJSIP, IAX2, DAHDI, LOCAL, or SMS providers and to review live inbound and outbound channel counters.

ProviderTechnology IdentitySelection

Technology	Use for	Typical fictional example
SIP	Legacy chan_sip carrier trunks or IP-authenticated SIP gateways.	Docs Telecom SIP Trunk at 203.0.113.20
PJSIP	Modern res_pjsip carrier trunks with endpoint, AOR, auth, and identify rows.	Docs Telecom PJSIP Trunk with TLS/SRTP
IAX2	IAX2 gateways or legacy interconnects.	Docs IAX2 Gateway on port 4569
DAHDI	Analog, PRI, or hardware channel-group routing controlled outside SIP/PJSIP realtime.	Docs Analog Gateway
LOCAL	Local PBX routing targets that should be selected like a descriptiveprovider.	Docs nameLocal forRoute
SMS	SMS administratorsdelivery via HTTP, JSON, SOAP, SIP MESSAGE, SMSPortal, or AGI script.	Docs SMS JSON Gateway

Configuration Workflow

• Create or open a provider from Admin > Providers.
• Complete the shared identity, outbound, and ainbound stable peer namefields that matchesapply to the selected technology.
• For SIP, PJSIP, or IAX2, enable Use Realtime Account when MiRTA PBX should maintain the Asterisk peer,realtime PJSIP endpoint, IAX peer, local target, or SMS gateway identifier. Choose the technology and keeprows.
• Save the provider enabledonly unlessafter itreplacing isthe fictional documentation values with carrier-supplied production values.
• Assign providers to routing profiles and test inbound DID matching, outbound dialing, caller ID presentation, and SMS delivery.

Operational Notes

• Provider changes are global and can affect multiple tenants, routing profiles, DIDs, and SMS routes.
• Use documentation-reserved IP addresses and example domains only anfor inboundtraining reference.material;

  Outboundnever Calleruse ID

  them

  in production trunks.

• Provider-level CallerID and CallerID Name areoverride optionalextension-derived provider-levelcaller overrides.ID When one of them is filled,for every call routed through the provider uses that caller ID value regardless of extension caller ID, caller ID modification, regex fallback, or emergency caller ID settings.

  Leave both fields blank to have the caller ID set from the extension and the normal outbound caller ID rules. Use the override only when the carrier requires one fixed presentation number or name for the trunk.

  

  Routing and Limits

  Digits to add/remove normalize dialed numbers before delivery. Caller ID presentation controls privacy and screening flags. provider.

• Max outbound channels protectsprevents thea trunk from overuse;being whenoverused. When the limit is reached, routing skipscan continue to the next availableanother provider.

  Inbound and SMS

  Inbound digit manipulation and DID modification run before DID matching. SMS providers expose protocol-specific URL, JSON, SOAP, AGI, SIP MESSAGE, authentication, and content-type fields.