Skip to main content

Overview

ManageProviders are global carrier trunks andor external service providersservices used by routing profiles, inbound DIDs, SMS, and billing.

Use Admin > OverviewProviders to managecreate overview.

SIP,

ThisPJSIP, pageIAX2, isDAHDI, aLOCAL, startingor pointSMS forproviders administrators:and to review existinglive records, add only the objects needed by the deployment,inbound and keepoutbound nameschannel consistent across tenants, routing, and provisioning.counters.

TypicalProvider WorkflowIdentity

    Open the menu entry and confirm whether the record already exists. Create or edit the record with

    Use a descriptive name for administrators and a stable peer name that matches the Asterisk peer, PJSIP endpoint, IAX peer, local target, or SMS gateway identifier. Choose the technology and keep the provider enabled unless it is only thean requiredinbound optionsreference.

    first.

    Outbound

    SaveCaller ID

    CallerID and CallerID Name are optional provider-level overrides. When one of them is filled, every call routed through the recordprovider 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 reopenthe itnormal outbound caller ID rules. Use the override only when the carrier requires one fixed presentation number or name for the trunk.

    Provider outbound caller ID override fields
    Outbound provider settings with fictional caller ID override values.

    Routing and Limits

    Digits to verifyadd/remove normalize dialed numbers before delivery. Caller ID presentation controls privacy and screening flags. Max outbound channels protects the storedtrunk values.

    from Checkoveruse; dependentwhen objectsreached, routing skips to the next available provider.

    Inbound and SMS

    Inbound digit manipulation and DID modification run before deletingDID anythingmatching. thatSMS mayproviders beexpose usedprotocol-specific byURL, routing,JSON, billing,SOAP, provisioning,AGI, orSIP reporting.

    MESSAGE,

    Documentation Example

    For documentationauthentication, and testing,content-type use names prefixed with Docs Demo. Existing PBX nodes should be reused as examples; do not create additional nodes unless the deployment actually requires them.fields.

    Back to top