DPNSS Feature Transparency Diversion
Enhancements
Document Release History
Publication Date
Comments
June 13, 2006
Initial version of the document.
Feature History
Release
Modification
9.6(1)
This feature was introduced on the PWG 2200 software Release 9.6(1)
This document describes the DPNSS Feature Transparency Diversion Enhancements feature.
This feature is described in the following sections:
•
Feature Overview, page 1
•
Supported Standards, MIBs, and RFCs, page 3
•
Prerequisites for Using This Feature, page 4
•
Provisioning Tasks, page 4
•
Provisioning Examples, page 8
•
Software Changes for This Feature Module, page 8
•
Glossary, page 12
Feature Overview
This feature adds functionality to the PGW 2200 in feature transparency mode that allows modification
of Digital Private Network Signaling System No. 1 (DPNSS) diversion digits when they are sent in the
backward direction. Modifying DPNSS diversion digits is useful when the PGW 2200 is used to
interconnect Private Branch Exchanges (PBXs) that have different or incompatible dial plans in which
the diversion digits must be modified to be compatible with the calling party PBX.
This feature provides the following:
Corporate Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San José, CA 95134-1706 USA
Copyright © 2006 Cisco Systems, Inc. All rights reserved.
Feature Overview
•
The c party address received by the PGW in each of the service strings listed in Table 1-1 (passed
in a Number Acknowledge Message (NAM), End-to-End Message (EEM), or Clear Request
Message (CRM)) can be modified upon receipt according to the incoming sigPath property setting.
•
The c party address sent by the PGW in each of the service strings (passed in a NAM, EEM, or CRM)
can be modified according to the outgoing sigPath property setting.
•
The PGW enables you to flexibly modify the divert request data to enable correct number format
presentation across multiple PBX interconnections with nonaligned dial plans.
•
The lead digits that can be stripped from the divert number are provisionable.
•
The lead digits that can be inserted at the head of the divert number are provisionable.
Table 1-1
Service Strings That Can Be Modified
Supplementary Information String Name
Mnemonic
Id Code
Divert Immediate
DVT-I
40B
Divert on Busy
DVT-B
41B
Divert on No Reply
DVT-R
45
Night Service-Divert
NS-DVT
128A
Night Service-Redivert
NS-RDVT
131
Divert
DVT
152B
Divert-Redirection
DVT-RD
203
Divert-Call Failure
DVT-CF
204
Pick-Up Divert
PU-DVT
214B
CSCOgs028/CSCOnn030 introduced the software changes in the PGW 2200 to support the DPNSS
Feature Transparency Diversion Enhancements listed in “Software Changes for This Feature Module”
section on page 8.
Benefits
Support for Backward Service Invocation Requests
The software changes in this feature module address the following backward service invocation requests:
•
Diversion Immediate,
•
Diversion on Busy,
•
Diversion on No Reply,
•
Night Service Divert,
•
Night Service Redivert,
•
Divert,
•
Divert on Call Failure,
•
Call Pick Up Divert, and
•
Divert on Redirection.
DPNSS Feature Transparency Diversion Enhancements
2
Cisco MGC Software Release 9.6(1)
Supported Standards, MIBs, and RFCs
The divert number received by the PGW 2200 in each of the service strings listed in Table 1-1 (passed
in either a NAM, EEM, or CRM are modified upon receipt (provisionable on the ingress sigPath). The
divert number is again modified on output (provisionable on the egress sigPath) at the discretion of the
craftperson.
Ability to Flexibly Modify the Divert Request Data
This feature allows the user to flexibly modify the divert request data in the received data to enable the
correct number format presentation across multiple PBX interconnections with nonaligned dial plans.
The modifications at ingress and egress require that a maximum of six lead digits be removed from the
divert number. A maximum of six digits can also be inserted at the head of the divert number.
Restrictions
This feature is relevant only to the DPNSS Feature Transparent mode of operation.
Related Features and Technologies
The following feature and technology is related to this feature:
•
DPNSS Support on the PGW 2200
Related Documents
This document contains information that is related strictly to this feature. The documents that contain
additional information related to the Cisco Media Gateway Controller (MGC) are:
•
Release Notes for the Cisco Media Gateway Controller Software Release 9.6(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
•
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 Management Information Base Guide
•
Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and
Troubleshooting Guide
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported by this feature.
DPNSS Feature Transparency Diversion Enhancements
Cisco MGC Software Release 9.6(1)
3
Prerequisites for Using 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 Software Release 9 Management Information Base Guide.
RFCs
No new or modified RFCs are supported by this feature.
Prerequisites for Using This Feature
You must have Cisco MGC software Release 9.6(1). Prerequisites for this release can be found in the
Release Notes for the Cisco Media Gateway Controller Software Release 9.6(1).
Provisioning Tasks
The following sections describe the provisioning tasks related to this feature:
•
Provisioning Prerequisites, page 4
•
Provisioning Procedures, page 4
Provisioning Prerequisites
This section lists the data that you must gather to provision this feature. 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.
Collecting Provisioning Data
You must be ready to enter the following provisioning data for this feature:
•
MML name
•
Component description
•
The type of the external node
•
ISDN signaling type
Provisioning Procedures
This section covers the following provisioning topics:
•
Provisioning Basics, page 4
Provisioning Basics
Use the procedures in this section to start a provisioning session, save, and activate the changes you have
made.
DPNSS Feature Transparency Diversion Enhancements
4
Cisco MGC Software Release 9.6(1)
Provisioning Tasks
•
Starting a Provisioning Session, page 5
•
Saving and Activating Your Provisioning Changes, page 5
•
Ending a Provisioning Session Without Activating Your Changes, page 6
•
Retrieving Provisioning Data, page 6
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 might 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.
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.
Note
•
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 5, 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 6.
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 or prov-dply MML command 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.
DPNSS Feature Transparency Diversion Enhancements
Cisco MGC Software Release 9.6(1)
5
Provisioning Tasks
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 5.
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). Saving and activating using prov-cpy on such
a system requires 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.
Note
When you enter the prov-dply command, your provisioning session is 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
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 6
•
Retrieving Data for All Components, page 7
•
Retrieving Data for All Components of a Particular Type, page 7
•
Retrieving Data on the Current Provisioning Session, page 7
•
Retrieving Data on Supported Signaling Protocols, page 8
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:
DPNSS Feature Transparency Diversion Enhancements
6
Cisco MGC Software Release 9.6(1)
Provisioning Tasks
•
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 depends on 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
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
*/
DPNSS Feature Transparency Diversion Enhancements
Cisco MGC Software Release 9.6(1)
7
Provisioning Examples
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
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.
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
________________________________________
; Removing two digits from the incoming number
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:sigsvcprop:name="dpnss-path",FT_IncomingPFXdigitsRemove="2"
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
________________________________________
; Inserting four digits to the incoming number
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:sigsvcprop:name="dpnss-path",FT_IncomingPFXdigitsInsert="0123"
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
________________________________________
; Removing five digits from the outgoing number
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:sigsvcprop:name="dpnss-path",FT_OutgoingPFXdigitsRemove="5"
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
________________________________________
; Inserting three digits to the outgoing number
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:sigsvcprop:name="dpnss-path",FT_OutgoingPFXdigitsInsert="111"
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
Software Changes for This Feature Module
Feature Summary
CSCsd71264 introduced the software changes in the PGW 2200 that supports the DPNSS Feature
Transparency Diversion Enhancements feature. The following is a summary of the software changes.
New Properties
•
FT_IncomingPFXdigitsRemove
•
FT_IncomingPFXdigitsInsert
•
FT_OutgoingPFXdigitsRemove
•
FT_OutgoingPFXdigitsInsert
DPNSS Feature Transparency Diversion Enhancements
8
Cisco MGC Software Release 9.6(1)
Software Changes for This Feature Module
Properties
The properties in this section are 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.
FT_IncomingPFXdigitsRemove
Purpose:
This property indicates the number of diversion digits in a service string that are
removed when the PGW receives DPNSS messages in Feature Transparency mode.
Valid Values:
0 through 6
Default Value:
0
Domain:
X_sigPath
Protocol
Family
DPNSS
Example:
mml> prov-add:sigsvcprop:name="dpnss-path”,FT_IncomingPFXdigitsRemove="2"
The following commands are used to add, retrieve, update, and delete a configuration value for the
FT_IncomingPFXdigitsRemove property:
prov-add:sigsvcprop:name="dpnss-path",FT_IncomingPFXdigitsRemove="4"
prov-rtrv:sigsvcprop:name="dpnss-path"
prov-ed:sigsvcprop:name="dpnss-path",FT_IncomingPFXdigitsRemove="3"
prov-dlt:sigsvcprop:name="dpnss-path","FT_IncomingPFXdigitsRemove"
FT_IncomingPFXdigitsInsert
Purpose:
This property indicates the number of digits in the string that is inserted before the
diversion digits in a service string when the PGW receives DPNSS messages in
Feature Transparency mode.
Valid Values:
NULL or a digit string of 1 through 6 ASCII (0–9) characters
Default Value:
NULL
Domain:
X_sigPath
Protocol
Family
DPNSS
Example:
mml>
prov-add:sigsvcprop:name="dpnss-path",FT_IncomingPFXdigitsInsert="11"
The following commands are used to add, retrieve, update, and delete a configuration value for the
FT_IncomingPFXdigitsInsert property:
DPNSS Feature Transparency Diversion Enhancements
Cisco MGC Software Release 9.6(1)
9
Software Changes for This Feature Module
prov-add:sigsvcprop:name="dpnss-path",FT_IncomingPFXdigitsInsert="11"
prov-rtrv:sigsvcprop:name="dpnss-path"
prov-ed:sigsvcprop:name="dpnss-path",FT_IncomingPFXdigitsInsert="011"
prov-dlt:sigsvcprop:name="dpnss-path","FT_IncomingPFXdigitsInsert"
FT_OutgoingPFXdigitsRemove
Purpose:
This property indicates the number of diversion digits in a service string that are
removed when the PGW sends DPNSS messages in Feature Transparency mode.
Valid Values:
0 through 6
Default Value:
0
Domain:
X_sigPath
Protocol
Family
DPNSS
Example:
mml> prov-add:sigsvcprop:name="dpnss-path",FT_OutgoingPFXdigitsRemove="3"
The following commands are used to add, retrieve, update, and delete a configuration value for the
FT_OutgoingPFXdigitsRemove property:
prov-add:sigsvcprop:name="dpnss-path",FT_OutgoingPFXdigitsRemove="2"
prov-rtrv:sigsvcprop:name="dpnss-path"
prov-ed:sigsvcprop:name="dpnss-path",FT_OutgoingPFXdigitsRemove="3"
prov-dlt:sigsvcprop:name="dpnss-path","FT_OutgoingPFXdigitsRemove"
FT_OutgoingPFXdigitsInsert
Purpose:
This property indicates the number of digits in the string that is inserted before the
diversion digits in a service string when the PGW sends DPNSS messages in Feature
Transparency mode.
Valid Values:
NULL, or a digit string of 1 through 6 ASCII (0–9) characters
Default Value:
NULL
Domain:
X_sigPath
Protocol
Family
DPNSS
Example:
mml> prov-add:sigsvcprop:name=dpnss-path",FT_OutgoingPFXdigitsInsert="01"
The following commands are used to add, retrieve, update, and delete a configuration value for the
FT_OutgoingPFXdigitsInsert property:
prov-add:sigsvcprop:name="dpnss-path",FT_OutgoingPFXdigitsInsert="01"
DPNSS Feature Transparency Diversion Enhancements
10
Cisco MGC Software Release 9.6(1)
Software Changes for This Feature Module
prov-rtrv:sigsvcprop:name="dpnss-path"
prov-ed:sigsvcprop:name="dpnss-path",FT_OutgoingPFXdigitsInsert="011"
prov-dlt:sigsvcprop:name="dpnss-path","FT_OutgoingPFXdigitsInsert"
The parent objects for the properties involved in this feature are shown in Table 1-2.
Table 1-2
Software Properties Related to This Feature
FT_IncomingPFXdigitsRemove
X
FT_IncomingPFXdigitsInsert
X
FT_OutgoingPFXdigitsRemove
X
FT_OutgoingPFXdigitsInsert
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
The properties used for this feature are described in Table 1-3, and their dynamically provisionable
status is listed in Table 1-4.
Note
The following properties are added for this feature. The valid values and default values have not changed.
Table 1-3
Properties Added for This Feature Module
Property
Definition
FT_IncomingPFXdigitsRemove
Indicates the number of diversion digits in a service string that
are removed when the PGW receives DPNSS messages in
Feature Transparency mode. Valid values: 0 through 6.
Default Value: 0
This property is added in software Release 9.6(1).
FT_IncomingPFXdigitsInsert
Indicates the digits that are inserted in the string before the
diversion digits in a service string when the PGW receives
DPNSS messages in Feature Transparency mode. Valid values:
NULL, or a digit string of 1 through 6 ASCII (0–9) characters.
Default Value: NULL
This property is added in software Release 9.6(1).
DPNSS Feature Transparency Diversion Enhancements
Cisco MGC Software Release 9.6(1)
11
Glossary
Table 1-3
Properties Added for This Feature Module (continued)
Property
Definition
FT_OutgoingPFXdigitsRemove
Indicates the number of diversion digits in a service string that
are removed when the PGW sends DPNSS messages in Feature
Transparency mode. Valid values: 0 through 6.
Default Value: 0
This property is added in software Release 9.6(1).
FT_OutgoingPFXdigitsInsert
Indicates the digits that are inserted in the string before the
diversion digits in a service string when the PGW sends DPNSS
messages in Feature Transparency mode. Valid values: NULL,
or a digit string of 1 through 6 ASCII (0–9) characters.
Default Value: NULL
This property is added in software Release 9.6(1).
Provisioning Rules
Keep the following in mind when provisioning the DPNSS Feature Transparency Diversion
Enhancements feature.
•
Digit string characters removed or inserted are values of 0–9 only. No overdecadic digits are
supported.
•
If both of the incoming Feature Transparency prefix properties are enabled, then the digits are first
removed from and then inserted in the service strings listed in Table 1-1 found in the incoming line
message.
•
If both of the outgoing Feature Transparency prefix properties are enabled, then the digit are first
removed and then the digits are inserted in any of the service strings listed in Table 1-1 found in the
outgoing line message.
Table 1-4
Provisionable Properties
Property
Modified Value Takes Effect Without Restart
FT_IncomingPFXdigitsRemove
Yes
FT_IncomingPFXdigitsInsert
Yes
FT_OutgoingPFXdigitsRemove
Yes
FT_OutgoingPFXdigitsInsert
Yes
Glossary
Table 1-5 contains expansions of acronyms used in this feature module.
Table 1-5
Acronym Expansions
Acronym
Expansion
CCM
Cisco CallManager
CRM
Clear Request Message
DPNSS Feature Transparency Diversion Enhancements
12
Cisco MGC Software Release 9.6(1)
Glossary
Table 1-5
Acronym Expansions (continued)
Acronym
Expansion
DPNSS
Digital Private Network Signaling System No. 1
EEM
End-to-End Message
FT
Feature Transparency
ISRM
Initial Service Request Message
MGC
Media Gateway Controller
NAM
Number Acknowledge Message
PBX
Private Branch Exchange
PGW
PSTN Gateway
CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We
Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA,
CCDP, CCIE, CCIP, CCNA, CCNP, 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, FormShare, GigaDrive,
GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace,
MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX,
ScriptShare, SlideCast, SMARTnet, 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. (0601R)
DPNSS Feature Transparency Diversion Enhancements
Cisco MGC Software Release 9.6(1)
13