Downloads |
 Feedback
|
Table Of Contents
Routing Based on Redirecting Number
Understanding the Routing Based on Redirecting Number Feature
Starting a Provisioning Session
Saving and Activating Your Provisioning Changes
Ending a Provisioning Session Without Activating Your Changes
Modifying a Signaling Service Property
Deleting a Signaling Service Property
Software Changes for This Feature Module
Obtaining Documentation, Obtaining Support, and Security Guidelines
Routing Based on Redirecting Number
Document Release History
Feature History
9.6(1)
The Routing Based on Redirecting Number feature was introduced on the Cisco MGC software.
This document describes the Routing Based on Redirecting Number (RBRN) feature for Release 9.6(1) of the Cisco MGC Software and explains how to use it.
This feature is described in the following sections:
•
Understanding the Routing Based on Redirecting Number Feature
•
•
Understanding the Routing Based on Redirecting Number Feature
The RBRN feature enhances PGW 2200 routing capability by enabling number analysis and route selection based on the redirecting number contained in the H.323 Setup or SIP Invite message.
The feature is used to route a call from a PBX to its closest local or national TDM switch based on the redirecting number. This feature ensures that calls forwarded from one country to another use the correct dial plan by routing based on the redirecting number rather than the original calling party number.
Call Flow Example
Figure 1 shows how this feature can be used. In the figure, the service provider uses CLI prefix screening to select a customer-specific dial plan, and the calling party number to select an outgoing country dial plan. (Outgoing calls must utilize the TDM switch in their own country.)
In the figure, if a UK customer calls a party in France, the call is completed normally. However, if the party in France forwards the call to Germany, the proper outgoing TDM trunk cannot be selected based on the calling party number (UK). Instead, the PGW must determine the outgoing TDM trunk for the call based upon the redirecting number (France) in order to establish the call between the UK and Germany.
Figure 1 Routing Based on Redirecting Number Example
Feature Interactions
Routing Based on Redirecting Number (RBRN) has the following feature interactions:
•
If this feature is enabled, call screens using the redirecting number during A Digit Analysis are ignored because RBRN already uses the redirecting number (instead of the original A number) for the dial plan process.
•
–
–
–
–
–
–
•
Prerequisites
The RBRN feature has the following prerequisites:
•
•
Limitations
The RBRN feature has the following limitations:
•
•
The following limitations exist for this feature if it is enabled and the incoming call setupup message contains a redirecting number:
•
•
•
•
•
Currently CCM supports only a single instance of a redirecting number in a call flow. If a call is redirected more than once, the PGW does not modify the redirecting number from the original value.
In some instances an H.323 endpoint connected to the HSI might not provide the nonstandard portion of the H.323 setup message, in which case the PGW cannot retrieve the redirecting number.
Related Documents
This document contains information that is related strictly to this feature. The documents that contain additional information related to the Cisco Media Gateway Controller (MGC) are at the following url:
http://www.cisco.com/en/US/products/hw/vcallcon/ps2027/tsd_products_support_series_home.html
Provisioning Tasks
The following sections describe the provisioning tasks related to this feature.
Provisioning Prerequisites
This section lists the information you need to provision this feature. For more information on planning to provision the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Collecting Provisioning Data
You need the following data in order to provision this feature:
•
•
•
Table 2 lists the properties that you can configure for this feature.
Provisioning Procedures
The following sections summarize the procedures for making provisioning changes on your Cisco PGW 2200 system.
•
•
•
•
•
For more information about how to provision the Cisco PGW 2200, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Starting a Provisioning Session
To open a provisioning session to the Cisco PGW 2200, log in to the active PGW, start an MML session, and enter the following command:
prov-sta:srcver="curr_ver",dstver="mod_ver"Where:
•
–
–
Note
•
For example, to use a configuration version called ver1 as the basis for a version to be called ver2, enter the following command:
prov-sta:srcver="ver1",dstver="ver2"Once a provisioning session is underway, you can use the prov-add, prov-ed, and prov-dlt MML commands to add, modify, and delete components on your system. For more information on provisioning other components on your Cisco PGW 2200, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
There are two ways to close a provisioning session:
•
•
Saving and Activating Your Provisioning Changes
When you have completed making provisioning changes in your session, you can enter a command to save and activate your changes. There are two different provisioning MML commands that do this: prov-cpy and prov-dply.
Caution
The prov-cpy MML command saves and activates your changes on simplex (single-host) Cisco PGW 2200 systems.
The prov-dply MML command saves and activates your changes on the active and standby PGW in a continuous-service system. Do not use this command on a Cisco PGW 2200 in a simplex configuration.
Note
Caution
Ending a Provisioning Session Without Activating Your Changes
To end a provisioning session without saving and activating your changes, enter the prov-stp MML command. This command ends the current provisioning session and discards your changes.
Retrieving Provisioning Data
Use the prov-rtrv MML command to retrieve information about your current provisioning settings. The following sections describe how to use the prov-rtrv command:
•
•
•
•
•
Retrieving Data for an Individual Component
To retrieve provisioning data on an individual component in your system, enter the following command within an MML session on the active PGW:
prov-rtrv:component:name="MML_name"Where:
•
•
For example, to view the provisioning data for an SS7 signaling service called ss7svc1, enter the following command:
prov-rtrv:ss7path:name="ss7svc1"Retrieving Data for All Components
To retrieve data on all of the components provisioned on your system, enter the following command within an MML session on the active PGW:
prov-rtrv:allRetrieving Data for All Components of a Particular Type
To retrieve provisioning data on all components of a particular type on your system, enter the following command within an MML session on the active PGW:
prov-rtrv:component:name="mml-name"Where component is the MML component type associated with the desired component group. The Cisco Media Gateway Controller Software Release 9 Provisioning Guide contains a complete list of the MML component types.
For example, to view the provisioning data for all SIP services, enter the following command:
prov-rtrv:sigsvcprop:name="sip-path"Retrieving Data on the Current Provisioning Session
To retrieve provisioning data on the current provisioning session, enter the following command within an MML session on the active PGW:
prov-rtrv:sessionThe system returns a response similar to the following:
MGC-02 - Media Gateway Controller 2004-01-13 13:39:19M RTRV"session=jtest:session"/*Session ID = mml1SRCVER = activeDSTVER = jtest*/Retrieving Data on Supported Signaling Protocols
To retrieve protocol data for the current provisioning session, log in to the active Cisco MGC, start an MML session, and enter the following command:
prov-rtrv:variantsModifying a Signaling Service Property
To modify a Cisco PGW 2200 signaling service property, enter the following command within an MML session on the active PGW:
prov-ed:sigsvcprop:name="name","propertyname"Where:
•
•
For example, to modify the Cisco PGW 2200 signaling service property RedirNumForAnalysis to 1, enter the following command:
mml> prov-ed:sigsvcprop:name="sip-path",redirnumforanalysis="1"Deleting a Signaling Service Property
To delete a Cisco PGW 2200 signaling service property from your PGW configuration, enter the following command within an MML session on the active PGW:
prov-dlt:sigsvcprop:name="name","propertyname"Where:
•
•
For example, to delete the Cisco PGW 2200 signaling service property RedirNumForAnalysis, you enter the following command:
mml> prov-dlt:sigsvcprop:name="sip-path","redirnumforanalysis"
Note
Provisioning Example
The following is a provisioning example that includes commands to add, modify, and delete the RedirnumForAnalysis property on SIP and H.323 trunks. For additional provisioning examples for the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
________________________________________; Adding a dial plan;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;numan-add:dialplan:custgrpid="DP00",OVERDEC="NO"________________________________________; Configuring SIP service and a SIP link;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-add:sippath:NAME="sip-path",DESC="SIP path",MDO="IETF_SIP"prov-add:siplnk:NAME="sip-link",DESC="SIP link",SVC="sip-path",IPADDR="IP_Addr2", PORT=5060,PRI=1________________________________________; Adding a trunk for the E-ISUP sig path;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-add:trnkgrp:name="9700",type="IP",svc="eisup-hsi",clli="hsi-a"________________________________________; Adding an outgoing SIP trunk group;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-ADD:trnkgrp:NAME="3", CLLI="sip-path", SVC="sip-path", TYPE="IP_SIP", SELSEQ="LIDL", QABLE="N"prov-add:trnkgrpprop:name="3",custgrpid="DP01",MGCdomain="10.0.57.90", mgcsipversion="sip/2.0", Localport="5060"prov-add:siprttrnkgrp:name="3",url="10.0.20.112",srvrr=0,sipproxyport=5060,version="2.0",c utthrough=1,extsupport=1prov-add:rttrnk:name="rg3",trnkgrpnum=3prov-add:rtlist:name="rlst3",rtname="rg3"________________________________________; Adding an outgoing E-ISUP trunk group;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-add:trnkgrp:name="9700",type="IP",svc="eisup-hsi",clli="hsi-a"prov-add:rttrnkgrp:name="9700",type=4,reattempts=3,queuing=0,cutthrough=1, resincperc=0prov-add:rttrnk:weightedTG="OFF",name="eisup-rt9700",trnkgrpnum=9700prov-add:rtlist:name="eisup-rtlist-4",rtname="eisup-rt9700",distrib="OFF"________________________________________; Configuring a Dial Plan (DP00);;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;numan-add:dpsel:custgrpid="DP00",newdp="DP01"numan-add:digmodstring:custgrpid="DP00", name="digmoda", digstring="456222"numan-add:resultset:custgrpid="DP00",name="SwToDP1"numan-add:resulttable:custgrpid="DP00", name="moda", resulttype="AMODDIG", dw1="1", dw2="6", dw3="digmoda", setname="SwToDP1"numan-add:resulttable:custgrpid="DP00",name="SwitchDP1",resulttype="NEW_DIALPLAN",dw1="DP0 1",dw2="0",setname="SwToDP1"numan-add:resultset:custgrpid="DP00",name="SwToDP2"numan-add:resulttable:custgrpid="DP00",name="SwitchDP2",resulttype="NEW_DIALPLAN",dw1="DP0 2",dw2="0",setname="SwToDP2"numan-add:adigtree:custgrpid="DP00",callside="originating",digitstring="476",setname="SwTo DP1"numan-add:adigtree:custgrpid="DP00",callside="originating",digitstring="40",setname="SwToD P2"________________________________________; Adding the RedirnumForAnalysis property to a SIP Ingress Trunk;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-add:sigsvcprop:name="sip-path",redirnumforanalysis="1"________________________________________; Adding the RedirnumForAnalysis property to an H.323 Ingress Trunk;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-add:sigsvcprop:name="eisup-hsi",redirnumforanalysis="1"________________________________________; Modifying the RedirnumForAnalysis property on a SIP Ingress Trunk;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-ed:sigsvcprop:name="sip-path",redirnumforanalysis="1"________________________________________; Modifying the RedirnumForAnalysis property on an H.323 Ingress Trunk;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-ed:sigsvcprop:name="eisup-hsi",redirnumforanalysis="1"________________________________________; Deleting the RedirnumForAnalysis property from a SIP Path;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-dlt:sigsvcprop:name="sip-path","redirnumforanalysis"________________________________________; Deleting the RedirnumForAnalysis property from an H.323 Path;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-dlt:sigsvcprop:name="eisup-hsi","redirnumforanalysis"Software Changes for This Feature Module
Feature Summary
CSCsg37231 introduced software changes in the PGW 2200 to support the Routing Based on Redirecting Number feature.
New, Modified, and Deleted Elements
Parameters:
•
Related reference material:
Properties
Table 1 lists the parent object for the property that is used to support the Routing Based on Redirecting Number feature.
For information on other properties for the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Table 2 lists the properties used by the RBRN.
Note
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Glossary
Table 3 contains expansions of acronyms and technical terms used in this feature module.
This document is to be used in conjunction with the documents listed in the Related Documents section.
CCVP, the Cisco logo, and Welcome to the Human Network are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0710R)
