Routes

From Taridium

Revision as of 13:39, 3 December 2008 by Webmaster (Talk | contribs)
Jump to: navigation, search

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

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.

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 (see Pattern Matching)

Pattern Matching

Extension names are not limited to single specific extension 'numbers'. A single extension can also match patterns. 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
Personal tools
Namespaces
Variants
Actions
Toolbox