LOCAL Provider
Use LOCAL technology when a PBX-local route should be selected by routing profiles like a provider. LOCAL providers do not create SIP, PJSIP, or IAX realtime rows.
LOCAL Field Details
| Field | Applies to | Purpose | Fictional example |
|---|---|---|---|
| Technology | LOCAL only | Uses a local route target instead of an external SIP/IAX/DAHDI carrier account. | LOCAL |
| Peer Name | LOCAL only | Stable local-route identifier for administrators and routing profiles. | docs_local_route |
| Digits to Add / Remove | LOCAL only | Normalizes the number before local routing. | No add, remove 0 |
| CallerID and CallerID Name | LOCAL only | Optionally forces caller ID for calls sent through the local route. | +15551230000 and Docs Local |
| Max outbound channels | LOCAL only | Limits local-route concurrency, or Unlimited when no limit is needed. | Unlimited |
| Inbound options | LOCAL when used for inbound-like routing | Can still normalize destination numbers and set custom variables before matching. | Normalize number checked |
Shared Fields Still Used
LOCAL providers still use common identity, status, outbound digit manipulation, caller ID controls, max outbound channels, penalty, inbound normalization, DID modification, and custom variable fields. Additional SIP/SMS headers and realtime account settings are hidden.
Fictional LOCAL Example
Name: Docs Local Route
Peer Name: docs_local_route
Technology: LOCAL
Status: Enabled
Max outbound channels: Unlimited
Penalty: 50