Overview
Providers are global carrier trunks or external services used by routing profiles, inbound DIDs, SMS delivery, and cost handling. Use Admin > Providers to create SIP, PJSIP, IAX2, DAHDI, LOCAL, or SMS providers and to review live channel counters.
Technology Selection
| 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 provider. | Docs Local Route |
SMS | SMS delivery 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 inbound fields that apply to the selected technology.
- For SIP, PJSIP, or IAX2, enable Use Realtime Account when MiRTA PBX should maintain the Asterisk realtime rows.
- Save the provider only after replacing the 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 for training material; never use them in production trunks.
- Provider-level CallerID and CallerID Name override extension-derived caller ID for every call through the provider.
- Max outbound channels prevents a trunk from being overused. When the limit is reached, routing can continue to another provider.