Table Of Contents
Release Notes for the Cisco PGW 2200 Softswitch Release 9.7(3)
Cisco PGW 2200 Softswitch Software Compatibility Matrix
Host Minimum Server Requirements
Media Gateway Hardware Requirements
Cisco PGW 2200 Softswitch Management
New Features in Release 9.7(3)
A-Number Country Code Digit Remove Property
Backwards Propagation of SIP REFER over SS7 Using REL with RDN
Blind Take Back and Transfer Replacement
CODEC and DTMF Preferential Routing Enhancements
Configuration Check for Active and Standby
Digit Buffering for International Gateways
DPNSS Service Interworking with Cisco CallManager Using QSIG Tunneling
Enhanced Local Number Portability and Dial Plan Selection
Licensing Features for the Cisco PGW 2200 Softswitch
Live Upgrade from 9.6 Sparc to 9.7 Sparc and Opteron
Provisioning Multiple Incoming IP Trunks Feature
PGW-ITP Optimize Routing with MAP Query
PGW Support for HSI Non-RAS Mode
PGW TCP Transport for SIP Phase I
No Support for UDP/TCP Mixed Network
Pre Call Announcement After Address Complete Message
Presentation Number Modification
RADIUS Enhancement for Accounting
Ring Back Service Using CPC=3 for Voice Messaging
Sequential Network Consultation Transfer
SIP and ISUP Interworking for Call Hold and Terminal Portability
SIP Configurable Retransmissions
SIP Early-Dialog Offer/Answer Using PRACK/180/183
Provisioning the SIP Early-Dialog Offer/Answer Using PRACK/180/183 Feature
SIP FROM Interworking with SS7 and PRI
SIP Service Handling and Feature Interworking Enhancements
SIP Support of Take Back and Transfer in the Cisco Unified Contact Center
SS7 Take Back and Transfer RELEASE Message Parameter Modifications
Support for INAP Generic Number
Support for Individual SIP Cause Values
Support of Provisionable QoS for Signaling Traffic
Support of Trunk Group ID at the x-route-tag or tsp Parameter
Egress Trunk Group Property for SIP
Support of VXSM M3UA Signaling
Take Back and Transfer Phase 2
Usability Enhancements—Phase 1
XML-Based Trunk Group File Format
Release 9.7(3) Patch 26 and Earlier
Release 9.7(3) Patch 27 and Later
Installing and Upgrading the Software
Using the Patch Upgrade Procedure
SNMP Returns Wrong Status for Physical E1000G Interfaces
NGE Support for the PGW SNMP Stack
Known Issues and Operational Recommendations
FTP Not Enabled During Solaris 10 Installation
Core Dump When Active and Standby Use Different Patch Versions
Inappropriate Trunk Selection with Unreliable MGCP Path and LIDL Trunk Selection Sequence
Unexpected RADIUS Connectivity Alarms Under Traffic Load
Instability of the nge Interfaces on the Netra X4200 M2 Platform Under Duplex Mismatch Condition
System File vars.pm Error After Migration from Release 9.7(3) to Release 9.8(1)
Obtaining Documentation and Submitting a Service Request
Release Notes for the Cisco PGW 2200 Softswitch Release 9.7(3)
Revised: January 5, 2012Release 9.7(3) of the Cisco PGW 2200 Softswitch provides new features and significant performance improvements. The release can operate on Sparc or Sun AMD Opteron platforms. The Opteron platform provides higher performance.
These release notes describe the features and caveats for Release 9.7(3).
Contents
Release Notes for the Cisco PGW 2200 Softswitch Release 9.7(3) contain the following sections:
•
New Features in Release 9.7(3)
•
Known Issues and Operational Recommendations
•
Obtaining Documentation and Submitting a Service Request
Introduction
Interoperability between the old and traditional time division multiplexing (TDM) networks and the new and advanced packet networks is an essential part of technology adoption for packet networks. This release of the Cisco PGW 2200 Softswitch extends its capability to provide the bridge between the legacy public switched telephone network (PSTN) and next-generation packet networks—supporting centralized call control and intelligent routing for both TDM-based interfaces (SS7, PRI, QSIG, and DPNSS endpoints) and IP-based interfaces (and H.323 endpoints).
The Cisco PGW 2200 Softswitch provides a consistent and unified interconnection that supports the Cisco Voice Infrastructure and Applications (VIA) applications (Dial and Voice transit), Cisco Business Voice Services applications (Hosted or Managed IP Telephony), and Cisco Broadband Residential Voice applications (ETTx). The Cisco PGW 2200 Softswitch allows service providers to deploy and operate multiple network solutions while maintaining a stable interconnection to the PSTN.
Platform Support
For a list of supported platforms, see the following documents:
•
Cisco PGW 2200 Softswitch Hardware Installation Guide-Releases 7 & 9
•
Cisco PGW 2200 Softswitch Release 9.7 Software Installation and Configuration Guide
Software Required
For a list of software requirements, see Chapter 1 of the Cisco PGW 2200 Softswitch Software Release 9.7 Installation and Configuration Guide at:
http://www.cisco.com/en/US/products/hw/vcallcon/ps2027/tsd_products_support_series_home.html
CautionThe Cisco PGW 2200 Softswitch and HSI should be installed on dedicated platforms and should not reside with any other applications (SMTP, DNS, HTTP daemons, and so forth). The Cisco PGW 2200 Softswitch and HSI cannot reside on the same platform. Cisco VSPT software must be installed on a platform running the Cisco PGW 2200 Softswitch.
Cisco PGW 2200 Softswitch Software Compatibility Matrix
Table 1 shows Cisco PGW 2200 Softswitch software compatibility matrix.
Table 1 Cisco PGW 2200 Softswitch Software Compatibility Matrix
Component Type Role Hardware Software RequiredCisco PGW 2200 Softswitch Node
Call control
Cisco PGW 2200 Softswitch
Software Version 9.7(3)
—
—
Cisco HSI1
Release 4.3(2), with latest patch
ITP-L2
—
Cisco 2811 ITP-L
Cisco IOS Version 12.4(11)SW2
Integrated ITP-L
—
Cisco AS5400 Integrated ITP-L
Cisco IOS Version 12.4(7e)
Ethernet Switch/Router
—
Cisco Catalyst 2900XL
Current Release
—
—
Cisco Catalyst 5500
Current Release
—
—
Cisco Catalyst 6500
Current Release
CallManager
IP PBX and
key switchCisco CallManager
Version 4.2(1)
Cisco Unified CallManager Express
Version 4.0
—
—
Cisco Unified CallManager
Version 5.1
Unified Messaging Server
—
Cisco Unity
Version 4.0(4) SR1
ITP3
—
Cisco ITP 2651, Cisco ITP 72xx, Cisco ITP 75xx
Cisco IOS Version 12.4(10a)
Media Gateways (MGCP-controlled for PSTN trunking)
—
Cisco AS5350XM
Cisco IOS Version 12.4(1), 12.4T, or later
—
—
Cisco AS5400XM
Cisco IOS Version 12.4(1), 12.4T, or later
—
—
Cisco AS5850
Cisco IOS Version 12.4
—
—
Cisco AS5850 with STM1 module
Cisco IOS Version 12.4
—
—
Cisco MGX 8880 Media Gateway (VISM)
VISM 3.3.xx
—
—
Cisco MGX 8880 Media Gateway (Cisco VXSM)
VXSM 5.4.xx
Media Gateways (MGCP-controlled for PBX access)
—
Cisco 2651XM, 2691XM, 36xx, 37xx
Cisco IOS Version 12.4(3), Cisco IOS Version 12.4(5), or Cisco IOS Version 12.4(10a)
—
—
BRI backhaul: Cisco 1721 1751, 1751v, 1761, 1761v 2612
Cisco IOS Version 12.4(7)
—
—
PRI/Q.931 backhaul for call agents:
Cisco 2691Cisco IOS Version 12.3(7)T1
Firewall
—
Cisco PIX 515, 525, or 535 Security Appliance
Cisco PIX Security Appliance Version 7.0
Network Management
—
Cisco BAMS4
Version 3.30 with latest patch
—
—
Cisco MNM5
Version 2.7(3)
For correlation of the MNM patches with the Cisco PGW 2200 Softswitch patches, see http://www.cisco.com/en/US/docs/net_mgmt/mnm/2.7.3/release/note/CMNM_rn.html
—
—
Cisco VSPT6
Version 2.7(3)
For correlation of the VSPT patches with the Cisco PGW 2200 Softswitch patches, see http://www.cisco.com/en/US/docs/net_mgmt/vspt/2.7/release/notes/vspt273.html
—
—
CTM7 for MGX 8880 Media Gateway management
Version 8.0
—
—
CiscoWorks LMS8 for IOS and Catalyst devices
Version 2.5.1
Optional Software
—
Cisco IPM9
Version 2.3
—
—
CIC10
Version 3.5
1 Cisco HSI = Cisco H.323 Signaling Interface
2 ITP-L = IP Transfer Point LinkExtender
3 ITP = IP transfer point
4 Cisco BAMS = Cisco Billing and Measurement Server
5 Cisco MNM = Cisco MGC Node Manager
6 Cisco VSPT = Cisco Voice Services Provisioning Tool
7 CTM = Cisco Transport Manager
8 LMS = LAN Management Solution
9 IPM = Internetwork Performance Monitor
10 CIC = Cisco Info Center
Required Swap Space
For the Cisco PGW 2200 Softswitch software, partition 4 GB of swap space. Setting swap space at installation is recommended; however, you can change swap space at a later date by adding a swap file or repartitioning the swap space using the format menu (for example, reassigning how many cylinders are in each partition). The swap space requirement is determined by the amount of traffic. As traffic increases, use the MML rtrv-ne-health command to observe the amount of swap space that is being used; then decide to increase the swap space if more is needed.
Note
Solaris uses swap as a file system cache in addition to virtual memory paging. It is normal to observe both physical and virtual memory completely consumed on Solaris. It is better to monitor usage with vmstat -p and vmstat -p 1 along with iostat -xtc.
Host Hardware Requirements
Host Minimum Server Requirements
See Cisco PGW 2200 Softswitch Hardware Installation Guide-Releases 7 & 9 for the host minimum hardware requirements. Before using the minimum hardware configuration, consult with your Cisco representative to determine the hardware that will give you the best performance results based on your network configuration, proposed traffic, and desired processing power.
Media Gateway Hardware Requirements
Table 2 lists URLs for release notes that document media gateways.
Table 2 Media Gateway Release Notes Locations
Media Gateway Release Notes Release Notes LocationMGX8880 Voice Interworking Service Module (VXSM)
http://www.cisco.com/en/US/products/hw/gatecont/ps3869/prod_release_notes_list.html
MGX8000 Voice Gateway (VISM)
http://www.cisco.com/en/US/products/hw/gatecont/ps3869/prod_release_notes_list.html
AS5350 Universal Gateway
http://www.cisco.com/en/US/docs/ios/12_1/12_1xq/release/notes/rn5350xq.html
AS5400 Universal Gateway
http://www.cisco.com/en/US/docs/ios/12_1/12_1xd/release/notes/rn5400xd.html
AS5850 Universal Gateway
http://www.cisco.com/en/US/docs/ios/12_1/12_1xv/release/notes/rn5850xv.html
Local Area Network Switch
Your application might use one or more LAN switches from the Cisco Catalyst Switch family to connect the Cisco PGW 2200 Softswitch host to the media gateways (MGWs) and to the Cisco IP Transfer Point LinkExtenders (ITP-Ls) or Cisco IP Transfer Points (ITPs).
Note
LAN switches in Cisco PGW 2200 Softswitch user documentation refer to the Cisco Catalyst 5500 switch family (NEBS-compliant). The Cisco Catalyst 2900 XL is another NEBS-compliant LAN switch that can be used for a small configuration, but current Cisco PGW 2200 Softswitch user documentation does not address the Cisco Catalyst 2900 XL. See the Cisco Catalyst 2900 XL documentation for information about this switch.
Note
A LAN switch is not provided with the Cisco PGW 2200 Softswitch.
Supported Features
The features listed in Table 3 were inherited from earlier releases of the Cisco PGW 2200 Softswitch software and are still supported in Release 9.7(3).
Table 3 Supported Features in Release 9.7(3)
Feature PurposeLong-distance service through both indirect and direct access
Replaces the need for traditional TDM equipment.
Support for domestic and international dialing plans
Provides scalable and flexible service.
Support for automatic number identification (ANI) authorization
Adds security and prevents fraudulent use of the network.
Support for toll-free and 8XX numbers through the service control point (SCP)
Allows callers to use the free phone and premium services across the Tandem/Transit network.
Centralized element manager
Provides a method to configure and monitor the network.
ISUP PSTN interconnect with full continuity test (COT) support
Provides verification of the voice path.
Support for ISDN direct-access lines
Allows direct line access to the Cisco PGW 2200 Softswitch.
Support for E-ISUP inter-MGC signaling
Provides scalable and flexible service.
Support for advanced call routing
Provides scalable and flexible service.
Support for MGCP 1.0
Allows the Cisco PGW 2200 Softswitch to control media gateway connections.
Support for carrier-grade quality of service (QoS)
Replaces the need for traditional TDM equipment.
Support for SS7-to-SS7, SS7-to-ISDN, SS7-to-SIP, SS7-to-H.323, ISDN-to-SIP, ISDN-to-H.323, ISDN-to-ISDN, DPNSS-H323, and DPNSS-SS7 call types
Provides scalable and flexible service.
Support for voice-band telephony
Provides scalable and flexible service.
Support for ISDN data calls
Provides scalable and flexible service.
Support for real-time fax relay
Provides scalable and flexible service.
Support for modem passthrough
Provides scalable and flexible service.
Support for Cisco media gateways
Protects investment in Cisco equipment.
Provide a reliable IP link between the Cisco PGW 2200 Softswitch and access servers with RUDP1
No single point of failure in the connection between media gateways and the Cisco PGW 2200 Softswitch.
Call detail records for PSTN billing
Meets carrier-grade PSTN requirements for moving existing voice revenue streams to the packet environment and for creating new voice service opportunities. Provides a CDR2 viewer for viewing billing records.
Facility associated signaling provided by the Cisco ITP-Ls (T1/E1 WIC, optional with SS7)
•
Grooms off the bearer channels and then delivers them to the media gateway.
•
Delivers MTP-3 to the Cisco PGW 2200 Softswitch host over IP.
High Availability platform
Maintains established calls when there is a switchover from the active Cisco PGW 2200 Softswitch host to its paired standby host.
Sun Solaris 10
•
Y2K compliant
•
Open computing platform
Support for multiple OPCs3 , DPCs4 , and PRI D channels:
•
Support for 1500+ DPCs
•
Support for up to six OPCs plus 40+ CPCs5
•
Supports 504 PRI D channels
•
Scales cost-effectively to central office size
•
Flexible and scalable
Quasi-associated or fully associated signaling
Ready for international markets.
Complete continuity check (two-wire and four-wire)
Meets interconnect requirements.
NEBS Level 3 compliant
Telco-ready.
Several simplex or high availability platform options
Cost-effective options.
1 RUDP = Reliable User Datagram Protocol
2 CDR = call detail record
3 OPCs = origination point codes
4 DPCs = destination point codes
5 CPCs = capability point codes
Cisco PGW 2200 Softswitch Management
Table 4 provides an overview of the management components of the Cisco PGW 2200 Softswitch.
Table 4 Cisco PGW 2200 Softswitch Management Components
Management Component DescriptionCisco VSPT1
Cisco VSPT provides an easy-to-use graphical tool to provision the Cisco PGW 2200 Softswitch, certain gateways and the Cisco BAMS2 . VSPT can be used to create, copy, modify, and deploy configurations. VSPT Release 2.7(3) is now included with the Cisco MNM3 Release 2.7(3) and is no longer available as a download option.
Alarms and SNMP traps
The Cisco PGW 2200 Softswitch supports a comprehensive set of alarms (in accordance with ITU X.733).
•
Processing error alarms
•
QoS alarms
•
Equipment alarms
•
Communications alarms
•
Environment alarms
You can also configure the system to generate real-time alarms to local or remote terminals. All alarms are written to a log file in an uncompressed format for easy retrieval.
Measurements and statistics
You can obtain a variety of usage statistics from the Cisco PGW 2200 Softswitch. The data is recorded real-time and written to a file. You can specify the statistics to be collected and the time intervals for collection and writing to file. Each PEG count record includes:
•
Start time
•
Duration
•
Measured value
•
Category
•
Element measured
Cisco MNM
Cisco MNM is a management system for VoIP networks, including the Cisco PGW 2200 Softswitch, Cisco BAMS, Cisco HSI, Cisco ITP-L, and Catalyst switches. Cisco MNM contains a map viewer to manage large, evolving networks, an alarm browser, and performance management features. Cisco MNM allows individual components to be easily configured and managed.
1 Cisco VSPT = Cisco Voice Services Provisioning Tool
2 Cisco BAMS = Cisco Billing and Measurement Server
3 Cisco MNM = Cisco MGC Node Manager
New Features in Release 9.7(3)
The following features have been added to Release 9.7(3)
•
A-Number Country Code Digit Remove Property
•
Backwards Propagation of SIP REFER over SS7 Using REL with RDN
•
Blind Take Back and Transfer Replacement
•
CODEC and DTMF Preferential Routing Enhancements
•
Configuration Check for Active and Standby
•
Digit Buffering for International Gateways
•
DPNSS Service Interworking with Cisco CallManager Using QSIG Tunneling
•
Enhanced Local Number Portability and Dial Plan Selection
•
Licensing Features for the Cisco PGW 2200 Softswitch
•
Live Upgrade from 9.6 Sparc to 9.7 Sparc and Opteron
•
PGW-ITP Optimize Routing with MAP Query
•
PGW Support for HSI Non-RAS Mode
•
PGW TCP Transport for SIP Phase I
•
Pre Call Announcement After Address Complete Message
•
Presentation Number Modification
•
RADIUS Enhancement for Accounting
•
Ring Back Service Using CPC=3 for Voice Messaging
•
Sequential Network Consultation Transfer
•
SIP and ISUP Interworking for Call Hold and Terminal Portability
•
SIP Configurable Retransmissions
•
SIP Early-Dialog Offer/Answer Using PRACK/180/183
•
SIP FROM Interworking with SS7 and PRI
•
SIP Service Handling and Feature Interworking Enhancements
•
SIP Support of Take Back and Transfer in the Cisco Unified Contact Center
•
SS7 Take Back and Transfer RELEASE Message Parameter Modifications
•
Support for INAP Generic Number
•
Support for Individual SIP Cause Values
•
Support of Provisionable QoS for Signaling Traffic
•
Support of Trunk Group ID at the x-route-tag or tsp Parameter
•
Support of VXSM M3UA Signaling
•
Take Back and Transfer Phase 2
•
Usability Enhancements—Phase 1
•
XML-Based Trunk Group File Format
A-Number Country Code Digit Remove Property
This A-Number Country Code Digit Remove Property feature (CSCsa75618) introduces the trunk group property AdigitCCrm to the Cisco PGW 2200 Softswitch. If the AdigitCCrm trunk group property is a nonnull value and the A-number NOA is international, the Cisco PGW 2200 Softswitch can remove from one to five leading digits that match the AdigitCCrm property value (the country code). In addition to removal of the country code, the NOA value in the ISUP message is modified from international to national.
Note
For more information, see the A-Number Country Code Digit Remove Property feature module.
Backwards Propagation of SIP REFER over SS7 Using REL with RDN
The Backwards Propagation of SIP REFER over SS7 Using REL with RDN feature (CSCsl06237) allows a SIP REFER on the terminating call to be propagated back to the originating SS7 call by sending a REL that contains the redirection number and redirection information. The REFER is acknowledged with an indication of success and the call is immediately released on receipt of an RLC.
To activate this service, existing analysis FACILTY results are required against the Originating SS7 call.
DW1=3 DW2=2Call flow:-IAM ----> INVITE<----- 100 TryingACM<----<----- 180 RingingANM<----<------200 OK------>ACK<------REFER (refer-to: RDN)------>202 Accepted------>NOTIFY (sip frag 100 Trying)<------200 (NOTIFY)REL<----- (RDN in RDN Information)------->NOTIFY (sip frag 200 OK)<------200 (NOTIFY)RLC----->------->BYE<-------200 (BYE)Blind Take Back and Transfer Replacement
The Blind Take Back and Transfer Replacement feature (CSCsd28134) provides support on the Cisco PGW 2200 Softswitch of the blind take back and transfer of a call by using digits received midcall via DTMF to invoke a blind call transfer. This type of call flow is typically found in use by traditional TDM user support groups to transfer calls to a service agent from a different group or location. The DTMF digits are received from the called attendant in the conversation phase of the call, and the Cisco PGW 2200 Softswitch autonomously reroutes the call based upon the analysis of the received DTMF digits.
Cisco PGW 2200 Softswitch supports TDM-based transferring agents and calling party for this feature.
A new sigpath and trunkgroup property MidCallServiceCustID allows Cisco PGW 2200 Softswitch to enable this feature.
Note
For more information, see the Blind Take Back and Transfer Replacement feature module.
Call Reporting
The Call Reporting feature (CSCsx16398) enables the Cisco PGW 2200 Softswitch to generate an alarm if a caller dials a particular number. Users specify the number as a digit string (for example, the emergency number 999 in the United Kingdom, or 911 in the United States). In response to such an alarm, a security team can capture the alert and respond appropriately.
The Call Reporting feature also enables the Cisco PGW 2200 Softswitch to report call details by way of SNMP to a network element management system such as the Cisco Media Gateway Controller Node Manager (Cisco MNM). Also, users can provision the Call Reporting feature by using the Cisco Voice Services Provisioning Tool (Cisco VSPT) as an alternative method to an MML command session.
Calling Name Delivery (CNAM)
The Calling Name Delivery feature (CSCsc56989) allows the name of the calling party to be delivered to the called party if the called party has subscribed to the calling name delivery feature. Hence it is a terminating feature.
The Cisco PGW 2200 Softswitch supports Transactional Capabilities Application Part (TCAP) query to a CNAM database, if needed, based on the called party number. The retrieved CNAM is passed to the egress destination if and only if it is allowed based on calling name delivery blocking (CNAB) and calling identity delivery and suppression (CIDS) information.
Note
For more information, see the Calling Name Delivery (CNAM) feature module.
CODEC and DTMF Preferential Routing Enhancements
The CODEC and DTMF Preferential Routing Enhancements feature (CSCsa81867) provides the following:
•
Extends the Cisco PGW 2200 Softswitch ability to influence CODEC selection to IP calls (SIP and H.323).
•
Allows users to determine that there is no common CODEC or DTMF capability between a certain ingress and egress destination, allowing route advance to an egress destination that can either directly handle the combination, or else an IP-IP gateway that can perform transcoding.
•
Supports route advance when the type of DTMF interworking does not match.
Note
For more information, see the CODEC and DTMF Preferential Routing Enhancements feature module.
Configuration Check for Active and Standby
The Configuration Check for Active and Standby feature (CSCsq83084) checks the configurations on the active and the standby systems. If they are not the same, the Cisco PGW 2200 Softswitch raises a minor alarm to remind you.
This functionality is disabled as default. Use a parameter (pom.checkConfigInterval) in XECfgParm.dat to enable this functionality and to determine how often you want to check the configuration.
If you do not enable pom.checkConfigInterval, the Cisco PGW 2200 Softswitch does not enable this functionality. To check the configuration every 30 minutes, manually add a new line, for example:
"pom.checkConfigInterval = 1800 "in XECfgParm.datThe time unit is in seconds. If you set a checkConfigInterval less than 30 minutes, the Cisco PGW 2200 Softswitch sets this value to 30 minutes automatically.
The newly added alarm in alarmCats.dat is:
460 "Peer Config Mismatched" 1 Y "Configurations on Active and Standby not exactly the same" "Peer Config Mismatched" 3Digit Buffering for International Gateways
The Digit Buffering for International Gateways feature (CSCsa60885) adds a sigPath property (TBufferDigitLength) that allows you to limit the digit length of the called party number (B-number) in the outgoing ISUP IAM and SAM(s). If the number of digits in the next SAM is also greater than the limit, the number of digits in the SAM is limited again, until all digits are passed in SAM(s). This is required for proper interconnection to certain international networks.
This feature provides the following:
•
Ability to limit the called party number in the ISUP IAM and SAM message
•
Option for direct connection between the Cisco PGW 2200 Softswitch and certain international networks
The TBufferDigitLength property works with the following:
•
Built-in digit length limit of the terminating protocol—Maximum number of digits allowed in the outgoing IAM and SAM(s) is determined by the TBufferDigitLength and the build in protocol limitation, whichever is less.
•
OD32DigitSupport (sigPath property)—Setting OD32DigitSupport to 1, sets the built-in digit length limit to 32 digits.
•
TOverlap (sigPath property)—Setting TOverlap to 0, causes extra digits cut from the IAM to be discarded. A SAM is not allowed on the terminating side.
•
TMaxDigits (sigPath property)—TMaxDigits ensures the total number of digit in the IAM and SAM messages does not exceed the provisioned value.
Note
For more information, see the Digit Buffering for International Gateways feature module.
DPNSS Service Interworking with Cisco CallManager Using QSIG Tunneling
The DPNSS Service Interworking with Cisco CallManager Using QSIG Tunneling feature (CSCsb25089) enables full end-to-end route optimization for mixed Cisco Call Manager (CCM) and DPNSS PBX networks. In addition, numerous other services, such as call completion, call transfer, call diversion, and caller id can be inter-worked between CCM and DPNSS/QSIG networks. This feature allows the Cisco PGW 2200 Softswitch to interwork QSIG and DPNSS PBXs and provides an extensive set of feature support. Tunneled QSIG features can be interworked with both DPNSS and backhauled QSIG.
Note
For more information, see the DPNSS Service Interworking with Cisco CallManager Using QSIG Tunneling feature module.
Enhanced Local Number Portability and Dial Plan Selection
The Enhanced Local Number Portability and Dial Plan Selection feature (CSCsg38811) extends the table look up capability to provide searches with longest match and partial (substring) matches for the Ported number and A number dial plan selection tables.
The following are the benefits of this feature:
•
Makes the Times-ten database reading more flexible to support partial matching and longest matching in addition to exact matching.
•
Enhances the Local Number Portability (LNP) call processing to better deal with overlap receiving/sending using variable number lengths to minimize call set up delays.
•
Ensures that database sizes are sufficiently large to meet user needs now and for the future.
•
Ensures that database bulk loading is efficient.
Note
For more information, see the Enhanced Local Number Portability and Dial Plan Selection feature module.
FCI and TMR Provisioning
The FCI and TMR Provisioning feature (CSCee00580) adds the capability to set a default for the ISUP Forward Call Indicators (FCI) field and the ISUP Transmission Media Requirement (TMR) field. This enhancement enables new SIP sigpath properties used to control the mapping rule between ISUP-CLI and SIP headers. The new properties are shown in Table 5.
Flexible Cause Handling
The Flexible Cause Handling feature (CSCsr67508) changes the way that the Cisco PGW 2200 Softswitch handles cause analysis. When the external release is received, the cause is saved off separately, ready for any ultimate release following the exhaustion of all existing trunk groups. A new internal cause value 222 (IC_NO_TRKGRP_AVAILABLE) allows the following behavior: when the Cisco PGW 2200 Softswitch exhausts all Trunk Groups, this cause value is presented internally to cause analysis. This behavior allows a last chance routing if this cause value is configured in the cause table. If that final attempt finds no routing and the call is to be released, the cause originally received and saved from the terminating line side is used. In this way, you have the benefit of the original functionality enabling a last chance in cause analysis. This method complies with other requirements for maintaining and returning the received cause value when clearing the call.
Provision this feature if the call is rejected by the terminating side and Reattempt or Trunk group Advance is invoked to try all the available trunk groups in turn. When all the trunk groups are exhausted, use this cause value to run cause analysis and take desired actions, for example, to modify B number and select an alternative route or to change to a new dial plan.
To provision this feature, start a new provisioning session and add a new cause analysis. For example:
numan-add:cause:custgrpid="1111",causevalue=222,setname="rsetPeerPGW"This produces two results in result set rsetPeerPGW:
mml> numan-rtrv:resultset:custgrpid="1111",name="rsetPeerPGW"Full Number Translations
The Full Number Translations feature (CSCeg33917) provides a large-scale, number translation function on the Cisco PGW 2200 Softswitch. This feature enhances the current Cisco PGW 2200 Softswitch database query mode, which is used for local number portability (LNP) and calling line identification (CLI) screening, by handling contiguous ranges of numbers with analysis and modification capabilities. The Full Number Translations feature supports large-scale changes of individual numbers. This feature adds the NUM_TRANS result type that is implemented in analysis where the existing Times Ten database is used to store the dial plan numbers.
The full number replacement mechanism adds a general number replacement result type, NUM_TRANS, available for A-number and B-number analysis. In addition, a Times Ten query and full number translation table are added.
The purpose of this result is to indicate one of a possible enumerated list of numbers which require full replacement.
Note
For more information, see the Full Number Translations feature module.
Global Title Provisioning
This feature (CSCsa75613) provides support on the Cisco PGW 2200 Softswitch to provision the Signaling System 7 (SS7) global title used for Intelligent Network (IN) operations. With this feature, the Cisco PGW 2200 Softswitch can be provisioned to use an SS7 point code or to use an SS7 global title. Additionally, you can set the point code and subsystem number (SSN) if the point code method is used, or set the global title to use the calling number, called number, or a fixed value if the global title method is used.
This feature provides the following capabilities:
•
Provisioning the SS7 global title used for IN operations.
•
Using an SS7 point code or an SS7 global title.
•
Setting different IN service key, SSN, plus DPC routing method or global title routing for different services.
Note
For more information, see the Global Title Provisioning feature module.
H.248 Protocol
The H.248 Protocol feature provides another gateway control interface (in addition to MGCP) between the Cisco PGW 2200 Softswitch and the VXSM gateways. This interface is based on the ITU-SG16/IETF specification of H.248, which defines a decomposed gateway architecture. This architecture is composed of a media gateway controller (MGC) and the media gateways (MG), with distributed call control functionality between an MGC, an intelligent entity that manages the establishment and tearing down of calls, and an MG—a simple entity that responds to the MGC requests and independently processes media streams.
The Cisco PGW 2200 Softswitch fulfills the MGC functions specified in the H.248 series specification. The Cisco PGW 2200 Softswitch supports only the function of interworking with trunking gateways.
Note
For more information, see the H.248 Protocol feature module.
Increase Dial Plan Size
The Increase Dial Plan Size feature (CSCsb89438) allows the Cisco PGW 2200 Softswitch to increase the index for the dial plan from 16 bits to 32 bits. The new dial plan size limit is 256K digit nodes.
This feature makes changes to MML commands. The digitToPresent is removed from digit tree; therefore, the parameter digitToPresent is removed from NUMAN-ADD: BDIGITTREE and NUMAN-ADD: ADIGITTREE. For the same reason, similar changes are applied to NUMAN-ED and NUMAN_DLT commands.
Lawful Intercept
The Lawful Intercept (LI) feature on the Cisco PGW 2200 Softswitch allows authorized by a LEA (Law Enforcement Agency) personnel to intercept data from targeted calls and send the call data to a LI Mediation Device.
LI on the Cisco PGW 2200 Softswitch works within the architecture of the Cisco Service Independent Intercept (SII). This document describes the high-level architecture of Lawful Intercept in the Cisco PGW 2200 Softswitch based on Packet Cable Electronic Surveillance Specification and Packet Cable Event Message Specification.
Note
For more information, see the Lawful Intercept feature module.
Licensing Features for the Cisco PGW 2200 Softswitch
To manage licenses, Cisco PGW 2200 Softswitch provides license files that are stored in a directory where Cisco PGW 2200 Softswitch obtains the required license information. The Cisco PGW 2200 Softswitch uses the license file to enforce the capacity and features available. Each feature line of the license file is encrypted. Licensing also applies to HSI and BAMS components.
The Cisco PGW 2200 Softswitch requires a unique license file during the execution of the software. This license file allows the software to be loaded and run on a specified set of active and standby servers.
The Cisco PGW 2200 Softswitch tracks the number of ports that are configured in your Cisco PGW 2200 Softswitch node (one active and standby pair) and compares this to the number of Right To Use (RTU) licenses that you purchased. All port licenses are in time division multiplexing (TDM) (DS0) or call leg units. A licensing check is done at run-time.
The Cisco PGW 2200 Softswitch uses the FLEXlm license server from Macrovision Corporation as the license server for all components. To use Cisco PGW 2200 Softswitch software Release 9.7(3) and later, you must install a license server.
Note
For more information, see the Licensing Features for PGW 2200 feature module.
Live Upgrade from 9.6 Sparc to 9.7 Sparc and Opteron
The Live Upgrade From 9.6 Sparc to 9.7 Sparc and Opteron feature (CSCso49604) allows you to upgrade from Cisco PGW 2200 Softswitch Release 9.6 of the Sparc platform to Release 9.7 and later releases. The target platforms apply to Opteron as well as to Sparc. The normal upgrade and patching procedures since 9.7 are same as before and not broken by this feature. For more information, see Cisco PGW 2200 Softswitch Release 9.7 Software Installation and Configuration Guide at:
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/installation/software/SW1/97.html
Loose Routing Support
The Loose Routing Support feature (CSCsd83313) supports the SIP loose routing functionality as it is defined in RFC 3261, SIP: Session Initiation Protocol.
Previously, Cisco PGW 2200 Softswitch used strict routing as defined in RFC 2543, which is superseded by the loose routing mechanism defined in RFC 3261. The main difference between those two routing methods is that strict routing overwrites the request-line to indicate the next hop server address to forward the request; whereas, the request-line remains the same throughout the call routing in loose-routing (typically representing the final destination). This situation is true as long as the proxy handling the request is not responsible for the domain specified in the request-line.
The Loose Routing feature provides the following:
•
Ability to define the routing mode of the Cisco PGW 2200 Softswitch, strict or loose router (new property sipRoutingMode)
•
Flexible property control of ingress routing (new property sipIngressRoutingControl)
•
Flexible property control of egress routing (new property sipEgressRoutingControl)
•
Improved call matching based on To: From: tags
•
Additional CDR records—SIP Routing URI Source (Tag 4247), SIP Routing URI (Tag 4248)
•
Loose Routing that is fully backward compatible with strict routing applications
Mini-Parse Analyzing Tool
The Mini-Parse Analyzing Tool feature (CSCsk32769) supplies a tracing tool (mini_parse.pl) that can provide a detailed analysis of call flows.
Mini-parse provides a simple flow diagram of events that are contained in an MDL trace file (.trc).
Usage: mini_parse.pl [-d] [-b] [-i] [-m] [-s] <tracefile>
•
-d—adds additional message decode
•
-b—adds additional B Number analysis info
•
-m—print messages only (no internal signals)
•
-i—adds additional IN info
•
-s—adds state transitions
The output can be redirected to a file.
Multiple Incoming IP Trunks
The Multiple Incoming IP Trunks feature (CSCsj52735) allows multiple incoming trunkgroups to be configured under the SIP path and EISUP path. SIP trunkgroups can be differentiated by a combination of the source SIP proxy IP and Cisco PGW 2200 Softswitch listening port number. EISUP incoming trunkgroups can be differentiated by the H323SourceAddress retrieved from EISUP IAM message. Each trunkgroup can be provisioned separately with properties. When the Cisco PGW 2200 Softswitch is deployed under a multivendor environment and there are differences in these vendor SIP/EISUP implementations, Cisco PGW 2200 Softswitch can be provisioned with multiple incoming trunkgroups with different properties for different SIP/EISUP implementations.
CautionBecause the Multiple Incoming IP Trunks feature (included in Patches CSCOgs013 and CSCOnn013) modifies Cisco PGW 2200 Softswitch provisioning tables, we strongly recommend that you back up the current configuration before you upgrade and apply the back up configuration if the upgrade fails. Any configuration based on S13P13 is not backwards compatible.
This recommendation also applies if you upgrade to a patch later than S13P13 from a patch earlier than S13P13.
The Multiple Incoming IP Trunks feature modifies a CDR (Originating Trunk Group), Tag 4008, as described in Cisco PGW 2200 Softswitch Release 9 Billing Interface Guide.
A new SP-Group measurement (SP: IPIN REJ TOT) described in Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Provisioning Multiple Incoming IP Trunks Feature
A new sigpath property, IPINMAPPING, lets you assign specific trunk group attributes to different inbound sip calls. The following prov-add:ipinmapping command lets you add up to 10,000 entries to the IP Trunk Group selector table:
•
Configuration can be IP only or sipport only.
•
Sipport online help displays sipports configured in a previous siplnk.
•
If allowedNetmask is empty, Cisco PGW 2200 Softswitch treats it as default netmask 255.255.255.255. Or, you can configure netmask to filter an IP address. If (incoming msg's source IP & allowedNetmask)=(allowedIP & allowedNetmask), this IP is allowed. If there are several ipinmapping entries qualified, the longest match rule is applied.
•
Name of ipinmapping is the primary key to identify an ipinmapping entry.
•
New data file, ipinmapping.dat, records what is configured in ipinmapping.
prov-add:ipinmapping:
name—MML Name
desc—Description
sigsvc—SIP sigpath or EISUP sigpath
allowedIP—Allowed IP Address
allowedIPNetMask—Allowed Net Mask
sipport—Allowed SIP Port, only effective for SIP sigpath
trnkgrpnum—Trunk Group Number (display trnkgrps belong to this sigsvc)
prov-ed:ipinmapping:name="###"
prov-dlt:ipinmapping:name="###"
prov-add:sigsvcprop:ipinscreening
prov-ed:sigsvcprop:ipinscreening
•
Indication of whether the screening takes effect if no trnkgrp is found. Value range:
–
0—no screening
–
1—screening, discard if no trnkgrp found
–
2—screening, process with default if no trnkgrp found
•
Ipinscreening sigsvcprop is only effective on the SIP/EISUP sigpath.
•
Default value of ipinscreening sigsvcprop is 0.
•
Ipinscreening=0 stands for ipinmapping function disabled.
–
If sip sigsvcprop ipinscreening=0, you must specify a default SIP_IN trnkgrp for this sip sigpath, this default SIP_IN trnkgrp is treated as this sip sigpath's default incoming trnkgrp.
–
If eisup sigsvcprop ipinscreening=0, you can specify a default trnkgrp for this eisup sigpath. If you leave it empty, the eisup trnkgrp with trnkgrpprop btechprefix=NULL is treated as the default incoming trnkgrp of the eisup sigpath.
•
Ipinscreening=1 stands for ipinmapping function enabled.
–
If sigsvcprop ipinscreening=1, you can specify default trnkgrp for this sigpath (SIP/EISUP) or leave it empty, the default trnkgrp is not mandatory.
–
If sigsvcProp ipinscreening=1, if no ipinmapping matched, a new call message is dropped.
•
Ipinscreening=2 stands for ipinampping function enabled.
–
If sip sigsvcprop ipinscreening=2, you must specify a default SIP_IN trnkgrp for this sip sigpath, this default SIP_IN trnkgrp is treated as the default incoming trnkgrp of the sip path.
–
If eisup sigsvcprop ipinscreening=2, you can specify a default trnkgrp for this eisup sigpath. If you leave it empty, the eisup trnkgrp with trnkgrpprop btechprefix=NULL is treated as the default incoming trnkgrp of the eisup sigpath.
–
If sigsvcProp ipinscreening=2, if no ipinmapping entry is matched, a new call message is processed with the default incoming trnkgrp of the incoming sigpath.
Batch file capabilities are provided for populating the Trunk Group Selector table.
Provisioning Example 1
prov-ed:sigsvcprop:ipscreening=2Prov-add:siplnk:name="siplnk1",svc="sippath-1",ipaddr="IP_ADDR1",port=5060Prov-ed:siplnk:name="siplnk1",port=5063Prov-ed:siplnk:name="siplnk1",port-5065Prov-dlt:siplnk:name="siplnk1",port-5065Prov-ed:siplnk:name="siplnk1",port-5064Prov-add:trnkgrp:name="1000",svc="sippath-1",type=SIP_INProv-add:trnkgrp:name="1010",svc="sippath-1",type=SIP_INProv-add:trnkgrp:name="1020",svc="sippath-1",type=SIP_INProv-add:trnkgrp:name="1030",svc="sippath-1",type=SIP_IN,defaut=1Prov-add:trnkgrp:name="1040",svc="sippath-1",type=SIP_INProv-add:ipinmapping:name="sipinmapping-1",sigsvc="sippath-1",allowedIP="10.0.14.145", sipport=5063,trnkgrpNum=1000Prov-add:ipinmapping:name="sipinmapping-2",sigsvc="sippath-1",allowedIP="10.0.14.145", allowedIPNetmask="255.255.255.128",trnkgrpNum=1040Prov-add:sipinmapping:name="sipinmapping-3",sigsvc="sippath-1",sipport=5064, trnkgrpNum=1010Prov-add:sipinmapping:name="sipinmapping-4",sigsvc="sippath-1",allowedIP="10.0.14.145", trnkgrpNum=1020The following sip INVITE messages are received:
sip INVITE (srcaddr=10.0.14.145,dstport=5063) select trnkgrp 1000sip INVITE (srcaddr=10.0.14.187,dstport=5064) select trnkgrp 1040sip INVITE (srcaddr=10.0.14.87,dstport=5064) select trnkgrp 1010sip INVITE (srcaddr=10.0.14.145,dstport=5064) select trnkgrp 1020sip INVITE (srcaddr=10.0.24.176,dstport=5063) select default trnkgrp 1030Because sigsvc "sippath-1" ipinscreening=2, the default trunkgroup is selected (although no ipinmapping entry matches).
For SIP incoming trunkgroups mapping, the mapping rule priorities are: IP+Port > IP only > Port only. That is, if IP+Port mapping fails, IP only mapping is tried. If IP only mapping fails, Port only mapping is tried. If the trunkgroup mapping fails again, the mapping sequence continues until an entry is found.
Example 2
prov-ed:sigsvcprop:ipscreening=1Prov-add:trnkgrp:name="2000",svc="eisuppath-1",type=IPProv-add:trnkgrp:name="2010",svc="eisuppath-1",type=IP,default=1Prov-add:ipinmapping:name="eisupinmapping-1",sigsvc="eisuppath-1",allowedIP="10.0.14.145", trnkgrpNum=2000The following eisup IAM message is received:
Eisup IAM (H323 source address = 10.0.14.145)trnkgrp 2000 is selected
Eisup IAM (H323 source address = 10.0.14.187)Cisco PGW 2200 Softswitch can not find a trunkgroup; although, there is a default trunkgroup, eisup.screenging=1. This IAM is discarded.
Per Call Trace Enhancement
The Per Call Trace Enhancement feature (CSCea78597) implements some enhanced functions based on the original per call trace, including collecting per call trace on calling and called party number, adding MCL setting, capturing long duration calls, collecting call trace on cause value, and fixing per call trace on a particular sigPath/Span/cic (or trunkgroup/trunk) combinations.
To implement this feature, there is a new XECfgParm parameter, CallNumberToWriteIntoTracefile, that limits the call number to write into a trace file while stopping a long duration call trace.
The start trace (sta-sc-trc) MML command is modified to perform the following:
In the active node:
mml>sta-sc-trc:<sigpath>:[span=x[,rng=y]][,tc=z[,rng=w]][,anubmer=="callingparty number"] [,bnumber="calledpartynumber"][,causevalue=c][,incompleteoverlapnumber] [,duration=d][,mcl=m] [,autostop][,prd=n][,log="log"],confirmmml>sta-sc-trc:<trunkgroup>:[trk=x[,rng==]][,anubmer="callingpartynumber"] [,bnumber="called partynumber"][,causevalue=c][,incompleteoverlapnumber] [,duration=d][,mcl=m] [,autostop][,prd=n][,log="log"],confirmIn the standby node:
mml>sta-sc-trc:<sigpath>:[span=x[,rng=y]][,tc=z[,rng=w]][,mcl=m][,prd=n][,log="log"], confirmmml>sta-sc-trc:<trunkgroup>:[trk=x[,rng=y]][,mcl=m][,prd=n][,log="log"],confirmPGW-ITP Optimize Routing with MAP Query
The PGW-ITP Optimize Routing with MAP Query feature (CSCsi10115) allows the Cisco PGW 2200 Softswitch to optimize routing based on a subscriber location within a mobile network.
A new property, ItpActionRequest, indicates that the Cisco PGW 2200 Softswitch should send a customized SIP invite to the ITP to return the location of a mobile subscriber. Setting this property to map-app indicates that the Cisco PGW 2200 Softswitch should send a customized SIP invite to the ITP to return the location of a mobile subscriber. The customized SIP invite causes the ITP to send a MAP query to the service provider HLR for the current mobile station roaming number (MSRN) of the mobile subscriber. The Cisco PGW 2200 Softswitch then routes the call to the closest Gateway MSC based upon the new MSRN.
If the Cisco PGW 2200 Softswitch is unable to optimize the call routing based on the MSRN, it continues to route calls based on using MSISDN (telephone number) of the mobile subscriber. The Cisco PGW 2200 Softswitch routes calls based on an MSISDN using cause analysis.
The new property, ItpActionRequest, is shown in Table 6.
Provisioning example:
Prov-ed:trnkgrpprop:name="xxx",ItpActionRequest="map-app"Prov-dlt:trnkgrpprop:name="xxx","ItpActionRequest"PGW Support for HSI Non-RAS Mode
The PGW Support for HSI Non-RAS Mode feature (CSCeb55640) enables service providers to create a simplified network without a gatekeeper for networks that do not require gatekeeper features such as security.
In Non-RAS mode, the Cisco PGW 2200 Softswitch converts called numbers into one or more IP address in the dial plan to support load sharing over multiple HSIs. This mechanism supports H.323 endpoints that have multiple IP addresses. With such support, when an initial IP address does not work, attempts are made to use the alternative IP addresses for the same endpoint.
If the Cisco PGW 2200 Softswitch sends an IP address to the HSI over E-ISUP, the HSI sends a SETUP directly to the endpoint. In addition, the Cisco PGW 2200 Softswitch stores the H.323 destination IP address in the Call Detail Record (CDR).
Cisco PGW 2200 Softswitch Support of Non-RAS mode enables deployment of a Cisco PGW 2200 Softswitch with a connected Cisco HSI without a gatekeeper in networks that do not require admission or location of the H.323 endpoint, or when selection of the endpoint does not benefit from H.323 mechanisms such as Resource Availability Indication (RAI). Examples of such deployments can include Cisco CallManager (CCM) or H.323 ITS. In some cases, an H.323 gateway provides the only connection to a PBX.
Note
A single Cisco H.323 Signaling Interface (HSI) cannot operate in both Registration, Admission and Status (RAS) and Non-RAS modes. If a network requires both modes of operation, the network must have multiple Cisco HSIs.
The new CDR tag is shown in Table 7.
Note
This tag is available only when the call uses the non-RAS feature.
Note
For more information, see the PGW Support for HSI Non-RAS Mode feature module.
PGW TCP Transport for SIP Phase I
The PGW TCP Transport for SIP Phase I feature (CSCsh66146) allows the Cisco PGW 2200 Softswitch to configure TCP or UDP as the default transport for both send and receive directions. UDP is the default.
UDP to TCP Migration
If you are a SIP-over-UDP-based user and want to migrate to SIP over TCP, use the following steps:
Step 1
Stop the standby Cisco PGW 2200 Softswitch node.
Step 2
Change the XECfgParam.dat to TCP.
Step 3
Start the standby Cisco PGW 2200 Softswitch node.
Step 4
Switchover the Cisco PGW 2200 Softswitch node.
Step 5
Stop the current standby Cisco PGW 2200 Softswitch node.
Step 6
Change the XECfgParam.dat to TCP.
Step 7
Start the current standby Cisco PGW 2200 Softswitch node.
After the preceding steps, the Cisco PGW 2200 Softswitch uses UDP as a transport for old calls, and only handles new SIP calls over TCP. The Cisco PGW 2200 Softswitch always creates both a UPD and a TCP socket. The Cisco PGW 2200 Softswitch rejects the new call over an un-configured transport. Cisco PGW 2200 Softswitch needs to handle the middle call request and response over an un-configured transport, because old calls still use UDP as transport. For the middle call request, Cisco PGW 2200 Softswitch should reject REFER to PGW over un-configured transport because REFER might cause UDP/TCP interworking issues in this migration case.
In summary, the Cisco PGW 2200 Softswitch supports UDP to TCP migration with the limitation that REFER is not supported on old active calls after migration. TCP to UDP migration is also supported, but, after migration, the Cisco PGW 2200 Softswitch does not reject a REFER message, so the Cisco PGW 2200 Softswitch uses the new transport protocol (TCP) to create a new call leg. The result is that the incoming call leg uses UDP but the outgoing call leg uses TCP. Retransmission is a problem, but the call can release correctly.
The Cisco PGW 2200 Softswitch uses the IP address IP_Addr1 and port 5060 to start both the TCP and UDP listener socket.
•
TCP and UDP must use the same IP and Port.
•
In IOCM, the TCP and UDP SIP Link use the same state machine. When the Cisco PGW 2200 Softswitch sets the SIP link to IS or OOS, both TCP and UDP are set to IS or OOS.
No Support for UDP/TCP Mixed Network
The Cisco PGW 2200 Softswitch supports UDP only and TCP only as a system global configuration. If the Cisco PGW 2200 Softswitch is configured as UDP only, it handles a new SIP call only over UDP. If the Cisco PGW 2200 Softswitch is configured as TCP only, it handles a new SIP call only over TCP.
To support UDP/TCP migration, the Cisco PGW 2200 Softswitch creates both a TCP and a UDP socket in either mode. For more information, see the "UDP to TCP Migration" section.
The Cisco PGW 2200 Softswitch populates a configured transport-to-transport parameter of Request-URI/RecordRoute/Route/Contact/VIA/ReferTo headers, but it does not use the transport parameter from others because the Cisco PGW 2200 Softswitch always uses the transport configuration. If the Cisco PGW 2200 Softswitch is configured as TCP only, and RecordRoute from next hop is UDP, the Cisco PGW 2200 Softswitch still sends a subsequence SIP request to next hop over TCP. If the Cisco PGW 2200 Softswitch is configured as UDP only and RecordRoute from next hop is TCP, it still sends a subsequence SIP request to next hop over UDP.
XECfgParm.dat Parameter
The XECfgParm.dat file configuration parameters added to this feature are in Table 8. For information on the other XECfgParm.dat parameters, see Cisco PGW 2200 Softswitch Release 9.7 Software Installation and Configuration Guide at:
http://www.cisco.com/en/US/products/hw/vcallcon/ps2027/tsd_products_support_series_home.html
POM File Service Enhancement
The POM File Service Enhancement feature (CSCsi54885) improves the prov-dply/prov-sync performance to allow Cisco PGW 2200 Softswitch to support thousands of dial plans without impacting existing functions.
Pre Call Announcement After Address Complete Message
The Pre Call Announcement After Address Complete Message feature (CSCsb56721) provides support for pre-call announcements that are played directly after the Address Complete Message (ACM) is received by the Cisco PGW 2200 Softswitch or an equivalent message such as Alerting is received over outgoing protocols such as H.323 or SIP. Pre-call announcement is used to play a short announcement to inform the calling party of the cost per minute for a call.
Note
This feature supports TDM-to-IP calls and TDM-to-TDM hairpinned calls. The announcement is supported only on the TDM side of an IOS gateway.
Note
When this announcement is played after receiving the receipt of an ACM, the called party might answer during the announcement, causing the calling party to miss the initial speech.
The existing sigpath property, *.AnnSuppressInbandInfo, has been given a more generic name, *.LocalAnnBehavior, to reflect the three options associated with it.
Valid values are:
•
0 (default)—Play announcement after all digits have been received. An early ACM is sent before the announcement is played to indicate "inband information available." The call is routed after the announcement is played.
When using this option, the Cisco PGW 2200 Softswitch might force an enbloc, which can result in an unacceptable post-dial delay.
•
1—Play announcement after enough digits have been received to determine a route. Early ACM is not sent before playing the announcement (it is assumed that the voicepath is already cut back after IAM). The call is routed after the announcement is played.
When overlap sending is also used, depending on the number dialed, some users might receive the pre-call announcement while the final digits are being dialed.
•
2—Route the call after enough digits have been received to determine a route. Play the announcement after an address complete indication (ACM) is received from the terminating side. This method is introduced in this feature.
Presentation Number Modification
The Presentation Number Modification feature lets the Cisco PGW 2200 Softswitch modify the presentation number (PN) for calls between a PSTN network on one side and a SIP server on the other. The requirement is to modify PN prefixes. Before the introduction of this feature, the Cisco PGW 2200 Softswitch could modify a calling party number (A-number). The Cisco PGW 2200 Softswitch also could modify a PN, but only if an A-number was present. This feature enables the Cisco PGW 2200 Softswitch to modify a PN when no A-number is present.
Note
For more information, see the Presentation Number Modification feature module.
RADIUS Enhancement for Accounting
The RADIUS Enhancement for Accounting feature (CSCse18042) provides radius interface support on the Cisco PGW 2200 Softswitch for Call Detail Record (CDR) data. CDR data is sent to a preconfigured radius server at the end of the call. CDR data for PSTN to IP calls as well as IP to PSTN calls is supported.
Note
For more information, see the RADIUS Enhancement for Accounting feature module.
Redirect Server
The Redirect Server feature (CSCsk41224) allows the Cisco PGW 2200 Softswitch to act as a redirect server. For DPNSS, this is very useful because it allows for a gradual migration from traditional PBXs to IP telephony. The Cisco PGW 2200 Softswitch can be configured with the migrated phone numbers. Numbers that are not migrated can cause a divert, which essentially means that two circuits are not tied up for the duration of the call.
The Redirect Server feature adds a new result type (REDIRECT), modifies two CDRs (SERVICE USAGE DATA, Tag 4239 and REDIRECTION NUMBER, Tag 4065), and adds a new measurement (CALL: SuccRedirected). These new elements are described in the following documents:
•
Cisco PGW 2200 Softswitch Release 9 Dial Plan Guide (through Release 9.7)
•
Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide
•
Cisco PGW 2200 Softswitch Release 9 MML Command Reference.
Note
The Redirect Server feature is enabled for DPNSS only. It does not work for SIP.
Provisioning Examples
Add a service:
numan-add:service:custgrpid="1111",name="redirection"Add a full translation number in the timesten table:
numan-add:fullnumbertrans:svcname="redirection",numtype="1",digstring="611111", translatednum="11111"Add the REDIRECT result type in a to-be-matched A/B number digit string:
numan-add:resultset:custgrpid="1111",name="set1111"numan-add:resulttable: custgrpid="1111",setname="set1111",resulttype="REDIRECT", dw1="redirection;numan-add:bdigtree:custgrpid="1111",callside="originating",digitstring="6", setname="set1111"Ring Back Service Using CPC=3 for Voice Messaging
The Ring Back Service Using CPC=3 for Voice Messaging feature (CSCsi40004) adds the capability to modify the called party category (CPC) value to 3 on the backward call indicators (BCI) parameter in the address complete message (ACM) message for ring back service to support voice messaging services in Mexico.
•
Mexican Q.767 ISUP variant supports called party CPC value 3, but modified called party CPC parameter is applicable to all ISUP variants, including Q.767, Q.761, and ANSI SS7.
•
Both signaling mode and call control mode use dial plan number analysis as the called party CPC modification trigger.
•
The existing result type CPCMOD is reused to implement this feature.
•
For consistency, called party CPC is available in both A-number and B-number analysis.
Result Type Definitions
The result types listed in Table 9 support the validation of dw2 in the result type CPCMOD.
To allow modification to both the calling party CPC and the called party CPC at the same time, Cisco PGW 2200 Softswitch allows a maximum of two CPCMOD results provisioned in one result set.
For information on other result type definitions for the Cisco PGW 2200 Softswitch, see Cisco PGW 2200 Softswitch Release 9 Dial Plan Guide (through Release 9.7).
Provisioning Examples
The following are MML command examples for CPCMOD result type.
•
Change the calling party category parameter to PAYPHONE in the outgoing IAM message. Use the DW2 default value:
NUMAN-ADD:RESULTTABLE:CUSTGRPID="T002",NAME="result45",RESULTTYPE="CPCMOD", SETNAME="cpcset1",DW1="15"•
Change the calling party category parameter to PAYPHONE in the outgoing IAM message. Explicitly set DW2:
NUMAN-ADD:RESULTTABLE:CUSTGRPID="T002",NAME="result45",RESULTTYPE="CPCMOD", SETNAME="cpcset1",DW1="15",DW2="0"•
Change the called party category parameter to 3 in the backward ACM message. To modify the called party category, set DW2 to 1:
NUMAN-ADD:RESULTTABLE:CUSTGRPID="T002",NAME="result32",RESULTTYPE="CPCMOD", SETNAME="cpcset2",DW1="3",DW2="1"Sequential Network Consultation Transfer
The Sequential Network Consultation Transfer feature (CSCsj08981) enables the Cisco PGW 2200 Softswitch to perform sequential network consultation transfer (NCT) calls. That is, the Cisco PGW 2200 Softswitch can perform another NCT after the first NCT is completed. With this new feature introduced, to invoke a second NCT, call agents do not have to invoke a network blind transfer (NBT) or an intelligent take back and transfer (iTNT) before the second NCT. Call agents can start a second NCT right after the first NCT is completed.
The sequential NCT feature is an enhancement to the previous feature, SIP Support of Take Back and Transfer in the Cisco Unified Contact Center.
Note
For more information, see the Sequential Network Consultation Transfer feature module.
SIP and ISUP Interworking for Call Hold and Terminal Portability
The SIP and ISUP Interworking for Call Hold and Terminal Portability feature (CSCsb56422) supports the message mapping between SIP and ISUP for call hold and terminal portability on the Cisco PGW 2200 Softswitch. The implementation is based on Q.1912.5 Annex B.10 for Call Hold and Annex B.13 for Terminal Portability (TP). Q.1912.5 defines signaling interworking between SIP and ISUP.
The Cisco PGW 2200 Softswitch also supports ISUP and SIP/HSI interworking for Call hold and TP across EISUP (intra PGW). The following scenario is supported: ISUP -> PGW1 -> PGW2 -> SIP/HSI. Either ISUP invoking call hold or SIP/HSI invoking call hold is supported.
Note
For more information, see the SIP and ISUP Interworking for Call Hold and Terminal Portability feature module.
SIP Configurable Retransmissions
The SIP Configurable Retransmissions feature (CSCsc37919) supports the capability to configure SIP Retransmissions handling. The new properties introduced with this feature are used to configure the number or retries and the time intervals between retries as linear (new) or exponential (current standards-based method). In addition, the SIP Timer C is also made configurable.
If the Cisco PGW 2200 Softswitch works as a proxy, for example, the call is from sip to sip, the properties InviteRetries and NonInviteReqRetries are disabled.
This feature changes the switch-time behavior of the Support of DNS SRV and SIP Load-Sharing feature (introduced in Release 9.6(1)). The Cisco PGW 2200 Softswitch does not support more than two DNS proxy servers because the SIP Configurable Retransmissions feature modifies the switch time behavior to support only two DNS proxy servers.
The new properties are shown in Table 10.
SIP Early-Dialog Offer/Answer Using PRACK/180/183
The SIP Early-Dialog Offer/Answer Using PRACK/180/183 feature (CSCso02350) supplies a new SDP offer/answer capability that can support SDP negotiation using PRACK/180/183 in SIP early dialog as in RFC3261/3262. Normally this feature is used in H323/SIP -> SIP call.
CautionWhen H323 calls SIP in fast start mode and the terminal SIP uses the 100rel response, and the originator (H323) and terminal (SIP) have different CODECs, the call fails or has no voice path (CSCso86755). The workaround is to have the same CODEC for both.
This enhancement cannot support the call scenario H323 -> SIP with slow start mode. Change the supportreliable100="UNSUPPORTED" in this case
This recommendation also applies if you upgrade to a patch higher than patch CSCOgs014/CSCOnn014 from a patch earlier than CSCOgs014/CSCOnn014.
Provisioning the SIP Early-Dialog Offer/Answer Using PRACK/180/183 Feature
You must set the trunk group property supportreliable100 to SUPPORTED or MANDATORY. For SIP -> SIP call, use this feature when both the calling and the called party use the 100rel response.
SIP FROM Interworking with SS7 and PRI
The SIP FROM Interworking with SS7 and PRI feature (CSCsg42352) supports the mapping of the SIP FROM header (display name).
The received DISPLAY IE in SETUP message from the NI2+ interface is mapped into UUIE field in the outgoing IAM message. This information is sent out without any modification from the incoming DISPLAY IE.
The receiving of the UUIE with IA5 encoded text in an IAM message is mapped into DISPLAY IE of SETUP message of NI2+. This information is sent out without any modification from the incoming UUIE.
This service is only used in Nailed mode. A new sigpath property, CNAPService, enables this feature on the Cisco PGW 2200 Softswitch.
Table 11 shows the definition for the new sigpath property, CNAPService.
The following provisioning example enables the service:
prov-ed:sigsvcprop:name="isup-path",CNAPService="1"The following provisioning example disables the service. It is the default behavior.
prov-ed:sigsvcprop:name="isup-path",CNAPService="0"SIP Overlap Signaling
The SIP Overlap Signaling feature (CSCso14089) supports SIP overlap signaling between the Cisco PGW 2200 Softswitch and the Cisco BTS 10200 Softswitch products using a derivative of draft-zhang-sipping-overlap-01, a method for overlap signaling in SIP.
Both the Cisco PGW 2200 Softswitch and BTS 10200 support the sending and receiving of overlap dialed digits over SIP. The Cisco PGW 2200 Softswitch also supports the sending/receiving of overlap digits over the SS7 network.
Note
For more information, see the SIP Overlap Signaling feature module.
SIP Service Handling and Feature Interworking Enhancements
The SIP Service Handling and Feature Interworking Enhancements feature (CSCef54992) introduces a Back to Back User Agent (B2BUA) mode of operation for SIP-to-SIP calls using the Cisco PGW 2200 Softswitch. It also enhances the existing mid-call service handling to better interwork SIP signaling for mid-call services. This feature allows Cisco PGW 2200 Softswitch handling of SIP-to-SIP calls, including intrusive replacement of E.164 addresses appearing in various headers and configurable handling of REFER and 3xx redirect messaging. In addition, this feature enhances the Cisco PGW 2200 Softswitch mid-call service handling for interworking of SIP redirection and transfers with SIP to SIP and SIP to other protocols.
Note
For more information, see the SIP Service Handling and Feature Interworking Enhancements feature module.
SIP Support of Take Back and Transfer in the Cisco Unified Contact Center
The SIP Support of Take Back and Transfer in the Cisco Unified Contact Center feature (CSCsh65871) enhances the Take Back and Transfer (Phase 2) feature. The new feature provides the capability to support the SIP trunks as the calling party or the transferring party for different call transfers.
With this new feature, the Cisco PGW 2200 Softswitch supports the following take back and transfer functions:
•
Basic Take Back and Transfer on SIP Trunks
•
DTMF Blind Transfer Under INAP Control on SIP Trunks
•
Network Blind Transfer Under INAP Control on SIP Trunks
•
Network Consultation Transfer Under INAP Control on SIP Trunks
Note
For more information, see the SIP Support of Take Back and Transfer in the Cisco Unified Contact Center feature module.
SS7 Take Back and Transfer RELEASE Message Parameter Modifications
The SS7 Take Back and Transfer RELEASE Message Parameter Modifications feature (CSCsq44014) introduces two new properties, ReferRedirectingNOA and ReferRedirectingInd, that allow you to manipulate the content in REL msg.
•
ReferRedirectingNOA—NOA value of redirection number in ITU SS7 REL message for blind transfer by sip REFER, use internal NOA value.
Value range:
–
1—NOA_NONE
–
2—NOA_UNKNOWN
–
3—NOA_SUBSCRIBER
–
4—NOA_NATIONAL
–
5—NOA_INTERNATIONAL
•
ReferRedirectingInd—Redirecting indicator of Redirection Information in ITU SS7 REL message for blind transfer by sip REFER.
Value range:
–
0—No redirection
–
1—Call rerouted
–
2—Call rerouted, all redirection information presentation restricted
–
3—Call diverted
–
4—Call diverted, all redirection information presentation restricted
–
5—Call rerouted, redirection number presentation restricted
–
6—Call diversion, redirection number presentation restricted
Support for INAP Generic Number
The Support for INAP Generic Number feature (CSCsb56451) supports the Generic Number parameter in the INAP InitialDP and the INAP Connect operations. It enables use of dual CLI functionality in SIP networks.
Support for Individual SIP Cause Values
The Support for Individual SIP Cause Values feature (CSCsf00200) provides one-to-one mapping on the Cisco PGW 2200 Softswitch for SIP cause values mapping to internal values. This mapping allows more flexibility for supporting different user/country requirements.
To fully support this enhancement in a SIP-H323 call scenario, use HSI Release 4.3. Patch 2 or later. The corresponding HSI caveat is CSCsi58113.
Because a new cause table is introduced with this feature, when you install the patch for this feature, you should add the following new cause table elements to old provisioned dial plans. For example:
numan-add:cause:custgrpid="1111",causevalue=217,setname="CSCOADRST2"numan-add:cause:custgrpid="1111",causevalue=218,setname="CSCOADRST2"numan-add:cause:custgrpid="1111",causevalue=177,setname="CSCOADRST1"numan-add:cause:custgrpid="1111",causevalue=197,setname="CSCOADRST1"numan-add:cause:custgrpid="1111",causevalue=206,setname="CSCOADRST1"numan-add:cause:custgrpid="1111",causevalue=208,setname="CSCOADRST1"numan-add:cause:custgrpid="1111",causevalue=213,setname="CSCOADRST1"Support of Location Mapping
The Support of Location Mapping feature (CSCsb65484) on the Cisco PGW 2200 Softswitch provides support for both cause code and location mapping with the ability to modify location values.
The Cisco PGW 2200 Softswitch is currently able to map release cause information into different values by the use of the Cause mapping table, however it cannot map or modify location values that are required by some users.
This feature allows the Cisco PGW 2200 Softswitch the following functionality:
•
Map to different cause and location values based on received cause values and location values (existing)
•
Map to a different cause value based on the received cause value and location values
•
Map cause value to new values without changing location values (existing)
•
Map to a new cause value and location value based on received cause value
•
Override the default location value with a new location value
•
Use the default location value if no Location value is set
•
Map a location value to new values without changing cause values, with the use of wildcard of cause value
Note
For more information, see the Support of Location Mapping feature module.
Support of Provisionable QoS for Signaling Traffic
The Support of Provisionable QoS for Signaling Traffic feature (CSCee21241) allows you to set the appropriate priority for various signaling traffic to be transported between the Cisco PGW 2200 Softswitch and Cisco EGW and other call control entities, like Cisco CallManager, Cisco Unity, SIP servers and Gatekeepers, and Gateways over QoS-enabled IP networks.
Cisco EGW already supports fixed QoS in clustering over the WAN implemented by IPtables packages. Now the QoS is provided by the Cisco PGW 2200 Softswitch; this supports dynamically provisionable QoS for both the Cisco PGW 2200 Softswitch and Cisco EGW.
The QoS feature is supported for use by the Cisco PGW 2200 Softswitch itself. TimesTen would continue to use IPtables packages to get QoS support.
Note
The Clustering Over the WAN feature (for Cisco EGW) and technology is related to this feature.
This feature adds provisionable QoS support with the default value set to DSCP CS3 in accordance with Cisco baseline QoS recommendations for the following:
•
Signaling paths:
–
MGCP
–
EISUP
–
SIP
–
ISDN Backhaul over RUDP
–
DPNSS Backhaul over SCTP
–
BRI Backhaul over TCP
–
ISUP Backhaul over SCTP
–
QBE
–
AXL
–
LI
•
Various checkpointing traffic between Cisco PGW 2200 Softswitch and Cisco EGW
Note
For more information, see the Support of Provisionable QoS for Signaling Traffic feature module.
Support of Trunk Group ID at the x-route-tag or tsp Parameter
The Support of Trunk Group ID at the x-route-tag or tsp Parameter feature (CSCsg49496) enables the support of ingress trunk group tag id at the SIP x-route-tag or tsp parameter of the SIP via header. Table 12 shows the new trunk group properties.
Ingress Trunk Group Property
The TrunkGroupTagLabel property can be configured in any ingress trunk group, including SIP, EISUP, SS7, PRI, DPNSS and QSIG. Because this property is a common property for all kinds of ingress trunk groups, it can be retrieved and written to CC in LCM module when the TCC is determined to be either SIP or EISUP to another Cisco PGW 2200 Softswitch. A provisioning example of this property is:
Prov-ed:trnkgrpprop:name="9000",custgrpid="DP00",trunkgrouptaglabel="westarea_trunkgroup1"Egress Trunk Group Property for SIP
An egress trunk group property TrunkGrpTagLabelTransEnable of type integer is added for SIP trunk group to decide whether and how to transmit trunk group tag label in the outgoing INVITE message. This trunk group property is only applicable for SIP trunk group when it acts as an egress trunk group. A provisioning example of this property is:
prov-ed:trnkgrpprop:name="9000",custgrpid="DP00",MGCdomain="10.0.57.90", TrunkGrpTagLabelTransEnable="1"Support of VXSM M3UA Signaling
The Support of VXSM M3UA Signaling feature (CSCsl70032) adds the M3UA protocol for the VXSM entry in extNodeTypes.dat. The combination of M3UA and MGCP/H248 is supported on the VXSM/MGX8880 from the Cisco PGW 2200 Softswitch side.
Note
Because SS7 and MGCP/H.248 are backhauled to the same single VXSM card, provision only one external node for both SS7 service and MGCP (or H.248).
Before this feature, the Cisco PGW 2200 Softswitch allowed the VXSM to be defined as an External Node (with EXTNODE TYPE = VXSM), but it refused to define that same VXSM as an M3UA, SUA, or IUA signaling gateway.
The following is a provisioning example for this feature:
prov-add:OPC:NAME="opc1",DESC="sh-plum",NETADDR="2.2.2",NETIND=2,TYPE="TRUEOPC"prov-add:DPC:NAME="dpc1",DESC="inet3",NETADDR="1.1.1",NETIND=2prov-add:EXTNODE:NAME="mgx-8850-1",DESC="MGX8800-VXSM1",TYPE="VXSM",ISDNSIGTYPE="N/A", GROUP=1prov-add:EXTNODE:NAME="mgx-8850-2",DESC="MGX8800-VXSM2",TYPE="VXSM",ISDNSIGTYPE="N/A", GROUP=1; MEGACO LEG to 1st VXSM cardprov-add:H248PATH:NAME="h248sctp-vxsm1",DESC="Service to vxsm1(H248sctp)", EXTNODE="mgx-8850-1"prov-add:ASSOCIATION:NAME="h248-assoc-1",DESC="service to vxsm1(h248sctp)", EXTNODE="mgx-8850-1",SGP="N/A",TYPE="H248",IPADDR1="IP_Addr1",IPADDR2="N/A",PORT=2970, PEERADDR1="10.0.78.2",PEERADDR2="0.0.0.0",PEERPORT=2970,IPROUTE1="",IPROUTE2="", RCVWIN=18000,MAXINITRETRANS=10,MAXINITRTO=2000,MAXRETRANS=5,CUMSACKTO=300,BUNDLETO=100, MINRTO=300,MAXRTO=3000,HBTO=2000,IPPRECEDENCE="ROUTINE",DSCP="N/A",MAXRETRANSDEST=3; MGCP LEG to 2nd VXSM cardprov-add:MGCPPATH:NAME="mgcp-vxsm2",DESC="Service to vxsm2(mgcp)",EXTNODE="mgx-8850-2"prov-add:IPLNK:NAME="mgcp-iplink1",DESC="MGCP link to vxsm2",SVC="mgcp-vxsm2", IPADDR="IP_Addr1",PORT=2427,PEERADDR="10.0.81.2",PEERPORT=2427,PRI=1,IPROUTE=""prov-add:SGP:NAME="sgp-vxsm1",DESC="SGP for VXSM1",EXTNODE="mgx-8850-1"prov-add:SGP:NAME="sgp-vxsm2",DESC="SGP for VXSM2",EXTNODE="mgx-8850-2"prov-add:M3UAROUTE:NAME="m3uart1",DESC="pgw to vxsm1",OPC="opc1",DPC="dpc1", EXTNODE="mgx-8850-1",PRI=1prov-add:M3UAROUTE:NAME="m3uart2",DESC="pgw to vxsm2",OPC="opc1",DPC="dpc1", EXTNODE="mgx-8850-2",PRI=2;if want loadshare, set PRI=1prov-add:M3UAKEY:NAME="m3ua-key",DESC="M3UAKEY for ss7link1",OPC="opc1",DPC="", ROUTINGCONTEXT=222,SI="ISUP",NETWORKAPPEARANCE=1prov-add:SS7PATH:NAME="ss7-link1",DESC="PGW1 to DPC1",MDO="Q761_BASE",CUSTGRPID="1111", SIDE="network",DPC="dpc1",OPC="",M3UAKEY="m3ua-key",ORIGLABEL="",TERMLABEL="";M3UA ASSOCIATION to 1st VXSM cardprov-add:ASSOCIATION:NAME="asso-vxsm1",DESC="Association to vxsm1",EXTNODE="", SGP="sgp-vxsm1",TYPE="M3UA",IPADDR1="IP_Addr1",IPADDR2="N/A",PORT=2903, PEERADDR1="10.0.78.2",PEERADDR2="0.0.0.0",PEERPORT=2903,IPROUTE1="",IPROUTE2="", RCVWIN=18000,MAXINITRETRANS=10,MAXINITRTO=2000,MAXRETRANS=5,CUMSACKTO=300,BUNDLETO=100, MINRTO=300,MAXRTO=3000,HBTO=2000,IPPRECEDENCE="ROUTINE",DSCP="N/A",MAXRETRANSDEST=3;M3UA ASSOCIATION to 2nd VXSM cardprov-add:ASSOCIATION:NAME="asso-vxsm2",DESC="Association to vxsm2",EXTNODE="", SGP="sgp-vxsm2",TYPE="M3UA",IPADDR1="IP_Addr1",IPADDR2="N/A",PORT=2901, PEERADDR1="10.0.81.2",PEERADDR2="0.0.0.0",PEERPORT=2901,IPROUTE1="",IPROUTE2="", RCVWIN=18000,MAXINITRETRANS=10,MAXINITRTO=2000,MAXRETRANS=5,CUMSACKTO=300,BUNDLETO=100, MINRTO=300,MAXRTO=3000,HBTO=2000,IPPRECEDENCE="ROUTINE",DSCP="N/A",MAXRETRANSDEST=3Take Back and Transfer Phase 2
The Take Back and Transfer feature (CSCse99755) enables the Cisco PGW 2200 Softswitch to perform a variety of different call transfers upon request from a service control point (SCP) such as Cisco Intelligent Contact Management (ICM) using the Intelligent Network Application Protocol's (INAP) CS-1 (ITU Q.1218 Capability Set 1)/CS-2 (ITU Q.1228 Capability Set 2) capabilities to support different contact centers.
The Take Back and Transfer feature supports two new operations:
•
DTMF Blind Transfer under INAP Control
•
Consultation Transfer
Note
For more information, see the Take Back and Transfer feature module.
Usability Enhancements—Phase 1
The Usability Enhancements—Phase 1 feature (CSCsv78723) includes additions and modifications to the software that enable customers to monitor the operation of the system more fully. The enhancements include:
•
Two new MML commands and five modified MML commands.
•
New script named collectdata enables service providers to collect debug trace data from files in several different directories and to create a log that collects activity for a specified period of time.
•
Service providers can display, in the platform.log, pstack information for the heartbeat time-out process before the system procM process kills the heart-beat time-out process.
Note
The pstack is a function performed by the operating system running on the Sun platform to check the status of threads running for active processes. Experienced system engineers can search the platform.log for pstack information.
This feature provides the following benefits:
•
MML commands that enable you to retrieve system status and performance data in greater detail, which makes troubleshooting the system more efficient.
•
The new script, collectdata, which compiles information from files in several directories. The script creates a log of system activity that occurs during a specified period of time. The log generated by the collectdata script enables you to find important system data without having to search in several different directories.
•
You can retrieve information from the platform.log about the heartbeat time-out process produced by the pstack before the system procM process kills the heartbeat time-out process.
Note
For more information, see the Usability Enhancements—Phase 1 feature module.
XML-Based Trunk Group File Format
The XML-Based Trunk Group File Format feature (CSCse63290) allows the Cisco PGW 2200 Softswitch trunk group import/export files to be in XML format rather than fixed record format. The trunk group import/export file are changed from a fixed field format to an XML-based format that permits the addition of trunk group properties without impacting provisioning mechanisms like MML and VSPT for existing users.
Note
Do not manually edit the export_trkgrp.dat file. Make changes to the configuration through provisioning.
Installation Notes
This section contains information and procedures you can use to remove, upgrade, or install the Cisco PGW 2200 Softswitch software. It also contains information about software patches.
Acquiring the Software
The Cisco PGW 2200 Softswitch software is provided to users on a CD. Before installing the software, check the solution release notes and the web for the most current patch level. If the information on the CD matches the information provided on the web and in the solution release notes, install the software and patches directly from the CD.
If the web information is more current, complete the following procedure to obtain software patches from Cisco.com.
Release 9.7(3) Patch 26 and Earlier
Software files for Patch 26 and earlier are located in the following directories.
Note
You must be logged into www.cisco.com to see these patches.
Media Gateway Controller 9.7(3) Sparc Version:
http://www.cisco.com/pcgi-bin/tablebuild.pl/mgc-973-sparc
Media Gateway Controller 9.7(3) Opteron Version:
http://www.cisco.com/pcgi-bin/tablebuild.pl/mgc-973-opteron
Release 9.7(3) Patch 27 and Later
Use the following procedure to locate the software files for Patch 27 and later:
Step 1
From the Cisco.com page, select the Download Software link (located under Support).
The Download Software page appears.
Step 2
From the Software Center page, select the Voice and Unified Communications link.
A login box appears.
Step 3
Enter your Cisco.com user name and password and press OK.
After authentication, a list of Voice and Unified Communications products appears.
Step 4
Select links in the following sequence:
•
IP Telephony
•
Call Control
•
Cisco PGW 2200 Softswitch
•
Cisco PGW 2200 Softswitch Software Version 9
Step 5
Select the links for the desired software release.
Installing and Upgrading the Software
CautionBefore upgrading from a current version of Software Release 9 to a later level, you must verify software release version compatibility by contacting Cisco TAC (see the "Obtaining Documentation and Submitting a Service Request" section) or your Cisco account representative. Software release version incompatibility may cause service disruption.
CautionBecause the Multiple Incoming IP Trunks feature (included in Patches CSCOgs013 and CSCOnn013) modifies Cisco PGW 2200 Softswitch provisioning tables, we strongly recommend that you back up the current configuration before you upgrade and apply the back up configuration if the upgrade fails. Any configuration based on S13P13 is not backwards compatible.
This recommendation also applies if you upgrade to a patch higher than S13P13 from a patch earlier than S13P13.
If you are installing software Release 9.7(3) for the first time, see Cisco PGW 2200 Softswitch Release 9.7 Software Installation and Configuration Guide for instructions.
Note
In Cisco PGW 2200 Softswitch Release 9.7 Software Installation and Configuration Guide, note the following change: In the "Configuring SNMP Support Resources" section, SNMP MIB measurements are valid only on the active node. They are not replicated to the standby node.
CautionWhen you upgrade a redundant system, verify that the pom.dataSync parameter (located in /opt/CiscoMGC/etc/XECfgParm.dat) is set to false to maintain calls and preserve your configuration.
CautionNo validation is performed on the IDs you enter. If you enter an invalid ID, the utilities package does not add any accounts.
Tip
If you have trouble installing the utilities package, make sure that you do not have a transpath group in your group file (located in the directory /etc).
Using the Patch Upgrade Procedure
To install software patches, use the procedure provided in the technical note Patch Upgrade Procedure for Cisco PGW 2200 Softswitch Release 9.6 and Later.
The protocol packaging has been improved so that you need only load and install protocols that you require. Previously, the entire protocol suite was packaged and delivered as a unit. With the improved packaging protocol:
•
The standard installation script allows you to specify which protocol sets are required on your platform.
•
Only packages containing the desired protocols are installed as part of the standard installation.
The same number of packages available with the initial release still exist; however, they have a new nomenclature that is required for support of patching later in the release life cycle. You have the option to install only the packages containing required protocols.
The protocol packages are labeled CSCOnnvvv:
•
nn—Indicates the specific protocols you need for your environment
•
vvv—Indicates the version level of the patch
For example, at the time of the release, you are given protocol patch CSCO01000.pkg. The 01 indicates a specific protocol applicable to your environment; 000 indicates the revision level. The next time a set of protocol patches is built, the 000 is increased by 1 (001).
Note
If you encounter issues with Cisco PGW 2200 Softswitch operation, ensure that the latest patch version is installed before trying to obtain technical support.
Note
You must always install the 00 protocol package when upgrading a protocol patch level. If the 00 protocol package is not installed, the upgrade attempt fails. The Protocol File Missing alarm displays.
Use the patch script (new shell script provided with the standard installation) located in the /opt/SW directory (created during the initial base software installation) to confirm which patch packages to install (using the patch status command), and then copy these packages into your local directory (/opt/SW) from the release directory where you can use the script to install the patches.
The installation script requires one of the following options:
•
Option 1—patch status gives output showing which protocol patches are installed on the system. The installed protocol packages are required (must be downloaded) for you to update the software. The exception is if you need a new protocol that was not previously delivered. In this case, you need to download an extra package (the package that the new protocol is delivered in). This option should be run before the current patches are removed from the system.
•
Option 2—patch all automatically searches the local directory (/opt/SW) and the installed system to determine the most recent available patch and automatically updates the system with that patch. This applies to protocol and system patches. All uninstall and install activities are handled by the script. The command for this is patch all. The patch all command does not require a second argument.
•
Option 3—patch system [latest |<alternate patch number>] specifies the exact patch level for system patches you choose to install on the system. You can specify that any available patch level be installed. All uninstall and install activities are handled by this script. This option requires one of the following arguments:
–
latest—Installs the most recently downloaded patch. This argument should be used with the system and protocol commands used in options 3 and 4.
–
<number>—Indicates the patch number <vvv> that you want to install. This argument should be used with the system and protocol commands used in options 3 and 4.
•
Option 4—patch protocol [latest |<alternate patch number>] specifies the exact patch level for protocol patches you choose to install on the system. You can specify that any available patch level be installed. All uninstall and install activities are handled by this script. This option requires one of the following arguments:
–
latest—Installs the most recently downloaded patch. This argument should be used with the system and protocol commands used in options 3 and 4.
–
<number>—Indicates the patch number <vvv> that you want to install. This argument should be used with the system and protocol commands used in options 3 and 4.
The following is sample output of option 2, patch all, which automatically searches the local directory and the installed system to determine the most recent available patch located in /opt/SW (protocol and system) and automatically updates the system with that patch level:
va-butterfly:104> patch allThe following patches are about to be removed from your system:CSCO00018CSCO01018CSCO02018CSCO10018CSCO20018CSCO21018CSCO30018CSCO31018CSCO32018CSCO33018CSCO40018CSCO41018CSCO50018CSCO60018CSCO70018CSCO71018CSCO80018CSCOgs017The following patches are about to be added to your system from the local directory:The following patch(es) are about to be added to your system from the local directory:CSCO00018.pkgCSCO01018.pkgCSCO02018.pkgCSCO10018.pkgCSCO20018.pkgCSCO21018.pkgCSCO30018.pkgCSCO31018.pkgCSCO32018.pkgCSCO33018.pkgCSCO40018.pkgCSCO41018.pkgCSCO50018.pkgCSCO60018.pkgCSCO70018.pkgCSCO71018.pkgCSCO80018.pkgCSCOgs017.pkgAre you sure this add/remove scenario is correct? [y] [y,n,?,q]System-Level Equivalency
Table 13 provides the system level equivalency for each protocol patch. For example, after you install CSCOnn001, Release 9.7(3) is equivalent to Release 9.6(1) patch level CSCOnn037 (contains all patches and features included in Release 9.6(1) up to patch CSCOnn037).
Table 14 provides the system level equivalency for each system patch. For example, after installing CSCOgs002, release 9.7(3) is equivalent to release 9.6(1) patch level CSCOgs036 (contains all patches and features included in release 9.6(1) up to patch CSCOgs036).
Patch Test Combinations
Table 15 provides a list of the patch combinations that were used during testing. Use this list to determine which protocol and system patches should be installed before you run the Cisco PGW 2200 Softswitch software. It does not matter which patch (protocol or system) is installed first.
Release 9.7(3) S35P35
Release 9.7(3) S35P35 resolves the following caveats:
Identifier Severity Component DescriptionCSCtr11781
2
engine
Hold timer is not reset after receiving.
CSCtj62056
3
install
PGW MGC_Toolkit doesn't convert CDRs.
CSCtq66988
3
mdl-q761
Issue comes when "reattempt" is set on call release from ss7 side.
CSCtq67629
3
engine
PGW fax transfer fails after session refresh INVITE.
CSCtq947591
3
mdl-sip
One way audio during NCT between PGW, TDM site, and SIP site.
CSCtr69566
3
mdl-cdr
Wrong value for Dialed Number Nature of Address.
CSCtd877771
4
mdl-callctrl
PGW is not responding to REL message.
CSCtr089691
4
engine
Memory corruption and pointer mishandling caused PGW to core.
CSCtr22705
4
engine
PGW9.7(3)_p34 - DBDip error in platform.log file.
CSCtu17153
4
enhancement
PGW goes OOS when radius accounting is enabled.
CSCtw71268
4
mdl-sip
Old Display name stays in headers if RPID/PAI-D has no Display name.
CSCtf56167
6
engine
TgAdvance release cause code transparency from terminating call leg.
CSCtf85678
6
mdl-sip
BT CR Enhancement for handling the Generic Number.
CSCtr40620
6
engine
Hairpining (TDM switched) for ISUP/ISUP calls and ringback tone for MGCP.
1 Only limited unit testing has been performed for this defect.
Release 9.7(3) S34P34
Release 9.7(3) S34P34 resolves the following caveats:
Identifier Severity Component DescriptionCSCtn675941
3
engine
No ringback tone. PGW sends 183 progress without SDP instead of 180 ringing.
CSCtg91916
4
mml
Removing a percent route failing through batch mml.
CSCtk95441
4
engine
PGW reads incorrect value of remote retrieval indicator.
CSCtl21313
4
engine
Provisioning behavior of respectSipUriUserParm on trnkgrpprop.
CSCtj03366
6
engine
Make redirectional info optional from EISUP IAM message.
1 Because of the tool limitation, only unit testing has been performed for this defect.
Release 9.7(3) S33P33
Release 9.7(3) S33P33 resolves the following caveats:
CSCOnn032
Patch CSCOnn032 resolves the following caveats:
SNMP Returns Wrong Status for Physical E1000G Interfaces
The SNMP returns wrong status for physical E1000G interfaces procedure is used to check the status of the physical E1000G interfaces on the Cisco PGW 2200 Softswitch. The following procedure should only be used by customers who need to check the status of the physical E1000G interfaces.
To check the status of the physical E1000G interfaces, use the following procedure:
Step 1
Download the snmpdm and mib2agt files from the following URL:
Step 2
Copy both the snmpdm file and the mib2agt file to the /opt/CiscoMGC/snmp directory.
Step 3
Run the cd /opt/CiscoMGC/snmp command to change the directory.
Step 4
Run the vi startcia.sh command.
Step 5
Replace the line /opt/CiscoMGC/snmp/snmpdm -tcplocal -nodrweb with /opt/CiscoMGC/snmp/snmpdm -ip_proto -tcplocal -nodrweb.
Step 6
Run the pgrep snmpdm command, and note the process ID that is displayed, for use in the next step.
Step 7
Run the kill -9 PID-from-previous-step command to stop the current process.
Step 8
Run the pgrep mib2agt command, and note this process ID that is displayed, for use in the next step.
Step 9
Run the kill -9 PID-from-previous-step command to stop the current process.
NGE Support for the PGW SNMP Stack
The NGE support for the PGW SNMP Stack procedure is used to check the status of an NGE interface on the Cisco PGW 2200 Softswitch. The following procedure should only be used by customers who need to check the status of an NGE interface.
To check the status of the NGE interfaces, use the following procedure:
Step 1
Download the snmpdm and mib2agt files from the following URL:
Step 2
Copy both the snmpdm file and the mib2agt file to the /opt/CiscoMGC/snmp directory.
Step 3
Run the cd /opt/CiscoMGC/snmp command to change the directory.
Step 4
Run the vi startcia.sh command.
Step 5
Replace the line /opt/CiscoMGC/snmp/snmpdm -tcplocal -nodrweb with /opt/CiscoMGC/snmp/snmpdm -ip_proto -tcplocal -nodrweb.
Step 6
Run the pgrep snmpdm command, and note the process ID that is displayed, for use in the next step.
Step 7
Run the kill -9 PID-from-previous-step command to stop the current process.
Step 8
Run the pgrep mib2agt command, and note this process ID that is displayed, for use in the next step.
Step 9
Run the kill -9 PID-from-previous-step command to stop the current process.
CSCOnn031
Patch CSCOnn031 resolves the following caveats:
CSCOnn030
Patch CSCOnn030 resolves the following caveats:
CSCOnn029
Patch CSCOnn029 resolves the following caveats:
CSCOnn028
Patch CSCOnn028 resolves the following caveats:
CSCOnn027
Patch CSCOnn027 resolves the following caveats:
CSCOnn026
Patch CSCOnn026 resolves the following caveats:
CSCOnn025
Patch CSCnn025 resolves the following caveats:
CSCOnn024
Patch CSCOnn024 resolves the following caveats:
CSCOnn023
Patch CSCOnn023 resolves the following caveats:
CSCOnn022
Patch CSCOnn022 resolves the following caveats:
CSCOnn021
Patch CSCOnn021 resolves the following caveats:
Identifier Severity Component DescriptionCSCsw65500
2
mdl-connctrl
973S21: cic=INTERFACE_DISABLED when AS5400 reply 400 error or miss reply.
CSCOnn020
Patch CSCOnn020 resolves the following caveats:
Identifier Severity Component DescriptionCSCsv75084
3
mdl-analysis
CG_PN_CPY and A_NUM_NPI_TYPE behavior not consistent with 9.5(2).
CSCsv65839
6
design
PGW-SIP-DPNSS causing 491.
CSCOnn019
Patch CSCOnn019 resolves the following caveats:
CSCOnn018
Patch CSCOnn018 resolves the following caveats:
CSCOnn017
Patch CSCOnn017 resolves the following caveats:
CSCOnn016
Patch CSCOnn016 resolves the following caveats:
Identifier Severity Component DescriptionCSCsr03189
2
mdl-eisup
9.7(3)S15: EISUP parameter 169 should remain in PGW-H323.
CSCOnn015
Patch CSCOnn015 resolves the following caveats:
CSCOnn014
Patch CSCOnn014 resolves the following caveats:
CSCOnn013
Patch CSCOnn013 resolves the following caveats:
CSCOnn012
Patch CSCOnn012 resolves the following caveats:
CSCOnn011
Patch CSCOnn011 resolves the following caveats:
CSCOnn010
Patch CSCOnn010 resolves the following caveats:
CSCOnn009
Patch CSCOnn009 resolves the following caveats:
CSCOnn008
Patch CSCOnn008 resolves the following caveats:
CSCOnn007
Patch CSCOnn007 resolves the following caveats:
CSCOnn006
Patch CSCOnn006 resolves the following caveats:
CSCOnn005
Patch CSCOnn005 resolves the following caveats:
CSCOnn004
Patch CSCOnn004 resolves the following caveats:
CSCOnn003
Patch CSCOnn003 resolves the following caveats:
CSCOnn002
Patch CSCOnn002 resolves the following caveats:
CSCOnn001
Patch CSCOnn001 resolves the following caveats:
CSC0gs032
Patch CSCOgs032 resolves the following caveats:
CSCOgs031
Patch CSCOgs031 resolves the following caveats:
CSCOgs030
Patch CSCOgs030 resolves the following caveats:
CSCOgs029
Patch CSCOgs029 resolves the following caveats:
CSCOgs028
Patch CSCOgs028 resolves the following caveats:
CSCOgs027
Patch CSCOgs027 resolves the following caveats:
CSCOgs026
Patch CSCOgs026 resolves the following caveats:
CSCOgs025
Patch CSCOgs025 resolves the following caveats:
CSCOgs024
Patch CSCOgs024 resolves the following caveats:
CSCOgs023
Patch CSCOgs023 resolves the following caveats:
CSCOgs022
Patch CSCOgs022 resolves the following caveats:
CSCOgs021
Patch CSCOgs021 resolves the following caveats:
CSCOgs020
Patch CSCOgs020 resolves the following caveats:
CSCOgs019
Patch CSCOgs019 resolves the following caveats:
CSCOgs018
Patch CSCOgs018 resolves the following caveats:
CSCOgs017
Patch CSCOgs017 resolves the following caveats:
CSCOgs016
Patch CSCOgs016 resolves the following caveats:
Identifier Severity Component DescriptionCSCsr03189
2
mdl-eisup
9.7(3)S15:EISUP parameter 169 should remain in PGW-H323.
CSCOgs015
Patch CSCOgs015 resolves the following caveats:
CSCOgs014
Patch CSCOgs014 resolves the following caveats:
CSCOgs013
Patch CSCOgs013 resolves the following caveats:
CSCOgs012
Patch CSCOgs012 resolves the following caveats:
CSCOgs011
Patch CSCOgs011 resolves the following caveats:
CSCOgs010
Patch CSCOgs010 resolves the following caveats:
CSCOgs009
Patch CSCOgs009 resolves the following caveats:
CSCOgs008
Patch CSCOgs008 resolves the following caveats:
CSCOgs007
Patch CSCOgs007 resolves the following caveats:
CSCOgs006
Patch CSCOgs006 resolves the following caveats:
Additional information:
See the "Patch Test Combinations" section to determine which protocol and system patches are needed.
CSCOgs005
Patch CSCOgs005 resolves the following caveats:
Additional information:
See the "Patch Test Combinations" section to determine which protocol and system patches are needed.
CSCOgs004
Patch CSCOgs004 resolves the following caveats:
Additional information:
See the "Patch Test Combinations" section to determine which protocol and system patches are needed.
CSCOgs003
Patch CSCOgs003 resolves the following caveats:
Additional information:
See the "Patch Test Combinations" section to determine which protocol and system patches are needed.
CSCOgs002
Patch CSCOgs002 resolves the following caveats:
Additional information:
See the "Patch Test Combinations" section to determine which protocol and system patches are needed.
CSCOgs001
Patch CSCOgs001 resolves the following caveats:
Additional information:
See the "Patch Test Combinations" section to determine which protocol and system patches are needed.
Protocols Supported
Table 16 shows the protocols that are supported:
Table 16 Supported Protocol Variants
Protocol Variant Name Protocol Family Switch TypeANSISS7_2K
SS7-ANSI
0
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
dummy
AVM
0
dummy
MGCP
0
dummy
SGCP
0
dummy
TCAPOverIP
0
dummy
VSI
0
EISUP
EISUP
0
ETS_300_102
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_AUSTRIAN_C2
SS7-ITU
0
ISUPV2_CZECH
SS7-ITU
0
ISUPV2_DUTCH
SS7-ITU
0
ISUPV2_FINNISH96
SS7-ITU
0
ISUPV2_FRENCH
SS7-ITU
0
ISUPV2_GERMAN1
SS7-ITU
0
ISUPV2_ISRAEL
SS7-ITU
40
ISUPV2_JAPAN
SS7-Japan
10
ISUPV2_JAPAN_C2
SS7-Japan
0
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
SS7-UK
15
ISUPV3_UK_C3
SS7-UK
0
ISUPV3_UK_C3 SS7-UK
SS7-UK
0
ISUPV3_UK_C4
SS7-UK
15
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
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_BELG_C2
SS7-ITU
0
Q761_BELG_C3
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_GERMAN2
SS7-ITU
0
Q761_INDIA
SS7-ITU
0
Q761_JAPAN
SS7-Japan
10
Q761_KOREAN
SS7-ITU
0
Q761_MALAYSIAN
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
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_NIGERIAN
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
1 ISUPV2_GERMAN has ETS_300_356 as the base variant and GERMAN as the country variant.
2 Q761_GERMAN has Q761 as the base variant, SIEMENS as the country variant, and MOBILCOM as the customer variant.
Known Issues and Operational Recommendations
This section contains information about known issues and the corresponding workarounds in the Cisco PGW 2200 Softswitch software Release 9.7(3).
Note
For more information about Cisco IOS issues and workarounds, see the Cisco IOS release notes for your platform.
FTP Not Enabled During Solaris 10 Installation
FTP is not activated during the Solaris 10 installation for the Cisco PGW 2200 Softswitch. Adjunct systems that require FTP access to the Cisco PGW 2200 Softswitch are affected by this issue.
Note
BAMS systems that have the security patches (CSCOh013 and CSCOk9000) installed are not affected. The CSCOk9000 package is restricted by export laws and may not be available to all users.
Table 17 lists commands that can be used to enable, disable, and check the ftp status.
Table 17 FTP Commands
Use to: CommandCheck the daemon for ftp status
svc -a|grep ftp
Enable ftp
svcadm enable ftp
Disable ftp
svcadm disable ftp
Note
For more information, see caveat number CSCsd38259.
Core Dump When Active and Standby Use Different Patch Versions
If you set pom.dataSync in XECfgParm.dat to true on a standby Cisco PGW 2200 Softswitch that is run on a patch earlier than 9.7(3) CSCOgs007/CSCOnn007, there will be an engine core dump.
To avoid this core dump, follow these steps to use a Cisco PGW 2200 Softswitch patch earlier than 9.7(3) CSCOgs007/CSCOnn007.
Step 1
Stop the Cisco PGW 2200 Softswitch when an engine core dump happens.
Step 2
Set pom.dataSync in XECfgParm.dat to false.
Step 3
Copy mdlProcess.dat in /opt/CiscoMGC/etc/CONFIG_LIB/new to /opt/CiscoMGC/etc.
Step 4
Copy mdlProcess.dat in /opt/CiscoMGC/etc/CONFIG_LIB/new to /opt/CiscoMGC/etc/active_link.
Step 5
Restart the Cisco PGW 2200 Softswitch.
This engine core dump also can happen when you downgrade a newly installed 9.7(3) CSCOgs007/CSCOnn007 to a previous patch. After the downgrade, perform Step 3 and Step 4.
The pom.dataSync must be set to false when doing an upgrade to 9.7(3) CSCOgs017/CSCOnn017 or later. Otherwise, the standby Cisco PGW 2200 Softswitch will be OOS.
Inappropriate Trunk Selection with Unreliable MGCP Path and LIDL Trunk Selection Sequence
If you set the trunk selection sequence (SELSEQ) to its default value, LIDL (least idle), there is a risk that the Cisco PGW 2200 Softswitch will select a significant number of temporarily unavailable trunks, which causes calls to fail. This kind of call failure can happen when an overloaded media gateway responds to the Cisco PGW 2200 Softswitch with a temporary MGCP error (400 to 499), or the Cisco PGW 2200 Softswitch does not receive a response from the media gateway in time. The workaround for this known issue is to set the trunk selection sequence to a value other than LIDL in Cisco PGW 2200 Softswitch Release 9.7(3) S21P21. The CDETS number for this issue is CSCsw65500.
Note
The documentation is being revised to indicate that LIDL is the default value for SELSEQ.
Unexpected RADIUS Connectivity Alarms Under Traffic Load
If you enable RADIUS accounting on the Cisco PGW 2200 Softswitch and there is a high traffic load, the system might generate RADIUS connectivity alarms unexpectedly. The CDETS number for this issue is CSCtd03089.
Instability of the nge Interfaces on the Netra X4200 M2 Platform Under Duplex Mismatch Condition
The Netra X4200 M2 server has four Gigabit Ethernet interfaces:
•
Net 0 (nge0)
•
Net 1 (nge1)
•
Net 2 (e1000g0)
•
Net 3 (e1000g1)
For Cisco PGW 2200 Softswitch deployments that use this platform, the nge interfaces can experience a hard hang if a network duplex mismatch occurs during operation. For stability purposes, we recommend that you use the Net 2 (e1000g0) and Net 3 (e1000g1) interfaces, and not the nge0 and nge1 interfaces. The CDETS number for this issue is CSCtd40144.
System File vars.pm Error After Migration from Release 9.7(3) to Release 9.8(1)
After you have migrated from Cisco PGW 2200 Softswitch Release 9.7(3) CSCOgs027/CSCOnn027 to Release 9.8(1) CSCOgs007/CSCOnn007 and later, there is an error in the /opt/CiscoMGC/lib/perl5/5.00503/vars.pm file after installation.
The following line shows line 17 of vars.pm after installation:
if ($sym =~ tr/A-Za-Z_0-9//c) {Correct line 17 should be:
if ($sym =~ tr/A-Za-z_0-9//c) {The workaround for this known issue is to manually change line 17 of vars.pm file from "if ($sym =~ tr/A-Za-Z_0-9//c) {" to "if ($sym =~ tr/A-Za-z_0-9//c) {" and save the file. The CDETS number for this issue is CSCtf30543.
Caveats
Use Bug Toolkit to query caveats. The tool is located at:
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl
Related Documentation
This document contains information that is related to software Release 9.7(3). The documents that contain additional information related to the Cisco PGW 2200 Softswitch are at:
http://www.cisco.com/en/US/products/hw/vcallcon/ps2027/tsd_products_support_series_home.html
You can find the Cisco PGW 2200 Softswitch documentation map at:
http://www.cisco.com/en/US/products/hw/vcallcon/ps2027/products_documentation_roadmaps_list.html
Before Installation
Before you install the Cisco PGW 2200 Softswitch software, consult the following related documentation for information about hardware installation and system requirements:
•
The Overview Guide for your solution
•
Cisco PGW 2200 Softswitch Hardware Installation Guide - Releases 7 & 9
•
Cisco PGW 2200 Softswitch Release 9.7 Software Installation and Configuration
Note
Load the most recent patch set as indicated in the "Installation Notes" section.
•
Cisco Media Gateway Controller Release 9 Regulatory Compliance and Safety Information
•
The Gateway Installation Guide for your solution
After Installation
After you install the Cisco PGW 2200 Softswitch software, consult the following related documentation for information on configuring and provisioning your system:
•
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
•
The Provisioning Guide for your solution
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, 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
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2009-2012 Cisco Systems, Inc. All rights reserved.


