CHAPTER20 SIP Definitions
Mediant 1000 Gateway & E-SBC | User's Manual
● 'Source Tags' parameter (IPOutboundManipulation_SrcTags): tag denoting the calling
users
● 'Destination Tags' parameter (IPOutboundManipulation_DestTags): tag denoting the
called users
Using Dial Plan Tags for Call Setup Rules
You can use Dial Plan tags in Call Setup rules, configured in the Call Setup Rules table (see
Configuring Call Setup Rules ). The Call Setup rule can be assigned to an IP Group and is
processed by the device for the classified source IP Group immediately before the routing process
(i.e., Classification > Manipulation > Dial Plan table > Call Setup rules > Routing). The result of the
Call Setup rule (i.e., source and/or destination tag) can be used as the matching characteristics for
locating a suitable IP-to-IP Routing rule in the IP-to-IP Routing table.
You can configure Call Setup rules to query the Dial Plan table for a specified key (prefix) in a
specified Dial Plan to obtain the corresponding tag. The Call Setup rule can then perform many
different manipulations (based on Message Manipulation syntax), including modifying the name of
the tag. The tags can be used only in the 'Condition', 'Action Subject' and 'Action Value' fields.
Using Dial Plans for IP-to-Tel or Tel-to-IP Call Routing
For deployments requiring hundreds of routing rules (which may exceed the maximum number of
rules that can be configured in the routing tables), you can employ Dial Plan tags to represent the
many different calling (source) and called (destination) prefix numbers as matching input
characteristics in your IP-to-Tel and Tel-to-IP routing rules. Tags are typically implemented when
you have users of many different called and/or calling numbers that need to be routed to the same
destination. In such a scenario, instead of configuring many routing rules to match all the required
prefix numbers, you need only to configure a single routing rule using the tag to represent all the
possible prefix numbers.
An example scenario where employing tags could be useful is in deployments where the device
needs to service calls in a geographical area that consists of many local area codes, where the area
codes are serviced by different SIP Trunks (for Tel-to-IP) and Trunk Groups (for IP-to-Tel). Another
example includes routing local calls and International calls using different SIP Trunks. In such a
scenario, instead of configuring hundreds of routing rules to represent each local area code and the
International dialing code, you can simply configure two routing rules where one is assigned a
unique tag representing the local area codes and the other is assigned a tag representing
International calls.
● Source and destination tags can be used in the same routing rule.
● The same tag can be used for source and destination tags in the same routing rule.
The procedure below describes how to configure tag-based routing for Gateway calls based on the
following example setup:
■ Tel-to-IP routing: Local calls whose destination tag is "NYPSP0" are routed to IP Group "SP-0"
and calls whose destination tag is "NYPSP1" are routed to IP Group "SP-1".
■ IP-to-Tel routing: Local calls whose destination tag is "NYPSP0" are routed to Trunk Group 1
and calls whose destination tag is "NYPSP1" are routed to Trunk Group 2.
➢ To configure tag-based routing for IP-to-Tel and Tel-to-IP calls:
1. Open the Dial Plan table (see Configuring Dial Plans), and then configure your Dial Plan rules,
for example:
- 506 -
To Next Page
Loading...
Need help?
General
