Routes

From Taridium

(Difference between revisions)
Jump to: navigation, search
Line 15: Line 15:
== 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:
+
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===
===Special Characters for Pattern Matching===
Line 28: Line 28:
===Examples===
===Examples===
-
   NXXXXXX       matches a NANP 7 digit telephone number such as 555-1212
+
   _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
+
   _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,
+
   _9011.          matches any string of at least five characters that starts with 9011,
                   but it does not match the four-character string 9011 itself.
                   but it does not match the four-character string 9011 itself.

Revision as of 19:23, 9 December 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.

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

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.
Personal tools
Namespaces
Variants
Actions
Toolbox