AudioCodes Mediant 2600 - Dial Plan Prefix Tags for Routing

User's Manual 434 Document #: LTRT-42060
Mediant 2600 E-SBC
 Empty lines are ignored.
 Lines beginning with a semicolon ";" are ignored. The semicolon can be used for
comments.
Creating a Dial Plan file is similar for all Dial Plan features. The main difference is the
syntax used in the Dial Plan file and the method for selecting the Dial Plan index.
 To create a Dial Plan file:
1. Create a new file using a text-based editor (such as Notepad) and configure your Dial
Plans, as required.
2. Save the file with the ini file extension name (e.g., mydialplanfile.ini).
3. Convert the ini file to a dat binary file, using AudioCodes DConvert utility. For more
information, refer to DConvert Utility User's Guide.
4. Load the converted file to the device, as described in ''Loading Auxiliary Files'' on
page 429.
5. Select the Dial Plan index that you want to use. This depends on the feature and is
described in the respective section.
30.1.3.2 Dial Plan Prefix Tags for Routing
30.1.3.2.1 Dial Plan Prefix Tags for SBC IP-to-IP Routing
For deployments requiring many SBC IP-to-IP routing rules that exceed the maximum
number of rules that can be configured in the IP-to-IP Routing table, you can employ user-
defined string labels (tags) to represent the many different prefix calling (source) and called
(destination) numbers. The prefix tags are used in the IP-to-IP Routing table (see
''Configuring SBC IP-to-IP Routing Rules'' on page 368) as source and destination URI
user parts matching characteristics for the routing rule. Prefix tags are typically
implemented when you have calls of many different called or calling numbers that need to
be routed to the same destination. Thus, instead of configuring a routing rule for each
prefix number, you need to configure only one routing rule using the prefix tag.
For example, this feature is useful in deployments that need to handle hundreds of call
routing scenarios such as for a large geographical area (a state in the US). Such an area
could consist of hundreds of local area codes as well as codes for international calls. The
local calls and international calls would need to be routed to different SIP trunks. Thus,
instead of configuring many routing rules for each call destination type, you can simply
configure two routing rules, one with a unique prefix tag representing the different local
area codes and the other with a prefix tag representing international calls.
Note: When using prefix tags, you need to configure manipulation rules to remove the
tags before the device sends the calls to their destinations.
You configure prefix tags in the Dial Plan file, using the following syntax:
[ PLAN<index> ]
<prefix number>,0,<prefix tag>
where:
 Index is the Dial Plan index
 prefix number is the called or calling number prefix (ranges can be defined in
brackets)
 prefix tag is the user-defined prefix tag of up to nine characters, representing the prefix
number