Routes
From Taridium
| Line 1: | Line 1: | ||
| - | Routes basically tell ipbx what to do with incoming and outgoing calls. In a standard configuration any SIP, IAX or PSTN call is processed by 'Inbound Routing', in the same way any calls to extensions that cannot be found locally are sent to the 'Outbound Routing' for further processing. Note that some special applications such as Multi | + | Routes basically tell ipbx what to do with incoming and outgoing calls. In a standard configuration any SIP, IAX or PSTN call is processed by 'Inbound Routing', in the same way any calls to extensions that cannot be found locally are sent to the 'Outbound Routing' for further processing. Note that some special applications such as [[Multi Site]] Support do not need outbound/inbound routing configuration. |
== Inbound Routing == | == Inbound Routing == | ||
Revision as of 19:56, 20 November 2008
Routes basically tell ipbx what to do with incoming and outgoing calls. In a standard configuration any SIP, IAX or PSTN call is processed by 'Inbound Routing', in the same way any calls to extensions that cannot be found locally are sent to the 'Outbound Routing' for further processing. Note that some special applications such as Multi Site Support do not need outbound/inbound routing configuration.
Inbound Routing
Inbound routes simply allow you to specify patterns or fully qualified extension and assign them to an extension, group, IVR etc.
Auto Extensions
Auto Extensions allows you to automatically match up DID's with local extensions. The match is based off the DID/DDI specified in the User configuration (or if a pure channel the External Caller ID). Matches can be strict (full match) or based on a number of digits (right to left). An example would be a Telco that only passes the 3 last digits of the dialed DID/DDI. This route needs only to be once.
Outbound Routing
Outbound routes allow you to specify where to find certain extensions, either fully qualified or by means of a pattern.
