Dial Plan Prefix Tags For Ip-To-Tel Routing - AudioCodes Mediant 2000 User Manual

Media gateway
Hide thumbs Also See for Mediant 2000:
Table of Contents

Advertisement

SIP User's Manual
An example of a Dial Plan file with indices (in ini-file format before conversion to binary
*.dat) is shown below:
[ PLAN1 ]
; Area codes 02, 03, - phone numbers include 7 digits.
02,7
03,7
; Cellular/VoIP area codes 052, 054 - phone numbers include 8
digits.
052,8
054,8
; International prefixes 00, 012, 014 - number following
prefixes include 7 to 14 digits.
00,7-14
012,7-14
014,7-14
; Emergency number 911 (no additional digits expected).
911,0
[ PLAN2 ]
; Supplementary services such as Call Camping and Last Calls
(no additional digits expected), by dialing *41, *42, or *43.
*4[1-3],0
Notes:
9.1.4

Dial Plan Prefix Tags for IP-to-Tel Routing

The device supports the use of string labels (or "tags") in the external Dial Plan file for
tagging incoming IP-to-Tel calls. The special "tag" is added as a prefix to the called party
number, and then the 'IP to Trunk Group Routing' table uses this "tag" instead of the
original prefix. Manipulation is then performed after routing in the Manipulation table, which
strips the "tag" characters before sending the call to the endpoint.
This feature resolves the limitation of entries in the 'IP to Trunk Group Routing' (IP-to-Tel
call routing) for scenarios in which many different routing rules are required. For example, a
city may have many different area codes, some for local calls and others for long distance
calls (e.g. 425-202-xxxx for local calls, but 425-200-xxxx for long distance calls).
For using tags, the Dial Plan file is defined as follows:
Number of dial plan (text)
Dial string prefix (ranges can be defined in brackets)
User-defined routing tag (text)
The example configuration below assumes a scenario where multiple prefixes exist for local
and long distance calls:
Version 5.8
If the external dial plan file is used for digit mapping rules, then the
parameter DigitMapping is ignored.
For E1 CAS MFC-R2 variants (which don't support terminating digit for
the called party number, usually I-15), the external Dial Plan file and the
DigitMapping parameter are ignored. Instead, you can define a Dial Plan
template per trunk using the parameter CasTrunkDialPlanName_x.
403
9. IP Telephony Capabilities
October 2009

Advertisement

Table of Contents
loading

Table of Contents