Table Of Contents
Release Notes for the Cisco PGW 2200 Softswitch Release 9.7(3)
Contents
Introduction
Platform Support
Software Required
Cisco PGW 2200 Softswitch Software Compatibility Matrix
Required Swap Space
Host Hardware Requirements
Host Minimum Server Requirements
Media Gateway Hardware Requirements
Local Area Network Switch
Supported Features
Cisco PGW 2200 Softswitch Management
New Features in This Release
A-Number Country Code Digit Remove Property
Backwards Propagation of SIP REFER over SS7 Using REL with RDN
Blind Take Back and Transfer Replacement
Call Reporting
Calling Name Delivery (CNAM)
CODEC and DTMF Preferential Routing Enhancements
Configuration Check for Active/Standby
Digit Buffering for International Gateways
DPNSS Service Interworking with Cisco CallManager Using QSIG Tunneling
Enhanced Local Number Portability and Dial Plan Selection
FCI and TMR Provisioning
Flexible Cause Handling
Full Number Translations
Global Title Provisioning
H.248 Feature
Increase Dial Plan Size
Lawful Intercept
Licensing Features for the Cisco PGW 2200 Softswitch
Live Upgrade From 9.6 Sparc to 9.7 Sparc & Opteron
Loose Routing Support
Mini-Parse Analyzing Tool
Multiple Incoming IP Trunks
Provisioning This Feature
Provisioning Example 1
Example 2
Per Call Trace Enhancement
PGW-ITP Optimize Routing with MAP Query
PGW Support for HSI Non-RAS Mode
PGW TCP Transport for SIP Phase I
UDP to TCP Migration
No Support for UDP/TCP Mixed Network
XECfgParm.dat Parameter
POM File Service Enhancement
Pre Call Announcement After Address Complete Message
Presentation Number Modification
RADIUS Enhancement for Accounting
Redirect Server
Provisioning Example
Ring Back Service using CPC=3 for Voice Messaging
Result Type Definitions
Provisioning Examples:
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 This Feature
SIP FROM Interworking with SS7 and PRI
SIP Overlap Signaling
SIP Service Handling and Feature Interworking Enhancements
SIP Support of Take Back and Transfer in the Cisco Unified Contact Center
SS7 Takeback and Transfer RELEASE Message Parameter Modifications
Support for INAP Generic Number
Support for Individual SIP Cause Values
Support of Location Mapping
Support of Provisionable QoS for Signaling Traffic
Support of Trunk Group Id at the x-route-tag or tsp Parameter
Ingress Trunk Group Property
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
Installation Notes
Acquiring the Software
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
System Level Equivalency
Patch Test Combinations
CSCOnn028
CSCOnn027
CSCOnn026
CSCOnn025
CSCOnn024
CSCOnn023
CSCOnn022
CSCOnn021
CSCOnn020
CSCOnn019
CSCOnn018
CSCOnn017
CSCOnn016
CSCOnn015
CSCOnn014
CSCOnn013
CSCOnn012
CSCOnn011
CSCOnn010
CSCOnn009
CSCOnn008
CSCOnn007
CSCOnn006
CSCOnn005
CSCOnn004
CSCOnn003
CSCOnn002
CSCOnn001
CSCOgs028
CSCOgs027
CSCOgs026
CSCOgs025
CSCOgs024
CSCOgs023
CSCOgs022
CSCOgs021
CSCOgs020
CSCOgs019
CSCOgs018
CSCOgs017
CSCOgs016
CSCOgs015
CSCOgs014
CSCOgs013
CSCOgs012
CSCOgs011
CSCOgs010
CSCOgs009
CSCOgs008
CSCOgs007
CSCOgs006
CSCOgs005
CSCOgs004
CSCOgs003
CSCOgs002
CSCOgs001
Protocols Supported
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
Caveats
Related Documentation
Before Installation
After Installation
Obtaining Documentation and Submitting a Service Request
Release Notes for the Cisco PGW 2200 Softswitch Release 9.7(3)
Revised: October 21, 2009
Release 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
•
Introduction
•Platform Support
•Supported Features
•New Features in This Release
•Installation Notes
•Protocols Supported
•Known Issues and Operational Recommendations
•Caveats
•Related Documentation
•Obtaining Documentation and Submitting a Service Request
Introduction
Interoperability between the old world time division multiplexing TDM networks and the new world 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 the following url:
http://www.cisco.com/en/US/products/hw/vcallcon/ps2027/tsd_products_support_series_home.html
Caution The Cisco PGW 2200 Softswitch and HSI should be installed on dedicated platforms and should not reside with any other applications (SMTP, DNS, HTTP daemons, etc). 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 Cisco PGW 2200 Softswitch Software Compatibility Matrix
Component Type
|
Role
|
Hardware
|
Software Required
|
Cisco PGW Node
|
Call control
|
Cisco PGW 2200 Softswitch
|
Software Version 9.7(3)
|
| |
|
HSI (H.323)
|
Release 4.3(2), with latest patch
|
IP Transfer Point LinkExtender (ITP-L)
|
|
Cisco 2811 ITP-L
|
Cisco IOS Version 12.4(11)SW2
|
Integrated IP Transfer Point LinkExtender (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 switch
|
Cisco 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
|
IP transfer point
|
|
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 higher
|
| |
|
Cisco AS5400XM
|
Cisco IOS Version 12.4(1), 12.4T, or higher
|
| |
|
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 2691
|
Cisco 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 Billing and Measurement Server (BAMS)
|
Version 3.30 with latest patch
|
| |
|
Cisco MGC Node Manager (MNM)
|
Version 2.7(3)
For correlation of the MNM patches with the Cisco PGW 2200 patches, see http://www.cisco.com/en/US/docs/net_mgmt/mnm/2.7.3/release/note/CMNM_rn.html
|
| |
|
Cisco VSPT
|
Version 2.7(3)
For correlation of the VSPT patches with the Cisco PGW 2200 patches, see http://www.cisco.com/en/US/docs/net_mgmt/vspt/2.7/release/notes/vspt273.html
|
| |
|
Cisco Transport Manager (CTM) for MGX 8880 Media Gateway management
|
Version 8.0
|
| |
|
CiscoWorks LAN Management Solution (LMS) for IOS and Catalyst devices
|
Version 2.5.1
|
Optional Software
|
|
Cisco Internetwork Performance Monitor (IPM)
|
Version 2.3
|
| |
|
Cisco Info Center (CIC)
|
Version 3.5
|
Required Swap Space
For the Cisco PGW 2200 Softswitch software, you need to 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; you can 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
Refer to the 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.
Local Area Network Switch
Your application might use one or more local area network (LAN) switches from the Cisco Catalyst Switch family to connect the Cisco PGW 2200 Softswitch host to the MGWs and to the Cisco SLTs or ITPs.
Note User documentation refers 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. Refer to 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
|
Purpose
|
Long-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.
|
Provides a reliable IP link between the Cisco PGW 2200 Softswitch and access servers with Reliable User Datagram Protocol (RUDP)
|
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 CDR 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
|
Established calls are maintained 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 1500+ destination point codes (DPCs)
•Support for up to six origination point codes (OPCs) plus 40+ Capability Point Codes
•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.
|
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
|
Description
|
Cisco Voice Services Provisioning Tool (VSPT)
|
Cisco Voice Services Provisioning Tool (VSPT) provides an easy-to-use graphical tool to provision the Cisco PGW 2200, certain gateways and the Billing and Measurement Server (BAMS). VSPT can be used to create, copy, modify, and deploy configurations. VSPT 2.7(3) is now included with the Cisco MGC Node Manager 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 MGC Node Manager (MNM)
|
MNM is a management system for VOiP networks, including the Cisco PGW 2200 Softswitch, BAMS, HSI, ITP-L, and Catalyst switches. MNM contains a map viewer to manage large, evolving networks, an alarm browser, and performance management features. MNM allows individual components to be easily configured and managed.
|
New Features in This Release
The following features have been added to this release:
•A-Number Country Code Digit Remove Property
•Backwards Propagation of SIP REFER over SS7 Using REL with RDN
•Blind Take Back and Transfer Replacement
•Call Reporting
•Calling Name Delivery (CNAM)
•CODEC and DTMF Preferential Routing Enhancements
•Configuration Check for Active/Standby
•Digit Buffering for International Gateways
•DPNSS Service Interworking with Cisco CallManager Using QSIG Tunneling
•Enhanced Local Number Portability and Dial Plan Selection
•FCI and TMR Provisioning
•Flexible Cause Handling
•Full Number Translations
•Global Title Provisioning
•H.248 Feature
•Increase Dial Plan Size
•Lawful Intercept
•Licensing Features for the Cisco PGW 2200 Softswitch
•Live Upgrade From 9.6 Sparc to 9.7 Sparc & Opteron
•Loose Routing Support
•Mini-Parse Analyzing Tool
•Multiple Incoming IP Trunks
•Per Call Trace Enhancement
•PGW-ITP Optimize Routing with MAP Query
•PGW Support for HSI Non-RAS Mode
•PGW TCP Transport for SIP Phase I
•POM File Service Enhancement
•Pre Call Announcement After Address Complete Message
•Presentation Number Modification
•RADIUS Enhancement for Accounting
•Redirect Server
•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 Overlap Signaling
•SIP Service Handling and Feature Interworking Enhancements
•SIP Support of Take Back and Transfer in the Cisco Unified Contact Center
•SS7 Takeback and Transfer RELEASE Message Parameter Modifications
•Support for INAP Generic Number
•Support for Individual SIP Cause Values
•Support of Location Mapping
•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 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 1 to 5 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
This 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.
ACM<----<----- 180 Ringing
<------REFER (refer-to: RDN)
------>NOTIFY (sip frag 100 Trying)
REL<----- (RDN in RDN Information)
------->NOTIFY (sip frag 200 OK)
Blind Take Back and Transfer Replacement
This 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 form the called attendant in the conversation phase of the call, and the PGW autonomously reroutes the call based upon the analysis of the received DTMF digits.
PGW supports TDM-based transferring agents and calling party for this feature.
A a new sigpath/trunkgroup property MidCallServiceCustID allows PGW 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. You 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 (CMNM). Also, you can provision the Call Reporting feature by using the Cisco Voice Services Provisioning Tool (VSPT) as an alternative method to an MML command session.
Calling Name Delivery (CNAM)
This 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 PGW 2200 supports 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
This feature (CSCsa81867) provides the following:
•Extends the PGW 2200 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/Standby
This 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. You 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. If you want to check the configuration every 30 minutes, you manually add a new line like:
"pom.checkConfigInterval = 1800 "in XECfgParm.dat
The 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" 3
Digit Buffering for International Gateways
This 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:
•The ability to limit the called party number in the ISUP IAM and SAM message
•The option for direct connection between the PGW 2200 and certain international networks
The TBufferDigitLength property works with the following:
•The built in digit length limit of the terminating protocol—The 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
This 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
This 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
This 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.
Table 5 New SIP Properties for FCI and TMR Provisioning
Property
|
Definition
|
DefaultFCINatInd
|
Provisions the FCI A bit (national call indicator) integer. If you do not configure it, then the SIP module takes the default value. Both ISUP and TUP use this bit. For eisup national indicator transparency, the PGW checks for the existence of national indicator. If there is already an A_CC_oNatInd, the PGW uses it rather than generate it from NOA.
Valid Values: 0 or 1 (integer)
where:
0= national call
1= international call
Default Value=0 indicates that the call will be treated as national call
Dynamically Reconfigurable: yes
|
DefaultTmr
|
Provisions the Transmission medium requirement (TMR).
Valid Values: String
SPEECH
UNRES_64K
AUDIO_3K
Default Value: SPEECH
Dynamically Reconfigurable: yes
|
Flexible Cause Handling
This 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 for any reason 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 of the trunk groups are exhausted, you can 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 PGW database query mode, which is used for local number portability (LNP) and 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 also 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 Feature
The H.248 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 a MG, a simple entity that responds to the MGC's 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 feature module.
Increase Dial Plan Size
This 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 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.
Lawful Intercept 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 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 PGW 2200 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/standby servers.
The Cisco PGW 2200 Softswitch tracks the number of ports that are configured in your PGW node (one active/standby system) and compares this to the number of Right To Use (RTUs) licenses that you purchased. All port licenses are in 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 higher, 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 & Opteron
This feature (CSCso49604) allows you to upgrade from Cisco PGW 2200 Softswitch Release 9.6 of the Sparc platform to Release 9.7 and higher 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 the Cisco Media Gateway Controller Software Installation and Configuration (Release 9.7) document at
http://www.cisco.com/en/US/products/hw/vcallcon/ps2027/prod_installation_guides_list.html
Loose Routing Support
This feature (CSCsd83313) supports the SIP loose routing functionality as it is defined in RFC 3261, SIP: Session Initiation Protocol.
Previously, PGW 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 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 PGW, 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
This 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
This feature (CSCsj52735) allows multiple incoming trunkgroups to be configured under the SIP path and EISUP path. SIP trunkgroups can be differentiated by 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 PGW is deployed under a multivendor environment and there are differences in these vendors' SIP/EISUP implementations, PGW can be provisioned with multiple incoming trunkgroups with different properties for different SIP/EISUP implementations.
Caution Because the Multiple Incoming IP Trunks feature (included in Patches CSCOgs013 and CSCOnn013) modifies PGW 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 lower than S13P13.
The Multiple Incoming IP Trunks feature modifies a CDR (Originating Trunk Group), Tag 4008, as described in the Cisco Media Gateway Controller Software Release 9 Billing Interface Guide.
A new SP-Group measurement (SP: IPIN REJ TOT) described in the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Provisioning This Feature
A new sigpath property, IPINMAPPING, lets you assign specific trunk group attributes to different inbound sip calls. The prov-add:ipinmapping command, lets you add up to 10,000 entries to the IP Trunk Group selector table.
•The configuration can be IP only or sipport only.
•Sipport online help displays sipports configured in a previous siplnk.
•If allowedNetmask is empty, PGW 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), then this IP is allowed. If there are several ipinmapping entries qualified, the longest match rule is applied.
•The ipinmapping name is the primary key to identify an ipinmapping entry.
•A 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
•Indicates whether the screening takes effect if no trnkgrp is found. Value range integer range 0 to 2): 0 (no screening), 1 (screening, discard if no trnkgrp found), 2 (screening, process with default if no trnkgrp found).
•This ipinscreening sigsvcprop is only effective on the SIP/EISUP sigpath.
•The default value of ipinscreening sigsvcprop is 0.
•Iinscreening=0 stands for ipinmapping function disabled.
–For 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.
–For eisup sigsvcprop ipinscreening=0, you can specify a default trnkgrp for this eisup sigpath. If you leave it empty, then the eisup trnkgrp with trnkgrpprop btechprefix=NULL is treated as this eisup sigpath's default incoming trnkgrp.
•Ipinscreening=1 stands for ipinmapping function enabled.
–For sigsvcprop ipinscreening=1, you can specify default trnkgrp for this sigpath(SIP/EISUP) or leave it empty, the default trnkgrp is not mandatory.
–For sigsvcProp ipinscreening=1, if no ipinmapping matched, a new call message will be dropped.
•Ipinscreening=2 stands for ipinampping function enabled.
–For sip sigsvcprop ipinscreening=2, you must specify a default SIP_IN trnkgrp for this sip sigpath, this default SIP_IN trnkgrp is be treated as this sip path's default incoming trnkgrp.
–For 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 this eisup sigpath's default incoming trnkgrp.
–For sigsvcProp ipinscreening=2, if no ipinmapping entry is matched, a new call message will be processed with incoming sigpath's default incoming trnkgrp.
Batch file capabilities will be provided for populating the Trunk Group Selector table.
Provisioning Example 1
prov-ed:sigsvcprop:ipscreening=2
Prov-add:siplnk:name="siplnk1", svc="sippath-1",ipaddr="IP_ADDR1",port=5060
Prov-ed:siplnk:name="siplnk1",port=5063
Prov-ed:siplnk:name="siplnk1",port-5065
Prov-dlt:siplnk:name="siplnk1",port-5065
Prov-ed:siplnk:name="siplnk1",port-5064
Prov-add:trnkgrp:name="1000", svc="sippath-1", type=SIP_IN
Prov-add:trnkgrp:name="1010", svc="sippath-1", type=SIP_IN
Prov-add:trnkgrp:name="1020", svc="sippath-1", type=SIP_IN
Prov-add:trnkgrp:name="1030", svc="sippath-1", type=SIP_IN, defaut=1.
Prov-add:trnkgrp:name="1040", svc="sippath-1", type=SIP_IN
Prov-add:ipinmapping:name="sipinmapping-1",sigsvc="sippath-1",allowedIP="10.0.14.145",
sipport=5063, trnkgrpNum=1000
Prov-add:ipinmapping:name="sipinmapping-2",sigsvc="sippath-1",allowedIP="10.0.14.145",
allowedIPNetmask="255.255.255.128", trnkgrpNum=1040
Prov-add:sipinmapping:name="sipinmapping-3",sigsvc="sippath-1",sipport=5064,
trnkgrpNum=1010
Prov-add:sipinmapping:name="sipinmapping-4",sigsvc="sippath-1",
allowedIP="10.0.14.145",trnkgrpNum=1020
The following sip INVITE messages are received:
sip INVITE (srcaddr=10.0.14.145, dstport=5063) select trnkgrp 1000
sip INVITE (srcaddr=10.0.14.187, dstport=5064) select trnkgrp 1040
sip INVITE (srcaddr=10.0.14.87, dstport=5064) select trnkgrp 1010
sip INVITE (srcaddr=10.0.14.145, dstport=5064) select trnkgrp 1020
sip INVITE (srcaddr=10.0.24.176, dstport=5063), select default trnkgrp 1030
Because sigsvc "sippath-1" ipinscreening=2, although no ipinmapping entry matches, the default trunkgroup is selected.
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, then Port only mapping. If the trunkgroup mapping fails again, the mapping sequence continues until an entry is found.
Example 2
prov-ed:sigsvcprop:ipscreening=1
Prov-add:trnkgrp:name="2000", svc="eisuppath-1", type=IP
Prov-add:trnkgrp:name="2010", svc="eisuppath-1", type=IP, default=1
Prov-add:ipinmapping:name="eisupinmapping-1",sigsvc="eisuppath-1",
allowedIP="10.0.14.145", trnkgrpNum=2000
The following eisup IAM messages are received
Eisup IAM (H323 source address = 10.0.14.145)
trnkgrp 2000 is selected
Eisup IAM (H323 source address = 10.0.14.187)
PGW can not find a trunkgroup, although there is a default trunkgroup but eisup.screenging=1. This IAM is discarded.
Per Call Trace Enhancement
This feature (CSCea78597) implements some enhanced functions based on the original per call trace, including collecting per call trace on calling/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"],confirm
mml>sta-sc-trc:<trunkgroup>:[trk=x[,rng==]]
[,anubmer="callingpartynumber"][,bnumber="called
partynumber"][,causevalue=c][,incompleteoverlapnumber][,duration=d][,mcl=m]
[,autostop][,prd=n][,log="log"],confirm
In the standby node:
mml>sta-sc-trc:<sigpath>:[span=x[,rng=y]][,tc=z[,rng=w]][,mcl=m][,prd=n][,log="log"],confi
rm
mml>sta-sc-trc:<trunkgroup>:[trk=x[,rng=y]][,mcl=m][,prd=n][,log="log"],confirm
PGW-ITP Optimize Routing with MAP Query
This feature (CSCsi10115) allows the Cisco PGW 2200 Softswitch to optimize routing based on a subscriber's location within a mobile network.
A new property, ItpActionRequest, indicates that the PGW 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 PGW 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 mobile subscriber's current mobile station roaming number (MSRN). The PGW then routes the call to the closest Gateway MSC based upon the new MSRN.
If the PGW is unable to optimize the call routing based on the MSRN, it continues to route calls based on using the mobile subscriber's MSISDN (telephone number). The PGW routes calls based on an MSISDN using cause analysis.
The new property, ItpActionRequest, is shown in Table 6.
Table 6 New Trunk Group Property for PGW-ITP Optimize Routing with MAP Query
Property
|
Definition
|
ItpActionRequest
|
Defines the indicator required ITP action.
Valid Values: String
It can be "map-app" only currently, depends on ITP's capability.
Default Value: NULL
Property Domain: _X_TrunkGroup
Protocol Family: SIP
Dynamically Reconfigurable: yes
|
Provisioning example:
Prov-ed:trnkgrpprop:name="xxx", ItpActionRequest="map-app"
Prov-dlt:trnkgrpprop:name="xxx", "ItpActionRequest"
PGW Support for HSI Non-RAS Mode
This 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 addresses 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).
PGW 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 include Cisco CallManager (CCM) or H.323 ITS, or cases in which an H.323 gateway provides the only connection to a PBX.
Note A single Cisco H.323 Signaling Interface (HSI) cannot operate in both RAS and Non-RAS modes. If a network requires both modes of operation, the network must have multiple Cisco HSIs.
The following new CDR tag was added:
CDR Tag Name
|
Description
|
H323 DESTINATION
Tag: 4236
|
Identifies the H.323 destination address associated with the terminal trunk group or sigpath.
Source: MDL
Format: IA5
Length: 1 to 29 octets
Data value: Content [IP Address]:[Port]
Example: 64.104.173.123:1720
Extended data value: No extended value
General information: This destination address is the H.323 address used in non-RAS mode. This IP address is the same as the H323PriAddr:H323PriPort or H323AltAddr:H323AltPort defined in the sigpath/trunkgroup property.
Includes CDBs: 1010, 1030, and 1110
Tag type: Generic
|
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
This feature (CSCsh66146) allows the PGW 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, you can 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 above steps, the Cisco PGW 2200 Softswitch uses UDP as a transport for old calls, and only handles new SIP calls over TCP. So the Cisco PGW 2200 Softswitch always creates both a UPD and a TCP socket. The Cisco PGW 2200 Softswitch must reject the new call over an un-configured transport, but PGW 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, PGW should reject REFER to PGW over un-configured transport because REFER might cause UDP/TCP interworking issue 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 for this feature are in Table 7. For information on the other XECfgParm.dat parameters, see the 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
Table 7 XECfgParm.dat Configuration Parameters
Configuration Parameter
|
Definition
|
SIP.CONN_IDLE_PERIOD
|
The length that one TCP connection can stay in an idle state. The value is Integer. The default is 0.
|
SIP.ConnLocalMsgQueueSize
|
The maximum size of the local outgoing message queue. The value is Integer.
|
SIP.Max_Connection
|
The maximum TCP connections supported by PGW simultaneously.
The value is integer.
|
SIP.TransportProtocol
|
The transport protocol PGW uses to make call. The call must be in TCP mode or in UDP mode.
The value is String: TCP or UDP
TCP mode—PGW accepts only sip calls over TCP transport.
UDP mode—PGW accepts only sip calls over UDP transport.
|
POM File Service Enhancement
This feature (CSCsi54885) improves the prov-dply/prov-sync performance to allow PGW to support thousands of dial plans without impacting existing functions.
Pre Call Announcement After Address Complete Message
This feature (CSCsb56721) provides support for pre-call announcements that are played directly after the Address Complete Message (ACM) is received by the PGW 2200 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 you are using this option, the PGW 2200 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 prior to 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 was introduced by 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 PGW 2200 could modify a calling party number (A-number). The PGW 2200 also could modify a PN but only if an A-number was present. This feature enables the PGW 2200 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
This feature (CSCse18042) provides radius interface support on the PGW 2200 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 feature (CSCsk41224) allows the PGW 2200 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 PGW 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 Cisco PGW 2200 Softswitch Release 9 Dial Plan Guide (through Release 9.7), the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide, and the 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 Example
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",translatedn
um="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",
Ring Back Service using CPC=3 for Voice Messaging
This 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 8 support the validation of dw2 in the result type CPCMOD.
To allow you to modify both the calling party CPC and the called party CPC at the same time, PGW 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 the Cisco MGC Software Release 9 Dial Plan Guide.
Table 8 New Result Type Definition
Result Number.
|
Result Type
|
Dataword1
|
Dataword2
|
Dataword3
|
Dataword4
|
Analysis Points
|
Result Type Valid For
|
Intermediate
|
End Point
|
A-digit analysis
|
B-digit analysis
|
Cause
|
Pre-analysis
|
45
|
CPCMOD
|
Integer (0 - 255)
Calling party CPC parameter
|
Integer 0 Default - calling party CPC
|
not used
|
not used
|
|
|
X
|
X
|
|
|
45
|
CPCMOD
|
Integer (0 - 3)
Called party CPC parameter
|
Integer 1
Called party CPC
|
not used
|
not used
|
|
|
X
|
X
|
|
|
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
This 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
This 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 invokes call hold or SIP/HSI invokes 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
This 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 will not support more than two DNS proxy server 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 9.
Table 9 New SIP and Trunk Group Properties for SIP Configurable Retransmissions
Property
|
Definition
|
InviteAttempts
|
Defines the transmission times for INVITE requests.
Valid Values: integer (1-15)
Default Value: 7
Property Domain: _X_TrunkGroup
Protocol Family: SIP
Dynamically Reconfigurable: yes
|
InviteWaitTimer
|
Defines the timer (in milliseconds) of waiting for final response of INVITE requests.
Valid Values: integer (10000-500000)
Default Value: 200000
Property Domain: _X_TrunkGroup
Protocol Family: SIP
Dynamically Reconfigurable: yes
|
NonInviteReqAttempts
|
Defines the transmission times for Non-INVITE requests
Valid Values: integer (1-15)
Default Value: 11
Property Domain: _X_TrunkGroup
Protocol Family: SIP
Dynamically Reconfigurable: yes
|
ResponseAttempts
|
Defines the transmission times for response.
Valid Values: integer (1-15)
Default Value: 11
Property Domain: _X_TrunkGroup
Protocol Family: SIP
Dynamically Reconfigurable: y
|
RetransMethod
|
Defines the re-transmission method.
Valid Values: integer (1: exponential 2: linear)
Default Value: 1
Property Domain: _X_TrunkGroup
Protocol Family: SIP
Dynamically Reconfigurable: yes
|
SIP Early-Dialog Offer/Answer Using PRACK/180/183
This 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.
Caution When 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. You should 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 lower than CSCOgs014/CSCOnn014.
Provisioning This 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
This feature (CSCsg42352) supports the mapping of the SIP FROM header (display name)
The received DISPLAY IE in SETUP message from the NI2+ interface will be 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 will be 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 a new sigpath property, CNAPService, enables this feature on the PGW 2200.
Table 10 CNAPService Property for SIP FROM Interworking with SS7 and PRI
Property
|
Definition
|
CNAPService
|
Enables the mapping of name between ISUP and NAS.
Valid Values: integer 0 or 1
Default Value: 0 (CNAP service is not enabled.)
Property Domain: SigPath
Protocol Family: SS7-ANSI, SS7-ITU
Dynamically Reconfigurable: yes
|
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
This 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
This feature (CSCef54992) introduces a Back to Back User Agent (B2BUA) mode of operation for SIP-to-SIP calls using the PGW 2200. It also enhances the existing mid-call service handling to better interwork SIP signaling for mid-call services. This feature allows PGW 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 PGW 2200 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
This 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 and/or the transferring party for different call transfers.
With this new feature, the Cisco PGW 2200 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 Takeback and Transfer RELEASE Message Parameter Modifications
This 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
This 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
This 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 higher. 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
This 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 PGW 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 11 shows the new trunk group properties.
Table 11 New Trunk Group Properties for Trunk Group Id at the x-route-tag / tsp Parameter
Property
|
Definition
|
TrunkGroupTagLabel
|
This property identifies name of the trunk group from which a call comes.
Valid values: 1 to 63 (string)
Default Value: "NULL"
Note This property does not support some special characters like #, >, and whitespace. MML forbids provisioning these characters to the TrunkGroupTagLabel.
|
TrunkGrpTagLabelTransEnable
|
This property indicates whether and how to send out the ingress trunk group tag label in the outgoing SIP INVITE message.
Valid values: 0, 1, or 2 (integer)
where:
0=not send Do not transmit ingress trunk group tag label in the outgoing INVITE message. This is the default value for this property.
1=send in x-route-tag parameter Transmit ingress trunk group tag label (if present) using x-route-tag parameter in the Via header.
2=send in tsp parameter Transmit ingress trunk group tag label (if present) using the tsp parameter in the Via header.
Default Value=0
Dynamically Reconfigurable: Y
|
Ingress Trunk Group Property
The TrunkGroupTagLabel property can be configured in any ingress trunk group, including SIP, EISUP, SS7, PRI, DPNSS and QSIG. Since 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 PGW. 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
This 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, you need to 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=2
prov-add:EXTNODE:NAME="mgx-8850-1",DESC="MGX8800-VXSM1",TYPE="VXSM",ISDNSIGTYPE="N/A",GROU
P=1
prov-add:EXTNODE:NAME="mgx-8850-2",DESC="MGX8800-VXSM2",TYPE="VXSM",ISDNSIGTYPE="N/A",GROU
P=1
; MEGACO LEG to 1st VXSM card
prov-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,MAXRT
O=3000,HBTO=2000,IPPRECEDENCE="ROUTIN
E",DSCP="N/A",MAXRETRANSDEST=3
; MGCP LEG to 2nd VXSM card
prov-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=1
prov-add:M3UAROUTE:NAME="m3uart2",DESC="pgw to
vxsm2",OPC="opc1",DPC="dpc1",EXTNODE="mgx-8850-2",PRI=2 ;if want loadshare, set PRI=1
prov-add:M3UAKEY:NAME="m3ua-key",DESC="M3UAKEY for
ss7link1",OPC="opc1",DPC="",ROUTINGCONTEXT=222,SI="ISUP",NETWORKAPPEARANCE=1
prov-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 card
prov-add:ASSOCIATION:NAME="asso-vxsm1",DESC="Association to
vxsm1",EXTNODE="",SGP="sgp-vxsm1",TYPE="M3UA",IPADDR1="IP_Addr1",IP
ADDR2="N/A",PORT=2903,PEERADDR1="10.0.78.2",PEERADDR2="0.0.0.0",PEERPORT=2903,IPROUTE1="",
IPROUTE2="",RCVWIN=18000,MAXINITRETRA
NS=10,MAXINITRTO=2000,MAXRETRANS=5,CUMSACKTO=300,BUNDLETO=100,MINRTO=300,MAXRTO=3000,HBTO=
2000,IPPRECEDENCE="ROUTINE",DSCP="N/A
;M3UA ASSOCIATION to 2nd VXSM card
prov-add:ASSOCIATION:NAME="asso-vxsm2",DESC="Association to
vxsm2",EXTNODE="",SGP="sgp-vxsm2",TYPE="M3UA",IPADDR1="IP_Addr1",IP
ADDR2="N/A",PORT=2901,PEERADDR1="10.0.81.2",PEERADDR2="0.0.0.0",PEERPORT=2901,IPROUTE1="",
IPROUTE2="",RCVWIN=18000,MAXINITRETRA
NS=10,MAXINITRTO=2000,MAXRETRANS=5,CUMSACKTO=300,BUNDLETO=100,MINRTO=300,MAXRTO=3000,HBTO=
2000,IPPRECEDENCE="ROUTINE",DSCP="N/A
Take 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 in order 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
•A new script named collectdata enables service providers to collect debug trace data from files in a number of 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 a number of 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
This 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 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, you can 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/cgi-bin/tablebuild.pl/mgc-973-sparc
Media Gateway Controller 9.7(3) Opteron Version: http://www.cisco.com/cgi-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 displays.
Step 2 From the Software Center page, select the Voice and Unified Communications link.
A login box displays.
Step 3 Enter your Cisco.com user name and password and press OK.
After authentication, a list of Voice and Unified Communications products displays.
Step 4 Select links in the following sequence:
IP Telephony
Call Control
Cisco PGW 2200 Softswitch
Cisco PGW 2200 Software Version 9
Step 5 Select the links for the desired software release.
Installing and Upgrading the Software
Caution Before upgrading from a current version of Software Release 9 to a higher level, you must verify software release version compatibility by contacting Cisco TAC (see
Obtaining Documentation and Submitting a Service Request) or your Cisco account representative. Software release version incompatibility may cause service disruption.
Caution Because the Multiple Incoming IP Trunks feature (included in Patches CSCOgs013 and CSCOnn013) modifies PGW 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 lower than S13P13.
If you are installing software Release 9.7(3) for the first time, see the Cisco PGW 2200 Softswitch Release 9.7 Software Installation and Configuration Guide for instructions.
Note In the Cisco PGW 2200 Softswitch Release 9.7 Software Installation and Configuration Guide, observe the following change: In the "Configuring SNMP Support Resources" sections, SNMP MIB measurements are valid only on the active node. They are not replicated to the standby node.
Caution When 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.
Caution No 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 /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 set(s) 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 exists; 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 incremented by 1 (001).
Note If you encounter issues with PGW operation, please 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 your /opt/SW directory (created during the initial base software installation) to confirm which patch packages you need 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 you an 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 all
The following patches are about to be removed from your system:
The 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:
Are you sure this add/remove scenario is correct? [y] [y,n,?,q]
System Level Equivalency
Table 12 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 12 System Level Equivalencies for Protocol Patches
Patch Number
|
System Level Equivalency
|
CSCOnn028
|
9.6(1) Patch CSCOnn054
|
CSCOnn027
|
9.6(1) Patch CSCOnn054
|
CSCOnn026
|
9.6(1) Patch CSCOnn054
|
CSCOnn025
|
9.6(1) Patch CSCOnn054
|
CSCOnn024
|
9.6(1) Patch CSCOnn054
|
CSCOnn023
|
9.6(1) Patch CSCOnn054
|
CSCOnn022
|
9.6(1) Patch CSCOnn054
|
CSCOnn021
|
9.6(1) Patch CSCOnn054
|
CSCOnn020
|
9.6(1) Patch CSCOnn054
|
CSCOnn019
|
9.6(1) Patch CSCOnn054
|
CSCOnn018
|
9.6(1) Patch CSCOnn054
|
CSCOnn017
|
9.6(1) Patch CSCOnn054
|
CSCOnn016
|
9.6(1) Patch CSCOnn049
|
CSCOnn015
|
9.6(1) Patch CSCOnn049
|
CSCOnn014
|
9.6(1) Patch CSCOnn049
|
CSCOnn013
|
9.6(1) Patch CSCOnn046
|
CSCOnn012
|
9.6(1) Patch CSCOnn046
|
CSCOnn011
|
9.6(1) Patch CSCOnn046
|
CSCOnn010
|
9.6(1) Patch CSCOnn046
|
CSCOnn009
|
9.6(1) Patch CSCOnn046
|
CSCOnn008
|
9.6(1) Patch CSCOnn046
|
CSCOnn007
|
9.6(1) Patch CSCOnn046
|
CSCOnn006
|
9.6(1) Patch CSCOnn044
|
CSCOnn005
|
9.6(1) Patch CSCOnn039
|
CSCOnn004
|
9.6(1) Patch CSCOnn039
|
CSCOnn003
|
9.6(1) Patch CSCOnn037
|
CSCOnn002
|
9.6(1) Patch CSCOnn037
|
CSCOnn001
|
9.6(1) Patch CSCOnn037
|
Table 13 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).
Table 13 System Level Equivalencies for System Patches
Patch Number
|
System Level Equivalency
|
CSCOgs028
|
9.6(1) Patch CSCOgs054
|
CSCOgs027
|
9.6(1) Patch CSCOgs054
|
CSCOgs026
|
9.6(1) Patch CSCOgs054
|
CSCOgs025
|
9.6(1) Patch CSCOgs054
|
CSCOgs024
|
9.6(1) Patch CSCOgs054
|
CSCOgs023
|
9.6(1) Patch CSCOgs054
|
CSCOgs022
|
9.6(1) Patch CSCOgs054
|
CSCOgs021
|
9.6(1) Patch CSCOgs054
|
CSCOgs020
|
9.6(1) Patch CSCOgs054
|
CSCOgs019
|
9.6(1) Patch CSCOgs054
|
CSCOgs018
|
9.6(1) Patch CSCOgs054
|
CSCOgs017
|
9.6(1) Patch CSCOgs054
|
CSCOgs016
|
9.6(1) Patch CSCOgs048
|
CSCOgs015
|
9.6(1) Patch CSCOgs048
|
CSCOgs014
|
9.6(1) Patch CSCOgs048
|
CSCOgs013
|
9.6(1) Patch CSCOgs045
|
CSCOgs012
|
9.6(1) Patch CSCOgs045
|
CSCOgs011
|
9.6(1) Patch CSCOgs045
|
CSCOgs010
|
9.6(1) Patch CSCOgs045
|
CSCOgs009
|
9.6(1) Patch CSCOgs045
|
CSCOgs008
|
9.6(1) Patch CSCOgs045
|
CSCOgs007
|
9.6(1) Patch CSCOgs045
|
CSCOgs006
|
9.6(1) Patch CSCOgs043
|
CSCOgs005
|
9.6(1) Patch CSCOgs038
|
CSCOgs004
|
9.6(1) Patch CSCOgs038
|
CSCOgs003
|
9.6(1) Patch CSCOgs036
|
CSCOgs002
|
9.6(1) Patch CSCOgs036
|
CSCOgs001
|
9.6(1) Patch CSCOgs036
|
Patch Test Combinations
Table 14 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.
Table 14 Patch Test Combinations
Protocol Patch
|
System Patch
|
CSCOnn028
|
CSCOgs028
|
CSCOnn027
|
CSCOgs027
|
CSCOnn026
|
CSCOgs026
|
CSCOnn025
|
CSCOgs025
|
CSCOnn024
|
CSCOgs024
|
CSCOnn023
|
CSCOgs023
|
CSCOnn022
|
CSCOgs022
|
CSCOnn021
|
CSCOgs021
|
CSCOnn020
|
CSCOgs020
|
CSCOnn019
|
CSCOgs019
|
CSCOnn018
|
CSCOgs018
|
CSCOnn017
|
CSCOgs017
|
CSCOnn016
|
CSCOgs016
|
CSCOnn015
|
CSCOgs015
|
CSCOnn014
|
CSCOgs014
|
CSCOnn013
|
CSCOgs013
|
CSCOnn012
|
CSCOgs012
|
CSCOnn011
|
CSCOgs011
|
CSCOnn010
|
CSCOgs010
|
CSCOnn009
|
CSCOgs009
|
CSCOnn008
|
CSCOgs008
|
CSCOnn007
|
CSCOgs007
|
CSCOnn006
|
CSCOgs006
|
CSCOnn005
|
CSCOgs005
|
CSCOnn004
|
CSCOgs004
|
CSCOnn003
|
CSCOgs003
|
CSCOnn002
|
CSCOgs002
|
CSCOnn001
|
CSCOgs001
|
CSCOnn028
Patch CSCOnn028 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCtb64808
|
2
|
mdl-sip
|
SIP B2BUA with Rel1xx enabled, term 200 OK was ignored and call failed
|
CSCtb05894
|
3
|
mdl-analysis
|
PGW 9.7(3) in mdl call routing loosing the correct result code
|
CSCtb25486
|
3
|
mdl-sip
|
PGW should quote display-name containing "&"
|
CSCtb47015
|
3
|
mdl-eisup
|
Unknown parameter 168 - H323 Destination Address to SS7
|
CSCtb74772
|
3
|
mdl-lcm
|
9.7(3)S22P22 ISDN backhaul channels hung
|
CSCtb90485
|
3
|
mdl-sip
|
9.7(3) Media is not re-established when the phone becomes available
|
CSCtb36324
|
4
|
mdl-eisup
|
9.7(3) Update duplicated parameter id for EISUP protocol
|
CSCOnn027
Patch CSCOnn027 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCta10670
|
2
|
mdl-sip
|
PGW2200 : One way call after hold,v-sol
|
CSCta59018
|
2
|
mdl-pri
|
PRI timeslots lock IN when receiving STATUS_ENQ on P25S25
|
CSCta79225
|
2
|
mdl-callctrl
|
PGW: Duplicated 200 OK when delayed MDCX ACK received
|
CSCta41698
|
3
|
protocol
|
VXSMH.248 fails calls with unsupported media type
|
CSCsz80980
|
4
|
mdl-sip
|
9.7(3)S24P24 - error CP_ERR_INV_ARG appears on all calls
|
CSCta49886
|
4
|
mdl-sip
|
PGW does not accept the '_' character in username of SDP o line?,v-sol
|
CSCta69940
|
6
|
mdl-sip
|
Fax fails Reinvite for T38 from callmanager to PGW with mtp's allocated
|
CSCtb05775
|
6
|
mdl-lcm
|
CALL_XFER_ACTIVATE notification inside FACILITY message ignored,v-sol
|
CSCOnn026
Patch CSCOnn026 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsx93168
|
3
|
mdl-lcm
|
973S23P23: DTMF detection fails after hold/resume
|
CSCsy94822
|
3
|
mdl-sip
|
973: Return 400 to REFER msg with user name missing in Refered-By header
|
CSCsz27866
|
3
|
mdl-sip
|
PGW should set refresher=uas when uac doesnot support session timer
|
CSCsz52920
|
3
|
mdl-lcm
|
CCM call transfer no-audio after PGW upgrade to patch 24
|
CSCsz55536
|
3
|
mdl-sip
|
200 OK is discarded when bye also after 302 redirection
|
CSCsz57541
|
3
|
mdl-sip
|
9.7(3)S25: PGW release the call after receiving REFER message
|
CSCsz69916
|
3
|
mdl-sip
|
Call Hung when TCC REL before 200OK and CANCEL received later
|
CSCsz69921
|
3
|
mdl-in
|
oDisconnect Event is not reported to SCP,v-sol
|
CSCsz75771
|
3
|
mdl-sip
|
PGW SIP (GTD) handling as per 3204
|
CSCsz96705
|
3
|
mdl-eisup
|
PGW2200: RBT problem for ISUP-EISUP-SIP(302)-SIP call,v-sol
|
CSCta02899
|
3
|
mdl-callctrl
|
wrong invokeid range interworking with ccm,v-sol
|
CSCta07886
|
3
|
mdl-callctrl
|
9.7(3) Duplicated 200 OK when 100 rel enabled for sip-mgcp call
|
CSCsz10290
|
6
|
mdl-sip
|
CANCEL not sent when PGW sends Release to PSTN for cause code 18
|
CSCsz40842
|
6
|
mdl-pri
|
accept Display IE of hex 0x28 and parse to a string
|
CSCsz62864
|
6
|
ioccsip
|
Include the SUSPEND/Network message as well as SUSPEND/Subscriber messa
|
CSCsz62982
|
6
|
mdl-sip
|
9.7(3)S24P24 - PGW release call once receiving 488 for SUS/RES service
|
CSCta25117
|
6
|
toolkit
|
9.7(3)S26P26: Toolkit enhancement for CDR ie display
|
CSCta44108
|
6
|
engine
|
9.7(3)S26P26: enlarge Display name length and dump it in CDE 4079
|
CSCOnn025
Patch CSCnn025 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsx72544
|
2
|
mdl-dpnss
|
CLI is not correctly packed in diverted call NAM msg
|
CSCsy84261
|
2
|
mdl-cdr
|
AOC charge units for final AOCperiodictimer interval are not recorded,v-sol
|
CSCsr47942
|
3
|
mdl-callctrl
|
PGW can't handle an "image/t38" re-INVITE glare condition
|
CSCsx81513
|
3
|
engine
|
PGW sends malformed SIP BYE after receiving ISUP/SUS,ecats-dbahn-E00041
|
CSCsy71523
|
3
|
engine
|
PGW doesn't respond to UPDATE when update media
|
CSCsy79412
|
3
|
mdl-cdr
|
Call Limit results in Empty CDR Tag 4232 and 4233,v-sol
|
CSCsx16398
|
6
|
design
|
Featurette Call Reporting
|
CSCsx37270
|
6
|
mdl-dpnss
|
PGW doesn't map OCN (Originatig Called Number) in ISRM
|
CSCsx75893
|
6
|
protocol
|
Override the called number with the CPN in the MIME of the INVITE
|
CSCsx78511
|
6
|
ioccli
|
drop other number modifications when FNT is successfully
|
CSCsx96110
|
6
|
mdl-pri
|
Invalid Presentation Indicator Cause STATUS msg and call realeased
|
CSCsy75726
|
6
|
design
|
PGW 9.7(3) EISUP SIP incorrect internal mapping of 171 IC_CALL_LIMIT_REJ
|
CSCsy75870
|
6
|
mdl-sip
|
Add UPDATE in Allow header for non-100 response
|
CSCsy95047
|
6
|
engine
|
Need to add CPC values 12 and 249 for Danish ISUP variants
|
CSCOnn024
Patch CSCOnn024 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsx59347
|
2
|
engine
|
Echo canceller is disabled when announcement is played.
|
CSCsx72518
|
2
|
mdl-pri
|
tunnel QSIG chain call forward failed.
|
CSCsv59149
|
3
|
engine
|
PGW : handle CPG hold with two genericnotification parameters,v-sol.
|
CSCsw15424
|
3
|
mdl-sip
|
SIP-EISUP/H323,MOH at terminal side, wrong SDP bring to original side.
|
CSCsx81234
|
3
|
mdl-sip
|
973S23P23:SDP Session Version not refreshed when PGW receives ACK w/sdp.
|
CSCsy03667
|
3
|
engine
|
R digit moddification should be possible when redirecting number analysis.
|
CSCsy39074
|
3
|
mdl-lcm
|
In Xfer with SIP REFER, PGW doesn't send 2nd NOTIFY after the BYE.
|
CSCsv80617
|
6
|
design
|
PGW CODEC Preference handling for Reinvites / MDCX.
|
CSCsw47810
|
6
|
mdl-callctrl
|
Support different Call-ID for partial B2BUA mode.
|
CSCsx49298
|
6
|
ioccli
|
HUCS LI and PGW Radius Event message, incorrect A number in Radius.
|
CSCsx76602
|
6
|
mdl-sip
|
PGW should respond to SIP INFO with Remote-Party-ID field,tac-repro.
|
CSCOnn023
Patch CSCOnn023 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsx32058
|
2
|
mdl-sip
|
PGWp21 sending 200 OK with SDP a=inactive stopping RTP traffic, v-sol.
|
CSCsv25849
|
3
|
mdl-lcm
|
9.7(3)P19: call hung when release the call before PGW gets MDCX response.
|
CSCsw17963
|
3
|
design
|
B num mod does not take effect when used in cause analysis for cause 222.
|
CSCsw53177
|
3
|
mdl-lcm
|
973S21P21: No INFO to SIP when GW reports dtmf to PGW for SS7 to SIP call.
|
CSCsw68669
|
3
|
mdl-sip
|
PGW responds with SIP 491 to re-Invite w/o sdp.
|
CSCsw95917
|
3
|
mdl-analysis
|
Overflow to final overflow route list in a 2-route list PERCRTE fails.
|
CSCsv64530
|
6
|
mdl-callctrl
|
Rework on the H248GatewayReserveValue for H.248 DO codec negotiation.
|
CSCsx34460
|
6
|
design
|
Add SS7 SIGPATH to SuppressCHGNtoCGPNMapping feature, v-sol.
|
CSCOnn022
Patch CSCOnn022 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsu98552
|
3
|
mdl-lcm
|
LI: QoS_Reserve is not sent when cut through at ACM in EISUP call.
|
CSCsv11352
|
3
|
design
|
Allow to send cause value "IC_NO_CIRCUIT_AVAILABLE" to release call.
|
CSCsv14158
|
3
|
mdl-lcm
|
973S19P19: C - D DTMF relay fails even if disable midcallservicecustid.
|
CSCsv22877
|
3
|
mdl-sip
|
973P18: call match failed after BYE/ALSO transfer without ringing.
|
CSCsv29334
|
3
|
mdl-pri
|
No NSF found in SETUP for ATT41495_C2 variant.
|
CSCsv33895
|
3
|
mdl-sip
|
9.7(3) IPinmapping replies from wrong port and wrong domain in RR.
|
CSCsv36244
|
3
|
mdl-sip
|
973S19: some parameters are missing in ReInvite/CPG when you do call hold.
|
CSCsv43006
|
3
|
mdl-sip
|
PGW must quote display-name containing comma.
|
CSCsv48438
|
3
|
mdl-lcm
|
973S19P19: NCT to EISUP - EISUP side causes call failure.
|
CSCsv51058
|
3
|
mdl-cdr
|
973S19P19: 4012: Dialed_Num in 1110 prints the dialed number twice.
|
CSCsv51224
|
3
|
mdl-lcm
|
9.7(3)S19P19:Hangcalls found after blind transfer twice.
|
CSCsv54071
|
3
|
mdl-sip
|
9.7(3)-EISUP to SIP dtmf relay: not all dtmf from occ be relayed to tcc.
|
CSCsv93978
|
3
|
mdl-eisup
|
973S19P19: H323 to SIP CCM call, hold/resume on SIP side causes failure.
|
CSCsv97013
|
3
|
mdl-q767
|
9.7(3) PGW Italian Q767 variant does not support RDN, OCN.
|
CSCsw42345
|
3
|
mdl-in
|
INAP Additional calling party number (tag 25) should be ahead of tag 26.
|
CSCsr97419
|
6
|
mdl-q761
|
Capability to manipulate Presentation Number.
|
CSCsu26049
|
6
|
iocceisup
|
PGW unrecognized ISUP parameter issue, v-sol.
|
CSCsv72283
|
6
|
mdl-q761
|
New Zealand needs IAM sent with Redirect Counter > 5.
|
CSCsv84586
|
6
|
mdl-callctrl
|
Support to disable SIP/H.323 initiated hold to CPG interworking.
|
CSCOnn021
Patch CSCOnn021 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsw65500
|
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
|
Description
|
CSCsv75084
|
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:
Identifier
|
Severity
|
Component
|
Description
|
CSCsu78770
|
2
|
mdl-lcm
|
Answer and Release at the same time trigger hung call.
|
CSCsv23236
|
2
|
engine
|
CSCsv23226: AOC: FACILITY message rejected by PBX, v-sol.
|
CSCsv28412
|
2
|
ioccsip
|
PGW sends 409 Conflict if modified SDP received before MDCX finishes.
|
CSCsr50351
|
3
|
mdl-sip
|
406 returned when no expected SDP present in PRACK.
|
CSCsr79561
|
3
|
mdl-sip
|
973P17:no recvonly in 200ok for Hold re-invite(SDP).
|
CSCsu33028
|
3
|
mdl-sip
|
SipToIsupHopCntRatio = 0 doesn't disable mapping from SIP to ISUP.
|
CSCsu44843
|
3
|
mdl-pri
|
No Ringback tone, when ACM with inband info available received on ISUP.
|
CSCsu48962
|
3
|
mdl-lcm
|
9.7(3)S18:The 2nd 222 cause analysis failed after change DP& B num analysis.
|
CSCsu53683
|
3
|
mdl-sip
|
9.7(3)P15 9.7(3)S15 PGW does not treat header name as case insensitive.
|
CSCsu58962
|
3
|
mdl-q761
|
PGW unrecognized message/Parameter issue for exchange type A.
|
CSCsu79629
|
3
|
mdl-connctrl
|
PGW does not send SIP Ack for 200 ok.
|
CSCsu80629
|
3
|
mdl-eisup
|
973S18: PGW does not handle refer across eisup, call transfer fails.
|
CSCsu93950
|
3
|
msl-pei
|
PGW should recognize the unexpected spare value in calling party number.
|
CSCsu94482
|
3
|
mdl-lcm
|
SS7 to SIP call hold failed when GTD enabled.
|
CSCsv03263
|
3
|
mdl-in
|
Does not release trunk when receiving 500 Int.
|
CSCsv04242
|
3
|
mdl-lcm
|
No Progress out on PRI when receiving ACM with No_Indication from SS7.
|
CSCsv06445
|
3
|
mdl-ni2
|
Should support SERVICE/SERVICE ACKNOWLEDGE for NI2.
|
CSCsv10081
|
3
|
mdl-mgcp
|
MGCP controller sends MCDX recvonly in transfer leads to one-way audio.
|
CSCsv16642
|
3
|
mdl-sip
|
Diversion-extension in front of several other diversion values.
|
CSCsv23675
|
3
|
mdl-sip
|
SIP call failure if 200 ok to INVITE is received before 200 ok for PRACK
|
CSCsv25634
|
3
|
mdl-sip
|
PGW: ID is missing in the NOTIFY EVENT header.
|
CSCsj08981
|
6
|
mdl-callctrl
|
Dynamite Enhancement: Support NCT after NCT completion.
|
CSCsu89990
|
6
|
mdl-in
|
PGW 2200 Calling Party Category change.
|
CSCsv06593
|
6
|
msl-in
|
Mapping Charging Number to Additional callingParty number for INAP message.
|
CSCOnn018
Patch CSCOnn018 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsr53229
|
2
|
mdl-pri
|
PGW: Through charging won't work in 9.7 version, v-sol.
|
CSCsu37433
|
2
|
mdl-eisup
|
Calls released when DPNSS call is diverting from pgw9.7 to pgw9.6, ipngn-huc2-pgw.
|
CSCsu67904
|
2
|
mdl-eisup
|
Conferencing fails to establish a second connection, ipngn-huc2-pgw.
|
CSCsu72706
|
2
|
iocceisup
|
PGW 961 DPNSS ---> EISUP ---> PGW973 DPNSS.
|
CSCsu76626
|
2
|
mdl-sip
|
Double commit 973CAN: SIP - PROXY - PGW - CCM - SIP call fails.
|
CSCso98239
|
3
|
mdl-callcontext
|
PGW does not destroy terminating call context with INAP re-route.
|
CSCsr22452
|
3
|
mdl-callctrl
|
DPNSS NAM message too large.
|
CSCsr48168
|
3
|
mdl-sip
|
9.7(3)P14:PGW do not send 400 Bad Request for Req-URI contain "xxx".
|
CSCsr70248
|
3
|
flovr
|
973S17P17:Blind transfer fails after sw-over caused by PGW not reply ACK.
|
CSCsr73022
|
3
|
mdl-sip
|
9.7(3)P17 9.7(3)S17: mishandling of retransmitted ACK when after 200 OK.
|
CSCsr97445
|
3
|
mdl-sip
|
9.7(3)P16 9.7(3)S16 no contact or RR field when reroute.
|
CSCsu00046
|
3
|
engine
|
IN_TRIGGER overlap LNP problem.
|
CSCsu26337
|
3
|
mdl-dpnss
|
Ringing call disconnects after 7 seconds.
|
CSCsu35301
|
3
|
mdl-sip
|
9.7(3) 9.7(3)P18 9.7(3)S18 PGW init disconnection at double SIP: ACK.
|
CSCsu39447
|
3
|
engine
|
The call is hanging for some cases when CPG comes after ANM.
|
CSCsr67508
|
6
|
design
|
PGW Cause code analysis.
|
CSCOnn017
Patch CSCOnn017 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsr11673
|
2
|
mdl-sip
|
Default DTMF duration not configurable with SIP INFO dtmf-relay.
|
CSCsr24484
|
2
|
mdl-sip
|
SIP ACK (SDP) & reinvite (SDP) - causing occ not respond to reinvite (SDP).
|
CSCsr30588
|
2
|
mdl-eisup
|
9.7(3)S15:EISUP parameter 169 should remain in PGW-H323.
|
CSCsq29006
|
3
|
mdl-sip
|
"483 Too Many Hops" returned when received Max-Forwards=1.
|
CSCsq36329
|
3
|
mdl-connctrl
|
MGCP 527 for COT on H323-->SS7 call.
|
CSCsq55277
|
3
|
mdl-lcm
|
PGW 9.7.3 P14 MOH from CCM sometimes not heard on PSTN-side.
|
CSCsq62671
|
3
|
mdl-q761
|
Should not send out empty connected number in CPG.
|
CSCsq65008
|
3
|
mdl-sip
|
973S15P15: SIP-SIP blind transfer-SS7 fails caused by VIA refresh error.
|
CSCsq83178
|
3
|
mdl-cdr
|
CDR Tag 4201, 4202, 4242, and 4243 missing in SIP-EISUP calls.
|
CSCsq93100
|
3
|
ioccsip
|
SIP invite with "csel=index" invalidates any CIC value passed.
|
CSCsq98488
|
3
|
mdl-sip
|
After receive not support scheme, PGW sends back 400 Bad Request.
|
CSCsq98659
|
3
|
mdl-lcm
|
Local Ringback tone causes no sendrecv when TDM answers.
|
CSCsr00732
|
3
|
mdl-sip
|
Call Hung on PGW when receiving OPTIONS coming end with 0a.
|
CSCsr62308
|
3
|
mdl-lcm
|
973S17P17: SS7-SS7 hairpin call fails caused by play ringback tone error.
|
CSCsr45082
|
4
|
mdl-sip
|
9.7(3)P17 9.7(3)S17 Too many CANCEL signals.
|
CSCsq47869
|
6
|
mdl-sip
|
973S12P12: BYE/ALSO is not supported in SIP-SS7 transfer.
|
CSCsq60202
|
6
|
mdl-q761
|
ISUPV2_FINNISH96 support only NPI value 110 (national use).
|
CSCsq77467
|
6
|
mdl-lcm
|
UUIE protocol discriminator configurable for some SS7 variant.
|
CSCOnn016
Patch CSCOnn016 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsr03189
|
2
|
mdl-eisup
|
9.7(3)S15:EISUP parameter 169 should remain in PGW-H323.
|
CSCOnn015
Patch CSCOnn015 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCso89145
|
2
|
mdl-sip
|
Wrong response sent to OCC when InviteWaitTimer expires.
|
CSCsq26195
|
2
|
mdl-lcm
|
TDM side cannot hear music when on call hold.
|
CSCsq28577
|
2
|
replicator
|
9.7(3)P15: Coredump found at supercell automation.
|
CSCsq48425
|
2
|
ioccsip
|
SIP OOB DTMF */# using INFO dtmf-relay sent as 10/11 and not */#.
|
CSCsq62673
|
2
|
mdl-connctrl
|
973S14:Error RQNT MGCP Package cause call release when MOH.
|
CSCsq75518
|
2
|
mdl-ni2
|
973S15P15: No ring back tone when NI2 - PGW - SIP PROXY - NI2.
|
CSCsk11476
|
3
|
mdl-sip
|
973S8P8: IncreaseLocalSDPVersion() Overflowed When SDP Version > 2^31.
|
CSCsl00218
|
3
|
mdl-q761
|
973S9P9: REL after CGBA receiving a CGB (hardware oriented).
|
CSCsl87653
|
3
|
mdl-ansi-ss7
|
973S11P11: LCall to TCC After EFail in Switchover Results in Hung Call.
|
CSCsm16526
|
3
|
mdl-sip
|
PGW does not include trnkgrp's localport on outgoing INVITE's record-route.
|
CSCso91875
|
3
|
mdl-sip
|
973S12P12: BYE/ALSO is not supported in ss7-sip-transfer-sip.
|
CSCso94814
|
3
|
design
|
973S14P14: PGW cannot send prack with sdp when receiving 183.
|
CSCsq14093
|
3
|
mdl-sip
|
Privacy Feature does not work for SIP-SIP call on 9.7(3).
|
CSCsq16394
|
3
|
design
|
973S14P14:h323 to sip call failed in slowstart with tunnel QSIG.
|
CSCsq18858
|
3
|
mdl-lcm
|
SIP iTNT: After transfer, the call is rejected with Incomplete address.
|
CSCsq19183
|
3
|
mdl-sip
|
UPDATE Session refresher RECOMMENDED not to contain an offer.
|
CSCsq26241
|
3
|
mdl-in
|
PGW ignores DFC and therefore new Connect after Temporary Connection.
|
CSCsq41985
|
3
|
mdl-sip
|
9.7(3) SIP-SS7 call hung if 487 ACK in wrong format.
|
CSCsq49691
|
3
|
design
|
973S15P15:PGW response incorrect Require header of 421.
|
CSCsq53587
|
3
|
mdl-sip
|
PGW should acknowledges the 487 with different to tag.,v-sol.
|
CSCsq60495
|
3
|
mdl-sip
|
PGW need to be able to handle Invite from Linksys with ref=,v-sip.
|
CSCsq72207
|
3
|
mdl-q761
|
PGW 9.7.3 OCC hung call legs during stress.
|
CSCsm03911
|
4
|
mdl-cdr
|
PGW973S12P12: CDB 4004 is incorrect in ABORTED CDB(1030) in diversion.
|
CSCsk38410
|
6
|
mdl-lcm
|
9.7(3)S9P9: No remote ring tone generated for 183 w/ sdp info.
|
CSCsm91420
|
6
|
mdl-cdr
|
Introduce a new CDR tag to record iTNT digit string for iTNT service.
|
CSCso14089
|
6
|
mdl-sip
|
SIP overlap support.
|
CSCso77759
|
6
|
mdl-mgcp
|
PGW to modify MGCP connection in ANSWER status when CPG is Rcvd.
|
CSCso81973
|
6
|
mdl-lcm
|
SIP/NI Calling Name to Q931+ Display I.E.
|
CSCso86783
|
6
|
mdl-analysis
|
9.7(3)S14 9.7(3)P14: CG_PN_COPY for redirected calls.
|
CSCso89453
|
6
|
mdl-sip
|
SIP to ISUP number mapping does not work in 9.7(3).
|
CSCso94787
|
6
|
mdl-eisup
|
9.7(3)S14: EISUP does not handle unrecognized parameter correctly.
|
CSCsq21629
|
6
|
mdl-mgcp
|
Enhancement:disable detectfaxmodemtone in T38 fax.
|
CSCsq26344
|
6
|
mdl-q761
|
Support for NOA 112 & 113 in DK ISUP.
|
CSCsq31467
|
6
|
mdl-eisup
|
A parameter 169 (A9) (NODEIndicators) which leaks out to SS7.
|
CSCOnn014
Patch CSCOnn014 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsl89398
|
3
|
mdl-sip
|
973S11P11: SIP Attended Transfer Fails.
|
CSCsm14486
|
3
|
mdl-sip
|
9.7(3)S12P12: retransmit the wrong ACK would be accepted by PGW.
|
CSCsm41611
|
3
|
mdl-sip
|
SIP-CT: No Proceeding State after "199 Unknown" Response, Compliance.
|
CSCsm49974
|
3
|
mdl-lcm
|
973S13P3:No SDP update to Gateway for SS7-EISUP-SIP call, when CPG w/SDP.
|
CSCsm54882
|
3
|
engine
|
Diversion occurs after ACM with a redirecting information.
|
CSCsm84241
|
3
|
design
|
973S13P13: pgw cant trigger iTNT after incorrect number dialed on agent.
|
CSCsm93958
|
3
|
mdl-sip
|
973S13P13: A side doesn't release when C is busy.
|
CSCsm96298
|
3
|
mdl-sip
|
9.7(3)P13PGW uses wrong parameter name "Events" in the Call-Info header,.
|
CSCsm96878
|
3
|
engine
|
Invalid '=' char inserted in to Via Branch in SIP request.
|
CSCso06314
|
3
|
mdl-q761
|
ISUP message/parameter compatibility support enhancement.
|
CSCso08769
|
3
|
mdl-q761
|
9.7(3)P12:REL with redirection num cause call hang-up in signaling mode.
|
CSCso11858
|
3
|
mdl-mgcp
|
PGW 9.7.3 (MDCX) empty R: field restricts midcall out of band DTMF.
|
CSCso32909
|
3
|
mdl-lcm
|
No CPG message after 183 with SDP if a SIP redirecting occurred before.
|
CSCso37975
|
3
|
mdl-sip
|
9.7(3):S13P13:extra international prefix + for display name in 302 forwarding.
|
CSCso39701
|
3
|
mdl-sip
|
9.7(3)P13: 100 trying should not be forwarded in proxy mode for BYE also.
|
CSCso39811
|
3
|
mdl-analysis
|
9.7(3):S13P13:RETRY_ACTION cause SIPTNS dw1 info lost after reattempt.
|
CSCsl96209
|
6
|
mdl-sip
|
Mapping cic parameter in SIP message to ISUP TNS.
|
CSCsm16340
|
6
|
mdl-sip
|
PGW reverse Record-Route header in 200 for re-INVITE.
|
CSCsm62121
|
6
|
ioccsip
|
PGW SIP INFO to support content-type: application/dtmf-relay.
|
CSCsm91841
|
6
|
mdl-sip
|
PGW support for BW logical forking: different to tag in 200OK.
|
CSCso02350
|
6
|
mdl-sip
|
PRACK is sent without SDP when receiving 18X with SDP.
|
CSCso32183
|
6
|
mdl-lcm
|
9.7(3) PGW should Support CHARGE_IND in backward CPG & ANM.
|
CSCOnn013
Patch CSCOnn013 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsm13911
|
2
|
mdl-sip
|
973S12P12: PGW does not accept the 200 ACK message when SIP-SIP Fax call.
|
CSCsm14330
|
2
|
mdl-lcm
|
PGW 9.7(3): No bidirection voice on calls from PSTN to SIP, v-sol.
|
CSCsl45342
|
3
|
mdl-sip
|
SIPit: PGW includes sdp in 200 OK to bye when tcc side retransmit 200 OK.
|
CSCsl74202
|
3
|
mdl-sip
|
PGW fails parsing whitespace among header values.
|
CSCsl92226
|
3
|
mdl-sip
|
973S11P11: SIP-SIP REINVITE, PGW Send 200OK to Orig When Term Not Respond.
|
CSCsl94961
|
3
|
mdl-sip
|
9.7(3)P12:Unsupported header is not included in 420 (Bad Extension).
|
CSCsm10005
|
3
|
mdl-sip
|
Routing of ACK/BYE is wrong in a canceled call, v-sol.
|
CSCsm18880
|
3
|
mdl-lcm
|
973S12P12:Fax does not fallback to voice in SS7-SIP fax call.
|
CSCsm38816
|
3
|
mdl-pri
|
Incorrect behavior of CallStateCompatibilty on PRI.
|
CSCsm63809
|
3
|
mdl-analysis
|
PGW: DB_XLATED get Min and Max back from Times-ten and Min is zero.
|
CSCsm79816
|
3
|
mdl-mgcp
|
9.7.3S12P12: no voice path when blind Call transfers after 302.
|
CSCsh65871
|
6
|
mdl-callctrl
|
mdl-callctrl, Dynamite phase3: Support SIP Transferring/Calling Agent.
|
CSCOnn012
Patch CSCOnn012 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsl49560
|
2
|
iocceisup
|
No QSIG Facility included in EISUP IAM Re-Attempt.
|
CSCsl51838
|
2
|
design
|
SIP Invite without SDP via EISUP - triggers CRCX in sendrecv.
|
CSCsl59469
|
2
|
mdl-sip
|
PRI --> SIP call fails since MDL cannot encode Alerting message.
|
CSCsl03825
|
3
|
mdl-sip
|
PGW only check the SDP version id, not check the session id.
|
CSCsl13018
|
3
|
mdl-sip
|
SIP fails to check comma within callid.
|
CSCsl13207
|
3
|
mdl-sip
|
T38 fax fails after PGW switch-over.
|
CSCsl18316
|
3
|
mdl-sip
|
T38 fax fails when do fax after blind Call transfer.
|
CSCsl20247
|
3
|
mdl-sip
|
9.7(3)S10P10:diversion reason and counter is lost for ISUP-SIP redirection.
|
CSCsl20267
|
3
|
mdl-q761
|
9.7(3)S10P10:REL w/o redirection info cause invalid diversion for ACM.
|
CSCsl23680
|
3
|
mdl-eisup
|
9.7(3)S10P10:diversion counter mapping fails when counter > 7 from SIP.
|
CSCsl23696
|
3
|
mdl-sip
|
9.7(3)S10P10:SIP side endless of loop for 302 if contact number is same.
|
CSCsl38958
|
3
|
measm
|
9.7(3)S11:backwards blind transferred call is counted as failure call.
|
CSCsl40855
|
3
|
mdl-q761
|
9.7(3) P11:SipToIsupInterworkingInd s/ for EISUP not working for BCI.
|
CSCsl45359
|
3
|
mdl-sip
|
SIPit: session timer does not work when using compact header 'x'.
|
CSCsl45456
|
3
|
mdl-sip
|
9.7(3) P11:REFER timer is not reset after reception of 202.
|
CSCsl60958
|
3
|
engine
|
Wrong CSeq in 400 Bad Request for an INFO message.
|
CSCsl69977
|
3
|
engine
|
SIP No Record-Route Header in 1xx Responses.
|
CSCsj71655
|
6
|
mdl-lcm
|
Subsequent services are blocked once FAX service is invoked.
|
CSCsl38500
|
6
|
mdl-dpnss
|
DPNSS to EISUP redirection number modification change request.
|
CSCsl51397
|
6
|
mdl-q761
|
Q761 variant Q761_97VER_RUSS_C2 to support TNS.
|
CSCOnn011
Patch CSCOnn011 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsk36078
|
2
|
mdl-ansi-ss7
|
973S9P9: Core dump of ISDNL3 caused by null pointer.
|
CSCsl07975
|
2
|
mdl-dpnss
|
Different redirecting number used by PGW for DPNSS local reroute.
|
CSCsl23689
|
2
|
mdl-analysis
|
TimesTen database number match for overlap.
|
CSCsl27760
|
2
|
mdl-dpnss
|
DPNSS Diverting info not mapped to OCN.
|
CSCsk34518
|
3
|
mdl-eisup
|
973S9P9: EISUP->SIP and refer to another SIP cause single voice
|
CSCsk68798
|
3
|
mdl-sip
|
973S10P10: C side doesn't release when A side releases after transfer.
|
CSCsk72531
|
3
|
mdl-q761
|
ISUP_GERMANV2: map Orig Redirection Reason to 0000 if FCI NI=1, v-sol.
|
CSCsk87845
|
3
|
mdl-sip
|
SIP MDL set the wrong destination port.
|
CSCsk94468
|
3
|
mdl-sip
|
973S9P9: T3: SIP-CT: "299 OK" response has been ignored.
|
CSCsk94474
|
3
|
mdl-sip
|
973S9P9: BYE-Request without ACK-Request in case of unsupported media.
|
CSCsl02106
|
3
|
mdl-sip
|
PGW 9.7.3 P_A_ID SIP:invite:user=phone parameter missing, v-sol.
|
CSCsl05795
|
3
|
mdl-sip
|
SIP to EISUP call hangs when REL received while waiting for term SDP, v-sol.
|
CSCsk69848
|
6
|
protocol
|
UPDATE message handling during call set-up for interworking and b2bua mode.
|
CSCsk88483
|
6
|
mdl-sip
|
SipToIsupInterworkingInd option support for EISUP.
|
CSCsl06237
|
6
|
mdl-q761
|
Backwards propagation of SIP REFER over SS7 using REL with RDN.
|
CSCOnn010
Patch CSCOnn010 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsk61336
|
2
|
mdl-sip
|
CC_DIG + BDigitCCPrefix Not Working for SIP.
|
CSCsj71883
|
3
|
mdl-eisup
|
973S7P7: single voice met in S7P7, happens every time.
|
CSCsk36405
|
3
|
mdl-sip
|
CCM SIP Phone to DPNSS - Unallocated Number, but reply 500 Error.
|
CSCsk38182
|
3
|
mdl-sip
|
973S9P9: no RQNT sent from second PGW when DTMF detecting is needed.
|
CSCsk51486
|
3
|
mdl-eisup
|
973S9P9: l_reqDtmfRpt is not checkpoint cause single voice after sw.
|
CSCsk61321
|
3
|
mdl-lcm
|
9.7(3)P9:TCC not destroyed when LReleaseAck arrives before LDeleteChanAc.
|
CSCsk78290
|
3
|
mdl-q761
|
SDP version increment wrong when force SDP for MDCX set.
|
CSCsk79850
|
3
|
mdl-sip
|
Req-URI not properly stored in 9.7(3) s9 p9, v-sol.
|
CSCsk40228
|
4
|
mdl-sip
|
973S9P9: Multiple Via headers included in the ACK when responding non-200.
|
CSCsk41224
|
6
|
engine
|
PGW needs option to modify OCN and Redirecting IE with RMODDIG.
|
CSCsk78282
|
6
|
mdl-lcm
|
FAC w/ Call transfer, active does not match INVITE (resume).
|
CSCOnn009
Patch CSCOnn009 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsj86306
|
2
|
mdl-sip
|
SIP to EISUP call gets stuck when BYE received during Alerting, v-sol.
|
CSCsk12203
|
2
|
mdl-sip
|
Re-invite for sip dpnss call fails after switchover.
|
CSCsk36289
|
2
|
mdl-sip
|
PGW 9.7(3) SIP INVITE Germany character not possible, v-sol.
|
CSCsj25913
|
3
|
mdl-sip
|
PGW fails to provide ringback for 18x following REFER.
|
CSCsj45438
|
3
|
mdl-sip
|
CCMSIP: No 200 OK to Unsolicited NOTIFY.
|
CSCsj67814
|
3
|
mdl-ansi-ss7
|
973S7P7: call release is abnormal after PGW switch-over.
|
CSCsj71883
|
3
|
mdl-eisup
|
973S7P7: single voice met in S7P7, happens everytime.
|
CSCsj77648
|
3
|
mdl-ansi-ss7
|
973S7P7:ANSI REL with RDN not trigger the mid-call service.
|
CSCsj83770
|
3
|
mdl-ansi-ss7
|
Standby failed to checkpoint with Active properly.
|
CSCsj87680
|
3
|
mdl-eisup
|
Result type PNMODDIG should not result in new GN-ACgPN added, v-sol.
|
CSCsj89997
|
3
|
mdl-eisup
|
EISUP link to remote PGW stays OOS while other 3 links are IS.
|
CSCsj91496
|
3
|
mdl-sip
|
973S8P8: SIP to SIP b2bua call fail if 1st TCC Invite reject by 422.
|
CSCsj94888
|
3
|
mdl-sip
|
973S8P8: Contact header missing in Subscribe msg.
|
CSCsj97089
|
3
|
mdl-sip
|
PGW adds user=phone to URI on switch-over.
|
CSCsk06508
|
3
|
mdl-sip
|
973S8P8:Call-Info need to removed when unsolicitednotifymethod=0.
|
CSCsk19442
|
3
|
iocceisup
|
PGW doesn't generate MCDX on HSI->EISUP->PGW Call Xfer (Ringback).
|
CSCsk17603
|
4
|
toolkit
|
SimWriter stops on DB_XLATED result type when no match, v-sol.
|
CSCsd20167
|
6
|
mdl-sip
|
Route List in wrong order on SIP Subsequent Request, Feature.
|
CSCsd83313
|
6
|
mdl-sip
|
PGW needs to support loose route, per RFC3261, Feature.
|
CSCsj60149
|
6
|
mdl-sip
|
Checkpointing - proxy mode - TCC sides tags not checkpointed.
|
CSCsj70270
|
6
|
mdl-eisup
|
Checking user=phone param for SIP username mapping to E.164,v-sol.
|
CSCsj93452
|
6
|
mdl-sip
|
PGW 9.7.3 SIP call is disconnected after 30 minutes.
|
CSCsk06382
|
6
|
mdl-sip
|
SIP call enhancement for ICMP unreachable message handle.
|
CSCsk10051
|
6
|
mdl-sip
|
Bad RC on EISUP after unsuccessful INVITE.
|
CSCOnn008
Patch CSCOnn008 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsj67872
|
2
|
ioccxgcp
|
VXSM and PGW context inconsistent and hung with traffic and ip restarted.
|
CSCsj67924
|
2
|
mdl-lcm
|
PGW 9.7(3): run sporadically in MCL values for low CPS, v-sol.
|
CSCsj77930
|
2
|
mdl-sip
|
PGW sets the Screening indicator falsely SIP->PSTN, v-sol.
|
CSCsj21507
|
3
|
mdl-sip
|
973S6P6: PGW Retransmit INVITE After Rcv 18x In Fixed Proxy Mode.
|
CSCsj58315
|
3
|
mdl-sip
|
PGW 9.7(3): Problem with DTMF in INFO, v-sol.
|
CSCsj62155
|
3
|
mdl-sip
|
No answer checkpoint in an HSI to SIP call when no SDP in initial Invite.
|
CSCsj63692
|
3
|
mdl-sip
|
973S7P7: ss7 side call forward failed after PGW receiving 503.
|
CSCsj65837
|
3
|
mdl-sip
|
PGW setting incorrect content-length in NOTIFY message.
|
CSCsj72044
|
3
|
mdl-eisup
|
No check for HopCounter (Max-Forwards) > 31 for SIP to EISUP call, v-sol.
|
CSCsj39768
|
5
|
mdl-mgcp
|
PGW send down remote sdp when re-seizing channel on OLC.
|
CSCsj71821
|
5
|
mdl-sip
|
9.7(3):NOA BLACKLIST SIP call, rejected by 500.
|
CSCea78597
|
6
|
other
|
Per Call Trace feature.
|
CSCse83505
|
6
|
design
|
H248 Feature for PGW 9.7.
|
CSCsj60149
|
6
|
mdl-sip
|
Checkpointing - proxy mode - TCC sides tags not checkpointed.
|
CSCOnn007
Patch CSCOnn007 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsj24893
|
2
|
mdl-cdr
|
PGW generating corrupt CDRs.
|
CSCsj26603
|
2
|
mdl-cdr
|
Called number can not be populated in CDR when trunkgroup is congested.
|
CSCsj36094
|
2
|
ioccxgcp
|
Gateway SDP is not modified if SDP supplied to PGW in ack for Reinvite.
|
CSCsj56179
|
2
|
mdl-eisup
|
973S7P7: mdo/so version inconsistency.
|
CSCsi08360
|
3
|
mdl-lcm
|
9.7(3)IXS: The PGW sends out wrong Info for SS7 Callhold over SIP-GTD.
|
CSCsi66656
|
3
|
mdl-lcm
|
973S6P6: PGW sends out multiple unnecessary Invites after blind transfer.
|
CSCsi66948
|
3
|
mdl-lcm
|
Call fails announcement fails.
|
CSCsi68836
|
3
|
mdl-in
|
9.7.3 S6P6:SS7 IN Call hangs up when cdp length is not long enough.
|
CSCsi69962
|
3
|
mdl-sip
|
CCMSIP:UPDATE after CME consultant transfer leads pgw to release call.
|
CSCsi70022
|
3
|
mdl-sip
|
PGW SIP Cancel Request Tag in To Not Removed.
|
CSCsi70126
|
3
|
mdl-q761
|
Retry redirecting behavior in 9.7(3) is not correct.
|
CSCsi80219
|
3
|
mdl-sip
|
973S6P6: PGW Answer 200 OK without SDP to Update with new SDP Offer.
|
CSCsi96131
|
3
|
ioccsip
|
9.7(3)S6P6 one-way voice after sip blind transfer.
|
CSCsi96137
|
3
|
ioccsip
|
9.7(3)S6P6 one-way voice after sip to sip, then blind transfer to ccm.
|
CSCsj02932
|
3
|
mdl-sip
|
9.7(3):mapgw:extra international prefix + added for forwarding num.
|
CSCsj04760
|
3
|
engine
|
973S7P7 Error log in standby when call connected, no full call in standby.
|
CSCsj04927
|
3
|
engine
|
9.7(3):mapgw:normal forwarding call counts as failed call mml rtrv-ne-heal.
|
CSCsj05027
|
3
|
mdl-pri
|
9.7(3):mapgw:incoming pri call hangs up for msrn with optimized routing.
|
CSCsj05646
|
3
|
mdl-lcm
|
973S6P6: local handling not invoke for ss7 to sip CFU to sip if FAC=2,2.
|
CSCsj12802
|
3
|
mdl-cdr
|
New tariff timer (T2345 ) causes high MCL,v-sol.
|
CSCsj17759
|
3
|
mdl-lcm
|
973S6P6: sip invoke 2543 hold/resume fail for sip -- hsi call.
|
CSCsj28795
|
3
|
engine
|
Disable hairpinning for MGX8260 extnode type,v-sol.
|
CSCsj35824
|
3
|
mdl-sip
|
9.7(3):mapgw: hostname of Route header identifies ITP instead of PGW.
|
CSCsj37558
|
3
|
mdl-analysis
|
Modification applied to b-number is not populated in CDR.
|
CSCsj37775
|
3
|
mdl-callctrl
|
DiversionInfo presents in early ACM if not handle the 302 as Diversion.
|
CSCsj39691
|
3
|
mdl-sip
|
S6P6: IOS formats of Call-Info header for sip-NOTIFY need to generate.
|
CSCsj44948
|
3
|
engine
|
973S7P7: Core Dump when active/standby use different patch version.
|
CSCsj47251
|
3
|
engine
|
PGW BDigitCCrm modification not in CDR tag 4014 when call is retried,v-sol.
|
CSCsj52158
|
3
|
mdl-mgcp
|
973S7P7: RQNT packet changed and caused error response.
|
CSCsj05323
|
4
|
engine
|
973S6P6:request line of INVITE message lost maddr and callside.
|
CSCsf00200
|
6
|
mdl-analysis
|
PGW - Support for individual SIP cause values.
|
CSCsf16085
|
6
|
mdl-lcm
|
H323 to CCM 5.0 call using sip trunk one way voice path.
|
CSCsi10115
|
6
|
mdl-sip
|
Featurette: ITP-Based Gateway MSC on PGW 2200.
|
CSCsi40004
|
6
|
mdl-analysis
|
Featurette: Ring Back Service using CPC=3.
|
CSCOnn006
Patch CSCOnn006 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsi44950
|
2
|
mdl-callctrl
|
PGW releases the call when COT is required and CON is received in response, Mistral.
|
CSCsi48188
|
2
|
mdl-callctrl
|
PGW incorrectly sends cot on previous circuit on iTnT or NBT call leg.
|
CSCsi65205
|
2
|
engine
|
Call rerouting failing over inter-pgw EISUP link,v-sol.
|
CSCsi65367
|
2
|
mdl-mgcp
|
973S6P6: one way voice path for basic SS7 to SIP call.
|
CSCsh70865
|
3
|
mdl-lcm
|
PGW H323 Call rerouting fail by PGW.
|
CSCsh97766
|
3
|
mdl-sip
|
973ST: PGW doesn't answer 200OK to UPDATE.
|
CSCsh99750
|
3
|
mdl-lcm
|
Dynamite:NCT to H323 C side with IVR first failed.
|
CSCsi09948
|
3
|
engine
|
Calls hang up when destinationRoutingAddress for INAP Connect is Invalid.
|
CSCsi10007
|
3
|
mdl-lcm
|
Dynamite: PGW fail to reattempt if incoming is EISUP.
|
CSCsi10098
|
3
|
mdl-sip
|
CCMSIP: pgw sends out two 180 responses when map dpnss name to 180.
|
CSCsi21818
|
3
|
mdl-sip
|
CCMSIP: UPDATE msg (used for RPID refresh) leads pgw to release call.
|
CSCsi21879
|
3
|
mdl-sip
|
SIP: Unsolicited Notify for DTMF relay does not work.
|
CSCsi22300
|
3
|
mdl-sip
|
9.7(3): the behavior of inhibitSipFromMapping = 3 not correct.
|
CSCsi25271
|
3
|
mdl-lcm
|
RO setup in overlap mode fail.
|
CSCsi27128
|
3
|
pgw-restricted
|
CDE 4228 tag length incorrect in pgw.
|
CSCsi28603
|
3
|
mdl-sip
|
973S5P5: One way voice path when Hold/Resume after REFER local handling.
|
CSCsi28821
|
3
|
mdl-sip
|
973S5P5: rel100 wrong handled.
|
CSCsi30335
|
3
|
mdl-sip
|
CCM5SIP: Contact header missing in NOTIFY.
|
CSCsi30692
|
3
|
mdl-lcm
|
SS7 to QSIG across EISUP reroute to QSIG, then iTNT failed.
|
CSCsi31993
|
3
|
mdl-sip
|
973S5P5: Via header wrong constructed when Session Timer expires.
|
CSCsi32387
|
3
|
mdl-sip
|
No RBT in the call from SIP to H323.
|
CSCsi35514
|
3
|
mdl-lcm
|
S5P5: Hold service logic not correct after sw-over.
|
CSCsi40338
|
3
|
engine
|
LI message of Qos Reserve/Release lost when hold/resume a call from SIP.
|
CSCsi41740
|
3
|
mdl-sip
|
S5P5: ACK wrong handled when 1st Invite has no SDP.
|
CSCsi44921
|
3
|
mdl-in
|
Backup trunk is not attempted and RSF is sent to ICM when LChan failed, ddts.
|
CSCsi46443
|
3
|
engine
|
S5P5: Contact header wrongly constructed due to checkpoint.
|
CSCsi53372
|
3
|
mdl-callctrl
|
PGW send a subsequent COT after the IAM without Cot Ind.
|
CSCsi54759
|
3
|
mdl-lcm
|
noAnswer Timer does not work for IN call.
|
CSCsi65231
|
3
|
mdl-eisup
|
One way voice when invoke hold to HSI across EISUP.
|
CSCsi68630
|
3
|
mdl-analysis
|
PGW using cause analysis the outgoing B number is not refresh correct.
|
CSCsi69318
|
3
|
mdl-lcm
|
Delayed continuity message causes call failure.
|
CSCsi78345
|
3
|
mdl-lcm
|
PGW disconnects the call with Leg1StateError.
|
CSCsi80247
|
3
|
mdl-ni2
|
973S6P6 No RBT in QSIG--PGW--SIP(183).
|
CSCsi81728
|
3
|
mdl-lcm
|
PGW does not close TCAP dialog when release is received soon after IAM.
|
CSCsi16705
|
4
|
sim
|
Resolve sim failure in 973 for CSCsh92671.
|
CSCsi26925
|
4
|
sim
|
sinap sim file for memory reduction didn't set memory reduction flag.
|
CSCsi27216
|
4
|
sim
|
Branch 9.7 head SIM files fail.
|
CSCsg66853
|
6
|
mdl-sip
|
Code re-organization for SIP mdl.
|
CSCsh57584
|
6
|
design
|
PGW to remove RN when presentation indicator = restricted.
|
CSCsi31034
|
6
|
mdl-sip
|
New InhibitSipFromMapping value.
|
CSCOnn005
Patch CSCOnn005 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsi32487
|
2
|
mml
|
S5P5:CSCsi10098, CSCsh57584 shall not be included.
|
CSCsh65911
|
3
|
engine
|
9.7(3)LTG: no li message send to MD when overlap time out .
|
CSCsh69205
|
3
|
mdl-sip
|
973EFT: PGW not associate 200 OK (to ReInvite and BYE) to call.
|
CSCsh77445
|
3
|
engine
|
No Qos LI msgs sent in sip->ss7 CFB->h323, PGW_LI.
|
CSCsh90540
|
3
|
mdl-in
|
CNM: IAM with GN, NOA is not "Unique or non-unique national number".
|
CSCsh90993
|
3
|
mdl-mgcp
|
MGCP statistics in DLCX ack parsing failed because CDR tags empty.
|
CSCsh96775
|
3
|
mdl-eisup
|
CNM:SS7-SIP EISUP call failed if IAM GN is not calling name and w/o char.
|
CSCsh97891
|
3
|
mdl-sip
|
973ST: PGW does not reject INVIET w/ To Tag if no <>.
|
CSCsh99467
|
3
|
mdl-sip
|
S4P4-ST: PGW rejects the INVITE with tel URI P-Asserted-Id header.
|
CSCsi03178
|
3
|
mdl-in
|
ST-CNM:TcapTimer is still sent from engine to mdl if Remote SSN is OOS.
|
CSCsi13492
|
3
|
mdl-sip
|
9.7(3)IXS:call cannot rel from SIP side after it meets 4XX error of MGCP.
|
CSCsi19891
|
3
|
mdl-sip
|
The second callhold message was not mapped after the first rejected.
|
CSCsi25546
|
3
|
mdl-analysis
|
P1 605650493 /Digits lost if B number provisioned with ANN in overlap.
|
CSCsi00174
|
4
|
mdl-sip
|
B2BUA: Via headers incorrect when internal release generates BYE.
|
CSCsb56422
|
6
|
mdl-sip
|
SIP and ISUP Interworking for Call Hold and Terminal Portability, Featurette.
|
CSCsg36734
|
6
|
ioccli
|
LI based on trunk group.
|
CSCsh71021
|
6
|
mdl-sip
|
PGW : Special property name for satellite_circuit_in_connection support., v-sol.
|
CSCsh92671
|
6
|
mdl-callcontext
|
Dynamite: Support routing call to alternate location for IDP failure.
|
CSCsi06627
|
6
|
ioccli
|
PGW: Treat hairpin call as non-hairpin if LI enabled.
|
CSCOnn004
Patch CSCOnn004 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsh54810
|
3
|
mdl-sip
|
Route header wrong constructed if pgw receives individual route headers.
|
CSCsh62249
|
3
|
mdl-analysis
|
NPI modification is lost when entering a new dial plan, v-sol.
|
CSCsh69057
|
3
|
mdl-lcm
|
oMin/oMax don't work in enbloc-enbloc call mode.
|
CSCsh69078
|
3
|
mdl-analysis
|
After reanalysis, overlap-overlap call fails when longest match disabled.
|
CSCsh77498
|
3
|
mdl-lcm
|
NBT to H323 side failed due to mgcp getting 527 response.
|
CSCsh77605
|
3
|
mdl-lcm
|
Dynamite:RSF reported instead of oAbandon when originating expires early.
|
CSCsh83802
|
3
|
mdl-lcm
|
Dynamite: If memory reduction enabled, the iTNT/NBT call fails.
|
CSCsh92615
|
3
|
mdl-in
|
The CNAM service uses RR item conflict with Dynamite in IN module.
|
CSCsh92779
|
4
|
mdl-sip
|
Detection of unexpected To: tag in INVITE not sending 481.
|
CSCsc56989
|
6
|
other
|
Calling Name Delivery (CNAM) Featurette.
|
CSCOnn003
Patch CSCOnn003 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsg59929
|
3
|
mdl-sip
|
973ST: SIPA-SS7B, transfer SIPA to SIPC, sw-over, SIPC cannot release call.
|
CSCsh33306
|
3
|
mdl-sip
|
PGW does not send ACM backwards on expiry of T_oiw1,TP303008, H00123.
|
CSCsh36296
|
3
|
mdl-sip
|
Change INFO mapping to INFO-INFO in b2bua mode.
|
CSCsh46559
|
3
|
mdl-lcm
|
PGW: 9.7(3): Codec preferential routing, v-sol.
|
CSCsh54405
|
3
|
mdl-sip
|
9.7(3)S2P2 SIP TCC should reject the FAX Re-Invite directly.
|
CSCsh54572
|
3
|
design
|
No MDCX message sent out after receiving 200 OK when cutthrough at 183.
|
CSCsh60643
|
3
|
mdl-sip
|
973EFT: SIP to EISUP, From: anonymous is not map to CLIR.
|
CSCsh64193
|
3
|
mdl-lcm
|
PGW does not re-route the Call after o_NoAnswer timeout.
|
CSCsh67457
|
3
|
mdl-mgcp
|
973ST: NCT failed with cause code 51 due RSF.
|
CSCsg42352
|
6
|
mdl-lcm
|
SIP From Interworking with SS7 & PRI (change request), featurette.
|
CSCsg49496
|
6
|
mdl-sip
|
Support of Trunk Group Id at the x-route-tag / tsp parameter, featurette.
|
CSCsh18492
|
6
|
gtd
|
Map value of GPD/GED to GTD message.
|
CSCsh39226
|
6
|
mdl-lcm
|
PGW report the failure to ICM until exhausting all the possible resource.
|
CSCsh43254
|
6
|
mdl-lcm
|
Support ICM Network Blind Transfer.
|
CSCsh58920
|
6
|
mdl-lcm
|
Support B number string modification for intelligent blind transfer.
|
CSCOnn002
Patch CSCOnn002 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsg81520
|
2
|
upgrade
|
973ST Upgrade: SIP calls cannot be checkpointed correctly due to B2BUA.
|
CSCsh24412
|
2
|
engine
|
Wrong call match if pgw change username and no Route-tag in RequestLine.
|
CSCsg59929
|
3
|
mdl-sip
|
973ST: SIPA-SS7B, transfer SIPA to SIPC, sw-over, SIPC cannot release call.
|
CSCsg61816
|
3
|
mdl-sip
|
PGW does not cancel the call to C-party in SSCT when A-party cancels the call.
|
CSCsg99242
|
3
|
mdl-sip
|
Hold after Blind Transfer fail.
|
CSCsg99265
|
3
|
mdl-sip
|
PGW sends out SDP with only "a=recvonly" included after sw-over.
|
CSCsg99278
|
3
|
mdl-sip
|
Resume after Hold failure leads call to release.
|
CSCsh37947
|
3
|
mdl-sip
|
973EFT: PGW send wrong RN NOA when mapping SIP 302 with digit leading +.
|
CSCsh42699
|
3
|
mdl-sip
|
973EFT: PGW mapping to wrong SIP From header when cgpninclude=1.
|
CSCsh46871
|
3
|
mdl-sip
|
PGW: The Route header handling in 9.7(3) is incorrect.
|
CSCsh55987
|
3
|
mdl-sip
|
973ST: from 961 to 973 upgrade PGW sends out BYE w/ empty Call-ID.
|
CSCsh57658
|
3
|
mdl-sip
|
Branch value is invalid in Via header for SIP INVITE message.
|
CSCsg38811
|
6
|
provision
|
Enhanced LNP and Dialplan Selection Featurette, Featurette.
|
CSCOnn001
Patch CSCOnn001 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsh24412
|
2
|
engine
|
Wrong call match if pgw change username and no Route-tag in RequestLine.
|
CSCsd63700
|
3
|
mdl-analysis
|
BCMOD does not work in overlap scenario.
|
CSCsg46838
|
3
|
mdl-sip
|
973ST: SIP-EISUP call, from EISUP transfer to SIP failed.
|
CSCsh33182
|
3
|
mdl-callctrl
|
Resolve the conflicts for feature Dynamite.
|
CSCsh39350
|
4
|
sim
|
Resolve sim failure after dynamite collapse.
|
CSCse99755
|
6
|
mdl-callctrl
|
Feature: Dynamite, intelligent blind Xfer and consultative Xfe.
|
CSCOgs028
Patch CSCOgs028 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCta91465
|
3
|
engine
|
Engine core on standby PGW
|
CSCta92433
|
3
|
mml
|
9.7(2)S25P25: delete crptmesg doesn't make relativity check with result
|
CSCta98306
|
3
|
mml
|
PGW 9.7(3) fails to edit descripton for EISUPPATH, MGCPPATH, SS7PATH,v-sol
|
CSCtb10143
|
3
|
procm
|
9.7(3):pom coredump
|
CSCtb16406
|
3
|
engine
|
PGW 9.7(3) opteron linexlate provisioning not working properly
|
CSCtb81681
|
3
|
engine
|
releasing call not finding codec on the egress side, while configured,v-sol
|
CSCOgs027
Patch CSCOgs027 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCta22655
|
2
|
iocm
|
973S24P24: ioChanMgr cored dump while adding Radius configuration
|
CSCta32512
|
2
|
engine
|
973: Engine cored dump while load traffic after remove the Radius config
|
CSCta41685
|
2
|
ioccsip
|
9.7(3)S26P26:SIP coredump when sip-route-v-sipuri overflow in ACK messag
|
CSCsz45274
|
3
|
install
|
9.7(3)S24: mgcTTmigrate error
|
CSCsz81362
|
3
|
iocm
|
Component can't be found error when execute "prov-cpy"
|
CSCsz82804
|
3
|
engine
|
set-admin-state:xxxx:reset,confirm MML command may lead to stuck CIC,v-sol
|
CSCta56038
|
3
|
install
|
973S26P26: OPERSAGT failed to start in new installed PGW
|
CSCta61704
|
3
|
mml
|
EISUP SIGPATH can not be deleted by mml
|
CSCtb04634
|
4
|
sim
|
simWriter core dumps when you have to many dialplans
|
CSCsz23314
|
6
|
engine
|
send SERVICE message out on set-admin-state::lock
|
CSCsz26512
|
6
|
measm
|
9.7(3): PGW enhancement to send CDB 1071 for PRI trunk groups
|
CSCtb17893
|
6
|
sim
|
simWriter support debug output
|
CSCOgs026
Patch CSCOgs026 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsz38202
|
2
|
mdl-pri
|
973S24: PRI AOC get wrong tariff table in opteron platform
|
CSCsz63108
|
2
|
engine
|
9.7(3)S25:engine core dump when sdp filed contain more ascii
|
CSCsz82836
|
2
|
mdl-lcm
|
CIC stuck in CALL=IN when call released while awaiting MGCP 200 OK,v-sol
|
CSCta22210
|
2
|
engine
|
9.7(3)S26P26:engine coredump when integer overflow in sdp media param
|
CSCsy42827
|
3
|
replicator
|
replicator,pom core dump on 9.7(3)
|
CSCsz40730
|
3
|
engine
|
9.7 core engine.smartallo with Radius,v-sol
|
CSCsz52134
|
3
|
mml
|
enlarge the constraint of cliprefix in one cliset from 10 to 1000
|
CSCsz94653
|
3
|
mdl-pri
|
Re-route may fail on TDM-TDM hairpin if SDP is different
|
CSCta17303
|
3
|
engine
|
PGW engine core and fails over,v-sol
|
CSCta37341
|
3
|
mdl-sip
|
SIP peer does not suport 100rel (no Provisional Response support)
|
CSCta44189
|
3
|
mdl-cdr
|
9.7(3): Empty value for CDR Tag 3001
|
CSCta44450
|
3
|
toolkit
|
SimWrite stops with errors message
|
CSCsv78723
|
6
|
engine
|
Enhancement of Usability
|
CSCsz44785
|
6
|
engine
|
Enhancement of per-call-trace for featurette "Incoming IP Trunk"
|
CSCsz62864
|
6
|
ioccsip
|
Include the SUSPEND/Network message as well as SUSPEND/Subscriber messa
|
CSCta25117
|
6
|
toolkit
|
9.7(3)S26P26: Toolkit enhancement for CDR ie display
|
CSCta44108
|
6
|
engine
|
9.7(3)S26P26: enlarge Display name length and dump it in CDE 4079
|
CSCOgs025
Patch CSCOgs025 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsy89074
|
2
|
ioccsip
|
9.7(3)S24P24:sip coredump when sip header "via" contain more ascii
|
CSCsw78251
|
3
|
replicator
|
9.7(3)S21P21: sw over back failed because of MSO refused,v-sol
|
CSCsx06018
|
3
|
install
|
973S22:dialplan are not converted when opteron PGW is up in liveupgrade
|
CSCsy39344
|
3
|
engine
|
9.7(3)S23P23:retreive call info detaill will coredump when run Codenomic
|
CSCsy76445
|
3
|
alrmm
|
Removed sessionsets create cosmetic GEN_ERR_UNKN_COMPID error message,v-sol
|
CSCsz00532
|
3
|
engine
|
pgw didn't release the call if no matched codec
|
CSCsx16398
|
6
|
design
|
Featurette Call Reporting,
|
CSCsx75893
|
6
|
protocol
|
Override the called number with the CPN in the MIME of the INVITE
|
CSCsx78511
|
6
|
ioccli
|
drop other number modifications when FNT is successfully
|
CSCsy48581
|
6
|
mml
|
PGW should support prefixes on SIP trunk groups
|
CSCsz00283
|
6
|
mml
|
9.7(3)P20:Multiple mml sessions operation will lead pgw core dump
|
CSCOgs024
Patch CSCOgs024 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsx60980
|
2
|
provision
|
PGW 9.7.3P20 ISDNL3 core dumps due to provisioning,v-sol.
|
CSCsy81415
|
2
|
other
|
973S24: pom coredump during supercell testing.
|
CSCsv51211
|
3
|
mml
|
Fullnumber translation - DB lookup fails.
|
CSCsx45987
|
3
|
iocm
|
PGW9.7(3)P17 cores with ioChanMgr,v-sol.
|
CSCsx46629
|
3
|
ioccli
|
PGW incorrectly formats Radius Event Message for LI Call_Answer.
|
CSCsx55722
|
3
|
snmp
|
The counter tpCALLLabelRejTOT doesn't show number of failed calls.
|
CSCsx99967
|
3
|
ioccsip
|
SIP IOCC core dump due to race condition between icmp and timer thread,v-sol.
|
CSCsy03667
|
3
|
engine
|
R digit modification should be possible when redirecting number analysis.
|
CSCsy38671
|
3
|
ioccisdnl3
|
973: ISDNBRI does not support Opteron platform.
|
CSCsu68575
|
4
|
mml
|
Nonsense warning when provision MML gwdefaultcodecstring.
|
CSCsv80617
|
6
|
design
|
PGW CODEC Preference handling for Reinvites / MDCX.
|
CSCsw47810
|
6
|
mdl-callctrl
|
Support different Call-ID for partial B2BUA mode.
|
CSCsx49298
|
6
|
ioccli
|
HUCS LI and PGW Radius Event message, incorrect A number in Radius.
|
CSCsy50232
|
6
|
mdl-dpnss
|
3845 HWIC1 slot is not support by PGW dpnss connection.
|
CSCsy70898
|
6
|
performance
|
Queue length MCL on X4600 Quadcore SIP - SIP traffic.
|
CSCOgs023
Patch CSCOgs023 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsx49567
|
2
|
iocceisup
|
EISUP link can't be recovered to IS due to network packet loss.
|
CSCsw16902
|
3
|
mmlhelp
|
PGW profile ISUPTMRPROFILE have wrong variant mml help in Q761_BASE.
|
CSCsw42239
|
3
|
ioccc7
|
9.7(3)S16: byte-order issue in rudp debug log of SS7.
|
CSCsw42479
|
3
|
iocceisup
|
9.8(1)MCP: after swoveriplnk between PGW and HSI cannot become "IS".
|
CSCsw45342
|
3
|
engine
|
Log level cannot recover even MCL3 if set all components to debug.
|
CSCsw48009
|
3
|
engine
|
9.7(3) IPinmapping replies from wrong port.
|
CSCsw79851
|
3
|
other
|
config-db: TT Permsize max limit should be 12G for 70M data support.
|
CSCsx06385
|
3
|
measm
|
No SIP measurements after sw-over sometimes, v-sol.
|
CSCsx57841
|
3
|
iocceisup
|
EISUP RUDP need more DEBUG level logs.
|
CSCsw82209
|
4
|
mdl-tools
|
ca-tool is not showing date/time of the calls in the MDL trace, v-sol.
|
CSCsw74049
|
6
|
mdl-sip
|
Correct sim errors in CSCsv65839 and add some sim for CSCsv84586.
|
CSCOgs022
Patch CSCOgs022 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsw50610
|
2
|
measm
|
9.7(3)S21: measMgr sometimes will coredump when the standby PGW is up.
|
CSCsv04219
|
3
|
engine
|
Call match fail for 2 quick incoming INVITE or UPDATE after 1xx.
|
CSCsv25679
|
3
|
engine
|
PGW Alarm OverloadHeavy on Standby after failover, v-sol.
|
CSCsv29334
|
3
|
mdl-pri
|
No NSF found in SETUP for ATT41495_C2 variant.
|
CSCsv31731
|
3
|
provision
|
Spansize option missing in the nailedtrnk component.
|
CSCsv33895
|
3
|
mdl-sip
|
9.7(3) Ipinmapping replies from wrong port and wrong domain in RR.
|
CSCsv44880
|
3
|
ioccsip
|
No Timestamp header appears in 100 (Trying) response.
|
CSCsv54856
|
3
|
other
|
config-db project.max-shm-memory not persistent after reboot.
|
CSCsv84945
|
3
|
iocm
|
Ipinmap configurations failed to pass to iocc.
|
CSCsv90949
|
3
|
flovr
|
ALM=\"Peer Config Mismatched\ for ipinMapping.dat, v-sol.
|
CSCsv97013
|
3
|
mdl-q767
|
9.7(3) PGW Italian Q767 variant doesn't support RDN, OCN.
|
CSCsw17159
|
3
|
provision
|
Error during deleting a dial plan.
|
CSCsw21134
|
3
|
ioccc7
|
9.7(3)S16:SS7 coredump when load test and set log level=debug.
|
CSCsw26588
|
3
|
upgrade
|
97(3):migration issue about export_trkgrp.dat.
|
CSCsw36200
|
3
|
iocceisup
|
9.7.3P17 - EISUP process 100% cpu utilization, v-sol.
|
CSCsw42108
|
3
|
other
|
9.7(3)S21 default value of property ItpActionRequest not consistent.
|
CSCsw77355
|
3
|
ioccc7
|
SS7 cores on STANDBY PGW in 9.7(3) on prov-dply after provisioning, v-sol.
|
CSCsv72283
|
6
|
mdl-q761
|
New Zealand need IAM sent with Redirect Counter > 5.
|
CSCsv84586
|
6
|
mdl-callctrl
|
Support to disable SIP/H.323 initiated hold to CPG interworking.
|
CSCOgs021
Patch CSCOgs021 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsv99130
|
2
|
engine
|
PGW 9.7(3)P19 Engine SIGSEGV in setupGlareCall.
|
CSCsw21134
|
3
|
ioccc7
|
9.7(3)S16:SS7 C7Link congestion caused memory exhaustion and coredump.
|
CSCOgs020
Patch CSCOgs020 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsv75074
|
2
|
mml
|
Property CGPN included in properties.dat is false formatted.
|
CSCsv81830
|
3
|
provision
|
Validation error when prov-ed an ipfaspath.
|
CSCsv65839
|
6
|
design
|
PGW-SIP-DPNSS causing 491.
|
CSCOgs019
Patch CSCOgs019 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsu61833
|
2
|
ioccc7
|
Standby is struck in OOS when provision from new.
|
CSCsu76015
|
2
|
ioccc7
|
TIOS_ERR_RUDP_BUF_TOO_LARGE: Buffer too large in rudp_send().Received 23.
|
CSCsv04315
|
2
|
engine
|
Hung Proc in map results in call failing.
|
CSCsv50918
|
2
|
engine
|
973S19P19: Engine core dump on standby when doing NCT after NCT.
|
CSCsv06585
|
2
|
upgrade
|
PRI Tariff Table get lost after migration.
|
CSCsv06659
|
2
|
design
|
S19P19: need a default value for the mdo on eisuppath.
|
CSCsr60001
|
3
|
replicator
|
973S17:slave PGW sticks in oos when master pgw re-config eisup.
|
CSCsu39537
|
3
|
engine
|
973S16:kill-call with cid is failed.
|
CSCsu46708
|
3
|
sua
|
973P18: no SUA message sent for 800 when both LNP and 800 service added.
|
CSCsu48977
|
3
|
snmp
|
snmpget cannot measurements on Opteron.
|
CSCsu58962
|
3
|
mdl-q761
|
PGW unrecognized message/Parameter issue for exchange type A.
|
CSCsu62031
|
3
|
engine
|
rtrv-tc:all failure after blk-cic.
|
CSCsu96355
|
3
|
mml
|
numan-rtrv shows Incorrect NPI Block.
|
CSCsv14242
|
3
|
engine
|
CIC stuck in block state after enable hardware block and run blk-cic.
|
CSCsu46844
|
4
|
mdl-cdr
|
9.7(3)S18: In CDR, cause code not consistency with REL cause code 18.
|
CSCsj08981
|
6
|
mdl-callctrl
|
Dynamite Enhancement: Support NCT after NCT completion.
|
CSCOgs018
Patch CSCOgs018 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsu09711
|
2
|
engine
|
BTNUP message trigger Engine "kill ghost call".
|
CSCsu37433
|
2
|
mdl-eisup
|
Calls released when DPNSS call is diverting from pgw9.7 to pgw9.6, ipngn-huc2-pgw.
|
CSCsu79291
|
2
|
engine
|
973S18:engine coredump when do EISP call transfer service.
|
CSCsr21742
|
3
|
sua
|
973S15P15: rtrv-rssn after prov-dlt, prov-add is not accurate.
|
CSCsr24778
|
3
|
procm
|
973S16P16: Error log of ProcessManager caused by failure of finding tid.
|
CSCsr62413
|
3
|
mdl-tools
|
mgcTTmigrate permission denied.
|
CSCsr75948
|
3
|
toolkit
|
CDR Tag 4244 4245 in 1030 CDB cannot be shown in MGC_Toolkit.
|
CSCsr95646
|
3
|
engine
|
blk-cic doe not work correctly for some values of rng parameter.
|
CSCsq58094
|
6
|
enhancement
|
PGW Performance Enhancement on Call Processing and Provision.
|
CSCsr95475
|
6
|
mml
|
Enable non-interactive mml command-line on 97.
|
CSCOgs017
Patch CSCOgs017 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsq90783
|
2
|
performance
|
Multiple MGCP NOTIFY in short time cause memory leak.
|
CSCsr11511
|
2
|
mml
|
numan-cnvt:dialplan:"all" not generating dial plan bin files on opteron.
|
CSCsr30588
|
2
|
mdl-eisup
|
9.7(3)S15:EISUP parameter 169 should remain in PGW-H323.
|
CSCsr48289
|
2
|
flovr
|
Standby PGW POM core dump when active import mml for the first time.
|
CSCso25108
|
3
|
snmp
|
hostagt may consume high cpu.
|
CSCso94682
|
3
|
mml
|
The command "mml&" exhausts CPU resource.
|
CSCsq88394
|
3
|
provision
|
973S15:POM coredump when do switch-over sometimes.
|
CSCsr10768
|
3
|
provision
|
PGW973: Full num trans does not support over-decadic.
|
CSCsr13114
|
3
|
mml
|
973S15P15: Dial plan Error will repeat twice.
|
CSCsr43179
|
3
|
ioccm3ua
|
M3UA dest cannot be IS if ASPAC_ACK did not include routing context.
|
CSCsr44976
|
3
|
sccp-tcap
|
PGW can not parse TCAP messages with tag in extended format.
|
CSCsr55518
|
3
|
mml
|
973S17P17: Alarm for Pair Configuration Mismatched printed incorrectly.
|
CSCsm99233
|
4
|
provision
|
Redundant failure response messages after POM session close.
|
CSCsq83187
|
4
|
sun-tools
|
Wrong description while executing the .create_liusr script to add liusr.
|
CSCsr11568
|
4
|
mml
|
Incorrect text prompt for numan-cnvt.
|
CSCsl64508
|
6
|
provision
|
POM coredump when keep doing provision.
|
CSCso49604
|
6
|
install
|
Live upgrade from 9.6 Sparc to 9.7 Sparc & Opteron.
|
CSCsq77467
|
6
|
mdl-lcm
|
UUIE protocol discriminator configurable for some SS7 variant.
|
CSCsq83084
|
6
|
mml
|
Raise an alarm when configuration on active and standby not the same.
|
CSCOgs016
Patch CSCOgs016 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsr03189
|
2
|
mdl-eisup
|
9.7(3)S15:EISUP parameter 169 should remain in PGW-H323.
|
CSCOgs015
Patch CSCOgs015 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsj50238
|
2
|
mml
|
9.7(3)S7P7:mml core dump.
|
CSCso80413
|
2
|
provision
|
HU:PGW indicates provisioning successful but it is, in fact, missing on PGW, HUCS51BMR1.
|
CSCsq28577
|
2
|
replicator
|
9.7(3)P15: Coredump found at supercell automation.
|
CSCsq63769
|
2
|
ioccli
|
Wrong mapping of PGW cause codes to "CableLabs-Call-Termination-Cause".
|
CSCso06216
|
3
|
sccp-tcap
|
9.7(3):S13:lot of invalid sccp-tcap error log prompt in platform.log.
|
CSCso80165
|
3
|
ioccisdn13
|
ISDNL3 stuck in loop looking for invalid DChan componentId, v-sol.
|
CSCso89245
|
3
|
replicator
|
Porting:PGW core on global resource finalization race cond. multithread, v-sol.
|
CSCso91807
|
3
|
ioccisdn13
|
Dual switchover - ISDNL3 Coredump when switchover happened.
|
CSCso92182
|
3
|
ioccsip
|
973S14P14: PGW Cannot Handle TCP SIP Msg with Msgbody in Multi Packets.
|
CSCso94779
|
3
|
mdl-analysis
|
Route analysis tables are not deleted when ntRouter destruction.
|
CSCsq38172
|
3
|
sun
|
libxml2 vulnerability, psirt.
|
CSCsq60495
|
3
|
mdl-sip
|
PGW need to be able to handle Invite from Linksys with ref=,v-sip.
|
CSCso14089
|
6
|
mdl-sip
|
SIP overlap support.
|
CSCso81973
|
6
|
mdl-lcm
|
SIP/NI Calling Name to Q931+ Display I.E.
|
CSCOgs014
Patch CSCOgs014 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsl56671
|
2
|
provision
|
Standby PGW stuck in OOS while prov-dply SS7 configurations.
|
CSCsm45581
|
2
|
ioccsip
|
973s13p13: sip error byte order cause trunk mapping error.
|
CSCsm92603
|
2
|
iocceisup
|
SIP message with big SDP can not send out through EISUP.
|
CSCso06080
|
2
|
mdl-in
|
9.7(3)P13: TCAP cannot send out CANM query due to reach max dialogue.
|
CSCsl45478
|
3
|
sun
|
973S11P11: Core dump of POM when making calls and sw-over.
|
CSCsm04272
|
3
|
provision
|
Siptool mess message display.
|
CSCsm41418
|
3
|
ioccsip
|
9.7(3)S13: SIP LINK PRI value more than 2 cause SIP LINK failure.
|
CSCsm51940
|
3
|
engine
|
Multi-core load balance issue in performance test.
|
CSCsm86784
|
3
|
iocm
|
ioSigPath_MGCP does not handle s_setFOOS signal in "SP:Waiting Eng".
|
CSCsm94267
|
3
|
mml
|
Percentage route deleting not checked reference, v -sol.
|
CSCsm94647
|
3
|
mml
|
The behavior of "rtrv-cic:ss7svc1:cic=65535" is not correct.
|
CSCso01954
|
3
|
provision
|
Cannot add IP link when other IP links exist.
|
CSCso06120
|
3
|
provision
|
9.7(3)S13:InService CNAM SCCP addressing method is lost after reload PGW.
|
CSCso06218
|
3
|
other
|
Collectdata script execution error.
|
CSCso27920
|
3
|
sim
|
PGWSimWriter does not work correctly while traversing the anumdpsel-Table, v-sol.
|
CSCso42248
|
3
|
replicator
|
Cutoff timer expiring on Standby&sw-over make hung call in replicator.
|
CSCso44122
|
3
|
sun
|
Querying link status of ce virtual interface returns invalid argument.
|
CSCsj76125
|
6
|
sun-tools
|
9.7(3): update on PGW Data Collection script = collectdata, v-sol.
|
CSCsk84431
|
6
|
engine
|
Add pstack information into the platform.log once process core dump.
|
CSCsl96209
|
6
|
mdl-sip
|
Mapping cic parameter in SIP message to ISUP TNS.
|
CSCsm96641
|
6
|
mdl-sip
|
PGW: 9.7(3) CallHoldInterworkingEnabled property cannot change on EISUP, v-sol.
|
CSCso52019
|
6
|
provision
|
Update PGW data collection scripts with global variable and description.
|
CSCOgs013
Patch CSCOgs013 resolves the following caveats:
Identifier
|
Severity
|
Component
|
Description
|
CSCsk45882
|
2
|
iocm
|
973s9p9r2: standby iocm oos with IP recovery after network outage.
|
CSCsl72148
|
2
|
mdl-tools
|
973S11:get_trc.sh core dump happens when stop "m" action.
|
CSCsl90356
|
2
|
sccp-tcap
|
Trillium stops sending TCAP messages after a few weeks.
|
CSCsm14213
|
2
|
ioccsip
|
SIP IOCC enhancement for overload control.
|
CSCsm19336
|
2
|
engine
|
Engine and sip core dump.
|
CSCsm23239
|
2
|
iocm
|
PGW sets IP route M-OOS after few up and down of one interface.
|
CSCsl27950
|
3
|
mml
|
Dchan sigport range error.
|
CSCsl49411
|
3
|
procm
|
973S11:multiple MEGACO/M3UA processes exist in Active/Standby side.
|
CSCsl64720
|
3
|
