Dial Plan Prefix Tags For Routing - AudioCodes Mediant 1000B User Manual

Media gateway & enterprise session border controller (e-sbc)
Hide thumbs Also See for Mediant 1000B:
Table of Contents

Advertisement

User's Manual
pattern is found, it waits for two more digits and then after a timeout
(TimeBetweenDigits parameter), it sends the collected digits. Therefore, this
ensures that calls are not rejected as a result of their digit pattern not been
completed in the Dial Plan.
By default, if no matching digit pattern is found in both the Dial Plan and Digit Map,
the device rejects the call. However, if you set the DisableStrictDialPlan parameter
to 1, the device attempts to complete the call using the MaxDigits and
TimeBetweenDigits parameters. In such a setup, it collects the number of digits
configured by the MaxDigits parameters. If more digits are received, it ignores the
settings of the parameter and collects the digits until the inter-digit timeout
configured by the TimeBetweenDigits parameter is exceeded.

43.1.7.3 Dial Plan Prefix Tags for Routing

43.1.7.3.1 Dial Plan Prefix Tags for IP-to-Tel Routing
For deployments requiring many IP-to-Tel routing rules that exceed the maximum number
of rules that can be configured in the IP to Trunk Group 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 Trunk Group Routing
table (see 'Configuring IP-to-Trunk Group Routing Rules' on page 494) as source and
destination number 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:
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
Each prefix tag type - called or calling - must be configured in a dedicated Dial Plan index
number. For example, Dial Plan 1 can be for called prefix tags and Dial Plan 2 for calling
prefix tags.
Version 7.0
When using prefix tags, you need to configure manipulation rules to remove
727
Mediant 1000B Gateway and E- SBC
43. Software Upgrade

Advertisement

Table of Contents
loading

Table of Contents