Blind Take Back and Transfer Replacement
Document Release History
Publication Date
Comments
March 12, 2007
Initial version of document.
Feature History
Release
Modification
9.7(3)
The Blind Take Back and Transfer Replacement feature was introduced on
the Cisco MGC software.
This document describes support of blind take back and transfer of a call by using received DTMF digits
to invoke a blind call transfer.
This feature is described in the following sections:
•
Feature Overview, page 1
•
Supported Standards, MIBs, and RFCs, page 2
•
Prerequisites for Using This Feature, page 3
•
Provisioning Tasks, page 3
•
Provisioning Examples, page 9
•
Software Changes for This Feature Module, page 12
•
Obtaining Documentation, Obtaining Support, and Security Guidelines, page 14
•
Glossary, page 14
Feature Overview
This feature provides support on the Cisco PGW 2200 of the blind take back and transfer of a call by
using received DTMF digits to invoke a blind call transfer.
System patch CSCOgs003 introduced the software changes in the PGW 2200 to support the Blind Take
Back and Transfer Replacement feature are listed in “Software Changes for This Feature Module”.
Cisco MGC Software Release 9.7(3)
1
Blind Take Back and Transfer Replacement
Supported Standards, MIBs, and RFCs
Benefits
This feature provides the following benefits:
Reduce Operating Expenses
The Blind Take Back and Transfer Replacement feature functionality can be used by large enterprise
customers to avoid having to pay take back and transfer fees.
Allows Mid-call Transfers
In-band DTMF digits can be used to invoke a blind transfer service if the called party wants to transfer
the call.
Restrictions
The Blind Take Back and Transfer Replacement feature has the following restrictions:
•
Blind transfer capability can be invoked only from a TDM connection
•
The PGW 2200 uses MGCP to request DTMF digits from the serving media gateway when the media
gateway terminates the leg of a call
•
For a mid-call announcement, only local final announcements are supported to the redirection party'
•
No announcements are generated toward the calling party during a blind transfer, but an
announcement can be played to the calling party when the second call setup fails
•
When a gateway with a VXSM is used with the PGW 2200, announcements are not generated
•
DTMF digits are discarded if no dial plan entry is matched or the target number is not correct
•
The time interval of inter-digits timer is fixed to 3 seconds
Related Documents
This document contains information that is related 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
Supported Standards, MIBs, and RFCs
Standards
No standards are supported by this feature.
MIBs
No new or modified MIBs are supported by this feature. For more information on the MIBs used in the
Cisco MGC software, refer to the Cisco Media Gateway Controller Release 9 Management Information
Base Guide.
RFCs
No RFCs are supported by this feature.
Cisco MGC Software Release 9.7(3)
2
Blind Take Back and Transfer Replacement
Prerequisites for Using This Feature
Prerequisites for Using This Feature
The Cisco PGW 2200 must be running Cisco MGC software Release 9.7(3). Prerequisites for this release
can be found in the Release Notes for the Cisco Media Gateway Controller Software Release 9.7(3) at:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/relnote/rn973.htm.
Provisioning Tasks
The following sections describe the provisioning tasks related to this feature:
•
Provisioning Procedures, page 3
Provisioning Procedures
This provisioning is performed when mid-call service is supported by the PGW 2200 and a new mid-call
dial plan is created for an existing customer group ID, which is used for mid-call service analysis. This
section covers the following provisioning topics:
•
Provisioning Basics, page 11
Provisioning Basics
The procedures in this section describe how to start a provisioning session and how to save and activate
the changes you have made.
•
Starting a Provisioning Session, page 3
•
Saving and Activating Your Provisioning Changes, page 4
•
Ending a Provisioning Session Without Activating Your Changes, page 5
•
Retrieving Provisioning Data, page 5
For more detailed information about provisioning your Cisco PGW 2200, refer to the Cisco Media
Gateway Controller Software Release 9 Provisioning Guide.
Starting a Provisioning Session
You may need to start a provisioning session as part of your system operations. To do this, log in to the
active Cisco PGW 2200, start an MML session, and enter the following command:
prov-sta::srcver=”curr_ver”,dstver=”mod_ver”
Where:
•
curr_ver—The name of the current configuration version. In place of the name of the current
configuration version, you can also enter:
– new—A new default session configuration; no existing source configuration is available.
– active—Selects the active configuration as the source for configuration changes.
Cisco MGC Software Release 9.7(3)
3
Blind Take Back and Transfer Replacement
Provisioning Tasks
Note
•
If you do not know the name of your current configuration session, you can learn it by using the
procedure described in the “Retrieving Data on the Current Provisioning Session” section on
page 7.
mod_ver—A new configuration version name that contains your provisioning changes.
For example, to use a configuration version called ver1 as the basis for a version to be called ver2, you
would 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. This document describes how to
provision this feature. 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 your provisioning session: saving and activating your provisioning changes,
as described in the “Saving and Activating Your Provisioning Changes” section on page 4 or ending your
provisioning session without saving and activating your changes, as described in the “Ending a
Provisioning Session Without Activating Your Changes” section on page 5.
Saving and Activating Your Provisioning Changes
When you have completed making provisioning changes in your session, you must 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
Using the prov-cpy and prov-dply MML commands can severely impact your system’s call processing
performance, depending on the extent of your provisioning changes. We recommend that these
commands be issued during a maintenance window when traffic is minimal.
The prov-cpy MML command is used to save and activate your changes on simplex Cisco PGW 2200
(single-host) systems.
Note
When you enter the prov-cpy command, your provisioning session is also automatically ended. If you
want to make additional provisioning changes, you must start a new provisioning session as described
in the “Starting a Provisioning Session” section on page 3.
Caution
Do not use the prov-cpy command to save and activate your changes on a continuous-service
Cisco MGC system (one with active and standby hosts) system. Saving and activating using prov-cpy
on such a system would require using the prov-sync MML command to synchronize the provisioning
data on the active and standby hosts. The system does not indicate when the synchronization process
fails, which would create problems when a switchover operation occurs.
The prov-dply MML command is used to save and activate your changes on the active and standby
Cisco PGW 2200s in a continuous-service system. This command should not be used on a
Cisco PGW 2200 in a simplex configuration.
Cisco MGC Software Release 9.7(3)
4
Blind Take Back and Transfer Replacement
Provisioning Tasks
Note
When you enter the prov-dply command, your provisioning session is also automatically ended, unless
an error occurs during execution. If you want to make additional provisioning changes, you must start a
new provisioning session, as described in the “Starting a Provisioning Session” section on page 3.
Ending a Provisioning Session Without Activating Your Changes
If you want to end a provisioning session without saving and activating the changes you have entered,
enter the prov-stp MML command. This command ends your current provisioning session, and your
changes are not committed.
Retrieving Provisioning Data
You can use the prov-rtrv MML command to retrieve information about your current provisioning
settings. The ways you can use this command to retrieve provisioning data are described in the following
sections:
•
Retrieving Data for an Individual Component, page 5
•
Retrieving Data for All Components, page 5
•
Retrieving Data for All Components of a Particular Type, page 6
•
Retrieving Data on the Current Provisioning Session, page 6
•
Retrieving Data on Supported Signaling Protocols, page 6
Retrieving Data for an Individual Component
You can retrieve provisioning data on any individual component in your system. To do this, log in to the
active Cisco PGW 2200, start an MML session, and enter the following command:
prov-rtrv:component:name=MML_name
Where:
•
component—The MML component type associated with the desired component. You can find a
complete list of MML component types in the Cisco Media Gateway Controller Software Release 9
Provisioning Guide.
•
MML_name—The MML name for the desired component. You can determine the MML names for
the various components using the prov-rtrv:all MML command.
For example, to view the provisioning data for an SS7 signaling service called ss7svc1, you would enter
the following command:
prov-rtrv:ss7path:name=”ss7svc1”
The response to the command is dependent upon the component type associated with the desired
component. For example, to view the properties for an SUA routing key called suakey1, you would enter
the following command:
prov-rtrv:suakey:name=”suakey1”
Retrieving Data for All Components
You can retrieve data on all of the components provisioned on your system. To do this, log in to the active
Cisco PGW 2200, start an MML session, and enter the following command:
prov-rtrv:all
Cisco MGC Software Release 9.7(3)
5
Blind Take Back and Transfer Replacement
Provisioning Tasks
Retrieving Data for All Components of a Particular Type
You can retrieve provisioning data on all components of a particular type on your system. To do this, log
in to the active Cisco PGW 2200, start an MML session, and enter the following command:
prov-rtrv:component:”all”
Where: component is the MML component type associated with the desired component group. You can
find a complete list of MML component types in the Cisco Media Gateway Controller Software
Release 9 Provisioning Guide.
For example, to view the provisioning data for all SS7 signaling services, you would enter the following
command:
prov-rtrv:ss7path:”all”
Retrieving Data on the Current Provisioning Session
You can retrieve provisioning data on the current provisioning session. To do this, log in to the active
Cisco PGW 2200, start an MML session, and enter the following command:
prov-rtrv:session
The system returns a response similar to the following:
MGC-02 - Media Gateway Controller 2004-01-13 13:39:19
M RTRV
“session=jtest:session”
/*
Session ID = mml1
SRCVER = active
DSTVER = jtest
*/
Retrieving Data on Supported Signaling Protocols
You can retrieve protocol data for the current provisioning session. To do this, log in to the active
Cisco MGC, start an MML session, and enter the following command:
prov-rtrv:variants
Adding Dial Plan Data
The order in which you provision dial plan tables is important. Many tables refer to other tables that must
be defined first. The following list identifies the recommended sequence for dial plan provisioning:
1.
Create the dial plan file (unique CustGrpID)
2.
Provision Digit Modification
3.
Provision the Service
4.
Provision the Result and Result Sets
5.
Provision the A-numbers and B-numbers
6.
Provision CPC
7.
Provision TMR analysis
8.
Provision B-number NOA and NPI analysis
9.
Provision TNS
10. Provision NANP B-number normalization
Cisco MGC Software Release 9.7(3)
6
Blind Take Back and Transfer Replacement
Provisioning Tasks
11. Provision the Location value
12. Provision the Cause value
13. Provision the A and B Whitelist and Blacklist screening files
To begin the process of creating a dial plan, log in to the active Cisco PGW 2200, start an MML session,
and enter the following command:
mml> numan-add:component:custgrpid=cust_groupID,param_name=”param_value”,...
Where:
•
component—The name of the component type you want to add to your dial plan. A complete list of
the valid dial plan component types can be found in the Cisco Media Gateway Controller Software
Release 9 Dial Plan Guide.
•
cust_groupID—Customer group ID number associated with your dial plan.
•
param_name—The name of the parameter you want to configure for the selected component in your
dial plan. A complete list of the valid parameters for each dial plan component type can be found in
the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.
•
param_value—The value of the parameter you want to configure for the selected component in your
dial plan. A complete list of the valid values for the parameters of each dial plan component type
can be found in the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.
For example, to provision a route result type called resultone, you would enter the following command:
mml> numan-add:resulttable:custgrpid="t777",resulttype="route",setname="setone",
name="resultone",dw1="rtlistone"
Modifying an Element of Your Dial Plan Data
To modify an existing dial plan, log in to the active Cisco PGW 2200, start an MML session, and enter
the following command:
mml> numan-ed:component:custgrpid=”cust_groupID”,param_name=”param_value”,...
Where:
•
component—The name of the component type you want to modify in your dial plan. A complete list
of the valid dial plan component types can be found in the Cisco Media Gateway Controller Software
Release 9 Dial Plan Guide.
•
cust_groupID—Customer group ID number associated with your dial plan.
•
param_name—The name of the parameter you want to configure for the selected component in your
dial plan. A complete list of the valid parameters for each dial plan component type can be found in
the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.
•
param_value—The value of the parameter you want to configure for the selected component in your
dial plan. A complete list of the valid values for the parameters of each dial plan component type
can be found in the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.
For example, to modify a result table, you would enter the following command:
mml> numan-ed:resulttable:custgrpid="t777",resulttype="route",setname="setone",
name="resulttwo",dw1="rtlistone"
Cisco MGC Software Release 9.7(3)
7
Blind Take Back and Transfer Replacement
Provisioning Tasks
Deleting an Element from Your Dial Plan Data
To delete an element from your dial plan, log in to the active Cisco PGW 2200, start an MML session,
and enter the following command:
mml> numan-dlt:component:custgrpid="cust_groupID",name="MML_name"
Where:
•
component—The name of the component type you want to delete from your dial plan. A complete
list of the valid dial plan component types can be found in the Cisco Media Gateway Controller
Software Release 9 Dial Plan Guide.
•
cust_groupID—Customer group ID number associated with your dial plan.
•
MML_name—The MML name of the selected component you want to delete from your dial plan.
For example, to delete a result set called setone, you would enter the following command:
mml> numan-dlt:resultset:custgrpid="t001",name="setone"
Retrieving Dial Plan Data
You can use the numan-rtrv MML command to retrieve information about your current dial plan
settings. The ways in which you can use this command to retrieve dial plan data are described in the
following sections:
Note
•
Retrieving Data for an Individual Component, page 5
•
Retrieving Data for All Components of a Particular Type, page 6
You can verify dial plans using the translation verification viewer on the Cisco MGC toolbar. For
information on using the translation verification viewer, refer to the Cisco Media Gateway Controller
Software Release 9 Operations, Maintenance, and Troubleshooting Guide.
Retrieving Data for an Individual Component
You can retrieve dial plan data on any individual component on your system. To do this, log in to the
active Cisco PGW 2200, start an MML session, and enter the following command:
mml> numan-rtrv:component:custgrpid="cust_groupID",name="MML_name"
Where:
•
component—The name of the component type you want to retrieve from your dial plan. A complete
list of the valid dial plan component types can be found in the Cisco Media Gateway Controller
Software Release 9 Dial Plan Guide.
•
cust_groupID—Customer group ID number associated with your dial plan.
•
MML_name—The MML name of the selected component you want to retrieve from your dial plan.
For example, to retrieve the settings for a result set called setone, you would enter the following
command:
mml> numan-rtrv:resultset:custgrpid="t001",name="setone"
Cisco MGC Software Release 9.7(3)
8
Blind Take Back and Transfer Replacement
Provisioning Examples
Retrieving Data for All Components of a Particular Type
You can retrieve dial plan data on all components of a particular type on your system. To do this, log in
to the active Cisco PGW 2200, start an MML session, and enter the following command:
mml> numan-rtrv:component:custgrpid="cust_groupID","all"
Where:
•
component—The name of the component type you want to retrieve from your dial plan. A complete
list of the valid dial plan component types can be found in the Cisco Media Gateway Controller
Software Release 9 Dial Plan Guide.
•
cust_groupID—Customer group ID number associated with your dial plan.
For example, to retrieve the settings for all result sets in your dial plan, you would enter the following
command:
mml> numan-rtrv:resultset:custgrpid="t001",”all"
Provisioning Examples
This section provides a provisioning example for this feature. Additional provisioning examples for the
Cisco MGC software can be found in the Cisco Media Gateway Controller Software Release 9
Provisioning Guide.
; Start Provisioning Session
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-sta::srcver="existing",dstver="take_back",confirm
________________________________________
; SS7 External Node
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:EXTNODE:NAME="sltnode1",DESC="SLT 2600",TYPE="SLT",ISDNSIGTYPE="N/A",GROUP=0
prov-add:EXTNODE:NAME="sltnode2",DESC="SLT 2600",TYPE="SLT",ISDNSIGTYPE="N/A",GROUP=0
prov-add:EXTNODE:NAME="sltnode3",DESC="SLT 2600",TYPE="SLT",ISDNSIGTYPE="N/A",GROUP=0
________________________________________
; Point Codes
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:OPC:NAME="opc1",DESC="Our own point code",NETADDR="1.1.1",NETIND=2,TYPE="TRUEOPC"
prov-add:DPC:NAME="dpc1",DESC="dpc 1",NETADDR="2.2.2",NETIND=2
prov-add:DPC:NAME="dpc2",DESC="dpc 2",NETADDR="4.4.4",NETIND=2
prov-add:DPC:NAME="dpc3",DESC="dpc 3",NETADDR="8.8.8",NETIND=2
________________________________________
; SS7 Signal Services via SLT
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:SS7PATH:NAME="ss7svc1",DESC="SS7 service to DPC-2-2-2",MDO="ANSISS7_STANDARD",
CUSTGRPID="1111",SIDE="network",DPC="dpc1",OPC="opc1",M3UAKEY=""
prov-add:SS7PATH:NAME="ss7svc2",DESC="SS7 service to DPC-4-4-4",MDO="ANSISS7_STANDARD",
CUSTGRPID="1111",SIDE="network",DPC="dpc2",OPC="opc1",M3UAKEY=""
prov-add:SS7PATH:NAME="ss7svc3",DESC="SS7 service to
DPC-8-8-8",MDO="ANSISS7_STANDARD",CUSTGRPID="1111",SIDE="network",DPC="dpc3",OPC="opc1",M3
UAKEY=""
________________________________________
; SS7 linksets
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:LNKSET:NAME="linkset1",DESC="Linkset 1 to DPC 1",APC="dpc1",PROTO="SS7-ANSI",
TYPE="IP"
prov-add:LNKSET:NAME="linkset2",DESC="Linkset 2 to DPC 2",APC="dpc2",PROTO="SS7-ANSI",
TYPE="IP"
Cisco MGC Software Release 9.7(3)
9
Blind Take Back and Transfer Replacement
Provisioning Examples
prov-add:LNKSET:NAME="linkset3",DESC="Linkset 3 to DPC 3",APC="dpc3",PROTO="SS7-ANSI",
TYPE="IP"
________________________________________
; SS7 route
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:SS7ROUTE:NAME="route1",DESC="Route to DPC-2.2.2",OPC="opc1",DPC="dpc1",
LNKSET="linkset1",PRI=1
prov-add:SS7ROUTE:NAME="route2",DESC="Route to DPC-4.4.4",OPC="opc1",DPC="dpc2",
LNKSET="linkset2",PRI=1
prov-add:SS7ROUTE:NAME="route3",DESC="Route to DPC-8.8.8",OPC="opc1",DPC="dpc3",
LNKSET="linkset3",PRI=1
________________________________________
; Sessionset
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:SESSIONSET:NAME="c7sset1",EXTNODE="sltnode1",IPADDR1="IP_Addr1",
PEERADDR1="10.0.75.86",PORT=7000,PEERPORT=7000,TYPE="BSMV0"
prov-add:SESSIONSET:NAME="c7sset2",EXTNODE="sltnode2",IPADDR1="IP_Addr1",
PEERADDR1="10.0.75.87",PORT=7000,PEERPORT=7000,TYPE="BSMV0"
prov-add:SESSIONSET:NAME="c7sset3",EXTNODE="sltnode3",IPADDR1="IP_Addr1",
PEERADDR1="10.0.75.88",PORT=7000,PEERPORT=7000,TYPE="BSMV0"
________________________________________
; C7IPLinks
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:C7IPLNK:NAME="slink1-1",DESC="Signal link 1-1",LNKSET="linkset1",SLC=0,PRI=1,
TIMESLOT=0,SESSIONSET="c7sset1"
prov-add:C7IPLNK:NAME="slink2-1",DESC="Signal link 2-1",LNKSET="linkset2",SLC=1,PRI=1,
TIMESLOT=0,SESSIONSET="c7sset2"
prov-add:C7IPLNK:NAME="slink3-1",DESC="Signal link 3-1",LNKSET="linkset3",SLC=1,PRI=1,
TIMESLOT=0,SESSIONSET="c7sset3"
________________________________________
; MGCP External Node
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:EXTNODE:NAME="as-5400-1",DESC="AS-5400-1-Spans",TYPE="AS5400",ISDNSIGTYPE="N/A",
GROUP=0
prov-add:EXTNODE:NAME="as-5400-2",DESC="AS-5400-2-Spans",TYPE="AS5400",ISDNSIGTYPE="N/A",
GROUP=0
prov-add:EXTNODE:NAME="as-5400-3",DESC="AS-5400-3-Spans",TYPE="AS5400",ISDNSIGTYPE="N/A",
GROUP=0
________________________________________
; MGCP Path
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:MGCPPATH:NAME="mgcp5400-1",DESC="MGCP service to AS-5400-1",EXTNODE="as-5400-1"
prov-add:MGCPPATH:NAME="mgcp5400-2",DESC="MGCP service to AS-5400-2",EXTNODE="as-5400-2"
prov-add:MGCPPATH:NAME="mgcp5400-3",DESC="MGCP service to AS-5400-3",EXTNODE="as-5400-3"
_______________________________________
; MGCP IP Links
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:IPLNK:NAME="clink5400-1",DESC="MGCP link to AS-5400-1",SVC="mgcp5400-1",
IPADDR="IP_Addr1",PORT=2427,PEERADDR="10.0.75.81",
PEERPORT=2427,PRI=1,IPROUTE=""
prov-add:IPLNK:NAME="clink5400-2",DESC="MGCP link to AS-5400-2",SVC="mgcp5400-2",
IPADDR="IP_Addr1",PORT=2427,PEERADDR="10.0.75.82",
PEERPORT=2427,PRI=1,IPROUTE=""
prov-add:IPLNK:NAME="clink5400-3",DESC="MGCP link to AS-5400-3",SVC="mgcp5400-3",
IPADDR="IP_Addr1",PORT=2427,PEERADDR="10.0.75.83",
PEERPORT=2427,PRI=1,IPROUTE=""
________________________________________
; Signaling Service Property
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:sigsvcprop:NAME="mgcp5400-1",mgcpDomainNameRemote="S0/DS1-1/1@as-5400-1"
prov-add:sigsvcprop:NAME="mgcp5400-2",mgcpDomainNameRemote="S0/DS1-1/1@as-5400-2"
prov-add:sigsvcprop:NAME="mgcp5400-3",mgcpDomainNameRemote="S0/DS1-1/1@as-5400-3"
________________________________________
Cisco MGC Software Release 9.7(3)
10
Blind Take Back and Transfer Replacement
Provisioning Examples
; trunk group
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:TRNKGRP:NAME="7700", CLLI="CLLITG7700",SVC="ss7svc1",TYPE="TDM_ISUP",SELSEQ="ASC"
prov-add:TRNKGRP:NAME="8800", CLLI="CLLITG8800",SVC="ss7svc2",TYPE="TDM_ISUP",SELSEQ="ASC"
prov-add:TRNKGRP:NAME="8899", CLLI="CLLITG8899",SVC="ss7svc3",TYPE="TDM_ISUP",SELSEQ="ASC"
________________________________________
; switch trunk
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:switchtrnk:name="1", trnkgrpnum="7700",span="ffff",cic=1,cu="as-5400-1",
spansize=31,endpoint="s0/ds1-1/1@as-5400-1"
prov-add:switchtrnk:name="1", trnkgrpnum="8800",span="ffff",cic=1,cu="as-5400-2",
spansize=31,endpoint="s0/ds1-1/1@as-5400-2"
prov-add:switchtrnk:name="1", trnkgrpnum="8899",span="ffff",cic=1,cu="as-5400-3",
spansize=31,endpoint="s0/ds1-1/1@as-5400-3"
________________________________________
; routing trunk group
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:rttrnkgrp:name="7700",type=1,reattempts=3,queuing=0,cutthrough=2,resincperc=0
prov-add:rttrnkgrp:name="8800",type=1,reattempts=3,queuing=0,cutthrough=2,resincperc=0
prov-add:rttrnkgrp:name="8899",type=1,reattempts=3,queuing=0,cutthrough=2,resincperc=0
________________________________________
; route
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:rttrnk:weightedTG="OFF",name="rt77",trnkgrpnum=7700
prov-add:rttrnk:weightedTG="OFF",name="rt88",trnkgrpnum=8800
prov-add:rttrnk:weightedTG="OFF",name="rt99",trnkgrpnum=8899
________________________________________
; route list
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:rtlist:name="rtlist77",rtname="rt77",distrib="OFF"
prov-add:rtlist:name="rtlist88",rtname="rt88",distrib="OFF"
prov-add:rtlist:name="rtlist99",rtname="rt99",distrib="OFF"
________________________________________
; Normal Dial Plan
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
numan-add:dialplan:custgrpid="1111", OVERDEC="NO"
________________________________________
; Result Table and Result Set
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
numan-add:resultset:custgrpid="1111",name="set222"
numan-add:resulttable:custgrpid="1111",name="result222",resulttype="ROUTE",dw1="rtlist77",
setname="set222"
numan-add:resultset:custgrpid="1111",name="set333"
numan-add:resulttable:custgrpid="1111",name="result333",resulttype="ROUTE",dw1="rtlist88",
setname="set333"
numan-add:resultset:custgrpid="1111",name="set444"
numan-add:resulttable:custgrpid="1111",name="result444",resulttype="ROUTE",dw1="rtlist99",
setname="set444"
________________________________________
; B digit string for normal call analysis
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
numan-add:bdigtree:custgrpid="1111",callside="originating",digitstring="222",
setname="set222"
numan-add:bdigtree:custgrpid="1111",callside="originating",digitstring="333",
setname="set333"
numan-add:bdigtree:custgrpid="1111",callside="originating",digitstring="444",
setname="set444"
________________________________________
; Overdecadic Dial Plan for mid-call service
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
numan-add:dialplan:custgrpid="2222",overdec="yes"
________________________________________
; Support Midcall Service
Cisco MGC Software Release 9.7(3)
11
Blind Take Back and Transfer Replacement
Software Changes for This Feature Module
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:sigsvcprop:name="ss7svc2", MidCallServiceCustID="2222"
________________________________________
; Result Set
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
numan-add:resultset:custgrpid="2222",name="rset-tnt"
________________________________________
; Result Table
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
numan-add:resulttable:custgrpid="2222",name="tnt-len",
resulttype="INC_NUMBERING",setname="rset-tnt",dw1=0,dw2=7,dw3=7
;The total length of digits is 7 (including string *8 length) for blind transfer service.
numan-add:resulttable:custgrpid="2222",name="tnt-ann",resulttype="ANNOUNCEMENT",
setname="rset-tnt",dw1="33",dw2="0",dw4="2"
; Note: for mid-call announcement, the dw2 must be 0 and dw4 must be 2 (local and final
announcement)
; This announcement is played to redirection party if digits string
; cannot match further dial plan entries
________________________________________
; Digit String
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
numan-add:bdigtree:custgrpid="2222",callside="originating",digitstring="B8",
setname="rset-tnt"
________________________________________
; Result Set
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
numan-add:resultset:custgrpid="2222",name="rset-tnt1"
________________________________________
; Result Table
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
numan-add:resulttable:custgrpid="2222",name="tnt1-bmod",resulttype="BMODDIG",dw1="1",
dw2="2",setname="rset-tnt1"
numan-add:resulttable:custgrpid="2222",name="tnt1-rte",resulttype="ROUTE",dw1="rtlist99",
setname="rset-tnt1"
________________________________________
; Digit String
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
numan-add:bdigtree:custgrpid="2222",callside="originating",digitstring="B822",
setname="rset-tnt1"
;The digits *822xxx invokes mid-call service and transfer the call.
;The service;string '*8' is stripped from digits after analysis.
________________________________________
;Announcement ID in the TimesTen database announcement table
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
numan-add:announcement:annId=33,gwtype=”AS5350”,locationstring=”ann_id_22.au”,
playduration=10,repeat=1,interval=20
prov-cpy
Software Changes for This Feature Module
Feature Summary
CSCsd28134 introduced the software changes in the PGW 2200 to support the Blind Take Back and
Transfer Replacement feature. The following is a summary of the software changes.
New, Modified, and Deleted Elements
Parameters:
Cisco MGC Software Release 9.7(3)
12
Blind Take Back and Transfer Replacement
Software Changes for This Feature Module
•
MidCallServiceCustID
The following sections contain reference material related to this feature. Information is included on the
following areas:
•
Properties, page 13
Properties
The property in this section is used for this feature. For information on other properties for the Cisco
MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
The parent object for the property involved in this feature is found in Table 1-1.
Table 1-1
Software Property Related to this Feature
MidCallServiceCustID
X
X
X
VSI
TrunkGroup
TCAPOverIP
TALI-IOCC
SS7-UK
SS7-Japan
SS7-ITU
SS7-China
SS7-ANSI
SIP
SGCP
SESSION
RLM
MGCP
ISDNPRI
IOCC
EISUP
Property Name
DPNSS
AVM
Parent Object
X
The property used for this feature are described in Table 1-2 and their dynamically provisionable status
is listed in Table 1-3.
Note
The following properties are existing properties whose definitions were modified for this feature. The
valid values and default values have not changed.
Table 1-2
Properties
Property
Definition
MidCallServiceCustID
This is a 4-digit, alphanumeric character string that indicates
which dial plan is used for mid-call service analysis. If this
property value is 0000, no mid-call service is supported. Valid
range: 0000–any 4-digit alphanumeric character string.
Valid Values: 0000–any 4-digit alphanumeric character string.
Default Value: 0000
Table 1-3
Provisionable Properties
Property
Modified value takes effect without restart
MidCallServiceCustID
Yes
Cisco MGC Software Release 9.7(3)
13
Blind Take Back and Transfer Replacement
Obtaining Documentation, Obtaining Support, and Security Guidelines
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 1-4 contains expansions of acronyms and technical terms used in this feature module.
Table 1-4
Expansions
Acronym
Expansion
DTMF
dual-tone multifrequency
MGC
Cisco Media Gateway Controller
PGW
PSTN Gateway
TNT
take back and transfer
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, 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. (0711R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and
figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and
coincidental.
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco MGC Software Release 9.7(3)
14