Routes

From Taridium

To access your routes click on Configuration → Routing.

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.

Contents 1 Inbound Routing 1.1 Auto Extensions 2 Outbound Routing 3 Transformations 3.1 Examples 4 Pattern Matching 4.1 Special Characters for Pattern Matching 4.2 Examples

Inbound Routing

Inbound routes simply allow you to specify patterns (see Pattern Matching) or fully qualified extension and assign them to an extension, group, IVR etc. See also Destinations. Note that in certain cases the position of your route needs to be adjusted. This will for example be the case when you have overlapping number patterns.

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 present once.

Outbound Routing

Outbound routes allow you to specify where to find certain extensions/destinations, either fully qualified or by means of a pattern. See also Pattern Matching.

Note that in certain cases the position of your route needs to be adjusted. This will for example be the case when you have overlapping number patterns.

Transformations

Transformations allow you to modify extensions (dialed numbers) in certain situations. Currently ipbx supports three situations:

1. before inbound routing
2. before outbound routing
3. before inside routing

Numbers can be mapped one-to-one e.g. if a call is being sent as extension 200 to your ipbx you can have it processed as 500 instead. Assuming you have an inbound route with DID/DDI 500 etc.

The difference between before inside routing and before outbound routing is that the transformation is applied before any of the local extensions are looked up and with the latter after.

You can use the ${EXTEN} variable in the output field if you need to transform the incoming pattern.

Examples

Type before outbound routing, Pattern _NXXXXXX and Output +1212${EXTEN} - This rule will transform any 7 digit numbers to an E.164 pattern within the 212 area code prefixed. You will now have to match the newly formatted number in your outbound routes.

Pattern Matching

Extension names are not limited to single specific extension 'numbers'. A single extension can also match patterns. Patterns always start with a '_' underscore. In a pattern, the following characters have special meanings:

Special Characters for Pattern Matching

  X          matches any digit from 0-9
  Z          matches any digit from 1-9
  N          matches any digit from 2-9
  [1237-9]   matches any digit or letter in the brackets
             (in this example, 1,2,3,7,8,9)
  .          wildcard, matches one or more characters

Some incoming calls might not provide extension information and thus no way to match the incoming call. This will require the use of the reserved s extension. An example is the use of analog line cards.

Examples

  _NXXXXXX        matches a NANP 7 digit telephone number such as 555-1212
  _1NXXNXXXXXX    matches an area code and phone number preceeded by a one such as 1-860-555-1212
  _9011.          matches any string of at least five characters that starts with 9011,
                  but it does not match the four-character string 9011 itself.