QSIG Feature Transparency
Document Release History
Publication Date
Comments
September 30, 2003
Initial version of the document.
Feature History
Release
Modification
9.4(1)
This feature was introduced for MGC Release 9.4(1).
The Q Signaling (QSIG) Feature Transparency Feature is described in the following sections:
•
Feature Overview, page 2
– Related Documents, page 3
•
Supported Platforms, page 4
•
Supported Standards, MIBs, and RFCs, page 4
•
Prerequisites, page 4
•
Provisioning Tasks, page 4
•
Provisioning Examples, page 21
•
Command Reference, page 21
•
Reference Information, page 25
•
Obtaining Technical Assistance, page 29
•
Glossary, page 31
Cisco MGC Software Release 9.4(1)
1
QSIG Feature Transparency
Feature Overview
Feature Overview
QSIG Feature Transparency enables the Cisco PGW 2200 Softswitch to allow QSIG supplementary
services and any currently unreferenced QSIG data items to be transmitted over an outgoing QSIG
signaling link—if selected by routing. This feature applies to both call dependent and call independent
signaling, calls that do not reference a bearer channel. Additionally, backward requests for call
forwarding invocation/rerouting will be treated in the Cisco PGW 2200 Softswitch, in which the new
destination number will be reanalyzed and routed upon.
To flexibly configure QSIG Feature Transparency, each QSIG trunk group can be assigned a virtual
private network (VPN) name and assigned on-net and off-net index values into a set of predefined,
constant tables that describe how a particular feature will be handled. If the VPN names match on ingress
and egress trunk group, the on-net index is used to decide the behavior for a feature that may be presented
on the call. Likewise, if the VPN names do not match, then the off-net index is used. Currently, the only
valid defined tables are in the range of 1 through 8. Table 1 dictates that completely transparent operation
is required, or the call will not complete. Tables 2, 3, and 4 are set to feature transparency preferred, but
a nontransparent destination can be used if necessary to complete the call. Table 5 is set to indicate that
the attempted feature will be removed from the onward routed call, and the requestor is informed of this.
Tables 6 and 7 are set to release a feature call, and table 8 is set to remove the feature string and continue.
Note
These index table settings do not affect routing; they affect whether feature transparency occurs and
feature behavior in general.
Figure 1 on page 3 represents an example network with Cisco PGW 2200 Softswitches interconnecting
customer VoIP islands and providing an interface to the PSTN; customers are interconnected through
protocols, such as session initiation protocol (SIP), H.323, and QSIG. If QSIG is being used, QSIG
feature transparency is needed when calls complete via the Cisco PGW 2200 Softswitch and when QSIG
signaling is used for both incoming and outgoing call legs.
Cisco MGC Software Release 9.4(1)
2
QSIG Feature Transparency
Feature Overview
Figure 1
Example network with feature transparency requirements and SS7 interfaces
Customer
VoIP (H.323)
DPNSS
H.323
QSIG
QSIG
backhaul
HSI
EISUP
Service Provider
VoIP
EISUP
Customer
VoIP
SS7
PSTN
MGCP
QSIG
backhaul
SIP
QSIG
backhaul
Customer
VoIP
QSIG
QSIG
DPNSS
Customer
VoIP (SIP)
88962
PBX
PBX
Related Documents
This document contains information that is related strictly to the QSIG Feature Transparency Feature.
The documents that contain additional information related to the Cisco Media Gateway Controller
(MGC) are listed below:
•
Release Notes for Cisco Media Gateway Controller Software Release 9.4(1)
•
Cisco Media Gateway Controller Hardware Installation Guide
•
Regulatory Compliance and Safety Information for the Cisco Media Gateway Controller
•
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
•
Cisco Media Gateway Controller Software Release 9 Provisioning Guide
•
Cisco Media Gateway Controller Software Release 9 Dial Plan Guide
•
Cisco Media Gateway Controller Software Release 9 MML Command Reference Guide
•
Cisco Media Gateway Controller Software Release 9 Messages Reference Guide
•
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
•
Cisco Media Gateway Controller Software Release 9 MIB Guide
Cisco MGC Software Release 9.4(1)
3
QSIG Feature Transparency
Supported Platforms
•
Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and
Troubleshooting Guide
•
Cisco H.323 Signaling Interface Guide
•
Cisco Voice Services Provisioning Tool User Guide
•
Billing and Measurements Server User Guide
Supported Platforms
The hardware platforms supported for the Cisco MGC software are described in the Release Notes for
Cisco Media Gateway Controller Software Release 9.4(1).
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported by this feature.
MIBs
No new or modified standards 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 MIB Guide.
RFCs
No new or modified standards are supported by this feature.
Prerequisites
•
Cisco Media Gateway Controller (MGC) software Release 9.4(1). Prerequisites for this release can
be found in the Release Notes for the Cisco Media Gateway Controller Software Release 9.4(1).
•
Cisco IOS images with PRI backhaul and MGCP will support this feature.
Provisioning Tasks
The following sections describe the provisioning tasks related to this feature:
•
Planning for Provisioning, page 5
•
Provisioning Procedures, page 5
•
Troubleshooting Tips, page 21
Cisco MGC Software Release 9.4(1)
4
QSIG Feature Transparency
Provisioning Tasks
Planning for Provisioning
Before you provision QSIG Feature Transparency-related commands, you must have the following
information about your installation:
•
Dial plan information (depending on the source IP address of the call manager)
For more information on planning the provisioning for the rest of the Cisco MGC software, refer to the
Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Provisioning Procedures
The provisioning procedures for this feature can be found in the following sections:
•
Provisioning Basics, page 5
•
Provisioning QSIG Feature Transparency, page 15
•
Provisioning Call Forwarding, page 19
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 5
•
Saving and Activating your Provisioning Changes, page 6
•
Ending a Provisioning Session Without Activating your Changes, page 7
•
Retrieving Provisioning Data, page 7
For more detailed information about provisioning your Cisco PGW 2200 Softswitch, 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 into the
active Cisco MGC, 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.
Note
•
If you do not know the name of your current configuration session, you can use the procedure in
the “Retrieving Data on the Current Provisioning Session” section on page 12.
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:
Cisco MGC Software Release 9.4(1)
5
QSIG Feature Transparency
Provisioning Tasks
prov-sta::srcver=”ver1”,dstver=”ver2”
Once a provisioning session is underway, you may use the prov-add, prov-ed, or 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 your provisioning session: saving and activating your provisioning changes,
as described in the “Saving and Activating your Provisioning Changes” section on page 6 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 7.
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 the active Cisco MGC. This
command is typically used to save and activate changes on a Cisco MGC in a simplex configuration.
However, you can use the prov-cpy MML command on Cisco MGCs in high-availability or
continuous-service configurations, to save and activate your changes on the active Cisco MGC. If you
choose to do this, you should enter the prov-sync MML command immediately afterwards, to have your
changes saved and activated on the standby Cisco MGC.
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 5.
Caution
Using the prov-sync MML command can severely impact your system’s call processing performance.
We recommend that this command be issued during a maintenance window when traffic is minimal.
Note
When the prov-sync MML command is used to synchronize the provisioning settings on the standby
MGC host with current settings on the active MGC host, the system does not indicate when the
synchronization process has failed.
The prov-dply MML command is used to save and activate your changes on the active and standby
Cisco MGCs. This command is typically used to save and activate changes on Cisco MGCs in
high-availability or continuous-service configurations. This command should not be used on a Cisco
MGC in a simplex configuration.
Cisco MGC Software Release 9.4(1)
6
QSIG Feature Transparency
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 5.
Ending a Provisioning Session Without Activating your Changes
You may find that you want to end a provisioning session without saving and activating the changes you
have entered during your session. If this is the case, you can enter the prov-stp MML command. This
command ends your current provisioning session and your changes are not entered.
Retrieving Provisioning Data
You can use the prov-rtrv MML command to retrieve information about your current provisioning
settings. The ways in which you can use this command to retrieve provisioning data are described in the
following sections:
•
Retrieving Data for an Individual Component, page 7
•
Retrieving Data for All Components, page 9
•
Retrieving Data for All Components of a Particular Type, page 12
•
Retrieving Data on the Current Provisioning Session, page 12
•
Retrieving Data on Supported Signaling Protocols, page 13
Retrieving Data for an Individual Component
You can retrieve provisioning data on any individual component on your system. To do this, log in to the
active Cisco MGC, 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 individual components, enter commands as shown (in
bold text) in this section. The resulting output follows each command.
mml> prov-rtrv:ipfaspath:name="qsig1"
MGC-01 - Media Gateway Controller 2003-05-20 22:10:30.314 PST
M RTRV
"session=05-12:ipfaspath"
/*
NAME = qsig1
DESC = backhaul
EXTNODE = qs-mgcp6
MDO = ETS_300_172
CUSTGRPID = 1111
SIDE = network
ABFLAG = n
CRLEN = 2
*/
;
Cisco MGC Software Release 9.4(1)
7
QSIG Feature Transparency
Provisioning Tasks
mml> prov-rtrv:dchan:name="dchan1"
MGC-01 - Media Gateway Controller 2003-05-20 22:10:53.879 PST
M RTRV
"session=05-12:dchan"
/*
NAME = dchan1
DESC =
SVC = qsig1
PRI = 1
SESSIONSET = sess1
SIGSLOT = 1
SIGPORT = 0
*/
;
intvsc19 mml> prov-rtrv:sess
session - Provisioning Session
sessionprop - Session Set Properties
sessionset - Session Set
intvsc19 mml> prov-rtrv:sessionset:name="sess1"
MGC-01 - Media Gateway Controller 2003-05-20 22:11:21.161 PST
M RTRV
"session=05-12:sessionset"
/*
NAME = sess1-1
DESC = Session Set sess1 Backhaul Link 1
EXTNODE = qs-mgcp6
IPADDR = IP_Addr1
PORT = 1100
PEERADDR = 172.22.121.252
PEERPORT = 1100
TYPE = IPFAS
IPROUTE =
*/
;
intvsc19 mml> prov-rtrv:sigsvcprop:name="qsig1"
MGC-01 - Media Gateway Controller 2003-05-20 22:11:52.187 PST
M RTRV
"session=05-12:sigsvcprop"
/*
ADigitCCPrefix = 0
AInternationalPrefix = NULL
ANationalPrefix = NULL
BcInitState = IS
BDigitCCPrefix = 0
BDigitCCrm = NULL
BInternationalPrefix = NULL
BNationalPrefix = NULL
BothwayWorking = 1
CallForwardRerouteDisabled = 0
CCOrigin = NULL
CGBA2 = 0
CLIPEss = 0
CompressionType = 1
CorrelationCallIDFormat = 0
CotInTone = 2010
<Press 'SPACE' for next page, 'Enter' for next line or 'q' to quit this output>
CotOutTone = 2010
CotPercentage = 0
CustomerVPNid = 0001
CustomerVPNOffNetTblNum = 1
Cisco MGC Software Release 9.4(1)
8
QSIG Feature Transparency
Provisioning Tasks
CustomerVPNOnNetTblNum = 1
ExtCOT = Loop
FastConnect = 0
FAXsupport = 0
FeatureTransparencyDisabled = 0
ForwardCLIinIAM = 1
ForwardSegmentedNEED = 1
GLARE = 0
GRA2 = 0
GtdCapTypeProp = t0
GtdMsgFmt = c
IsupTransEarlyBackwardDisabled = 0
lapdDropErr = true
lapdKval = 7
lapdN200 = 6
lapdN201 = 260
<Press 'SPACE' for next page, 'Enter' for next line or 'q' to quit this output>
lapdT200 = 10
lapdT203 = 500
NatureOfAddrHandling = 0
Normalization = 0
OMaxDigits = 24
OMinDigits = 0
OOverlap = 0
OverlapDigitTime = 6
PostConnectToneDuration = 0
PostConnectToneValue = 0
PropagateSvcMsgBlock = true
RedirectingNbrMap = 0
RedirMax = 5
ReleaseMode = Async
RoutePref = 0
SdpXmitToH323Trigger = 0
spanId = ffff
SuppressCLIDigits = 0
T309Time = 90000
T310Time = 10000
<Press 'SPACE' for next page, 'Enter' for next line or 'q' to quit this output>
TMaxDigits = 24
TMinDigits = 0
TOverlap = 0
VOIPPrefix = 0
*/
;
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 MGC, start an MML session, and enter the following command:
prov-rtrv:all
The system returns a response similar to the following:
mml> prov-rtrv:all
MGC-01 - Media Gateway Controller 2003-05-20 22:04:24.422 PST
M RTRV
"session=05-12:all"
/*
NAME
COMPID
Parent Name
TID
Description
Cisco MGC Software Release 9.4(1)
9
QSIG Feature Transparency
Provisioning Tasks
---"linkset1"
"linkset2"
"linkset3"
"linkset4"
"linkset5"
"sc1-mgcp1"
mgcp sig path 1"
"sc1-mgcp2"
mgcp sig path 2"
"sip-sigchan"
"dp2-mgcp2"
mgcp sig path 2"
"qs1-mgcp2"
mgcp sig path 2"
"qs2-mgcp2"
mgcp sig path 2"
"eisup-pgwlnk1"
eisup"
"eisup-hsilnk1"
eisup"
"eisup-hsilnk2"
eisup"
-------00080001
00080002
00080003
00080004
00080005
00100001
----------"dpc1"
"dpc2"
"dpc3"
"dpc4"
"dpc5"
"sp1-mgcp1"
--LNKSET
LNKSET
LNKSET
LNKSET
LNKSET
IPLNK
----------"Linkset 1"
"Linkset 2"
"Linkset 2"
"Linkset 2"
"Linkset 2"
"sigchannel 1 for
00100002
"sp1-mgcp2"
IPLNK
"sigchannel 1 for
00100003
00100004
"sip-sigpath"
"sp1-mgcp5"
SIPLNK
IPLNK
"SIP sigchan"
"sigchannel 1 for
00100005
"sp1-mgcp6"
IPLNK
"sigchannel 1 for
00100006
"sp1-mgcp7"
IPLNK
"sigchannel 1 for
00100007
"eisup-pgw"
IPLNK
"sigchannel 1 for
00100008
"eisup-hsi1"
IPLNK
"sigchannel 1 for
00100009
"eisup-hsi2"
IPLNK
"sigchannel 1 for
<Press 'SPACE' for next page, 'Enter' for next line or 'q' to quit this output>
"sc1-mgcp3"
0010000a "sp1-mgcp3"
IPLNK
"sigchannel 1 for
mgcp sig path 2"
"dp1-mgcp1"
0010000b "sp1-mgcp4"
IPLNK
"sigchannel 1 for
mgcp sig path 2"
"route1"
00110001 "mgc-01"
SS7ROUTE
"Route to
DPC-2-2-2"
"route2"
00110002 "mgc-01"
SS7ROUTE
"Route to
DPC-3-3-3"
"route3"
00110003 "mgc-01"
SS7ROUTE
"Route to
DPC-3-3-3"
"route4"
00110004 "mgc-01"
SS7ROUTE
"Route to
DPC-3-3-3"
"route5"
00110005 "mgc-01"
SS7ROUTE
"notSet"
"opc"
00130001 "mgc-01"
OPC
"The vsc point
code"
"dpc1"
00130002 "mgc-01"
DPC
"Orig. point code"
"dpc2"
00130003 "mgc-01"
DPC
"Dest. point code"
"dpc3"
00130004 "mgc-01"
DPC
"Dest. point code"
"dpc4"
00130005 "mgc-01"
DPC
"Dest. point code"
"opc1"
00130006 "mgc-01"
OPC
"The vsc point
code"
"dpc5"
00130007 "mgc-01"
DPC
"Dest. point code"
"ss7svc1"
00150001 "dpc1"
SS7PATH
"SS7 service to
DPC-2-2-2"
"ss7svc2"
00150002 "dpc2"
SS7PATH
"SS7 service to
DPC-3-3-3"
"ss7svc3"
00150003 "dpc3"
SS7PATH
"SS7 service to
DPC-3-3-3"
"ss7svc4"
00150004 "dpc4"
SS7PATH
"SS7 service to
DPC-3-3-3"
"ss7svc5"
00150005 "dpc5"
SS7PATH
"Nothing defined"
"slt1"
00160001 "mgc-01"
EXTNODE
"SLT-c2600"
<Press 'SPACE' for next page, 'Enter' for next line or 'q' to quit this output>
"slt2"
00160002 "mgc-01"
EXTNODE
"SLT-c2600"
"mgcp1"
00160003 "mgc-01"
EXTNODE
"external node mgcp1"
"mgcp2"
00160004 "mgc-01"
EXTNODE
"external node mgcp2"
Cisco MGC Software Release 9.4(1)
10
QSIG Feature Transparency
Provisioning Tasks
"mgcp3"
mgcp2"
"dp-mgcp4"
mgcp2"
"dp-mgcp5"
mgcp2"
"qs-mgcp6"
mgcp2"
"qs-mgcp7"
mgcp2"
"eisup1"
eisup"
"eisup2"
eisup"
"eisup3"
eisup"
"slt3"
"slt4"
"slt5"
"eisup-pgw"
mgc"
"eisup-hsi1"
mgc"
"eisup-hsi2"
mgc"
"slink1-1"
"slink1-2"
"slink1-3"
00160005
"mgc-01"
EXTNODE
"external node -
00160006
"mgc-01"
EXTNODE
"external node -
00160007
"mgc-01"
EXTNODE
"external node -
00160008
"mgc-01"
EXTNODE
"external node -
00160009
"mgc-01"
EXTNODE
"external node -
0016000a
"mgc-01"
EXTNODE
"external node -
0016000b
"mgc-01"
EXTNODE
"external node -
0016000c
"mgc-01"
EXTNODE
"external node -
0016000d
0016000e
0016000f
00190001
"mgc-01"
"mgc-01"
"mgc-01"
"eisup1"
EXTNODE
EXTNODE
EXTNODE
EISUPPATH
"SLT-c2600"
"SLT-c2600"
"SLT-c2600"
"signal service -
00190002
"eisup2"
EISUPPATH
"signal service -
00190003
"eisup3"
EISUPPATH
"signal service -
001d0001
001d0002
001d0003
"linkset1"
"linkset2"
"linkset3"
C7IPLNK
C7IPLNK
C7IPLNK
"Signal link 1-1"
"Signal link 1-1"
"Signal link 1-1"
<Press 'SPACE' for next page, 'Enter' for next line or 'q' to quit this output>
"slink1-4"
001d0004 "linkset4"
C7IPLNK
"Signal link 1-1"
"slink1-5"
001d0005 "linkset5"
C7IPLNK
"notSet"
"qsig1"
00340001 "qs-mgcp6"
IPFASPATH
"backhaul"
"qsig2"
00340002 "qs-mgcp7"
IPFASPATH
"backhaul"
"sp1-mgcp1"
00350001 "mgcp1"
MGCPPATH
"signal service mgcp1"
"sp1-mgcp2"
00350002 "mgcp2"
MGCPPATH
"signal service mgcp1"
"sp1-mgcp3"
00350003 "mgcp3"
MGCPPATH
"signal service mgcp1"
"sp1-mgcp4"
00350004 "dp-mgcp4"
MGCPPATH
"signal service mgcp1"
"sp1-mgcp5"
00350005 "dp-mgcp5"
MGCPPATH
"signal service mgcp1"
"sp1-mgcp6"
00350006 "qs-mgcp6"
MGCPPATH
"signal service mgcp1"
"sp1-mgcp7"
00350007 "qs-mgcp7"
MGCPPATH
"signal service mgcp1"
"t1"
00370001 "mgc-01"
GTDPARAM
"notSet"
"t3"
00370002 "mgc-01"
GTDPARAM
"notSet"
"t4"
00370003 "mgc-01"
GTDPARAM
"notSet"
"t6"
00370004 "mgc-01"
GTDPARAM
"notSet"
"sip-sigpath"
003e0001 "SIP"
SIPPATH
"SIP sigpath"
"c7-2611-1"
00480001 "slt1"
SESSIONSET
"Session Set
c7-2611 Backhaul Link 1"
"c7-2612-1"
00480002 "slt2"
SESSIONSET
"Session Set
c7-2612 Backhaul Link 1"
"c7-2613-1"
00480003 "slt2"
SESSIONSET
"Session Set
c7-2613 Backhaul Link 1"
"c7-2614-1"
00480004 "slt2"
SESSIONSET
"Session Set
c7-2614 Backhaul Link 1"
<Press 'SPACE' for next page, 'Enter' for next line or 'q' to quit this output>
Cisco MGC Software Release 9.4(1)
11
QSIG Feature Transparency
Provisioning Tasks
"sess1-1"
00480005
Backhaul Link 1"
"sess2-1"
00480006
Backhaul Link 1"
"c7-2615-1"
00480007
c7-2615 Backhaul Link 1"
"dchan1"
00490001
"dchan2"
00490002
"assoc1"
004a0001
"assoc2"
004a0002
"dpnss1"
00550001
nas2600"
"dpnss2"
00550002
nas2600"
"qs-mgcp6"
SESSIONSET
"Session Set sess1
"qs-mgcp7"
SESSIONSET
"Session Set sess2
"slt5"
SESSIONSET
"Session Set
"qsig1"
"qsig2"
"dp-mgcp4"
"dp-mgcp5"
"dp-mgcp4"
DCHAN
DCHAN
ASSOCIATION
ASSOCIATION
DPNSSPATH
""
""
""
""
"backhaul to
"dp-mgcp5"
DPNSSPATH
"backhaul to
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 MGC, 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"
The system returns a response similar to the following:
mml> prov-rtrv:ss7path:"all"
MGC-01 - Media Gateway Controller 2003-05-20 22:15:10.488 PST
M RTRV
"session=05-12:ss7path"
/*
NAME
DPC
OPC
CUSTGRPID
SIDE
M3UAKEY
------------------------ss7svc1
dpc1
opc
1111
network
ss7svc2
dpc2
opc1
1111
network
ss7svc3
dpc3
opc
1111
network
ss7svc4
dpc4
opc
1111
network
ss7svc5
dpc5
opc
1111
network
*/
;
MDO
--Q761_GERMAN
ANSISS7_STANDARD
ISUPV2_ISRAEL
ISUPV2_ISRAEL
BTNUP_IUP
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 MGC, start an MML session, and enter the following command:
prov-rtrv:session
Cisco MGC Software Release 9.4(1)
12
QSIG Feature Transparency
Provisioning Tasks
The system returns a response similar to the following:
MGC-02 - Media Gateway Controller 2003-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
The system returns a response similar to the following:
mml> prov-rtrv:variants
MGC-01 - Media Gateway Controller 2003-05-20 22:15:37.303 PST
M RTRV
"session=05-12:variants"
/*
MDO File name
Protcol Family
Switch Type
-----------------------------------ANSISS7_92
SS7-ANSI
0
ANSISS7_C2
SS7-ANSI
20
ANSISS7_C3
SS7-ANSI
0
ANSISS7_E1
SS7-ANSI
23
ANSISS7_STANDARD
SS7-ANSI
0
ATT_41459
ISDNPRI
17
ATT_41459_C2
ISDNPRI
17
BELL_1268
ISDNPRI
22
BELL_1268_C2
ISDNPRI
22
BELL_SGCP
MGCP
0
BTNUP_BTNR167
SS7-UK
5
BTNUP_IUP
SS7-UK
5
DPNSS_BTNR188
DPNSS
26
EISUP
EISUP
0
<Press 'SPACE' for next page, 'Enter' for next line or 'q' to quit this output>
ETS_300_102
ISDNPRI
27
ETS_300_102_C2
ISDNPRI
27
ETS_300_121
SS7-ITU
0
ETS_300_172
ISDNPRI
29
ETS_300_356
SS7-ITU
0
GR317
SS7-ANSI
0
HONGKONG
SS7-ITU
0
IETF_DCS
SIP
0
IETF_SIP
SIP
0
ISUPV1_POLI
SS7-ITU
0
ISUPV2_32DIG
SS7-ITU
0
ISUPV2_AUSTRIAN
SS7-ITU
0
ISUPV2_CZECH
SS7-ITU
0
ISUPV2_DUTCH
SS7-ITU
0
ISUPV2_FINNISH96
SS7-ITU
0
ISUPV2_FRENCH
SS7-ITU
0
ISUPV2_GERMAN
SS7-ITU
0
ISUPV2_ISRAEL
SS7-ITU
40
ISUPV2_JAPAN
SS7-Japan
10
ISUPV2_JAPAN_C2
SS7-Japan
0
Cisco MGC Software Release 9.4(1)
13
QSIG Feature Transparency
Provisioning Tasks
<Press 'SPACE' for next page, 'Enter' for next line or 'q' to quit this output>
ISUPV2_NORWEGIAN
SS7-ITU
0
ISUPV2_POLISH
SS7-ITU
0
ISUPV2_SPANISH
SS7-ITU
0
ISUPV2_SPANISH_C2
SS7-ITU
0
ISUPV2_SWISS
SS7-ITU
0
ISUPV2_SWISS_C2
SS7-ITU
0
ISUPV2_VIETNAM
SS7-ITU
0
ISUPV3
SS7-ITU
0
ISUPV3_UK
SS7-UK
0
ISUPV3_UK_C2
SS7-UK
0
ISUPV3_UK_C3
SS7-UK
0
ISUPV3_UK_C4
SS7-UK
0
MGCPCAS
CAS
0
Q721_BASE
SS7-ITU
5
Q721_BRAZILIAN
SS7-ITU
5
Q721_CHINA
SS7-China
5
Q721_FRENCH
SS7-ITU
5
Q721_PHILLIPINE
SS7-ITU
5
Q761_97VER
SS7-ITU
0
Q761_ARGENTINA
SS7-ITU
0
<Press 'SPACE' for next page, 'Enter' for next line or 'q' to quit this output>
Q761_ARGENTINA_C2
SS7-ITU
0
Q761_AUSTRL
SS7-ITU
0
Q761_AUSTRL_C2
SS7-ITU
0
Q761_BASE
SS7-ITU
0
Q761_BELG
SS7-ITU
0
Q761_BELG_97VER
SS7-ITU
0
Q761_CHILE
SS7-ITU
0
Q761_CHINA
SS7-China
0
Q761_CHINA_C2
SS7-China
0
Q761_DANISH
SS7-ITU
0
Q761_GERMAN
SS7-ITU
0
Q761_INDIA
SS7-ITU
0
Q761_JAPAN
SS7-Japan
10
Q761_KOREAN
SS7-ITU
0
Q761_NEWZEALAND
SS7-ITU
0
Q761_PERU
SS7-ITU
0
Q761_PORTUGAL
SS7-ITU
0
Q761_SINGAPORE
SS7-ITU
0
Q761_SINGAPORE_C2
SS7-ITU
0
Q761_TAIWAN
SS7-ITU
0
<Press 'SPACE' for next page, 'Enter' for next line or 'q' to quit this output>
Q761_THAILAND
SS7-ITU
0
Q767_AUSTRALIA
SS7-ITU
0
Q767_BASE
SS7-ITU
0
Q767_BRAZIL
SS7-ITU
0
Q767_COLOMBIA
SS7-ITU
0
Q767_GUATEMALA
SS7-ITU
0
Q767_INDONESIA
SS7-ITU
0
Q767_ITAL
SS7-ITU
0
Q767_ITAL_C2
SS7-ITU
0
Q767_MEXICAN
SS7-ITU
0
Q767_RUSS
SS7-ITU
0
Q767_SINGAPORE
SS7-ITU
0
Q767_SPAN
SS7-ITU
0
Q767_SWED
SS7-ITU
0
Q767_TURKISH
SS7-ITU
0
Q931
ISDNPRI
27
Q931_AUSTRALIA
ISDNPRI
19
Q931_SINGAPORE
ISDNPRI
27
dummy
AVM
0
Cisco MGC Software Release 9.4(1)
14
QSIG Feature Transparency
Provisioning Tasks
dummy
MGCP
0
<Press 'SPACE' for next page, 'Enter' for next line or 'q' to quit this output>
dummy
SGCP
0
dummy
TCAPOverIP
0
dummy
VSI
0
*/
;
Provisioning QSIG Feature Transparency
Note
External nodes supporting IPFASPATH (PRI-backhaul) can be used for this feature.
QSIG Feature Transparency is provisioned when
1.
The incoming QSIG trunk group has a valid customer VPN ID property assigned.
2.
A valid customer table index property is assigned.
3.
The terminating trunk group is QSIG.
If, in addition, the VPN IDs match, then the call is considered on-net. In all other cases, the call defaults
to off-net.
Note
To provision QSIG Feature Transparency, all of the properties specific to QSIG are enabled at the
trunkgroup or Sigpath level.
Assigning a VPN ID to a Trunk Group
To assign a VPN ID to a trunk group, perform the following steps:
Step 1
Start a provisioning session as described in the “Starting a Provisioning Session” section on page 5.
Step 2
Enter the following command to assign a VPN ID to a trunk group:
prov-ed:trnkgrpprop:name="name", CustomerVPNid ="id"
Where:
•
name—The MML name of the previously configured trunk group.
•
id—The VPN ID you want to assign to the trunk group.The default value is 00000000. The ID can
be up to 8 alphanumeric characters. Absence of property will be treated as if no VPN ID is present.
Note
Connectionless calls—feature calls that have no physical bearer circuit associated—will not
have an associated trunk group; therefore, provisioning must be done at the system level. For
system level capability, /opt/CiscoMGC/etc/properties.dat must be edited manually. For more
information on the properties.dat file, refer to these publications: Cisco Media Gateway
Controller Software Release 9 Installation and Configuration Guide, Cisco Media Gateway
Controller Software Release 9 Dial Plan Guide.
For example, to assign the VPN ID ABIGBIZ1 to trunk group 1000, you would enter the following
command:
Cisco MGC Software Release 9.4(1)
15
QSIG Feature Transparency
Provisioning Tasks
prov-ed:trnkgrpprop:name="1000", CustomerVPNid="ABIGBIZ1"
Step 3
Repeat Step 2 for each trunk group to which you want to assign a VPN ID.
Step 4
If there are no other components that you need to provision, end your provisioning session as described
in the “Saving and Activating your Provisioning Changes” section on page 6.
Assigning a VPN ID to a Sigpath
To assign a VPN ID to a Sigpath, perform the following steps:
Step 1
Start a provisioning session as described in the “Starting a Provisioning Session” section on page 5.
Step 2
Enter the following command to assign a VPN ID to a system:
prov-ed:sigsvcprop:name="name", CustomerVPNid="id”
Where:
•
name—The MML name of the previously configured system.
•
id—The VPN ID you want to assign to the system. The default value is 00000000. The ID can be
up to 8 alphanumeric characters. Absence of property will be treated as if no VPN ID is present.
Connectionless calls—feature calls that have no physical bearer circuit associated—will not
have an associated trunk group; therefore, provisioning must be done at the system level.
Note
For example, to assign the VPN ID ABIGBIZ1 to system sigpath1, you would enter the following
command:
mml>prov-ed:sigsvcprop:name="sigpath1", CustomerVPNid ="ABIGBIZ1”
Step 3
Repeat Step 2 for each system to which you want to assign a VPN ID.
Step 4
If there are no other components that you need to provision, end your provisioning session as described
in the “Saving and Activating your Provisioning Changes” section on page 6.
Assigning an On-net Table Index to a Trunk Group
To assign an on-net table index to a trunk group, perform the following steps:
Step 1
Start a provisioning session as described in the “Starting a Provisioning Session” section on page 5.
Step 2
Enter the following command to assign an on-net table index:
prov-ed:trnkgrpprop:name="name", CustomerVPNOnNetTblNum="int"
Where:
name—The MML name of the previously configured trunk group.
int—The on-net index value that you want to assign to the trunk group. The default value is 0. Absence
of property will also be treated as if no VPN on-net table number is present. Valid values are 1 to 8 and
are defined as follows:
– 1—Dictates that completely transparent operation is required or the call will not complete.
Cisco MGC Software Release 9.4(1)
16
QSIG Feature Transparency
Provisioning Tasks
– 2—Sets to feature transparency preferred by a nontransparent destination can be used if
necessary to complete the call.
– 3—Sets to feature transparency preferred by a nontransparent destination can be used if
necessary to complete the call.
– 4—Sets to feature transparency preferred by a nontransparent destination can be used if
necessary to complete the call.
– 5—Sets to indicate that the attempted feature will be removed from the onward routed call, and
the indicator is informed of this.
– 6—Sets to release a feature call.
– 7—Sets to release a feature call.
– 8—Sets to remove the feature string and continue.
For example, to set the on-net index value of trunk group 1000 to feature transparency preferred, you
would enter the following command:
prov-ed:trnkgrpprop:name="1000", CustomerVPNOnNetTblNum="2"
Step 3
Repeat Step 2 for each on-net table index you want to assign.
Step 4
If there are no other components that you need to provision, end your provisioning session as described
in the “Saving and Activating your Provisioning Changes” section on page 6.
Assigning an Off-net Table Index to a Trunk Group
To assign an off-net table index to a trunk group, perform the following steps:
Step 1
Start a provisioning session as described in the “Starting a Provisioning Session” section on page 5.
Step 2
Enter the following command to assign an off-net table index:
prov-ed:trnkgrpprop:name="name", CustomerVPNOffNetTblNum="int"
Where:
name—The MML name of the previously configured trunk group.
int—The off-net index value that you want to assign to the trunk group. The default value is 0. Absence
of property will also be treated as if no VPN off-net table number is present. Valid values are 1 to 8 and
are defined as follows:
– 1—Dictates that completely transparent operation is required or the call will not complete.
– 2—Sets to feature transparency preferred by a nontransparent destination can be used if
necessary to complete the call.
– 3—Sets to feature transparency preferred by a nontransparent destination can be used if
necessary to complete the call.
– 4—Sets to feature transparency preferred by a nontransparent destination can be used if
necessary to complete the call.
– 5—Sets to indicate that the attempted feature will be removed from the onward routed call, and
the indicator is informed of this.
– 6—Sets to release a feature call.
– 7—Sets to release a feature call.
Cisco MGC Software Release 9.4(1)
17
QSIG Feature Transparency
Provisioning Tasks
– 8—Sets to remove the feature string and continue.
For example, to set the off-net index value of trunk group 1000 to indicate the attempted feature will be
removed from the onward routed call, you would enter the following command:
prov-ed:trnkgrpprop:name="1000", CustomerVPNOnNetTblNum="5"
Step 3
Repeat Step 2 for each off-net table index you want to assign.
Step 4
If there are no other components that you need to provision, end your provisioning session as described
in the “Saving and Activating your Provisioning Changes” section on page 6.
Verifying QSIG Feature Transparency Is Enabled or Disabled
To verify QSIG Feature Transparency is enabled or disabled, perform the following steps:
Step 1
Start a provisioning session as described in the “Starting a Provisioning Session” section on page 5.
Step 2
Enter the following command to check if QSIG Feature Transparency is enabled for a Sigpath:
prov-rtrv:sigsvcprop:name=”name”
Where:
name—The MML name of the previously configured Sigpath.
Or
Enter the following command to check if QSIG Feature Transparency is enabled for a trunkgroup:
prov-rtrv:trnkgrpprop:name=”name”
Where:
name—The MML name of the previously configured trunk group.
Step 3
Check the resulting output for the value of the FeatureTransparencyDisabled property:
prov-rtrv:sigsvcprop:name=”qsig1”
MGC-01 - Media Gateway Controller 2003-05-20 22:11:52.187 PST
M RTRV
“session=05-12:sigsvcprop”
/*
.
.
.
FeatureTransparencyDisabled=0
Where:
0—Indicates that the QSIG Feature Transparency is enabled.
1—Indicates that the QSIG Feature Transparency is disabled.
Step 4
If there are no other components that you need to provision, end your provisioning session as described
in the “Saving and Activating your Provisioning Changes” section on page 6.
Disabling QSIG Feature Transparency
To disable QSIG Feature Transparency, perform the following steps:
Cisco MGC Software Release 9.4(1)
18
QSIG Feature Transparency
Provisioning Tasks
Step 1
Start a provisioning session as described in the “Starting a Provisioning Session” section on page 5.
Step 2
Enter the following command to disable QSIG Feature Transparency:
prov-ed:trnkgrpprop:name="name", FeatureTransparencyDisabled="1"
Where:
name—The MML name of the previously configured trunk group.
1—This property will disable QSIG Feature Transparency toward another Cisco PGW or connected
H.323 signaling interface (HSI) when set to 1. The default value is 0, enabled, and absence of property
will also be treated as 0.
Note
Only assign this property to EISUP, DPNSS and QSIG trunk groups/system.
For example, to disable QSIG Feature Transparency on trunk group 1000, you would enter the following
command:
prov-ed:trnkgrpprop:name="1000", FeatureTransparencyDisabled="1"
Step 3
If there are no other components that you need to provision, end your provisioning session as described
in the “Saving and Activating your Provisioning Changes” section on page 6.
Provisioning Call Forwarding
Disabling Call Forwarding Reroute Capability on a Trunk Group
To disable Call Forwarding reroute capability on a trunk group, perform the following steps:
Step 1
Start a provisioning session as described in the “Starting a Provisioning Session” section on page 5.
Step 2
Enter the following command to disable Call Forwarding reroute capability on a trunk group:
prov-ed:trnkgrpprop:name="name", CallForwardRerouteDisabled="1"
Where:
name—The MML name of the previously configured QSIG trunk group.
I—This property will disable Call Forwarding reroute functionality when requested by the PBX if set to
1.The default value is 0, enabled, and absence of property will also be treated as 0.
Note
Only assign this property to QSIG trunk groups/system.
For example, to disable Call Forwarding reroute capability on trunk group 500, you would enter the
following command:
prov-ed:trnkgrpprop:name="500", CallForwardRerouteDisabled ="1"
Step 3
If there are no other components that you need to provision, end your provisioning session as described
in the “Saving and Activating your Provisioning Changes” section on page 6.
Cisco MGC Software Release 9.4(1)
19
QSIG Feature Transparency
Provisioning Tasks
Disabling Call Forwarding Reroute Capability on a System
To disable Call Forwarding reroute capability on a system, perform the following steps:
Step 1
Start a provisioning session as described in the “Starting a Provisioning Session” section on page 5.
Step 2
Enter the following command to disable Call Forwarding reroute capability on a system:
prov-ed:sigsvcprop:name="name", CallForwardRerouteDisabled="1
Where:
name—The MML name of the previously configured QSIG system.
I—This property will disable Call Forwarding reroute functionality when requested by the PBX if set to
1.The default value is 0, enabled, and absence of property will also be treated as 0.
Note
Only assign this property to QSIG trunk groups/system.
For example, to disable Call Forwarding reroute capability on system sigpath1, you would enter the
following command:
prov-ed:sigsvcprop:name="sigpath1", CallForwardRerouteDisabled ="1"
Step 3
If there are no other components that you need to provision, end your provisioning session as described
in the “Saving and Activating your Provisioning Changes” section on page 6.
Verifying Call Forwarding Reroute Capability Is Disabled
To verify Call Forwarding reroute capability is disabled, enter the following commands:
Step 1
Start a provisioning session as described in the “Starting a Provisioning Session” section on page 5.
Step 2
Enter the following command:
prov-rtrv:sigsvcprop:name=”name”
Where:
name—The MML name of the previously configured Sigpath.
Step 3
Check the resulting output for the value of the CallForwardRerouteDisabled property:
prov-rtrv:sigsvcprop:name=”qsig1”
MGC-01 - Media Gateway Controller 2003-05-20 22:11:52.187 PST
M RTRV
“session=05-12:sigsvcprop”
/*
.
.
.
CallForwardRerouteDisabled=1
Where:
0—Indicates that the feature is enabled.
1—Indicates that the feature is disabled.
Cisco MGC Software Release 9.4(1)
20
QSIG Feature Transparency
Provisioning Examples
Step 4
If there are no other components that you need to provision, end your provisioning session as described
in the “Saving and Activating your Provisioning Changes” section on page 6.
Troubleshooting Tips
For more information on troubleshooting the rest of the Cisco MGC software, refer to the Cisco Media
Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide.
Provisioning Examples
This section provides a provisioning example for this feature. For additional examples (including a
complete provisioning procedure for the Cisco PGW 2200 Softwitch) refer to the Cisco Media Gateway
Controller Software Release 9 Provisioning Guide.
Assigning a VPN ID and On-net and Off-net Indices to a Trunk Group
prov-ed:trnkgrpprop:name="1000", CustomerVPNid="ABIGBIZ1"
prov-ed:trnkgrpprop:name="1000", CustomerVPNOnNetTblNum="2"
prov-ed:trnkgrpprop:name="1000", CustomerVPNOffNetTblNum="5"
Assigning a VPN ID to a System
prov-ed:sigsvcprop:name="sigpath1", CustomerVPNid="ABIGBIZ1”
Disabling Feature Transparency
prov-ed:trnkgrpprop:name="1000", FeatureTransparencyDisabled="1"
Disabling the Call Forwarding Reroute Capability on a Trunk Group
prov-ed:trnkgrpprop:name="500", CallForwardRerouteDisabled ="1"
Disabling the Call Forwarding Reroute Capability on a System
prov-ed:sigsvcprop:name="sigpath1", CallForwardRerouteDisabled ="1"
Command Reference
The following sections contain reference material related to this feature. Information is included on the
following areas:
•
Properties, page 22
Cisco MGC Software Release 9.4(1)
21
QSIG Feature Transparency
Command Reference
Properties
New Properties
The following new properties are added to the PROV-ED provisioning command for this feature:
•
CustomerVPNid, page 22
•
CustomerVPNOnNetTblNum, page 22
•
CustomerVPNOffNetTblNum, page 23
•
FeatureTransparencyDisabled, page 24
•
CallForwardRerouteDisabled, page 25
CustomerVPNid
Purpose:
Assigns a VPN ID to a trunk group or system.
Syntax:
Trunk group
prov-ed:trnkgrpprop:name="name", CustomerVPNid ="id"
System
prov-ed:sigsvcprop:name="name", CustomerVPNid ="id”
Input
•
name—The MML name of the previously configured trunk group or system.
Description:
•
id—A string of 1-8 alphanumeric characters. The default value is 00000000.
An absence of property will be treated as if no VPN ID is present.
Example:
The MML command shown in the following example assigns the VPN ID
ABIGBIZ1 to trunk group 1000.
mml> prov-ed:trnkgrpprop:name="1000", CustomerVPNid ="ABIGBIZ1"
The MML command shown in the following example assigns the VPN ID
ABIGBIZ1 to system sigpath1.
mml> prov-ed:sigsvcprop:name="sigpath1", CustomerVPNid ="ABIGBIZ1”
Comments:
CustGrpid was used previously for this function.
Property Domain—TrunkGroup, System
Protocol Family—ISDNPRI, DPNSS
CustomerVPNOnNetTblNum
Purpose:
Assigns a VPN on-net profile table index to a particular trunk group.
Syntax:
prov-ed:trnkgrpprop:name="name", CustomerVPNOnNetTblNum ="int"
Cisco MGC Software Release 9.4(1)
22
QSIG Feature Transparency
Command Reference
Input
•
name—The MML name of the previously configured trunk group.
Description:
•
int—Valid property values are 0-8. The default value is 0. Absence of property
will be treated as if no VPN on-net table number is present.
– 1—Dictates that completely transparent operation is required or the call
will not complete.
– 2—Sets to feature transparency preferred by a nontransparent destination
can be used if necessary to complete the call.
– 3—Sets to feature transparency preferred by a nontransparent destination
can be used if necessary to complete the call.
– 4—Sets to feature transparency preferred by a nontransparent destination
can be used if necessary to complete the call.
– 5—Sets to indicate that the attempted feature will be removed from the
onward routed call, and the indicator is informed of this.
– 6—Sets to release a feature call.
– 7—Sets to release a feature call.
– 8—Sets to remove the feature string and continue.
Example:
The MML command shown in the following example assigns the VPN on-net
profile table index 2 to trunk group 1000.
mml> prov-ed:trnkgrpprop:name="1000", CustomerVPNOnNetTblNum ="2"
Comments:
Previously called CustGrptbl or VNET_TABLE_INDICES.
Property Domain—TrunkGroup, System
Protocol Family—ISDNPRI, DPNSS.
CustomerVPNOffNetTblNum
Purpose:
Assigns VPN off-net profile table index to a particular trunk group.
Syntax:
prov-ed:trnkgrpprop:name="name", CustomerVPNOffNetTblNum ="int"
Cisco MGC Software Release 9.4(1)
23
QSIG Feature Transparency
Command Reference
Input
•
name—The MML name of the previously configured trunk group.
Description:
•
int—Valid property values are 0 to 8. The default value is 0. Absence of
property will be treated as if no VPN off-net table number is present.
– 1—Dictates that completely transparent operation is required or the call
will not complete.
– 2—Sets to feature transparency preferred by a nontransparent destination
can be used if necessary to complete the call.
– 3—Sets to feature transparency preferred by a nontransparent destination
can be used if necessary to complete the call.
– 4—Sets to feature transparency preferred by a nontransparent destination
can be used if necessary to complete the call.
– 5—Sets to indicate that the attempted feature will be removed from the
onward routed call, and the indicator is informed of this.
– 6—Sets to release a feature call.
– 7—Sets to release a feature call.
– 8—Sets to remove the feature string and continue.
Example:
The MML command shown in the following example assigns the VPN off-net
profile table index 5 to trunk group 1000.
mml> prov-ed:trnkgrpprop:name="1000", CustomerVPNOffNetTblNum ="5"
Comments:
Property Domain—TrunkGroup/System
Protocol Family—ISDNPRI, DPNSS
FeatureTransparencyDisabled
Purpose:
Disables QSIG Feature Transparency for all calls on the PGW.
Syntax:
prov-ed:trnkgrpprop:name="name", FeatureTransparencyDisabled =“int”
Input
•
name—The MML name of the previously configured trunk group.
Description:
•
int—Valid property values. Default value is 0, and absence of property will be
treated as 0.
– 0 = Feature Transparency enabled
– 1= Feature Transparency disabled
Example:
The MML command shown in the following example disables QSIG Feature
Transparency on trunk group 1000.
mml> prov-ed:trnkgrpprop:name="1000", FeatureTransparencyDisabled ="1"
Comments:
Property Domain—TrunkGroup, System
Protocol Family—EISUP, DPNSS, ISDNPRI
Cisco MGC Software Release 9.4(1)
24
QSIG Feature Transparency
Reference Information
CallForwardRerouteDisabled
Purpose:
Syntax:
Disables Call Forwarding rerouting for all calls on the PGW.
Trunk group
prov-ed:trnkgrpprop:name="name", CallForwardRerouteDisabled ="int"
System
prov-ed:sigsvcprop:name=”name”, CallForwardRerouteDisabled=“int”
Input
•
name—The MML name of the previously configured trunk group or system.
Description:
•
int—Valid property values. Default value is 0, and absence of property will be
treated as 0.
– 0 = Call Forwarding reroute enabled
– 1= Call Forwarding reroute disabled
Example:
The MML command shown in the following example disables Call Forwarding
rerouting on trunk group 500.
mml> prov-ed:trnkgrpprop:name="500", CallForwardRerouteDisabled ="1"
The MML command shown in the following example disables Call Forwarding
rerouting on system sigpath1.
mml> prov-ed:sigsvcprop:name="sigpath1", CallForwardRerouteDisabled ="1"
Comments:
Property Domain—TrunkGroup, System
Protocol Family—DPNSS, ISDNPRI
Reference Information
The following sections contain reference material related to this feature. Information is included on the
following areas:
•
XECfgParm.dat Parameters, page 26
•
Alarms, page 26
•
Logs, page 26
•
Measurements, page 26
•
Billing Interface, page 27
•
Components, page 28
•
Properties, page 22
•
Processes, page 28
•
External Node Types, page 28
•
File Names for Supported SS7 Protocols, page 28
•
Result Type Definitions, page 28
Cisco MGC Software Release 9.4(1)
25
QSIG Feature Transparency
Reference Information
•
MGCP Results, page 29
•
NOA and NPI Codes, page 29
•
CPC and TMR Values, page 29
•
CPC and TMR Values, page 29
•
Provisioning Worksheets, page 29
•
Dial Plan Worksheets, page 29
XECfgParm.dat Parameters
This feature does not add, modify, or delete XECfgParm.dat parameters in the MGC software.For
information on the other XECfgParm.dat parameters, refer to the Cisco Media Gateway Controller
Software Release 9 Installation and Configuration Guide.
Alarms
This feature does not add, modify, or delete alarms in the MGC software.For information on the other
alarms for the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9
Messages Reference Guide.
Logs
This feature does not add, modify, or delete logs in the MGC software.For information on the other
alarms, refer to the Cisco Media Gateway Controller Software Release 9 Messages Reference Guide.
Measurements
This feature does not add, modify, or delete measurements in the MGC software.For information on the
other system measurements, refer to the Cisco Media Gateway Controller Software Release 9
Operations, Maintenance, and Troubleshooting Guide.
Cisco MGC Software Release 9.4(1)
26
QSIG Feature Transparency
Reference Information
Billing Interface
The following tables contains the billing interfaces that are added to support this feature.
Originating VPN ID (Tag: 4211)
Name: Originating VPN ID
Tag: 4211
Source: MDL
Description/Purpose: Identifies the VPN customer ID associated with the incoming trunk group or system.
It is used for feature transparency with access protocols DPNSS and QSIG.
Format: IA5
Length in Octets: 8
Data Value: Alphanumeric string
Associated with DPNSS and QSIG trunk groups, this string identifies a particular customer’s VPN.
Extended Data Value: No extended value.
General Information: The inclusion of this tag is based upon the presence of a VPN ID associated with the
incoming trunk group.
Note: If the incoming trunk group is EISUP, the VPN ID of the incoming trunk group of the remote PGW is
used if present.
MGC Release: Release 9.4(1)
Answered Deselecte Aborted Release
(1010)
d (1020) (1030) (1040)
Interrupted
(1050)
Ongoing
(1060)
Maintenance External
End of Call
(1070)
DB (1080) (1110)
Y
N
N
N
N
Y
N
N
Y
Terminating VPN ID (Tag: 4212)
Name: Terminating VPN ID
Tag: 4212
Source: MDL
Description/Purpose: Identifies the VPN customer ID associated with the outgoing trunk group or system.
It is used for feature transparency with access protocols DPNSS and QSIG.
Format: IA5
Length in Octets: 8
Data Value: Alphanumeric string
Associated with DPNSS and QSIG trunk groups, this string identifies a particular customer’s VPN.
Example: BTFNET1
Extended Data Value: No extended value.
General Information: The inclusion of this tag is based upon the presence of a VPN ID associated with the
outgoing trunk group.
Note: If the outgoing trunk group is EISUP, the VPN ID of the incoming trunk group of the remote PGW is
used if present.
MGC Release: Release 9.4(1)
Answered Deselecte Aborted Release
(1010)
d (1020) (1030) (1040)
Interrupted
(1050)
Ongoing
(1060)
Maintenance External
End of Call
(1070)
DB (1080) (1110)
Y
N
N
N
N
Y
N
N
Y
Cisco MGC Software Release 9.4(1)
27
QSIG Feature Transparency
Reference Information
For billing interface information for the rest of the Cisco MGC software, refer to the Cisco Media
Gateway Controller Software Release x Billing Interface Guide.
Components
This feature does not add, modify, or delete components in the MGC software. For information on the
rest of the components in the Cisco MGC software, refer to the Cisco Media Gateway Controller
Software Release x Provisioning Guide.
Properties
The following new properties are added to the prov-ed provisioning command for this feature:
•
CustomerVPNid, page 22
•
CallForwardRerouteDisabled, page 25
•
CustomerVPNid, page 22
•
CustomerVPNOnNetTblNum, page 22
•
CustomerVPNOffNetTblNum, page 23
For more information on these properties, see the “New Properties” section on page 22.
For information on other properties for the Cisco MGC software, refer to the Cisco Media Gateway
Controller Software Release 9 Provisioning Guide.
Processes
This feature does not add, modify, or delete processes in the MGC software.For information on other
processes for the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release
x Operations, Maintenance, and Troubleshooting Guide.
External Node Types
This feature does not add, modify, or delete external node types in the MGC software.
File Names for Supported SS7 Protocols
This feature does not add, modify, or delete supported SS7 protocols in the MGC software.
Result Type Definitions
This feature does not add, modify, or delete result type definitions in the MGC software. For information
on other result type definitions for the Cisco MGC software, refer to the Cisco Media Gateway
Controller Software Release 9 Provisioning Guide.
Cisco MGC Software Release 9.4(1)
28
QSIG Feature Transparency
Obtaining Technical Assistance
MGCP Results
This section does not add, modify, or delete MGCP results in the MGC software.For information on
other MGCP results for the Cisco MGC software, refer to the Cisco Media Gateway Controller Software
Release 9 Provisioning Guide.
NOA and NPI Codes
This feature does not add, modify, or delete NOA and NPI codes in the MGC software. For information
on other NOA and NPI codes for the Cisco MGC software, refer to the Cisco Media Gateway Controller
Software Release 9 Dial Plan Guide.
CPC and TMR Values
This feature does not add, modify, or delete CPC and TMR vales in the MGC software. For information
on other CPC and TMR values for the Cisco MGC software, refer to the Cisco Media Gateway
Controller Software Release 9 Dial Plan Guide.
Cause and Locations Codes
This feature does not add, modify, or delete cause and location codes in the MGC software. For
information on other cause and location codes for the Cisco MGC software, refer to the Cisco Media
Gateway Controller Software Release Dial Plan Guide.
Provisioning Worksheets
For worksheets covering the rest of the provisioning components in the Cisco MGC software, refer to
the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Dial Plan Worksheets
For worksheets covering the rest of the dial plan components in the Cisco MGC software, refer to the
Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can
obtain online documentation, troubleshooting tips, and sample configurations from online tools by using
the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access
to the technical support resources on the Cisco TAC Web Site.
Cisco MGC Software Release 9.4(1)
29
QSIG Feature Transparency
Obtaining Technical Assistance
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open
access to Cisco information, networking solutions, services, programs, and resources at any time, from
anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a
broad range of features and services to help you with these tasks:
•
Streamline business processes and improve productivity
•
Resolve technical issues with online support
•
Download and test software packages
•
Order Cisco learning materials and merchandise
•
Register for online skill assessment, training, and certification programs
If you want to obtain customized information and service, you can self-register on Cisco.com. To access
Cisco.com, go to this URL:
http://www.cisco.com
Technical Assistance Center
The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance
with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC
Web Site and the Cisco TAC Escalation Center.
Cisco TAC inquiries are categorized according to the urgency of the issue:
•
Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities,
product installation, or basic product configuration.
•
Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably
impaired, but most business operations continue.
•
Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects
of business operations. No workaround is available.
•
Priority level 1 (P1)—Your production network is down, and a critical impact to business operations
will occur if service is not restored quickly. No workaround is available.
The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of
service contracts, when applicable.
Cisco TAC Web Site
You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time.
The site provides around-the-clock access to online tools, knowledge bases, and software. To access the
Cisco TAC Web Site, go to this URL:
http://www.cisco.com/tac
All customers, partners, and resellers who have a valid Cisco service contract have complete access to
the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a
Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or
password, go to this URL to register:
http://www.cisco.com/register/
Cisco MGC Software Release 9.4(1)
30
QSIG Feature Transparency
Glossary
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco
TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC
Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These
classifications are assigned when severe network degradation significantly impacts business operations.
When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer
automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support
services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network
Supported Accounts (NSA). When you call the center, please have available your service agreement
number and your product serial number.
Glossary
The following table contains definitions of acronyms and technical terms used in this feature module.
Term
Definition
DPNSS
Digital Private Network Signaling System—A PBX standard developed in
the United Kingdom.
EISUP
Extended ISDN User Part—A proprietary protocol used to communicate
between Cisco MGC nodes and between a Cisco MGC node and a Cisco
H.323 System Interface.
H.323
H.323 allows dissimilar communication devices to communicate with
each other by using a standardized communication protocol. H.323 defines
a common set of CODECs, call setup and negotiating procedures, and
basic data transport methods.
HSI
H.323 Signaling Interface
ISDN
Integrated Services Digital Network
ISUP
ISDN User Part
MGC
Media Gateway Controller
MGCP
Media Gateway Control Protocol
MIB
Managed Information Base
MML
Man-Machine Language
PSTN
Public Switched Telephone Network
QSIG
Q (point of the ISDN model) Signaling. Signaling standard. Common
channel signaling protocol based on ISDN Q.931 standards and used by
many digital PBXs.
Cisco MGC Software Release 9.4(1)
31
QSIG Feature Transparency
Glossary
Term
Definition
SIP
Session Initiation Protocol
SS7
Signaling System 7
VoIP
Voice over IP. The capability to carry normal telephony-style voice over an
IP-based internet with POTS-like functionality, reliability, and voice
quality. VoIP enables a router to carry voice traffic (for example, telephone
calls and faxes) over an IP network. In VoIP, the DSP segments the voice
signal into frames, which then are coupled in groups of two and stored in
voice packets. These voice packets are transported using IP in compliance
with ITU-T specification H.323.
Cisco MGC Software Release 9.4(1)
32