Guest

Cisco PGW 2200 Softswitch

Release Notes for the Cisco Media Gateway Controller Software Release 9.2(2)

  • Viewing Options

  • PDF (1.1 MB)
  • Feedback
Release Notes for the Cisco Media Gateway Controller Software Release 9.2(2)

Table Of Contents

Release Notes for the Cisco Media Gateway Controller Software Release 9.2(2)

June 25, 2007

Contents

Introduction

Platform Support

Software Required

Required Swap Space

Host Hardware Requirements

Host Minimum Server Requirements

Media Gateway Hardware Requirements

Local Area Network Switch

Supported Features

Cisco MGC Management

Media Gateway Management

Cisco Signaling Link Terminal Management

Switching Protocols Supported

Related Documentation

Before Installation

After Installation

General Purpose Documents

Documentation Map

Installation Notes

Acquiring the Software

Installing and Upgrading the Software

Determining Which Protocol Patches/Families Are Installed On Your System

Determining Your System's Patch Level

New Features in This Release

32 Digit Support in Q.761 Korean ISUP

Seamless Upgrade

Derived FCI and BCI for Interworking

B-Digit Modification Enhancement

No SAM Sent in Hong Kong ISUP

Allow Multiple PCIs In All Protocols

NOA Cause14 32 Digit and Overdecadic for Spain/Italy/Belgium Featurette

NOA Cause14 32 Digit and Overdecadic for Spain/Italy/Belgium Featurette

BTNUP 3.1 KHz Custom Configuration

Software Inventory Control

Software Inventory Control Feature Modification

LNP Enhancements to Q.761_Portugal Protocol

Q767_Singapore.mdo File Created

Payphone Indicator From A-Number Analysis

Country Code Prefix Per Trunk Group Capability

German ISUP 32 Digit Support

Generic Transparency Descriptor Nature of Address Override

VSC3000/SC2200 Code Reference

Automatic Backup Utility

Protocol Packaging

Peruvian ISUP Timer Adjustment

Thailand ISUP with Generic Transparency Descriptor

BT UK ISUP Enhancements

New Version of Times Ten Database Software

Option 1

Option 2

Change to Install Script

Solaris 8 Revision Upgrade

New Cause Code for Call Re-Attempts

Features from Release 9.2(1)T

Time Conditional Routing

Redirecting Number CLI Screening Within a Digit Analysis

Austrian ISUP V2

Mid-Call DTMF Relay for HSI

Dual Ethernet and 4-Link SLT Support

Solaris 8 Support

Protocol Patches

Before Installing a Patch

System Level Equivalency

Patch Test Combinations

CSCOnn045

CSCOnn044

CSCOnn043

CSCOnn042

CSCOnn041

CSCOnn040

CSCOnn039

CSCOnn038

CSCOnn037

CSCOnn036

CSCOnn035

CSCOnn034

CSCOnn033

CSCOnn032

CSCOnn031

CSCOnn030

CSCOnn029

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

CSCOgs043

CSCOgs042

CSCOgs041

CSCOgs040

CSCOgs039

CSCOgs038

CSCOgs037

CSCOgs036

CSCOgs035

CSCOgs034

CSCOgs033

CSCOgs032

CSCOgs031

CSCOgs030

CSCOgs029

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

Supported SS7 Variants and ISUP Transparencies

Known Issues and Operational Recommendations

Installation Patch Tool Removes Packages Before Checking to See If The System Is Down

Using prov-cpy/prov-sync To Commit Configuration Changes on a Fault-Tolerant System

Do Not Use TimesTen Commands in PGW

Modifying the OPC of an SS7 Route

Migration of Dialplans Failed From 7.4(x) to 9.2(x)

CPU Timer Interval Is Not Disabled If CPUTimerInterval Parameter Is Set To 0

Do Not Use the ifconfig UNIX Commands to Shut Down Ethernet Interfaces

Conditional Routing Name Validation

Network Redundancy Between Dual Homed PGW and Single Homed NAS

Suppress CLIDigits Parameter Cannot Be Provisioned on EISUP Trunk1

Switchover Might Take Five to Ten Minutes After Bringing Hme Interfaces Down

Support for Individual IOCC logPrio in XECfgParm.dat

2651 Approved for Use In the PGW 2200

2611s SLTs

Caveats

Resolved Caveats for Software Release 9.2(2)

Open Caveats for Software Release 9.2(2)

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Contacting TAC by Using the Cisco TAC Website

Contacting TAC by Telephone


Release Notes for the Cisco Media Gateway Controller Software Release 9.2(2)


June 25, 2007

These release notes describe the features and caveats for the Cisco media gateway controller (MGC) software Release 9.2(2).


Note The Cisco MGC Software was formerly called the Cisco Telephony Controller software. Some documentation might use this older name.


Contents

Introduction

Platform Support

Supported Features

Switching Protocols Supported

Related Documentation

Installation Notes

Determining Which Protocol Patches/Families Are Installed On Your System

Determining Your System's Patch Level

New Features in This Release

Features from Release 9.2(1)T

Protocol Patches

Patch Test Combinations

Known Issues and Operational Recommendations

Caveats

Obtaining Documentation

Obtaining Technical Assistance

Introduction

Interoperability between the old world TDM (Time Division Multiplexing) networks and the new world packet networks is an essential part of the technology adoption life cycle for packet networks. This release of the Cisco PGW 2200 PSTN Gateway provides the bridge between the legacy public switched telephone network (PSTN) and next-generation packet networks - supporting SS7 interconnect for dial and H.323 and SIP networks and intelligent call control and routing for media gateway control protocol (MGCP), session initiation protocol (SIP) and H.323 networks.

The Cisco PGW 2200 provides a consistent and unified interconnection that can handle dialup services, MGCP, SIP, and H.323, as well as future standards. The PGW 2200 allows service providers to deploy and operate multiple network solutions while maintaining a stable interconnection to the PSTN.


Note The Cisco SS7 Interconnect for Voice Gateways 2.0 solution supports the transport of messages between different ISUP variants, except in specific cases where countries have developed variants outside of international standards.


Platform Support

For a list of supported platforms refer to the following documents:

Cisco Media Gateway Controller Hardware Installation Guide
Chapter 1, Table 1-1, Cisco MGC Host Configurations, at the following url:
http:///univercd/cc/td/doc/product/access/sc/rel7/hrdwrnst/index.htm

Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
(Chapter 1) at the following url:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/swinstl/index.htm.

Software Required

For a list of required software, refer to Chapter 1 of the Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide at the following url:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/swinstl/index.htm.

Required Swap Space

For the Cisco MGC 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, you should use the top command in UNIX to see how much swap space is being used; you should then decide if more is needed. You can use the MML command rtrv-ne-health to obtain information from the UNIX top from within MML.

Host Hardware Requirements

Host Minimum Server Requirements

Refer to the Cisco Media Gateway Controller Hardware Installation Guide 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 1 lists URLs for release notes that document media gateways.

Table 1 Media Gateway Release Notes Locations

Media Gateway Release Notes
Release Notes Location

MGX8260 (for Cisco SS7 PRI Grooming Application)

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8260/rel1_2/relnotes/120rn826.htm

VISM (for Cisco Tandem Offload Application)

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8850/vism21/210rnote.htm


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 MGC host to the MGWs and to the Cisco SLTs.


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 MGC 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 MGC.


Supported Features

The features listed in Table 2 were inherited from earlier releases of the Cisco MGC Software, and are still supported in Release 9.2(2).

Table 2 Supported Features in Release 9.2(2) 

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 COT support

Provides verification of the voice path.

Support for ISDN direct-access lines

Allows direct line access to the Cisco MGC.

Support for E-ISUP inter-MGC signaling

Provides scalable and flexible service.

Support for generic routing

Provides scalable and flexible service.

Support for MGCP 0.1, SGCP 1.0 and 1.1, and SRCP

Allows the Cisco MGC to control media gateway connections.

Edge-to-edge security

Prevents fraudulent use of the network.

Support for carrier-grade quality of service (QoS)

Replaces the need for traditional TDM equipment.

Support for SS7-to-SS7, SS7-to-ISDN, and ISDN-to-ISDN call types

Provides scalable and flexible service.

Support for voice-band telephony (G.711coding)

Provides scalable and flexible service.

Support for ISDN data calls

Provides scalable and flexible service.

Support for echo cancellation

Provides scalable and flexible service.

Support for Cisco media gateways

Protects investment in Cisco equipment.

Provides software upgrade of:

Cisco IOS

Cisco MGC and Sun Solaris software

Cisco SLT

These upgrade paths:

Protect investments

Provide low-cost ownership

Are part of a complete solution with Cisco IOS software

Provides a reliable IP link between Cisco MGC and access servers with Reliable User Datagram Protocol (RUDP)

No single point of failure in connection between media gateways and the Cisco MGC.

Call detail records for PSTN billing

Meets carrier-grade PSTN requirements to migrate existing voice revenue streams to the packet environment and to create new voice service opportunities. Provides a CDR viewer to view billing records.

Facility associated signaling provided by the Cisco SLTs (T1/E1 WIC, optional with SS7)

Grooms off the bearer channels and then delivers them to the media gateway.

Delivers MTP-3 to the MGC host over IP.

High Availability platform

Established calls are maintained when there is a switchover from the active MGC host to its paired standby host.

Sun Solaris 8

Y2K compliant

Open computing platform

Support for 600 destination point codes (DPCs)

Support for up to six origination point codes (OPCs) and 48 alias 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 MGC Management

Table 3 provides an overview of the management components of the Cisco MGC.

Table 3 Management Components of the Cisco MGC 

Management Component
Description

Cisco Voice Service Provisioning Tool (VSPT)

The Cisco VSPT is an optional configuration/provisioning tool for the Cisco PGW 2200. You can use its facilities to create, copy, modify, and deploy the configuration for the Media Gateway Controller host.

Cisco MGC Node Manager (CMNM)

CMNM is both a software requirement and an optional network management tool. It provides network management for the Cisco PGW 2200 that is beyond the provisioning functionality provided by the VSPT. CMNM provides fault, configuration, and performance management for all components of the Cisco MGC node.

Alarms

The Cisco MGC supports a comprehensive set of alarms (in accordance with ITU X.733):

Processing errors

QoS alarms

Equipment alarms

Communications alarms

Environment alarms

You can adjust the severity of alarms and thresholds to match your carrier's severity level definitions. 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.

PEG counts

You can obtain a variety of usage statistics from the Cisco MGC. 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


Media Gateway Management

The Cisco IOS software installed on the media gateways provides an array of network management components (described in Table 4) designed to meet the needs of today's large, complex networks. These management features provide the following benefits:

Reduce network bandwidth and processing overhead

Offload management servers

Conserve resources

Ease system configuration tasks

Cisco's integrated management simplifies administrative procedures and shortens the time required to diagnose and fix geographically dispersed networks. Configuration services reduce the cost of installing, upgrading, and reconfiguring network equipment.

Table 4 Network Management Components

Management Component
Description

SNMP and RMON support

Media gateways are fully manageable through use of the Simple Network Management Protocol (SNMP) and imbedded Remote Monitoring (RMON) capabilities:

SNMP provides for the collection of information about each controller and interface that can be polled through any SNMP-compatible network management system.

RMON acts as a remote protocol analyzer and LAN probe.

By using the Alarm RMON group, you can set a threshold on any integer-valued Management Information Base (MIB) variable. When the threshold is crossed, an event, defined in the Event RMON group, is triggered. With these capabilities, the system can detect and analyze overload conditions and congestion in real time.

Network management systems

The media gateways both support calling line identifier and the CiscoView GUI for comprehensive, flexible network management.

CiscoView provides dynamic status, statistics, and comprehensive configuration information for Cisco switches, routers, media gateways, Cisco SLTs, concentrators, and adapters. It displays a graphical view of Cisco devices, provides configuring and monitoring functions, and offers basic troubleshooting.



Note CiscoView and RMON are not supported on the Cisco MGX 8260.


Cisco Signaling Link Terminal Management

The Cisco SLT is managed using session manager software. The session manager software also manages the communication sessions between the following pairs of elements:

Active and standby MGC hosts within an MGC node

An MGC node and its media gateways for PRI backhaul

The Cisco SLTs and the active MGC host

An originating MGC node and a terminating MGC node

The session manager:

Maintains separate communication sessions between the above pairs of elements.

Uses Reliable User Datagram Protocol (RUDP) to communicate between the above pairs of elements. RUDP has TCP-like functionality with real-time efficiency.

In a continuous service configuration, handles additional traffic should a single MGC host, LAN switch, or Cisco SLT fail —with no impact on call processing.

Switching Protocols Supported

The PGW supports multiple signaling protocols, including SS7, PRI (ANSI, ITU, and ETSI), MGCP, H323, and SIP.

Related Documentation

Before Installation

Before you install the Cisco MGC software, consult the following related documentation for information about hardware installation and system requirements:

The Overview Guide for your solution

Cisco Media Gateway Controller Hardware Installation Guide:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/hrdwrnst/index.htm

Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/swinstl/index.htm

The Gateway Installation Guide for your solution

After Installation

After you install the Cisco MGC software, consult the following related documentation for information on configuring and provisioning your system:

Cisco Media Gateway Controller Software Release 9 Provisioning Guide:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/prvgde/index.htm

The Provisioning Guide for your solution

The most recent patch set should be loaded. Patches can be found at the following url:

http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml

General Purpose Documents

Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/omts/index.htm

Cisco Media Gateway Controller Software Release 9 Messages Reference Guide http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/errmsg/index.htm

Cisco Media Gateway Controller Software Release 9 MML Command Reference Guide http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/mmlref/index.htm

Cisco Media Gateway Controller Software Release 9 Dial Plan Guide
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/dplan/index.htm

Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/mgc_mib/index.htm

Cisco Media Gateway Controller Software Release 9 Management Information Base Guide
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/mgc_mib/index.htm

Documentation Map

Installation Notes

This section contains information and procedures you can use to remove, upgrade, or install the Cisco MGC software. It also contains information about software patches.

Acquiring the Software

The Cisco MGC software is provided to customers 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, the software and patch information can be installed directly from the CD.

Complete the following procedure to obtain software patches from CCO:


Step 1 From the Cisco Connection Online page, select the Software Center link(located under Service and Support).

The Technical Assistance Center page displays.

Step 2 From the Technical Assistance Center page, select the Voice Software link (located under Software Products and Downloads).

The Voice Software page displays.

Step 3 From the Voice Software page, select the Login option (located across the top of the page).

A login box displays.

Step 4 Enter your CCO user name and password then press OK.

After authentication the Voice Software page displays.

Step 5 Select the link for the desired software release. Software release links are located under the Cisco Media Gateway Controller heading.


Note Patches can also be obtained from CCO using the following urls:
www.cisco.com/kobayashi/sw-center/sw-voice.shtm
and
http://www.cisco.com/cgi-bin/tablebuild.pl/mgc-922


Installing and Upgrading the Software


Warning 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 Technical Assistance) or your Cisco account representative. Software release version incompatibility may cause service disruption.



Warning Before upgrading, refer to the "New Version of Times Ten Database Software" (page 96).



Caution Migration from Cisco MGC Software Release 7.4(x) to Cisco MGC Software Release 9.2(x) fails when the MML names used for the PRI backhaul IP links exceed 16 characters. Before attempting the migration, check all IP link names and ensure that they are 16 characters or less. The migration script uses the existing IP link names to create D-channel components, which are new components in Cisco MGC Software Release 9.(x). To do this, add 4 characters to the existing IP link name. If the existing IP link name is 17 characters or longer, the resultant D-channel name is longer than 20 characters and therefore invalid. (Maximum length of MML names is 20 characters in all releases.)

If you are installing software Release 9.2(2) for the first time, refer to the Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide for instructions.


Note In the Cisco Media Gateway Controller Software Release 9 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 upgrading 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.


Note If you have trouble installing the utilities package, make sure that you do not still have a transpath group in your group file (located in /etc).


Determining Which Protocol Patches/Families Are Installed On Your System

Complete the following procedure to determine which protocol patches are installed on your system:


Step 1 cd /opt/SW

Step 2 # ./patch status


The following is an example of the patch status command.

Currently installed protocol packages are:
00 
01 
30 

Note Package 00 is the base protocol software. It must always be installed on your system with any protocol version.


After obtaining a listing of protocol families that are installed on your system, use the protocol family numbers to determine what protocols are included in a package.

The following protocol families are available in Release 9.2(2):

Table 5 Protocol Families for Release 9.2(2) 

Protocol Type
Protocol Family Number
Protocol Family Contents

Miscellaneous Protocols

01

BTNUP_BTNR167
BTNUP_IUP

02

IETF_DCS
IETF_SIP
MGCPCAS

SS7 Protocol Family

10

ANSISS7_92
ANSISS7_CLEAR
ANSISS7_MCI
ANSISS7_STANDARD
GR317
GR317_C1
GR317_NOTPTX

PRI Protocol Family

20

ATT_41459
ATT_41459_C2
BELL_1268
BELL_1268_C3
BELL_SGCP

21

ETS_300_102
ETS_300_102_C1
ETS_300_121
ETS_300_172
ETS_300_356

Q761 Version 1 Protocol Family

30

Q761_ARGENTINA
Q761_ARGENTINA_C2
Q761_AUSTRL
Q761_AUSTRL_C2
Q761_BASE
Q761_BELG_BCOM
Q761_BELG_ISUP_CUJO
Q761_BELG_MOBI

31

Q761_CHILE
Q761_CHINA
Q761_CHINA_MOB
Q761_DANISH
Q761_INDIA
Q761_JAPAN
Q761_KOREAN
Q761_NEWZEALAND

32

Q761_97VER_BASE
Q761_PERU
Q761_PORTUGAL
Q761_SIEMENS_MOBI
Q761_SINGAPORE
Q761_SINGAPORE_C2
Q761_TAIWAN
Q761_THAILAND

33

HKTA_2202
ISUPV1_POLI

Q761 Version 2 Protocol Family

40

ISUPV2_32DIG
ISUPV2_AUSTRIAN
ISUPV2_CZECH
ISUPV2_FINNISH96
ISUPV2_FRENCH
ISUPV2_GERMAN
ISUPV2_JAPAN
ISUPV2_KPNPB

41

ISUPV2_NORWEGIAN
ISUPV2_NTT
ISUPV2_SPANISH
ISUPV2_SWISS
ISUPV2_SWISS_C2
ISUPV2_TELEFONICA
ISUPV2_TOKYO
ISUPV2_VIETNAM

Q761 Version 3 Protocol Family

50

ISUPV3
ISUPV3_FRENCH
ISUPV3_UK
ISUPV3_UK_AXE10
ISUPV3_UK_AXE10_BTNETCHAT
ISUPV3_UK_BTNETCHAT

Q721 Protocol Family

60

Q721_BASE
Q721_BRAZILIAN
Q721_CHINA
Q721_FRENCH
Q721_PHILLIPINE

Q767 Protocol Family

70

Q767_BASE
Q767_BRAZIL
Q767_COLOMBIA
Q767_GUATEMALA Q767_INDONESIA
Q767_ITAL Q767_ITAL_INTERCONNECT Q767_MEXICAN

71

Q767_RUSS
Q767_SINGAPORE
Q767_SPAN
Q767_SWED
Q767_TELSTRA
Q767_TURKISH

Q931 Protocol Family

80

Q931
Q931_AUSTRALIA
Q931_SINGAPORE


Determining Your System's Patch Level

To determine the patch level installed on your system, use the following command:

pkginfo | grep CSCO

The following is an example of the pkginfo command.

# pkginfo | grep CSCO 
application CSCO00015      Cisco Media Gateway Controller Software core system 
protocols 
application CSCO01015      Cisco Media Gateway Controller Software Miscellaneous 
Protocols 
application CSCO30015      Cisco Media Gateway Controller Software Q761 Version1 
family protocols 
application CSCOga000      Cisco Media Gateway Controller Software Licensing 
Components 
application CSCOga001      Cisco Media Gateway Controller Software Application 
application CSCOga002      Cisco Media Gateway Controller Software Database Components 
application CSCOga003      Cisco Media Gateway Controller Software SNMP Components 
application CSCOga004      Cisco Media Gateway Controller Software Toolkit 
Applications 
application CSCOgc001      Cisco Media Gateway Controller Software Configuration & 
Data Migration 
application CSCOgs014      Cisco Media Gateway Controller Software Patch Package 
application CSCOgt001      Cisco Media Gateway Controller Software Analyzer/Simulator 
utilities   CSCOgu000      Cisco Media Gateway Controller Software Common Utilities & 
Libraries 
utilities   CSCOh015       Media Gateway Controller Solaris 8 Patch Cluster 

In this example output of pkginfo, protocol patch CSCOnn015 and system patch CSCOgs014 are installed. Additionally, for each protocol patch, an entry is listed for each protocol family that is installed, protocol families 00, 01, and 30 are shown here.

The entry CSCO00015 indicates that protocol patch 015 (indicated by the last three digits) has protocol family 00 (indicated by the two digits preceding the last three digits) installed. The protocol packages are shown as CSCOnnvvv where:

nn—indicates the protocol family

vvv—indicates the version level of the patch


Note For more information on determining your patch level refer to the Protocol Patches section (page 26) of this document.


New Features in This Release

32 Digit Support in Q.761 Korean ISUP

This featurette (CSCec23340) adds 32-digit support to the Q.761 Korean ISUP.


Note For more information, refer to ddts ticket number CSCec23340.



Note This feature was added in patch CSCOnn037.


Seamless Upgrade

The Seamless Upgrade feature has been incorporated in release 9.3(2). To support seamless upgrade from earlier releases to 9.3(2), software changes have been installed using patches. For release 9.2(2), you must have a patch level greater than or equal to CSCOgs020.


Caution When upgrading the PGW 2200 platform from a patch level which does not support Seamless Upgrade to a patch level which does support seamless upgrade, the pom.dataSync parameter (located in XECfgParm.dat) must be set to false. If this parameter is not set to false, the standby system will not transition to the standby state; instead it will remain OOS.


Note Provisioning is not supported when the system is run on mismatched patches (one PGW node has a pre-Seamless Upgrade patch level and its peer has a Seamless Upgrade supported patch).



Note When both PGW 2200 nodes have been upgraded to a Seamless Upgrade supported patch level, normal provisioning can be done.


The following mml commands should not be used if one PGW 2200 node has a pre-Seamless Upgrade patch level and its peer has a Seamless Upgrade supported patch:

prov-sta

prov-cpy

prov-dply

prov-sync


Note The latest version of a patch is always required. Refer to CCO to determine the latest patch version available.


Derived FCI and BCI for Interworking

This featurette (CSCeb66052) addresses the requirements for setting the Forward Call Indicators (FCI) for ISUP/R2/T1CAS/PRI <-> ISUP interworking and Backward Call Indicators (BCI) for ISUP <-> ISUP/R2/T1CAS/PRI interworking.

These requirements apply to the following ISUP variants:

Q761_SINGAPORE

Q767_SINGAPORE

Q761_BASE

Q767_BASE

The PGW derives the remote protocol from the GTD Protocol Name field, then sets the FCI and BCI accordingly.

To enable this feature, manually add the following entry to the configurable section of XECfgParm.dat, using a UNIX editor (such as vi):

*.DerivedInterworkingFCIBCIEnable = 1

0 = Feature Disabled (default value), 1 = Feature Enabled

The Echo Control Device field (in the Backward Call Indicators and Nature of Connection Indicators) is now configurable on a SigPath. The property EchoCanRequired can be configured to control this field.


Note This featurette was added in patch CSCOnn036.


For more information, refer to the following documents:

Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide at the following url:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/swinstl/index.htm

Cisco Media Gateway Controller Software Release 9 Provisioning Guide at the following url:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/prvgde/index.htm

B-Digit Modification Enhancement

This featurette (CSCdy25786) strips the European number portability configuration (E_PORTED_NUM) output of the gateway number + the called party number (GN+CdPN) to allow the PGW to send out just the GN.

For Hong Kong local number portability (LNP), if a number is ported, a corresponding GN is appended to the CdPN in the IAM. The PGW uses E_PORTED_NUM which gives the number as GN+CdPN. An additional result type is created to allow the B-digit modification to delete the CdPN portion and send out just the GN.

In HK, there are currently 650k ported numbers, each with a unique GN. The GN length varies (2 to 12 digits long). This featurette strips E_PORTED_NUM out put of GN+CdPN from the last digit backward; since the CdPN has a fixed number of digits.

No SAM Sent in Hong Kong ISUP

This featurette (CSCdy30789) enables overlap functionality in HKTA_2202.

Allow Multiple PCIs In All Protocols

This featurette (CSCdx60152) allows multiple PCIs in all protocols. Calls that contain multiple PCIs are not rejected. The first PCI is considered and the second PCI is ignored.

NOA Cause14 32 Digit and Overdecadic for Spain/Italy/Belgium Featurette

This featurette (CSCdy32946) implements the mapping of LNP parameters on thetwo ITU protocols (ISUPV2_TELEFONICA and ISUPV2_SPANISH ITU). The parameters are:

1— Country specific NOA values

2—Cause 14 for QoR

3—32 and Overdecadic Digits support

NOA Cause14 32 Digit and Overdecadic for Spain/Italy/Belgium Featurette

This featurette (CSCdx61723) implements the mapping of LNP parameters on three ITU protocols (Spanish, Italian, and Belgium ISUP). The parameters are:

1—Country specific NOA values

2—Cause 14 for QoR

3—32 and Overdecadic Digits support (Spain requires both; Italian already supports both, and Belgium ISUP already supports Overdecadics).

BTNUP 3.1 KHz Custom Configuration

This featurette (CSCdx05822) extends the function of the existing defaultBC property to include BTNUP-based trunk groups. The property can be set to SPEECH or 3_1_KHZ. The default setting is SPEECH.

If the property is set to 3_1_KHZ, PGW converts the outgoing ISDN 3.1KHz (CAT3) call over the BTNUP TrunkGroup to ISDN speech (CAT2) call. This property has no impact on outgoing ISDN data (CAT1) and speech (CAT2) calls over the BTNUP TrunkGroup.

Software Inventory Control

This featurette (CSCdw61819) detects incompatible software versions residing on test systems in the various Cisco testing facilities. Each software release provides a file containing checksum information for all the libraries and executables being installed. The Software Inventory Control utility generates checksums on the production system then compares those checksums with the values in the installation master file. A discrepancy indicates that the software on the box does not match the software that was originally installed.


Note This featurette does not identify the source of a problem or the correct software to install. It does indicate if a problem exists prior to the testing of incompatible software.



Caution The Software Inventory Control feature uses a 32-bit CRC to calculate checksums. A 32-bit CRC can give over 4 billion possible CRC values (2 32 or 4,294,967,296). With so many CRC values it is possible for two different pieces of data to have the same CRC.

Software Inventory Control Feature Modification

The Software Inventory Control feature has been modified (CSCdy12454) to be less restrictive on the Solaris patches.

Patches that are installed but not in the input patch list or in the input patch list but not installed are treated as warnings—they may or may not cause problems for the MGC Software.

Patches that are installed but have a version number different from the version number in the input patch list are reported as errors.

Warning messages are only displayed if the verbose option (-v) is set.


Note The Software Inventory Control feature requires the Solaris patch cluster version 2.0(4) or higher due to changes in the input data files.



Note As of patch CSCOgs019, the Software Control Inventory feature has been enhanced to recognize the Netra 20 as a legitimate PGW 2200 host platform. Fore more information refer to CSCdy41805.


LNP Enhancements to Q.761_Portugal Protocol

This featurette (CSCdx21249) adds enhancements required to certify the PGW 2200 for interconnect with the PTT to the Portuguese ISUP variant in the Media Gateway Controller (MGC) code. The enhancements are:

Support for Overdecadic Digits—if a number is ported, the SCP provides a prefix that must be passed outbound to the PTT to allow the correct OLO to receive the call for the subscriber. The format of the prefix to send to the PTT is DXXXYYY<called party number>. The overdecadic D is sent in front of the number. As a requirement, the PGW must support all overdecadic digits (A-F) in Q761_Portugal protocol.

Mapping of Cause Value 14 in Portugal—switches must act on or generate external cause 14 releases to pass interconnect. The PGW must map external cause 14 releases to an internal release cause code. The PGW must support number portability when operating as an originating switch, transit switch, recipient switch, or donor switch supporting the following scenarios:

PGW is the Transit Switch and receives a cause 14 from a donor switch. PGW passes the cause 14 to the originating switch which performs the LNP lookup

PGW is the Donor Switch and after recognizing the number has been ported, generates a cause 14 and passes the cause 14 to the originating switch witch performs the destination LNP lookup.

PGW is the Originating Switch and receives a cause 14 from a donor switch. PGW performs the destination LNP lookup.

PGW is the Recipient Switch and routes the ported call.

Do Not Reject Calls if ACM Contains Multiple PCI (parameter compatibility indicators) Option—currently, the PGW either fails the call with a cause 95 or completes the call but sends CFN messages. The PGW cannot fail calls if the ACM contains multiple options (multiple PCI parameters). As a requirement, because the PCI is not a repeatable parameter, the PGW should act on the first PCI parameter, and ignore the subsequent parameters. This applies to all messages that contain PCI parameters.

Q767_Singapore.mdo File Created

A new .mdo file, Q767_SINGAPORE.mdo, has been created to support the Q767 Singapore IRI/ORI featurette.

Payphone Indicator From A-Number Analysis

This featurette (CSCdv42112) uses A-number analysis in the PGW 2200 to set the payphone indicator in the CPC of the IAM message. You must provision the PGW 2200 with a list of phones that are configured for payphone. The PGW 2200 handles these calls by returning an analysis result that can be used to set or not set the payphone indicator in the CPC of the IAM message. This featurette is generic for all protocols in which the CPC payphone value is 15(0F).

You must provision the A-digit tree with the CPCMOD result type for all payphone numbers.

The MML configuration of intermediate CPCMOD results in the result table is consistent with current practice. The following is an example:

NUMAN-ADD:RESULTTABLE:CUSTGRPID="T002", NAME="result45", RESULTTYPE="CPCMOD", 
SETNAME="cpcset1', DW1="payphone"

If you have existing dialplan, update it with following two commands. Otherwise, create a new dialplan with following two commands.


Note Replace xxxx by CUSTGRPID and yyyyyy by DigitString.


numan-add:resulttable:custgrpid="xxxx",resulttype="CPCMOD",dw1="payphone",setname="CPC
MODset",name="CPCMODresult"

numan-add:adigtree:custgrpid="xxxx",digitstring="yyyyyy",callside="originating",setnam
e="CPCMODset"

Make sure all SS7PATH requiring this feature uses the dialplan. You can assign a dialplan to a SS7PATH using following commands:


Note Replace zzzz by SS7PATH name.


prov-ed:SS7PATH:name="zzzz",CUSTGRPID="xxxx"

prov-add:sigsvcprop:name="zzzz",BOrigStartIndex="1"

prov-add:sigsvcprop:name="zzzz",BTermStartIndex="2"

Make sure all NASPATH requiring this feature uses dialplan. You can assign dialplan to a NASPATH using following commands:


Note Replace zzzz by NASPATH name.


prov-ed:NASPATH:name="zzzz",CUSTGRPID="xxxx"

prov-add:sigsvcprop:name="zzzz",BOrigStartIndex="1"

prov-add:sigsvcprop:name="zzzz",BTermStartIndex="2"

Country Code Prefix Per Trunk Group Capability

This featurette (CSCdv51699) allows you to route to different carriers for a given destination (on a per trunk group basis) where some carriers use an international format and other carriers use a national format. You can choose to apply or remove a country code and also optionally apply an international prefix.

This featurette introduces four new trunk groups and one new analysis result type which delivers the country code digits used for B-number manipulation. If the analysis result type is retrieved, it supplies the country code digit string that is internally stored until egress trunk group selection. During the final processing stage, the UCM checks to determine whether to prefix the called and calling party numbers with national or international prefixes (0 or 00).

German ISUP 32 Digit Support

This featurette (CSCdv54048) increases the calling and called party number to 32 digits in to the German ISUP protocol module.

Generic Transparency Descriptor Nature of Address Override

This featurette (CSCdv65542) allows the SC2200 to map the nature of address (NOA) parameter that has been modified by the route server into an outgoing IAM message.

VSC3000/SC2200 Code Reference

This featurette (CSCdv65590) renames existing code references from VSC, VSC3000, SC, and SC 2200 to a more generic MGC. These changes are applied to customer viewable area such as properties, messages, alarms, measurements and the GUI screen. Internal code references, such as variable names, will not be changed.

Automatic Backup Utility

This featurette (CSCdv70304) uses a script to backup the configuration data for the Cisco MGC software, select UNIX administrative files, and the Main Memory Database (MMDB). This script only performs full backups. It enables you to perform manual backups, schedule and administer automatic backups, and view a history of the last 30 backup operations performed.

The running of the restoration script must be done in a particular order, based on your network environment and the number of failed Cisco MGCs.

The following items should be noted:

If your Cisco MGC is a continuous service system, ensure that you perform backup procedures on both Cisco MGC hosts.

We recommend that you back up your system software during periods of low call volume to minimize the effect of the backup on your call processing.

After completing your backup, you must synchronize the databases on the active and standby Cisco MGCs. Contact TAC for assistance in synchronizing the databases.


Note The backup script is designed to have minimal impact on the CPU. However, we recommend that the script be run at off-peak hours.


For more information on this featurette, refer to the Cisco MGC Software Release 9 Operations, Maintenance, and Troubleshooting Guide at the following url:

http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/omts/index.htm

Protocol Packaging

This featurette (CSCdv83119) improves the protocol packaging so that you need only load and install protocols that you need. Previously, the entire protocol suite was packaged and delivered together. Delivering all protocols with each build and then each successive patch has the potential to cause usability problems because of the size of the protocol patch packages.

This featurette contains the following modifications:

The standard installation script was modified to allow the customer to specify which protocol set(s) are required on their platform.

Only packages containing the desired protocols are installed as part of the standard installation.

After this feature is applied, the same number of packages available with the initial release still exists; however, they have the new nomenclature required to support patching later in the release life cycle and you have the option to install only the packages containing required protocols.


Note You must always download the 00 protocol package when upgrading a protocol patch level. If the 00 protocol package is not downloaded, the upgrade attempt fails. You are advised that the package is missing.


A new directory, /opt/SW, is created during the initial base software installation. You must download all new patches into this directory location. A new shell script is provided with the standard installation and is also installed in the /opt/SW directory. A new alarm, Protocol file missing, has been added.

Peruvian ISUP Timer Adjustment

This featurette (CSCdv87227) changes the T6 timer from 60 seconds to 15 seconds. This reduces the time a call circuit is held.

Thailand ISUP with Generic Transparency Descriptor

This featurette (CSCdw07501) enables you to separate billing records generated by coin boxes from billing records generated by residential phones. Billing is handled by the Radius server on the H.323 network. Records are sorted in the Radius system to separate the coin box calls and residential calls.

BT UK ISUP Enhancements

This featurette (CSCdw32368) provides enhnancements that enable you to use the PGW 2200 as an originating and terminating end node in the network. The Redirecting Number parameter has been mapped to the Last Diverting Line Identity parameter. If both the Redirecting Number parameter and the Last Diverting Line Identity parameter exist in an incoming ISUP IAM message, they are both transferred as they are. If only one of the parameters exists (either Redirecting Number Parameter or Last Diverting Line Identity Parameter) that parameter is mapped to other parameter in the OCC side. When the UK ISUP is used with other protocols and the Redirecting parameter exists, the Redirecting parameter is mapped to th e Redirecting parameter and to the Last Diverting Line Identity parameter in the TCC side.

New Version of Times Ten Database Software


Note If you are migrating from MGC software Release 9.1(5), the requirement to migrate the Times Ten Database information was fulfilled during the 9.1(5) installation and no longer applies when you are installing this release.


Prior to uninstalling the previous release of the MGC software, you must run the following command:

/opt/TimesTen32/32/bin/ttMigrate -c DSN=howdydb /opt/CiscoMGC/etc/migrate.ttdb

If you do not run the migrate command before uninstalling the previous release, the following message displays when you install the new release:

A backup file was found for the database, but no migration file.

A migration file is required before you can upgrade to the latest release of Times Ten. If the previous message displays, complete one of the following procedures.

Option 1


Step 1 Reinstall the previous release of the MGC and run the following command:

/opt/TimesTen32/32/bin/ttMigrate -c DSN=howdydb /opt/CiscoMGC/etc/migrate.ttdb

Step 2 Uninstall the previous release.

Step 3 Reinstall the software.


Option 2


Step 1 If you do not want to save the data from the previous release, remove the file:

/opt/CiscoMGC/etc/export.ttdb

Step 2 Reinstall the software.



Note For option 1 and option 2, after upgrading the software on both machines, run the setup_replication.sh script on the standby MGC.


Change to Install Script

A new performance profile script has been added to this release. The system is automatically installed using a standard performance profile satisfactory for both nailed and switched solutions. This standard profile is a combination of the profiles where you selected to optimize the system to maximize the number of sustainable calls or to optimize the system to maximize the number of calls per second.

The profile takes effect when the MGC is restarted. A performance profile can be selected only at installation time. To change a selection, you must remove and reinstall the system. For more information on the install script, see the "Protocol Patches" section of these release notes.

Solaris 8 Revision Upgrade

This featurette (CSCdw47628) replaces the current version of Solaris 8 (released July 2001) used on the MGC and BAMS platforms with a more current release (October 2001). This upgrade was necessary to support the most recent hardware platform released by Sun (the Sunfire v120). The v120, which requires a Solaris operating system of October 2001 or later, replaces the AC/DC 200.

New Cause Code for Call Re-Attempts

This featurette (CSCeb07238) determines how calls released from the PGW when the following scenarios occur:

Glare on non-control circuit

Circuit Block after IAM before ACM

Circuit Reset after IAM before ACM

COT failure

The following entry must be manually added to the configurable parameter section of XECfgParm.dat using a UNIX editor (such as vi):

*.GlareReattemptCauseValue=44

Valid values are 1-127; the default value is 44.

If the GlareReattemptCauseValue entry is not added to XECfgParm.dat and patches CSCOnn035 and CSCOgs037 are added to the system, the PGW defaults to a value of 44 for call reattempts and the original behavior of mapping to CV=44 is used.


Note The GlareReattemptCauseValue parameter is not automatically migrated when upgrading from 9.2(2) to a later version of software. After upgrading you must manually re-add the parameter to XECfgParm.dat. After adding the parameter, the PGW must be restarted for the change to take effect.



Note This featurette is for nailed solutions only.


Features from Release 9.2(1)T

Time Conditional Routing

This featurette (CSCuk25661) enables you to provision time and day dependencies into the route selection on the VSC. Time conditional routing allows the route lists to be selected depending on the day of the week and holidays (special days) and a time band. Time of day and type of day (Mon, Tue, Wed, Thu, Fri, Sat, Sun, Holiday (1-3), and Default) are used as keys into the time conditional rouing table; the output from the time conditional routing table is a route list. An example of a time conditional routing table is shown in Table 6.

Table 6 Time Conditional Routing Table 

Day
Times
Route List

Monday

0000—0900

1

Monday

0901—1700

2

Monday

1701—2200

3

Monday

2201—2359

4

Tuesday

0000—1700

3

Tuesday

1701—2359

5

Sunday

0000—2359

2

Holiday1

0000—2359

4

Default

2



Note The Default entry is the default for type of day selection. It ensures that a route list can be picked up without having to provision every possible type of day into a table.


The following are guidelines on the dimensioning for time conditional routing tables:

You can have a maximum of 11 days per conditional routing block.

You can have a maximum of 5 individual route list entries per type of day.

The recommended maximum number of conditional routing blocks is 1000.

The time bands are specified using GMT with a granularity of hours and minutes.

Redirecting Number CLI Screening Within a Digit Analysis

This featurette (CSCdu67513) enables the analysis system to use the A-Digit tree for a mapping to BLACKLIST function on the Redirecting CLI value, when the property RedirectingATree is set.

Austrian ISUP V2

This featurette (CSCdv01785) modifies Swiss V2 ISUP V.2 MDO. It removes the UCIC message and create a new MDO for Telecom Austria.

Mid-Call DTMF Relay for HSI

This featurette (CSCdv11334) provides the ability to connect Cisco Call Managers to the PSTN using the VSC with the HSI adjunct as the PSTN gateway; AS5300 and AS5400 media gateways are used. The Cisco Call Manager supports out-of-band DTMF using H.245. The VSC and HSI adjunct receives the H.245 DTMF indications and forwards them to the Media Gateway for relay into the PSTN. The VSC also receives DTMF digits from the PSTN and signals them using H.245 out-of-band signaling to the Cisco Call Manager.

Dual Ethernet and 4-Link SLT Support

This featurette adds SLT support for two IP networks and two additional Session Manager sessions for Backhaul communication. These additions increase the resilience of SLT-VSC communications by supporting two RUDP sessions from each ethernet interface to each VSC.

Solaris 8 Support

This featurette replaces Solaris 2.6 operating environment with Solaris 8. The Solaris 8 operating environment introduces new features that extend its capabilities.

Protocol Patches

Patches are located in the following directory:

/auto/nssu-release/PATCHES/9.2.2/P1/CSCOxx001.pkg

The protocol packaging has been improved so that you need only load and install protocols that you need. Previously, the entire protocol suite was packaged and delivered together.

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 to support patching later in the release life cycle and 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 are built, the 000 is incremented by 1 (001).


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.


Note For more information on using the patch status command, refer to the Determining Which Protocol Patches/Families Are Installed On Your System section of this document.


The installation script requires one of the following options:

Option 1—patch status retrieves the status of the system. Use this option to determine which set of protocol packages are currently installed on your system. The installed protocol packages are required (must be downloaded) 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).

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 level. 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 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 any available patch level to 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 any available patch level to 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:
CSCO00018
CSCO01018
CSCO02018
CSCO10018
CSCO20018
CSCO21018
CSCO30018
CSCO31018
CSCO32018
CSCO33018
CSCO40018
CSCO41018
CSCO50018
CSCO60018
CSCO70018
CSCO71018
CSCO80018
CSCOgs017
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:
CSCO00018.pkg
CSCO01018.pkg
CSCO02018.pkg
CSCO10018.pkg
CSCO20018.pkg
CSCO21018.pkg
CSCO30018.pkg
CSCO31018.pkg
CSCO32018.pkg
CSCO33018.pkg
CSCO40018.pkg
CSCO41018.pkg
CSCO50018.pkg
CSCO60018.pkg
CSCO70018.pkg
CSCO71018.pkg
CSCO80018.pkg
CSCOgs017.pkg

Are you sure this add/remove scenario is correct?  [y] [y,n,?,q] 

Before Installing a Patch

Before installing a patch, you must shut down the Cisco MGC application, because the affected programs are part of the running system. To ensure that the MGC application has been shut down, execute the following command:

# /etc/init.d/CiscoMGC stop

After the Cisco MGC has been shut down, verify the currently installed software load to ensure that the patch being installed is both compatible with and meant for the software currently installed. You can verify this using the following command:

# sudo pkgparam CSCOgu000

After shutting down the Cisco MGC and verifying the software load, you can proceed with the installation.

System Level Equivalency

Table 7 provides the system level equivalency for each protocol patch. For example, after installing CSCOnn003, release 9.2(2) is equivalent to release 9.1(5) patch level CSCOgp014 (contains all patches and features included in release 9.1(5) up to patch CSCOgp014).

Table 7 System Level Equivalencies for Protocol Patches 

Patch Number
System Level Equivalency

CSCOnn045

Release 9.1(5) patch level CSCOgp020

CSCOnn044

Release 9.1(5) patch level CSCOgp020

CSCOnn043

Release 9.1(5) patch level CSCOgp020

CSCOnn042

Release 9.1(5) patch level CSCOgp020

CSCOnn041

Release 9.1(5) patch level CSCOgp020

CSCOnn040

Release 9.1(5) patch level CSCOgp020

CSCOnn039

Release 9.1(5) patch level CSCOgp020

CSCOnn038

Release 9.1(5) patch level CSCOgp020

CSCOnn037

Release 9.1(5) patch level CSCOgp020

CSCOnn036

Release 9.1(5) patch level CSCOgp020

CSCOnn035

Release 9.1(5) patch level CSCOgp020

CSCOnn034

Release 9.1(5) patch level CSCOgp020

CSCOnn033

Release 9.1(5) patch level CSCOgp020

CSCOnn032

Release 9.1(5) patch level CSCOgp020

CSCOnn031

Release 9.1(5) patch level CSCOgp020

CSCOnn030

Release 9.1(5) patch level CSCOgp020

CSCOnn029

Release 9.1(5) patch level CSCOgp020

CSCOnn028

Release 9.1(5) patch level CSCOgp020

CSCOnn027

Release 9.1(5) patch level CSCOgp019

CSCOnn026

Release 9.1(5) patch level CSCOgp019

CSCOnn025

Release 9.1(5) patch level CSCOgp019

CSCOnn024

Release 9.1(5) patch level CSCOgp019

CSCOnn023

Release 9.1(5) patch level CSCOgp019

CSCOnn022

Release 9.1(5) patch level CSCOgp019

CSCOnn021

Release 9.1(5) patch level CSCOgp019

CSCOnn020

Release 9.1(5) patch level CSCOgp019

CSCOnn019

Release 9.1(5) patch level CSCOgp019

CSCOnn018

Release 9.1(5) patch level CSCOgp018

CSCOnn017

Release 9.1(5) patch level CSCOgp018

CSCOnn016

Release 9.1(5) patch level CSCOgp018

CSCOnn015

Release 9.1(5) patch level CSCOgp018

CSCOnn014

Release 9.1(5) patch level CSCOgp017

CSCOnn013

Release 9.1(5) patch level CSCOgp017

CSCOnn012

Release 9.1(5) patch level CSCOgp017

CSCOnn011

Release 9.1(5) patch level CSCOgp017

CSCOnn010

Release 9.1(5) patch level CSCOgp017

CSCOnn009

Release 9.1(5) patch level CSCOgp016

CSCOnn008

Release 9.1(5) patch level CSCOgp015

CSCOnn007

Release 9.1(5) patch level CSCOgp015

CSCOnn006

Release 9.1(5) patch level CSCOgp014

CSCOnn005

Release 9.1(5) patch level CSCOgp014

CSCOnn004

Release 9.1(5) patch level CSCOgp014

CSCOnn003

Release 9.1(5) patch level CSCOgp014

CSCOnn002

Release 9.1(5) patch level CSCOgp013

CSCOnn001

Release 9.1(5) patch level CSCOgp010


Table 8 provides the system level equivalency for each system patch. For example, after installing CSCOgs003, release 9.2(2) is equivalent to release 9.1(5) patch level CSCOgs009 (contains all patches and features included in release 9.1(5) up to patch CSCOgs009).

Table 8 System Level Equivalencies for System Patches 

Patch Number
System Level Equivalency

CSCOgs043

Release 9.1(5) patch level CSCOgs017

CSCOgs042

Release 9.1(5) patch level CSCOgs017

CSCOgs041

Release 9.1(5) patch level CSCOgs017

CSCOgs040

Release 9.1(5) patch level CSCOgs017

CSCOgs039

Release 9.1(5) patch level CSCOgs017

CSCOgs038

Release 9.1(5) patch level CSCOgs017

CSCOgs037

Release 9.1(5) patch level CSCOgs017

CSCOgs036

Release 9.1(5) patch level CSCOgs017

CSCOgs035

Release 9.1(5) patch level CSCOgs017

CSCOgs035

Release 9.1(5) patch level CSCOgs017

CSCOgs034

Release 9.1(5) patch level CSCOgs017

CSCOgs033

Release 9.1(5) patch level CSCOgs017

CSCOgs032

Release 9.1(5) patch level CSCOgs017

CSCOgs031

Release 9.1(5) patch level CSCOgs017

CSCOgs030

Release 9.1(5) patch level CSCOgs017

CSCOgs029

Release 9.1(5) patch level CSCOgs017

CSCOgs028

Release 9.1(5) patch level CSCOgs017

CSCOgs027

Release 9.1(5) patch level CSCOgs016

CSCOgs026

Release 9.1(5) patch level CSCOgs016

CSCOgs025

Release 9.1(5) patch level CSCOgs016

CSCOgs024

Release 9.1(5) patch level CSCOgs016

CSCOgs023

Release 9.1(5) patch level CSCOgs015

CSCOgs022

Release 9.1(5) patch level CSCOgs015

CSCOgs021

Release 9.1(5) patch level CSCOgs015

CSCOgs020

Release 9.1(5) patch level CSCOgs015

CSCOgs019

Release 9.1(5) patch level CSCOgs014

CSCOgs018

Release 9.1(5) patch level CSCOgs014

CSCOgs017

Release 9.1(5) patch level CSCOgs013

CSCOgs016

Release 9.1(5) patch level CSCOgs013

CSCOgs015

Release 9.1(5) patch level CSCOgs013

CSCOgs014

Release 9.1(5) patch level CSCOgs013

CSCOgs013

Release 9.1(5) patch level CSCOgs012

CSCOgs012

Release 9.1(5) patch level CSCOgs012

CSCOgs011

Release 9.1(5) patch level CSCOgs012

CSCOgs010

Release 9.1(5) patch level CSCOgs012

CSCOgs009

Release 9.1(5) patch level CSCOgs012

CSCOgs008

Release 9.1(5) patch level CSCOgs011

CSCOgs007

Release 9.1(5) patch level CSCOgs010

CSCOgs006

Release 9.1(5) patch level CSCOgs010

CSCOgs005

Release 9.1(5) patch level CSCOgs009

CSCOgs004

Release 9.1(5) patch level CSCOgs009

CSCOgs003

Release 9.1(5) patch level CSCOgs009

CSCOgs002

Release 9.1(5) patch level CSCOgs008

CSCOgs001

Release 9.1(5) patch level CSCOgs006


Patch Test Combinations

Table 9 provides a list of the patch combinations that were used when testing. Use this list to determine which protocol and system patches should be installed before you run the MGC software. It does not matter which patch (protocol or software) is installed first.

Table 9 Patch Test Combinations 

Protocol Patch
System Patch

CSCOnn045

CSCOgs043

CSCOnn045

CSCOgs042

CSCOnn044

CSCOgs042

CSCOnn043

CSCOgs042

CSCOnn043

CSCOgs041

CSCOnn042

CSCOgs041

CSCOnn041

CSCOgs040

CSCOnn040

CSCOgs040

CSCOnn039

CSCOgs040

CSCOnn038

CSCOgs040

CSCOnn037

CSCOgs039

CSCOnn037

CSCOgs038

CSCOnn036

CSCOgs038

CSCOnn035

CSCOgs037

CSCOnn034

CSCOgs036

CSCOnn034

CSCOgs035

CSCOnn033

CSCOgs035

CSCOnn032

CSCOgs034

CSCOnn032

CSCOgs033

CSCOnn031

CSCOgs032

CSCOnn030

CSCOgs031

CSCOnn029

CSCOgs030

CSCOnn029

CSCOgs029

CSCOnn028

CSCOgs028

CSCOnn027

CSCOgs027

CSCOnn027

CSCOgs026

CSCOnn026

CSCOgs025

CSCOnn025

CSCOgs024

CSCOnn024

CSCOgs023

CSCOnn023

CSCOgs022

CSCOnn022

CSCOgs021

CSCOnn021

CSCOgs020

CSCOnn020

CSCOgs019

CSCOnn019

CSCOgs018

CSCOnn018

CSCOgs017

CSCOnn017

CSCOgs016

CSCOnn016

CSCOgs015

CSCOnn015

CSCOgs014

CSCOnn014

CSCOgs013

CSCOnn013

CSCOgs013

CSCOnn012

CSCOgs012

CSCOnn011

CSCOgs011

CSCOnn010

CSCOgs010

CSCOnn009

CSCOgs008

CSCOnn008

CSCOgs007

CSCOnn007

CSCOgs006

CSCOnn006

CSCOgs005

CSCOnn005

CSCOgs005

CSCOnn004

CSCOgs004

CSCOnn003

CSCOgs003

CSCOnn002

CSCOgs002

CSCOnn001

CSCOgs001


CSCOnn045


Caution The patch script located on CCO has been renamed patch.sh. Download the patch (patch.sh) to the /opt/SW directory on your system and rename it to patch. Permissions for this file should be set to 775. For example:

-rwxrwxr-x 1 root sys 15998 Sep 16 2002 patch 
 
Owner: root 
Group: sys 
Permissions 775 

Protocol patch CSCOnn045 resolves the following DDTS ticket:

Identifier
Severity
Component
Description

CSCee01496

2

mdl

RNI not present in IAM reroute message.


Additional information:

Protocol patch CSCOnn044 is superseded by the fixes provided in protocol patch CSCOnn045. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn044


Caution The patch script located on CCO has been renamed patch.sh. Download the patch (patch.sh) to the /opt/SW directory on your system and rename it to patch. Permissions for this file should be set to 775. For example:

-rwxrwxr-x 1 root sys 15998 Sep 16 2002 patch 
 
Owner: root 
Group: sys 
Permissions 775 

Protocol patch CSCOnn044 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCed59724

3

mdl-ni2

PGW should not send ATP when receiving ProgIndIE=3 from NI2+.

CSCed60740

3

mdl

IAM with code 11 or code 12 set PGW rejects call.

CSCed61002

3

mdl-q761

BCI fields in ISUP CON msg not set by ingress PGW Q761_SINGAPORE var.

CSCed67494

3

mdl-q761

Wrong Redirection Count for ISDN to ISUP call.


Additional information:

Protocol patch CSCOnn043 is superseded by the fixes provided in protocol patch CSCOnn044. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn043


Caution The patch script located on CCO has been renamed patch.sh. Download the patch (patch.sh) to the /opt/SW directory on your system and rename it to patch. Permissions for this file should be set to 775. For example:

-rwxrwxr-x 1 root sys 15998 Sep 16 2002 patch 
 
Owner: root 
Group: sys 
Permissions 775 

Protocol patch CSCOnn043 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCed19529

3

mdl-q767

Extra OBCI parameter inserted into CPG message by ingress PGW.

CSCed31576

3

mdl-q761

GTD CPC=29 needs to map to Q761_SINGAPORE CPC=2 on egress.


Additional information:

Protocol patch CSCOnn042 is superseded by the fixes provided in protocol patch CSCOnn043. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn042


Caution The patch script located on CCO has been renamed patch.sh. Download the patch (patch.sh) to the /opt/SW directory on your system and rename it to patch. Permissions for this file should be set to 775. For example:

-rwxrwxr-x 1 root sys 15998 Sep 16 2002 patch 
 
Owner: root 
Group: sys 
Permissions 775 

Protocol patch CSCOnn042 resolves the following DDTS ticket:

Identifier
Severity
Component
Description

CSCed29090

3

mdl-ni2

PGW early backward message causes ISDN orig call to fail.


Additional information:

Protocol patch CSCOnn041 is superseded by the fixes provided in protocol patch CSCOnn042. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn041


Caution The patch script located on CCO has been renamed patch.sh. Download the patch (patch.sh) to the /opt/SW directory on your system and rename it to patch. Permissions for this file should be set to 775. For example:

-rwxrwxr-x 1 root sys 15998 Sep 16 2002 patch 
 
Owner: root 
Group: sys 
Permissions 775 

Protocol patch CSCOnn041 resolves the following DDTS ticket:

Identifier
Severity
Component
Description

CSCed19529

3

mdl-q767

Extra OBCI parameter inserted into CPG message by ingress PGW.


Additional information:

Protocol patch CSCOnn040 is superseded by the fixes provided in protocol patch CSCOnn041. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn040


Caution The patch script located on CCO has been renamed patch.sh. Download the patch (patch.sh) to the /opt/SW directory on your system and rename it to patch. Permissions for this file should be set to 775. For example:

-rwxrwxr-x 1 root sys 15998 Sep 16 2002 patch 
 
Owner: root 
Group: sys 
Permissions 775 

Protocol patch CSCOnn040 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCed02204

3

mdl-q767

ISUP-ISUP CPC mapping is transparent for like-to-unlike SS7 variants.

CSCed02233

3

mdl-ni2

PI=8 inserted in NI2+ CONNECT by egress PGW.

CSCed04332

3

mdl-q767

NI2 PROG with PI=4 does not trigger ISUP CPG with ATP at ingress PGW.

CSCed05356

3

mdl-ni2

SS7 ATP created when recv isdn msgs with PI=8.


Additional information:

Protocol patch CSCOnn039 is superseded by the fixes provided in protocol patch CSCOnn040. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn039


Caution The patch script located on CCO has been renamed patch.sh. Download the patch (patch.sh) to the /opt/SW directory on your system and rename it to patch. Permissions for this file should be set to 775. For example:

-rwxrwxr-x 1 root sys 15998 Sep 16 2002 patch 
 
Owner: root 
Group: sys 
Permissions 775 

Protocol patch CSCOnn039 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCec58264

3

mdl-ni2

PGW to insert PRN in the REL-GTD sent in NI2-DISC.

CSCec79449

3

mdl-ni2

PGW needs to treat PRN.prot=uknow as ISUP/ISDN termination without i.


Additional information:

Protocol patch CSCOnn038 is superseded by the fixes provided in protocol patch CSCOnn039. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn038


Caution The patch script located on CCO has been renamed patch.sh. Download the patch (patch.sh) to the /opt/SW directory on your system and rename it to patch. Permissions for this file should be set to 775. For example:

-rwxrwxr-x 1 root sys 15998 Sep 16 2002 patch 
 
Owner: root 
Group: sys 
Permissions 775 

Protocol patch CSCOnn038 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCec24084

2

mdl-q761

PGW fails to generate E-ACM upon NI2-PROG with CPG GTD.

CSCec38281

2

mdl-q761

PGW generates BCI parm in ANM GTD causing ISUP Xparency violation.

CSCec44788

3

mdl-q761

T38 trigger needs to be aware of peer signaling.

CSCec52895

3

mdl-q761

Q761_SINGAPORE should start T6 and T38 simultaneously.


Additional information:

Protocol patch CSCOnn037 is superseded by the fixes provided in protocol patch CSCOnn038. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn037

Protocol patch CSCOnn037 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCec20353

2

mdl-q761

PGW inserts incorrect cld-pty-stat in BCI for q761-sng to T1CAS call.

CSCec26560

3

mdl-q761

BCI in CON wrong for Q761 SNG to V2-GW calls.

CSCec31582

3

mdl-q761

PGW generates OBCI parm in ACM violating ISUP transparency,ST_P2 singtel

CSCec31669

3

mdl-q761

No ATP reqd for non-ISDN terminations as indicated in NI2-GTD.

CSCec31673

3

mdl-q761

Set BCI-CldPtyStat=NoInd when No-GTD or GTD-w/o-PRN in NI2-PROG-PI8.

CSCec23340

6

other

32 digit support in Q.761 Korean ISUP.


Additional information:

Protocol patch CSCOnn036 is superseded by the fixes provided in protocol patch CSCOnn037. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCec23340—32 Digit Support in Q.761 Korean ISUP—Adds 32-digit support to the Q.761 Korean ISUP.

CSCOnn036

Protocol patch CSCOnn036 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCeb45858

2

mdl-ni2

PGW should not propagate ProgInd into ATP for ISUP-ISUP call w/GTD.

CSCeb61738

2

mdl

Netmeeting calls fail when GTD is configured with 9.4.1 PGW.

CSCea62111

3

mdl-q761

Call releases with CV#31 iso #102 when no RESUME after SUSPEND.

CSCeb44493

3

mdl-ni2

PGW rejects NI2-PROG from GW if ProgInd=5.

CSCeb66052

6

other

Derived FCI and BCI for Interworking featurette.


Additional information:

Protocol patch CSCOnn035 is superseded by the fixes provided in protocol patch CSCOnn036. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

Both patches CSCOnn036 and CSCOgs038 must be installed.

CSCeb66052—Derived FCI and BCI for Interworking featurette—this featurette addresses the requirements for setting the Forward Call Indicators (FCI) for ISUP/R2/T1CAS/PRI <-> ISUP interworking and Backward Call Indicators (BCI) for ISUP <-> ISUP/R2/T1CAS/PRI interworking.

These requirements apply to the following ISUP variants:

Q761_SINGAPORE

Q767_SINGAPORE

Q761_BASE

Q767_BASE

The PGW derives the remote protocol from the GTD Protocol Name field, then sets the FCI and BCI accordingly.

To enable this feature, manually add the following entry to the configurable section of XECfgParm.dat, using a UNIX editor (such as vi):

*.DerivedInterworkingFCIBCIEnable = 1

0 = Feature Disabled (default value), 1 = Feature Enabled

The Echo Control Device field (in the Backward Call Indicators and Nature of Connection Indicators) is now configurable on a SigPath. The property EchoCanRequired can be configured to control this field.

CSCOnn035

Protocol patch CSCOnn035 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCeb34155

2

mdl-ni2

PGW sends invalid NI2-PROG message for early-ACM scenario.

CSCdz22222

3

mdl-q761

CICs stuck in CALL=IN/OUT state on PGW and Idle on gateway.

CSCeb37075

3

mdl-ni2

Ingress PGW should not propagate PI=9 from Ni2-PROG to AccsTrnsprt.

CSCeb37105

3

mdl-ni2

Egress PGW should send NI2-PROG with PI9 for CPG transparency.

CSCeb07238

6

other

New Cause Code for Call Re-Attempts featurette.


Additional information:

Protocol patch CSCOnn034 is superseded by the fixes provided in protocol patch CSCOnn035. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

Both patches CSCOnn034 and CSCOgs037 must be installed.

CSCeb07238—New Cause Code for Call Re-Attempts— This featurette determines how calls released from the PGW when the following scenarios occur:

Glare on non-control circuit

Circuit Block after IAM before ACM

Circuit Reset after IAM before ACM

COT failure

The following entry must be manually added to the configurable parameter section of XECfgParm.dat using a UNIX editor (such as vi):

*.GlareReattemptCauseValue=44

Valid values are 1-127; the default value is 44.

If the GlareReattemptCauseValue entry is not added to XECfgParm.dat and patches CSCOnn035 and CSCOgs037 are added to the system, the PGW defaults to a value of 44 for call reattempts and the original behavior of mapping to CV=44 is used.


Note The GlareReattemptCauseValue parameter is not automatically migrated when upgrading from 9.2(2) to a later version of software. After upgrading you must manually re-add the parameter to XECfgParm.dat. After adding the parameter, the PGW must be restarted for the change to take effect.



Note This featurette is for nailed solutions only.


CSCOnn034

Protocol patch CSCOnn034 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCea63564

3

mdl-q767

CV#20 gets mapped to CV#31 iso being passed through.

CSCea86351

3

mdl-ni2

PGW should pass CV=4 without changing coding standard.


Additional information:

Protocol patch CSCOnn033 is superseded by the fixes provided in protocol patch CSCOnn034. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn033

Protocol patch CSCOnn033 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCea62136

2

mdl-ni2

PGW handling of early ACM and CPG with GTD not correct.

CSCea60697

3

mdl-ni2

No ISUP-transparency for early ACM.

CSCea62111

3

mdl-q761

Call releases with CV#31 iso #102 when T6 expires.

CSCea63564

3

mdl-q767

CV#20 gets mapped to CV#31 iso being passed through.

CSCea81076

3

mdl-ni2

GTD Protocol Name is overwritten by Prot Variant for Q767.

CSCea86351

3

mdl-ni2

PGW should pass CV=4 without changing coding standard.


Additional information:

Protocol patch CSCOnn032 is superseded by the fixes provided in protocol patch CSCOnn033. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn032

Protocol patch CSCOnn032 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCea29513

2

mdl-q761

Numbering Plan unkown is changed to spare by the PGW.

CSCdz28886

3

mdl-connctrl

CIC states on PGW not synced with bearer ch. states on GW.

CSCea12246

3

protocol

sc not mapping *#(over-decadic digits) to B/C.

CSCea25631

3

mdl-callctrl

Hung CIC due to race condition between call release and rerouting.


Additional information:

Protocol patch CSCOnn031 is superseded by the fixes provided in protocol patch CSCOnn032. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn031

Protocol patch CSCOnn031 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCea15726

3

mdl-ni2

PGW does not transparently pass cv-4 from NI2 to SS7 side.


The BELL_1268_C3 component was updated.

Additional information:

Protocol patch CSCOnn030 is superseded by the fixes provided in protocol patch CSCOnn031. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn030

Protocol patch CSCOnn030 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdz84480

3

mdl-sip

PSTN Rel w/Cause code=31 maps to incorrect SIP error code.


Additional information:

Protocol patch CSCOnn029 is superseded by the fixes provided in protocol patch CSCOnn030. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn029

Protocol patch CSCOnn029 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdz67868

2

mdl-ni2

PGW doesnt set the coding type correctly cause IE.

CSCdz63415

3

mdl-ansi-ss7

ANSI no response to tx CGB followed by RSC results hung cic.

CSCdz64782

3

mdl-ansi-ss7

Stuck cic resulted by glare at two way release mode.


This patch provides updates to the following:

Q761 Protocol Suite

Q767 Protocol Suite

ANSISS7 Protocol Suite

Additional information:

Protocol patch CSCOnn028 is superseded by the fixes provided in protocol patch CSCOnn029. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn028

Protocol patch CSCOnn028 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdz46770

2

mdl

Calling party number set to incomplete in O/G IAM message.

CSCdz56811

2

mdl-itu-ss7

Unresponded txd CGB followed by RSC cause locked CIC.

CSCdz58203

3

mdl-q761

CIC gets stuck on PGW upon glare condition.


This patch provides updates to the following:

Q761 Protocol Suite

Q767 Protocol Suite

GTD

Additional information:

Protocol patch CSCOnn027 is superseded by the fixes provided in protocol patch CSCOnn028. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn027

Protocol patch CSCOnn027 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdz32051

2

mdl-q767

Redirecting, Orig-Call and LRN fails EISUP when 32-digits or greater.

CSCdz32254

3

mdl-q721

Ring no answer needs to be mapped to cc=19 over NI2

CSCdz25233

3

mdl-q767

36-digit_overdecadic calling number dropped as opposed to truncated.


This patch provides updates to the following:

Q761 Protocol Suite

Q767 Protocol Suite

Q721 Protocol Suite

EISPU Protocol suite

Additional information:

Protocol patch CSCOnn026 is superseded by the fixes provided in protocol patch CSCOnn027. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn026

Protocol patch CSCOnn026 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdz19032

2

protocol

PGW2200 can not recognize 3 bytes Release Cause Indicator.

CSCdz11570

3

mdl-callctrl

Incorrect Handling of CallCutoffTimer in Standby PGW.

CSCdz15685

3

mdl-callctrl

Spontaneous switchover in PGW during Re-routing fo the call.

CSCdz08306

3

mdl-q721

CIC status mismatch problem.

CSCdz07399

6

mdl-q767

32 Digit Support on Q767_RUSS.


This patch provides updates to all protocols.

Additional information:

Protocol patch CSCOnn025 is superseded by the fixes provided in protocol patch CSCOnn026. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn025

Protocol patch CSCOnn025 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdy11273

2

mdl-ansi-ss7

Local Routing Number is lost with SuperCell release.

CSCdy62767

3

mdl-cdr

TAG 4106 FirstREL_TM is missing on CDR.

CSCdz07472

3

mdl-connctrl

GWNetworkContinuity not loaded for switched call.

CSCdy84847

3

mdl-ni2

BCI and OBI are changed on the Ingress Side of the call,ft1_0.

CSCdz01570

3

mdl-pri

PRI and NI2C variants do not map all NumberingPlans correctly.

CSCdy51717

3

mdl-q721

IAI wont unblock a remotely blocked cic in a switched env.


This patch provides updates the following:

PRI Protocol Suite

Q721 Protocol Suite

lcm

generic analysis

connection plane manager

Additional information:

Protocol patch CSCOnn024 is superseded by the fixes provided in protocol patch CSCOnn025. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn024

Protocol patch CSCOnn024 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdy68963

2

engine

PGW sends wrong GRSA during HW failure.

CSCdy81924

2

engine

Stuck CICs are created when the dpc recover from temporary outage.

CSCdy79280

2

mdl-analysis

Incomming prefix number not removed.

CSCdw81829

3

mdl-analysis

After switchover the call is not routed to the proper dialplan.

CSCdy80014

3

mdl-cdr

Nature Of Address Information is not checkpointed.

CSCdy73439

3

mdl-q761

GRS in response to RSC would not clear call in PGW.


This patch provides updates to all protocols.

Additional information:

Protocol patch CSCOnn023 is superseded by the fixes provided in protocol patch CSCOnn024. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn023

Protocol patch CSCOnn023 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdy62710

2

protocol

ORI is dropped by ingress PGW in a direct connet call.

CSCuk36123

2

protocol

Incorrect behaviour on release collision causes hung cic.

CSCdy62835

6

mdl-q761

NOA for called party number should have HK defined values.


This patch provides updates the following:

Q761 Protocol Suite

Q767 Protocol Suite

SS7 Protocol Suite

Additional information:

Protocol patch CSCOnn022 is superseded by the fixes provided in protocol patch CSCOnn023. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn022

Protocol patch CSCOnn022 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdy53419

2

mdl-q761

Dropping call when nature of connection has echo control set to 1.

CSCdy42418

3

engine

Object ptr rmgBearChan is NULL is added to platform.log after call.

CSCdx68938

3

mdl-callctrl

VSC should send endpoint level DLCX when a 515 error response received.

CSCdy49450

3

mdl-q767

PGW produces duplicate 1070 CDBs when CICs are unblocked.

CSCdy15279

6

protocol

Featurette: Vietnam ISUP Transparency.


This patch provides updates the following:

Q761 Protocol Suite

Q767 Protocol Suite

ConnectionPlaneManager

lcm

Additional information:

Protocol patch CSCOnn021 is superseded by the fixes provided in protocol patch CSCOnn022. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn021

Protocol patch CSCOnn021 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdy44728

2

mdl-q761

PGW does not pass RGN and OCN for HKTA 2200 isup variant.

CSCdy41352

3

mdl-eisup

PGW send RSC upon receive EISUP CPG w/PCI Discard Param set.

CSCdy31675

3

mdl-pri

Some HLC characteristics are not validated - calls fail.

CSCdy40382

3

mdl-q761

PCI generate should be transit interpretation.

CSCdy25786

6

mdl-analysis

Featurette for B-Digit Modification Enhancement.

CSCdy30789

6

mdl-q761

NO SAM is sent in HK ISUP.


This patch provides updates to all protocols.

Additional information:

Protocol patch CSCOnn020 is superseded by the fixes provided in protocol patch CSCOnn021. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCdy25786—B-Digit Modification Enhancement—This featurette (CSCdy25786) strips the European number portability configuration (E_PORTED_NUM) output of the gateway number + the called party number (GN+CdPN) to allow the PGW to send out just the GN.

For Hong Kong local number portability (LNP), if a number is ported, a corresponding GN is appended to the CdPN in the IAM. The PGW uses E_PORTED_NUM which gives the number as GN+CdPN. An additional result type is created to allow the B-digit modification to delete the CdPN portion and send out just the GN.

In HK, there are currently 650k ported numbers, each with a unique GN. The GN length varies (2 to 12 digits long). This featurette strips E_PORTED_NUM out put of GN+CdPN from the last digit backward; since the CdPN has a fixed number of digits.

CSCdy30789—No SAM is sent in HK ISUP—This featurette enables overlap functionality in HKTA_2202.

CSCOnn020

Protocol patch CSCOnn020 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdy37584

2

mdl-q761

Engine process crash and ioCcConfig not able to write to IPC.

CSCdy32910

3

mdl-btnup

BTNUP - ITUReasonCode being over written in CDR by Second REL.

CSCuk36578

3

mdl

SS7 release message mapped incorrectly to NI2+.

CSCdy20914

3

mdl-ansi-ss7

COT always fail if tone is returned before LPA.

CSCdy20931

3

mdl-ansi-ss7

If Initial IAM_w_COT fails subsequent COT fails.

CSCdy29781

3

mdl-btnup

BTNUP MGC sends two CCTF on clear at expiry of CSH Timer.

CSCdy24943

3

mdl-q721

Change request in Brazilian TUP to send charge in ACMs.

CSCdy24945

3

mdl-q721

IAI will not unblock a remotely blocked cic (TUP).

CSCdy37745

3

mdl-q761

HKTA_2202 - restriction about noa Calling party removed.

CSCdy38088

3

mdl-q761

Q761_KOREAN CPG should be accepted before ACM.


This patch provides updates to all protocols.

Additional information:

Protocol patch CSCOnn019 is superseded by the fixes provided in protocol patch CSCOnn020. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn019

Protocol patch CSCOnn019 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdy24009

2

mdl-ni2

No CDRs for segmentation calls with abnormal release.

CSCdy07127

3

mdl-q761

Charge indicator request.

CSCdy12998

3

mdl-q761

Q761_BELG_BCOM hop count support required for certification.

CSCdy20661

3

mdl-q761

PCI on egress should be present when on ingress.

CSCdy16761

3

mdl-btnup

H323 > HSI > BTNUP calls have CPC value 0 in IFAM/IAM.

CSCuk35488

3

mdl-sip

Incorrect MAPPING of SS7 CPG to SIP.

CSCdx60152

6

ioccc7

Allow multiple PCI in all protocols.

CSCdy32946

6

other

NOA, Cause 14, 32 Digit, Overdecadic for Spain.


This patch provides updates the following:

Q761 protocol suite

Q767 protocol suite

SIP protocols

BTUNP protocols

Additional information:

Protocol patch CSCOnn018 is superseded by the fixes provided in protocol patch CSCOnn019. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCdx60152—Allow multiple PCI in all protocols— This featurette allows multiple PCIs in all protocols. Calls that contain multiple PCIs are not rejected. The first PCI is considered and the second PCI is ignored.

CSCdy32946—NOA, Cause 14, 32 Digit, Overdecadic for Spain—This featurette implements the mapping of LNP parameters on the ISUPV2_TELEFONICA and ISUPV2_SPANISH ITU protocols. The parameters are:

1— country specific NOA values

2—Cause 14 for QoR

3—32 and Overdecadic Digits support

CSCOnn018

Protocol patch CSCOnn018 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdy18159

2

mdl-q761

UCIC should not be sent after receiving CFN in ISUPv2_German.

CSCdy17792

2

mdl-sip

Forwarded call discontinues after a 183 session progress.

CSCdy19818

2

mdl-sip

PGW should have recovery mechanism when CSPS does not forward 487.

CSCdy19107

3

mdl-q761

ISUP V2 German: Circuit Not Idle after confusion message was sent.

CSCdx82710

3

mdl-q767

CPG does not complete last leg of Q761-to-EISUP-to-Q767 call.

CSCdx68011

6

mdl-q767

NOA, Cause 14, 32 Digit and Overdecadic for Sweden featurette.


This patch provides updates the following:

CDR_MAN

Q761 suite

Q767 suite

SIP protocols

Additional information:

Protocol patch CSCOnn017 is superseded by the fixes provided in protocol patch CSCOnn018. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCdx68011—This featurette implements the mapping of LNP parameters on Swedish ISUP. Its valid values are:

1—Country specific NOA values

2—Cause 14 for QoR

3—32 digit support

CSCOnn017

Protocol patch CSCOnn017 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdy14230

1

mdl-connctrl

All calls fail on answer from PGW to HSI.

CSCdx84731

2

mdl-callctrl

Call reattempt at the same b channel for isdn nego resend-setup.

CSCuk34818

2

mdl-connctrl

Fax tone detect TG prop causes all H.323 calls to fail.

CSCuk36076

2

mdl-sip

Media not redirected when SIP re-invite received.

CSCuk35748

3

mdl-sip

PGW needs to ACK 487 subsequent to the CANCEL.

CSCdy04602

3

mdl

Incorrect BCI in the Connect message with Q767-RUSS.

CSCdx58164

3

mdl-btnup

PGW initiated CLR/RAN for ISDN call with BTNUP&MdlMemReduction=1,Mistral

CSCdx95586

3

mdl-cdr

CDB 1060 sometimes contains information redundant with 1010.

CSCdx78196

3

mdl-connctrl

On ft/mt notification VSC sends different codec string.

CSCuk24004

3

mdl-q761

VSC does not transit connected number info and discards call history.

CSCuk35763

3

mdl-q767

Tele2Italy: T9 not read from trunk group property.

CSCdy11856

3

mdl-sip

Call Forward pstn->ata->pstn hme0 unplugged with CSPS2.0.1.4.

CSCdy09331

3

protocol

Wrong release code dumped in CDR with BTNUP.


This patch provides updates to all protocols.

Additional information:

Protocol patch CSCOnn016 is superseded by the fixes provided in protocol patch CSCOnn017. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn016

Protocol patch CSCOnn016 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdy07337

2

mdl-eisup

32-digit calling and called numbers are not going through in ISUP.

CSCdy07876

2

mdl-q761

Q761 BELG_COM does not support 32 digits.

CSCdx93434

2

engine

Calls released with InvalidCallRef after failover.

CSCdy01025

2

mdl-q767

ORI insert does not work, ORI is dropped by Ingress SC.

CSCdx84748

3

mdl-q767

Wrong cause code on ISUP SUS T2 timer expiry.

CSCdx94208

3

mdl-q767

Q767: Several incorrect cause code mappings.

CSCdy00998

3

mdl-connctrl

When MDCX for ft/mt notification is NACKed DLCX is sent to one side.

CSCdy09017

3

mdl-cdr

CDR has wrong NOA when call goes through EISUP.


This patch provides updates to all protocols.

Additional information:

Protocol patch CSCOnn015 is superseded by the fixes provided in protocol patch CSCOnn016. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn015

Protocol patch CSCOnn015 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdy00248

2

mdl-analysis

PGW does not use Port # in SIP Contact info if MGCDomain is SRV record.

CSCdx85924

3

mdl-analysis

183 Session progress on Support183=2 or 3 on ACM.

CSCdx78195

3

mdl-connctrl

On reception of vbd/vbdt the VSC responds with wrong transaction id.

CSCdx95823

3

mdl-eisup

Userbusy Invalid B number calls from EISUP do not create CDR.

CSCdx85980

3

mdl-q767

Both collision calls are released with trkgrp property GLARE=1.

CSCdx85930

3

mdl-sip

PGW to ignore record route in SIP 180 ringing.

CSCdx61723

6

other

NOA Cause14 32 Digit and Overdecadic for Spain/Italy/Belgium featurette.


This patch provides updates to all protocols.

Additional information:

Protocol patch CSCOnn014 is superseded by the fixes provided in protocol patch CSCOnn015. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCdx61723—NOA Cause14 32 Digit and Overdecadic for Spain/Italy/Belgium Featurette—This featurette implements the mapping of LNP parameters on three ITU protocols (Spanish, Italian, and Belgium ISUP). The parameters are:

1—Country specific NOA values

2—Cause 14 for QoR

3—32 and Overdecadic Digits support (Spain requires both; Italian already supports both, and Belgium ISUP already supports Overdecadics).

CSCOnn014

Protocol patch CSCOnn014 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdx79979

1

mdl-callctrl

MUTE CALL (mute and released calls after linked dialplan).

CSCdx84756

3

mdl-cdr

Release missing in CDR if stp-call used.


This patch provides updates to the following:

lcm

cdr_man

Additional information:

Protocol patch CSCOnn013 is superseded by the fixes provided in protocol patch CSCOnn014. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn013

Protocol patch CSCOnn013 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdx85531

3

mdl-analysis

BNationalPrefix and BInternationPrefix not functioning on SIP trnkg.


This patch provides updates tothe SIP protocols.

Additional information:

Protocol patch CSCOnn012 is superseded by the fixes provided in protocol patch CSCOnn013. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

CSCOnn012

Protocol patch CSCOnn012 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdw54328

1

mdl-ni2

PGW does status query for IS call to gateway after switch-over.

CSCuk34932

2

mdl-analysis

Use of dw2=99 negates any B-number digmodstring with patch gs9/nn009.

CSCdw66353

3

mdl

IAM will not unblock a remotely blocked circuit in Q767.

CSCdx79819

3

mdl-ansi-ss7

Improper release cause code upon receiving GRS.

CSCdx66443

3

mdl-callctrl

GTD - node B type behaviour with unrecognised IE - drop by LCM.

CSCdx71519

3

mdl-sip

Ingress trunk group missing from CDR for SIP originated calls.


Additional information:

Protocol patch CSCOnn011 is superseded by the fixes provided in protocol patch CSCOnn012. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn011

Protocol patch CSCOnn011 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdx55274

2

mdl-q767

Wrong cause value on ingress (SS7) side on ISUP SUS timer expiry.

CSCdx56685

2

mdl-callctrl

CIC stuck with call out during load test.

CSCuk34257

2

mdl-eisup

Post answer CPG message not passed over EISUP.

CSCuk34258

2

mdl-q761

CPG message parameter discarded after transit over SS7.

CSCuk34269

2

mdl-q761

Transit of IAM containing CUG is rejected.

CSCdx58064

2

mdl-sip

For SIP-PSTN call, cutthrough does not work when distribution is on.

CSCdx61480

2

mdl-q767

Q767 call passes when NOA is set to 0 in CalledPtyNum parameter.

CSCuk24004

3

mdl-q761

VSC does not transit connected number information and discards call history.

CSCdx38642

3

mdl

Kill-call and CDR problems (will not write TimeStamp according to XECfg).

CSCdx62621

3

protocol

GTD-EBM support not operational when enabled per gateway.


Additional information:

Protocol patch CSCOnn010 is superseded by the fixes provided in protocol patch CSCOnn011. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn010

Protocol patch CSCOnn010 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdx52846

2

mdl-callctrl

RSC/GRS does not clear failed COT CIC.

CSCdx51734

2

mdl-connctrl

H323 calls cleared with incorrect location in REL.

CSCdx40330

2

mdl-ni2

Stuck-cic results even after successful RESTART procedure.

CSCdx52895

2

mdl-sip

Plus sign gets added in front of the number for diversion header.

CSCdw53003

3

mdl-analysis

MDP change fails if RTRN_START_ANALYSIS is in call processing path.

CSCdx50185

3

mdl-callctrl

TDM trunk group cut-through should be forced to 3 for HSI.

CSCdx41389

3

mdl-q767

Q.767: several incorrect cause codes mappings.


Additional information:

Protocol patch CSCOnn009 is superseded by the fixes provided in protocol patch CSCOnn010. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn009

Protocol patch CSCOnn009 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdx47581

2

mdl-analysis

AMODDIG does not work.

CSCdx50198

2

mdl-btnup

Calls released when Notify message is received containing o:D/T.

CSCdx32092

2

mdl-eisup

H323 calls not cleared on 5300 after HSI failure.

CSCdx12359

2

mdl-in

INAP trigger module does not support overdecadic digits.

CSCdx12373

2

mdl-in

INAP trigger module overwrites NOA values from analysis with orig CC.

CSCdx37857

3

mdl-q761

GTD - PDC not passing through.

CSCdx21249

6

protocol

LNP Enhancements to Q.761_Portugal Protocol.


Additional information:


Note Patches CSCOnn009 and CSCOgs008 are dependent on one another and must both be installed.


Protocol patch CSCOnn008 is superseded by the fixes provided in protocol patch CSCOnn009. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCdx21249—LNP Enhancements to Q.761_Portugal Protocol—This featurette defines enhancements to the Portuguese ISUP variant in the Media Gateway Controller (MGC) code. The enhancements are required to certify the PGW 2200, working with an Ericsson SCP, for interconnect with the PTT. The enhancements are:

Support for Overdecadic Digits—if a number is ported, the SCP provides a prefix that must be passed outbound to the PTT to allow the correct OLO to receive the call for the subscriber. The format of the prefix to send to the PTT is DXXXYYY<called party number>. The overdecadic D is sent in front of the number. As a requirement, the PGW must support all overdecadic digits (A-F) in Q761_Portugal protocol.

Mapping of Cause Value 14 in Portugal—switches must act on or generate external cause 14 releases to pass interconnect. The PGW must map external cause 14 releases to an internal release cause code. The PGW must support number portability when operating as an originating switch, transit switch, recipient switch, or donor switch supporting the following scenarios:

PGW is the Transit Switch and receives a cause 14 from a donor switch. PGW passes the cause 14 to the originating switch which performs the LNP lookup

PGW is the Donor Switch and after recognizing the number has been ported, generates a cause 14 and passes the cause 14 to the originating switch witch performs the destination LNP lookup.

PGW is the Originating Switch and receives a cause 14 from a donor switch. PGW performs the destination LNP lookup.

PGW is the Recipient Switch and routes the "ported" call.

Do Not Reject Calls if ACM Contains Multiple PCI (parameter compatibility indicators) Option—currently, the PGW either fails the call with a cause 95 or completes the call but sends CFN messages. The PGW cannot fail calls if the ACM contains multiple options (multiple PCI parameters). As a requirement, because the PCI is not a repeatable parameter, the PGW should act on the first PCI parameter, and ignore the subsequent parameters. This applies to all messages that contain PCI parameters.

CSCOnn008

Protocol patch CSCOnn008 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdx09742

2

mdl

SC2200 sent two releases.

CSCdx32341

2

mdl

SC does not pass RNI information received in GTD to IAM.

CSCdx35775

2

mdl

Call is not re-attempted in case of Glare for non-controlling SP.

CSCdx28953

2

mdl-compiler

MDL compiler should not allow integers in element lists.

CSCuk33581

2

mdl-ni2

TV fails with Generic number in GTD.

CSCdx17410

3

mdl

Upon T33 Timeout SC should send REL with cause Normal Unspecified.

CSCdw82503

3

protocol

mdo files no longer supported in release 9.2(2).


Additional information:

Protocol patch CSCOnn007 is superseded by the fixes provided in protocol patch CSCOnn008. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn007

Protocol patch CSCOnn007 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdx17286

2

mdl

SC does not map Ni2+ Progress to ISUP ACM after INR / INF.

CSCdx19494

2

mdl-sip

Contact header does not have port.

CSCdx06785

3

mdl

Receipt of unknown parameters in backward direction - Q.767.

CSCuk31918

3

mdl-callctrl

VSC does not request quaratine loop when sending DTMF to gateway.

CSCdx08903

3

mdl-ansi-ss7

SC2200 does not accept CCR for remotely blocked CIC.


Additional information:

Protocol patch CSCOnn006 is superseded by the fixes provided in protocol patch CSCOnn007. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn006

Protocol patch CSCOnn006 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCuk33007

3

mdl-q761

Mid-call DTMF not handled correctly from UK-ISUP to HSI.

CSCuk33545

2

mdl-callctrl

PGW sends ANM backwards before HSI completes negotiation.


Additional information:

Protocol patch CSCOnn005 is superseded by the fixes provided in protocol patch CSCOnn006. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn005

Protocol patch CSCOnn005 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdx13210

2

mdl

REL-CC 111 maps to 98 by SC.

CSCdw70720

2

mdl-ni2

Stuck CICs reset-cic does not send RSC.


Additional information:

Protocol patch CSCOnn004 is superseded by the fixes provided in protocol patch CSCOnn005. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn004

Protocol patch CSCOnn004 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdx11674

1

mdl

SC sends NI2+ SETUP to NAS before term COT test causing no voicepath.

CSCdx05697

2

mdl-q767

blk-cic does not work for single cic.

CSCdx07718

2

mdl-sip

PGW adds an extra @ symbol in the Route:header address.

CSCdx03183

3

mdl-q767

REL sent instead of RSC when COT received on idle CIC.


Additional information:

Protocol patch CSCOnn003 is superseded by the fixes provided in protocol patch CSCOnn004. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn003

Protocol patch CSCOnn003 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCuk32554

1

mdl-sip

CLI—Unable to Effect CLIR based on SuppressCLiDigits for SIP.

CSCdw32993

2

mdl

NOT from EISUP coming from HSI DTMF core dump.

CSCdw86561

2

mdl

Cause—Location always mapped to User in ISUP REL Message.

CSCdw90392

2

mdl

SC doesnt map Ni2+ Progress to ISUP ACM.

CSCdw90720

2

mdl

SC2200 rejects call with ISUP HOP counter=0 with incorrect cause.

CSCdw91343

2

mdl-sip

SIP callid missing in 1010 Answer tag in CDR record.

CSCdw94447

2

protocol

GTD not sent if Calling Party Number Incomplete indicator= incomplete.

CSCuk32755

2

mdl-sip

SIP to UK-ISUP calls do not contain calling line identity.

CSCdw91008

3

mdl

SC2200 changes location and coding standard fields in Release message.

CSCdx00400

3

mdl

SC need to support Chile ITU-BLUE specs for Recommendation Parameter.

CSCdw91044

3

mdl-q761

SC send RSC when it receives an ISUP MSU w/unrecognized message type.

CSCdx00903

3

mdl-q761

MDL ISUPV2_CZECH protocol variant does not support IPI=2.


Additional information:

Protocol patch CSCOnn002 is superseded by the fixes provided in protocol patch CSCOnn003. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn002

Protocol patch CSCOnn002 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdw70469

2

other

CIC went locally blocked after calls.

CSCuk31901

2

mdl-q761

No RLC sent after REL received on locally blocked circuit.

CSCdw66273

3

mdl

IAM message does not include RedirectionInfo IE in nailed solution.

CSCuk31917

3

mdl-eisup

DTMF digits not forwarded over EISUP.

CSCuk32088

1

mdl-eisup

Incoming calls are dropped when eisup link is put OOS and then IS.

CSCdw36850

2

mdl-ansi-ss7

ChargeNumber is dropped when same as calling party number.

CSCdw64942

2

mdl-sip

PGW unable to gracefully handle bad SIP headers; needs restart.

CSCdw73830

2

mdl-sip

INVITE diversion header is not mapped to re-direct number.

CSCdw79416

2

mdl

FCI mapping should be de-coupled from NOA of CDDN.

CSCuk31906

3

callctrl

WaitforAnswerTimeout trunk group parameter not being used.

CSCdw74149

3

mdl-sip

PGW does not respond to the REFER header.

CSCdw72061

6

mdl-sip

Provisioning of Dual CLI.

CSCdw73839

2

mdl-sip

SIP to PSTN call released after 15 seconds when divert uncond via CSPS.

CSCdw81870

2

mdl

SC always maps SR indicator in SUS/RES message to Network Initiated.

CSCdw26901

2

mdl

SS7 CICs in LOCMAN state after gateway reload with active calls.

CSCdv59315

3

mdl

Need to remove cause code translation towards NAS.


This patch provides updates to:

sagt

ca

sim

SS7

MGCP

SIP

ioChanMgr

engine

mml

libpolcomp.so

libpolnuman.so

libpolroute.so

lib_cmg.so

lib_cxn.so

lib_eng.so

lib_rmg.so

toolkit

iocm

Additional information:

Protocol patch CSCOnn001 is superseded by the fixes provided in protocol patch CSCOnn002. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Some bug fixes might require components that are contained in both patches. However, the bug might only be listed in either protocol patch CSCOnn002 or system patch CSCOgs002. To ensure that all bug fixes operate as designed, both protocol patch CSCOnn002 and system patch CSCOgs002 must be installed.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOnn001

Protocol patch CSCOnn001 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdw52076

2

mdl

SC2200 resets the circuit.

CSCdw42682

3

mdl-ni2

NI2 release state machine ignores LReleaseCont in REL initd. RelSeq.

CSCdw42692

3

mdl-ni2

NI2 release state machine ignores LReleaseCont on LinkFail in Conn. state.

CSCdw42696

3

mdl-ni2

NI2 rel. state machine does not send LRelComp on linkfail in some scenarios.

CSCdw42699

3

mdl-ni2

NI2 release state machine does not send proper signal to LCM on dic colsn.

CSCdw45305

3

mdl-ni2

NI2 release state machine does not send right signal to LCM on T305 exp+rcv.RLC.

CSCdw45332

3

mdl-ni2

NI2 release state machine does not send right signal to LCM on rcv.RestartAck.

CSCdv77873

6

protocol

Support for IRI/ORI parameters in Q.767 featurette.

CSCdw43415

6

protocol

Mandatory CLI Over Trunk Group featurette.


This patch provides updates to all protocols.

Additional information:

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

This protocol patch contains a new protocol, Q767_SINGAPORE. Since variant.dat has been updated and is included in the CSCOgs001 system patch, these two patches (protocol and system) are both required.

CSCOgs043

System patch CSCOgs043 resolves the following DDTS ticket:

Identifier
Severity
Component
Description

CSCsa98155

2

engine

Ghost Calls are created on STBY because of Replicator flap.


This patch provides updates to the following:

lib_cmg.so

Additional information:

System patch CSCOgs041 is superseded by the fixes provided in system patch CSCOgs042. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

CSCOgs042

System patch CSCOgs042 resolves the following DDTS ticket:

Identifier
Severity
Component
Description

CSCed57037

3

ioccpriip

Patch to capture RLM_DTYPE_START_Req as Error Level msgs.


This patch provides updates to the following:

ISDNIP

Additional information:

System patch CSCOgs041 is superseded by the fixes provided in system patch CSCOgs042. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

CSCOgs041

System patch CSCOgs041 resolves the following DDTS ticket:

Identifier
Severity
Component
Description

CSCed30469

3

engine

Unexpected RSC from PGW clears Active Call.


This patch provides updates to the following:

engine

lib_eng.so

lib_cmg.so

lib_rmg.so

lib_cxn.so

Additional information:

System patch CSCOgs040 is superseded by the fixes provided in system patch CSCOgs041. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

CSCOgs040

System patch CSCOgs040 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCec57330

3

ioccc7

SS7 core dump when PGW was going down - Not consistent.

CSCea59671

4

mmdb

Provide script to remove TimesTen replication.


This patch provides updates to the following:

added delete_replication.sh

Additional information:

System patch CSCOgs039 is superseded by the fixes provided in system patch CSCOgs040. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

CSCOgs039

System patch CSCOgs039 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCec29137

2

snmp

memory leak in the sagt process.

CSCec24423

3

engine

Failed to get FCIBCIEnable property value.

CSCec34513

3

pxelogger

Control characters in platform.log messages corrupts grep display.


This patch provides updates to the following:

patch

engine (and engine libraries)

sagt

mmSAgt

MGCP

libsa.so

libpxelog.so

libxe.so

Additional information:

System patch CSCOgs038 is superseded by the fixes provided in system patch CSCOgs039. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

CSCOgs038

System patch CSCOgs038 resolves the following DDTS ticket:

Identifier
Severity
Component
Description

CSCeb66052

6

other

Derived FCI and BCI for Interworking featurette.


This patch provides updates to the following:

XECfgParm.dat

propSet.dat

Additional information:

System patch CSCOgs037 is superseded by the fixes provided in system patch CSCOgs038. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

Both patches CSCOnn036 and CSCOgs038 must be installed.

For information on the Derived FCI and BCI featurette, refer to information provided in patch CSCOnn036.

CSCOgs037

System patch CSCOgs037 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCeb33315

2

provision

Migration from 9.2(2) to 9.4(1) fails due to missing percRoute.dat.

CSCeb35457

3

engine

Deleted naspath continues to be CheckPointed.

CSCeb07238

6

other

New Cause Code for Call Re-Attempts featurette.


This patch provides updates to the following:

engine

mml

pom

XECfgParm.dat

Additional information:

System patch CSCOgs036 is superseded by the fixes provided in system patch CSCOgs037. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

Both patches CSCOnn034 and CSCOgs037 must be installed.

For information on the New Cause Code for Call Re-Attempts featurette, refer to the New Cause Code for Call Re-Attempts in the New Features in This Release section of this document.

CSCOgs036

System patch CSCOgs036 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCea53419

3

iocm

MSO Warmstart Error.

CSCea83537

3

provision

corrupted files.dat should not stop the provisioning command.

CSCea90444

3

provision

local port number of session set should not be changed via prov-ed.

CSCeb06939

3

engine

reset cic clears GW block.

CSCeb15001

3

ioccc7

Core from SS7 process due to race condition.


This patch provides updates to the following:

ioChanMgr

engine

mml

libpolcomp.so

libpol

SS7

Additional information:

System patch CSCOgs035 is superseded by the fixes provided in system patch CSCOgs036. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

CSCOgs035

System patch CSCOgs035 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCea19890

3

mml

vld-cic command timed out in variant Q767_BASE.

CSCea43229

3

engine

rtrv-admin-state causes core file.

CSCea45365

3

cmm

CMM: CDR_Viewer: CDE-Tag_4108 and CDE-Tag_4109 are reversed.

CSCea47661

3

provision

No file exported with subdirectory specified in prov-add:files.

CSCea47734

3

mml

Incorrect message for prov-dlt:files:name=bcfile.

CSCea47883

3

provision

Can not import trkgrp file after prov-dlt:files:name=trkgrp.

CSCea63749

3

provision

DialPlan prov err: resulttable:The result .. cannot be connected to.


This patch provides updates to the following:

ioChanMgr

engine

mml

libpolcomp.so

libpolnuman.so

presentation.dat

propSet.dat

position.dat

Additional information:

System patch CSCOgs034 is superseded by the fixes provided in system patch CSCOgs035. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

CSCOgs034

System patch CSCOgs034 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCea28944

3

mmlhelp

Invalid target<pt code> need to be removed from prt-call.

CSCea37989

3

engine

files.dat corrupted

CSCea38411

3

provision

prov-rtrv:siprttrnkgrp dumps junk along with output data.

CSCea39925

3

engine

Query-cic and rtrv-cic show different cic state.


This patch provides updates to the following:

mml help

mml

engine

pol

mmlCommands.dat

Additional information:

System patch CSCOgs033 is superseded by the fixes provided in system patch CSCOgs034. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

CSCOgs033

System patch CSCOgs033 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCea19223

3

engine

After switchover the call duration in mute call report incorrect.

CSCea14695

3

provision

prov-ed:siprttrnkgrp url=new_entry prov-rtrv causes core dump.

CSCea20373

3

ioccisdnl3

ISDNL3 core file.

CSCea27254

3

toolkit

TOOLKIT: CDR_View: GUI hangs if query on Call_Reference_ID.

CSCea22996

3

ioccxgcp

mgcp-1 process terminates when mgcp communication to gw is lost.


This patch provides updates to the following:

MGC Toolkit

libpol

MGCP

ISDNL3

engine

mml

Additional information:

System patch CSCOgs032 is superseded by the fixes provided in system patch CSCOgs033. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

CSCOgs032

System patch CSCOgs032 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCea03671

2

ioccc7

SC not able to send msgs to certain destinations on large configs.

CSCea03686

2

ioccc7

Switchover fails to complete: Boxes stopped in standby.

CSCea19102

2

upgrade

DialPlan is not migrated while doing upgrade 7.4(11) to 9.4(0.11).

CSCdz74989

3

ioccc7

MSO refused warm start-up failed.

CSCdz83181

3

mml

MML updates needed for commands involving trunk group.

CSCdz85720

3

engine

Manual CIC Block does not work when BLK=GATEWAY & REMAUTO.

CSCdz89613

3

provision

Editing individual rttrnkgrp props corrupts trunkGroup AttrubuteIdx.

CSCea07185

3

toolkit

TOOLKIT: Measurement_Viewer: CURRENT_STOP_TIME selection broken.

CSCea10287

3

provision

sigsvcprop error message misleading.

CSCea11634

3

toolkit

TOOLKIT: MGC_Backup and MGC_Restore flickers open/close at startup.

CSCea15124

3

engine

Engine does not disconnect from TimesTen database on shutdown.

CSCea17264

3

engine

Larger number of engine errors on the standby box for released calls.


This patch provides updates to the following:

MML help

MGC Toolkit

replicator

ISDNIP

MGCP

SIP

EISUP

ISDNL3

TALI

engine

mml

SS7

Additional information:

System patch CSCOgs031 is superseded by the fixes provided in system patch CSCOgs032. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

CSCOgs031

System patch CSCOgs031 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdz83084

2

iocm-sj

IOCM comes up in stopped state after upgrading 9.2(2) to 9.3(2).

CSCdz50457

3

engine

Core file created.

CSCdz85745

3

usability

Inconsistency in naming of IP-Addresses on MGC_Setup.


This patch provides updates to the following:

engine

IOCM

mml help

MGC_Setup

Additional information:

System patch CSCOgs030 is superseded by the fixes provided in system patch CSCOgs031. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

CSCOgs030

System patch CSCOgs030 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdz41460

2

snmp

CIAgent does not detect the SUN V120 ERI ethernet interfaces.

CSCdz63501

3

mmlhelp

MML help:prov-exp SIGNAL needs to be removed as a valid TID.


This patch provides updates to the following:

mmlhelp

mib2agt

Additional information:

System patch CSCOgs029 is superseded by the fixes provided in system patch CSCOgs030. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

CSCOgs029

System patch CSCOgs029 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdz58556

3

engine

PGW - crash after switchover.

CSCdz69216

3

iocceisup

EISUP hog CPU.

CSCdy48084

3

iocm

rtrv-tc:all Interface Disabled. Must bounce PGW.

CSCdz32935

3

provision

Deleted CONDRTE name still appears in prov-exp.

CSCdz68301

6

engine

Add Call duration in Suspected mute call log in PGW.

CSCdx88717

6

iocm

dmfe interfaces (10/100BaseT) not supported.



This patch provides updates to the following:

libpom.so

libpolfiles.so

libpolroute.so

libda.so

libpolnuman.so

lib_cmg.so

libpolcomp.so

lib_cxn.so

lib_eng.so

lib_rmg.so

foverd

EISUP

MGCP

ISDNL3

ioChanMgr

engine.no_smartalloc

engine.smartalloc

pom

mml

Additional information:

System patch CSCOgs028 is superseded by the fixes provided in system patch CSCOgs029. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

CSCOgs028

System patch CSCOgs028 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdz47294

3

dumper

CDE tag 6004 in CDR file header and footer exceeds limit in spec.

CSCdz54239

3

engine

Engine cannot free up bearChan after receiving channel mgmt calls.

CSCdz52337

3

mmlhelp

mml-help: Error in prov-add:files session.

CSCdz 53889

3

provision

Allow Priority 2 route for Mated STP pair.


This patch provides updates to the following:

libpolcomp.so

libpolnuman.so

lib_cmg.so

lib_eng.so

cdrDmpr

mml

engine.no_smartalloc

engine.smartalloc

Additional information:

System patch CSCOgs027 is superseded by the fixes provided in system patch CSCOgs028. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

CSCOgs027

System patch CSCOgs027 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdy71765

2

iocm

Dynamic delete and readd of DPC - Mate remains INB.

CSCdz42426

2

upgrade

Script needed to replicate Timesten between 9.2(2) and 9.3(2).

CSCdz41539

3

engine

Error incorrectly printed in platform log is misleading.

CSCdz43256

3

engine

Do not allow dynamic deletion of Trunk with active call.

CSCdz37648

4

engine

Need more debug info for mute call.


This patch provides updates to the following:

mod_replication_port.sh

librudp.so

libsa.so

libmmdb.so

libpom.so

libpolbase.so

libpolfiles.so

libconvutil.so

libda.so

libpolroute.so

libxe.so

libpolnuman.so

lib_cmg.so

libpolcomp.so

lib_cxn.so

lib_eng.so

lib_rmg.so

cfgM

almM

mmdbd

mmTest

measMgr

procM

cms

cdrDmpr

amDmpr

ISDNIP

replicator

EISUP

SS7

foverd

ISDNL3

TALI

TCAP

sagt

mmSAgt

ioChanMgr

mml

engine.no_smartalloc

engine.smartalloc

Additional information:

System patch CSCOgs026 is superseded by the fixes provided in system patch CSCOgs027. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

CSCOgs026

System patch CSCOgs026 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdz30575

2

upgrade

Migration of dialplans failed from 7.4(x) to 9.2(x).

CSCdz15886

3

other

The config-lib tool changes the dat files ownership under ../etc.

CSCdz29535

3

other

chk_inv fails for Solaris patches on Sol8 OS 02/02.

CSCdz27504

3

procm

PGW OOS due to IPLINK de-provision.

CSCdx65443

3

provision

Dynamic reconfig of some numbering plan trunk group properties fails.

CSCdy82535

3

provision

Invalid route priority not detected in provisioning.

CSCdz30678

3

toolkit

In MDL environment, get_trc.sh fails as .so files missing.


This patch provides updates to the following:

libpolbase.so

libpolcomp.so

libpolfiles.so

libpolroute.so

libpolnuman.so

chk_inv

procM

pom

mml

Toolbar.tbc

config-lib

get_trc.sh

migrate_cpp_5_6

Additional information:

System patch CSCOgs025 is superseded by the fixes provided in system patch CSCOgs026. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

CSCdz30575—Migration of Dialplans Failed from 7.4(x) to 9.2(x)—If you receive the migrating dialplan error during migration, refer to the Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide, Chapter 5, Upgrading to Cisco MGC Software Release 9.3(2), at the following url:

http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/swinstl/index.htm.

CSCOgs025

System patch CSCOgs025 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdz23398

2

provision

STBY comes up OOS if pom.dataSync is set to TRUE.

CSCdy46285

3

engine

SC2200:Memory Leak in engine.smartalloc over period of time.

CSCdy85209

3

engine

Incorrect clear cause.

CSCdz11836

3

engine

SC need to synchronize bearer channel status.

CSCdz15685

3

mdl-callctrl

Spontaneous switchover in PGW during Re-routing fo the call.

CSCdz14120

3

pxelogger

LogView:Log Default Date/Time-Range off 1hr.


This patch provides updates to all libraries and binaries.

Additional information:

System patch CSCOgs024 is superseded by the fixes provided in system patch CSCOgs025. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

CSCOgs024

System patch CSCOgs024 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdz01483

3

ioccxgcp

mgcp link OOS when more than 1 local IP addresses are used.

CSCdy83812

3

measm

Meas Mgr counts duplicate measurements against max limit.

CSCdz03288

4

engine

Error log for failed call was chopped.


This patch provides updates to:

libxe.so

libpolnuman.so

lib_cmg.so

MGCP

engine.no_smartalloc

engine.smartalloc

Additional information:

System patch CSCOgs023 is superseded by the fixes provided in system patch CSCOgs024. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

CSCOgs023

System patch CSCOgs023 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdy68963

2

engine

PGW sends wrong GRSA during HW failure.

CSCdy74282

2

engine

Desired platform field in XECfgParm is case sensitive it should not.

CSCdy77004

2

iocceisup

EISUP core when setting eisup links OOS or IS.

CSCdy78597

2

iocceisup

EISUP core dump upon switchover.

CSCdy21573

3

engine

SVC=Notset is set in IPLNK configuration.

CSCdy77222

3

engine

Need to print out error log if mute call is detected.

CSCdy69559

3

iocceisup

EISUP link not function correctly after migrating 9.2(2) to 9.3(1)T.


This patch provides updates to:

lib_cmg.so

lib_cxn.so

libpolcomp.so

lib_eng.so

lib_rmg.so

engine.no_smartalloc

engine.smartalloc

EISUP

Additional information:

System patch CSCOgs022 is superseded by the fixes provided in system patch CSCOgs023. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

CSCOgs022

System patch CSCOgs022 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdy66616

1

mml

Unable to prov more than 32 links error msg with valid batch file.

CSCdy61442

2

engine

CPU Timer Interval is not disabled if CPUTimerInterval is set to 0.

CSCdx20455

2

provision

SIP: rttrnkgrp entry with type=9 mess up rttrnkgrp & siprttrnkgrp table.

CSCdx95892

2

iocm

Dynamic re-add of ss7path, dpc, trunks are not added properly.

CSCdy49086

2

iocm

Calls release with NtwkOutOfOrder/Resource-Unavail after failovers.

CSCdy50259

3

ioccxgcp

MGCP Retry message in platfrom.log should be printed at all levels.

CSCdy48913

3

iocm

MGCP-Link: OFF-DUTY link set back to IS, still shows OFF-DUTY.

CSCdy57808

3

iocm

CGB sent when one mgcp link oos, off_duty moves when both link oos.


This patch provides updates to:

libpolcomp.so

lib_eng.so

engine.no_smartalloc

engine.smartalloc

ioChanMgr

mml

MGCP

Additional information:

System patch CSCOgs021 is superseded by the fixes provided in system patch CSCOgs022. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

CSCOgs021

System patch CSCOgs021 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdy57649

2

provision

Provisioning is not blocked during Seamless upgrade.

CSCdy62867

3

engine

MGCP ERR: Unrecognized control vector 99.

CSCdy51856

3

iocm

When C7LNK-INH is executed twice, link goes into CONFiguration mode.

CSCdy56160

3

provision

Invalid conditional routing names allowed in 9.2(2) causing migrate problems.

CSCdy21663

3

toolkit

Toolkit: CDR_Viewer: Eight 1060 tags not displayed for EndOfCall-CDB.

CSCdy37888

3

toolkit

Retired tags need to be removed from CDR viewer code.

CSCdy39103

3

toolkit

Please remove tag 5000 in 1090 and 1100 in the viewer.


This patch provides updates to:

libconvutil.so

libpolroute.so

SS7

MGCP

SIP

EISUP

ISDNL3

TALI

pom

ioChanMgr

position.dat

Additional information:

System patch CSCOgs020 is superseded by the fixes provided in system patch CSCOgs021. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

CSCdy56160—Invalid conditional routing names allowed in 9.2(2) causing migrate problems—In previous 9.2(2) releases, conditional routing name validation did not occur. Therefore, the potential that invalid conditional routing names were created exists.

As of patch CSCOgs021, conditional routing name validation occurs in release 9.2(2). Previously existing configurations should be checked to ensure that invalid names are not used. Conditional routing names should consist of 1-20 alphanumeric characters. If your conditional routing name is invalid, the routeAnalysis.dat file must be edited. Contact TAC so that the engineering team can be notified to have your information modified.

If an invalid conditional routing name is used in release 9.2(2) and you attempt to upgrade to a newer release (9.3(2) and higher), the migration will fail because the validation of the conditional route name fails.

CSCOgs020

System patch CSCOgs020 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdy39073

2

flovr

Switchover takes too long when active process crashes.

CSCdy45291

2

ioccxgcp

MGCP link shows wrong state in standalone mode.

CSCdy46777

3

engine

Blk-cic not operational - no CGB sent out.

CSCdy44942

3

mdl-tools

Option G for get_trc.sh does not work.

CSCdy44110

3

mml

sta-softw needs to be removed from MML help.

CSCdy46328

3

provision

Provisioning should allow different sw-types on same SS7 IOCC.


This patch provides updates to:

lib_cmg.so

lib_cxn.so

lib_eng.so

lib_rmg.so

libpom.so

libpolcomp.so

pom

replicator

sagt

mmSAgt

ioChanMgr

engine.no_smartalloc

engine.smartalloc

mml

foverd

get_trc.sh

sta-softw.help

stp-softw.help

Additional information:

System patch CSCOgs019 is superseded by the fixes provided in system patch CSCOgs020. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

For information on provisioning restrictions imposed while upgrading to patches that support the Seamless Upgrade feature, refer to Seamless Upgrade under the New Features section.

CSCOgs019

System patch CSCOgs019 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdy36697

2

engine

Unable to modify SC config due to absence of SS7 route for some dpc.

CSCdy11883

2

ioccsip

Either hme down no pgw TRYING response to INVITE.

CSCdy15578

3

iocm

OFF_DUTY state of MGCP/IP-LNK is mismatch between active and standby.

CSCdy38844

3

mml

MML core dumps on prov-export.

CSCdy38706

3

provision

MMLHELP: Get INPUT INVALID TARGET when executing HELP:PROV-EXP.

CSCdy41805

6

other

Ratigan - Netra 20 Support.


This patch provides updates to:

chk_inv

engine.no_smartalloc

engine.smartalloc

lib_cmg.so

lib_cxn.so

lib_eng.so

lib_rmg.so

libpom.so

ioChanMgr

mml

Additional information:

System patch CSCOgs018 is superseded by the fixes provided in system patch CSCOgs019. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCdy41805—The Software Control Inventory feature has been enhanced to recognize the Netra 20 as a legitimate PGW 2200 host platform.

CSCOgs018

System patch CSCOgs018 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdy30928

2

provision

prov-add: nailedtrunk cannot add NAS dsttimeslot range 1-31 for E1 SPAN.

CSCdy18222

2

engine

set-admin-state: lock causes CGB with immediate release sent to far end.

CSCdy12454

3

other

Software inventory control does not properly handle Solaris patches.

CSCdy24054

3

other

Software inventory control program cannot find MGC files.


This patch provides updates to:

chk_inv

engine.no_smartalloc

engine.smartalloc

lib_cmg.so

lib_cxn.so

lib_eng.so

lib_rmg.so

libpolbase.so

libpolcomp.so

libpolfiles.so

libpolnuman.so

libpolroute.so

libpom.so

mmSAgt

mml

pom

replicator

sagt

Additional information:

System patch CSCOgs017 is superseded by the fixes provided in system patch CSCOgs018. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOgs017

System patch CSCOgs017 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdy14868

2

provision

Modify nailed trunk SRCSVC field cause DSTTIMESLOT set to junk value.

CSCdy07603

3

provision

Invalid CIC are allowed in prov-add:nailedtrnk w/SPANSIZE specified.

CSCdy19113

3

provision

Not able to change CLIDefaultAllowed property using mml command.

CSCdx68011

6

engine

NOA, Cause 14, 32 Digit and Overdecadic for Sweden.


This patch provides updates to:

libpolbase.so

libpolcomp.so

libpolfiles.so

libpolnuman.so

libpolroutes.so

lib_eng.so

libpom.so

engine.no_smartalloc

engine.smartalloc

pom

mml

Additional information:

System patch CSCOgs016 is superseded by the fixes provided in system patch CSCOgs017. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOgs016

System patch CSCOgs016 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdx88061

2

ioccsip

Siplink always in service although hme interface is down.

CSCdy11069

2

ioccsip

Need to add maddr parameter to Contact header - TEMPORARY.

CSCdy12278

2

ioccsip

PGW fails to recognize its own via in a comma separated list.

CSCdy14417

2

replicator

Active calls are ramdomically dropped when testing failover SC2200.

CSCdy04577

3

engine

COT_FAIL CIC stuck indefinitely upon failover.

CSCdy08358

3

engine

selseq=ITU2 CIC selection information request.

CSCdy08356

3

mdl-cdr

Incorrect release cause code in CDR record.

CSCdy05018

4

mml

Diaglog command issues need addressed.


This patch provides updates to:

lib_eng.so

lib_rmg.so

engine.no_smartalloc

engine.smartalloc

replicator

ioChanMgr

SIP

mml

Additional information:

System patch CSCOgs015 is superseded by the fixes provided in system patch CSCOgs016. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOgs015

System patch CSCOgs015 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdx85634

2

engine

Engine_smartall core dumps during 24 hour test.

CSCdy02534

2

engine

Core dump; not able to export dialplans.

CSCdx70782

3

provision

numan-rtrv:cause INDEX should be CAUSEVALUE.

CSCdx92221

3

iocm

RTRV-RTE shows incorrect state after TFP message.

CSCdy10708

3

mmlhelp

Documents need to describe transient state query-cic.

CSCdx72511

3

userdoc

Documents need to more clearly define kill-call.


This patch provides updates to:

lib_cmg.so

lib_eng.so

lib_cxn.so

lib_rmg.so

libpolfiles.so

libpolnuman.so

libpolroute.so

replicator

engine.no_smartalloc

engine.smartalloc

ioChanMgr

mml

Additional information:

System patch CSCOgs014 is superseded by the fixes provided in system patch CSCOgs015. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOgs014

System patch CSCOgs014 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdy00230

2

other

Mulitple call forwards between SIP and PSTN.

CSCdx94403

3

engine

When controller is down CGB with immediate release to be sent.

CSCdx37330

3

ioccsip

Active system does not show correct state of SIP links.

CSCdx37375

3

ioccsip

Wrong state of SIP links when SIP link is set to OOS.

CSCdx77744

3

iocm

Setting of EISUP-links leads to mismatch status on EISUP-DEST.

CSCdx93172

3

mml

mml does not allow two ip links with same ip address and peer port.

CSCdx60231

3

mmlhelp

For BTNUP reset-cic does not work.

CSCdx60893

3

provision

Need validation for prova-add:nailed src/dsttimeslot field.

CSCdx77137

3

provision

Failures to write provisioning data to disk are not caught.

CSCdx92417

3

provision

Prov-add allows duplicate ss7 cics.

CSCdx84557

3

replicator

Call synchronization does not occur with only Link B connected.

CSCdx61723

6

other

NOA Cause14 32 Digit and Overdecadic for Spain/Italy/Belgium featurette.


This patch provides updates to:

lib_cmg.so

lib_eng.so

libconvutil.so

libda.so

libpolbase.so

libpolcomp.so

libpolfiles.so

libpolnuman.so

libpolroute.so

libpom.so

replicator

engine.no_smartalloc

engine.smartalloc

SIP

MGCP

SS7

EISUP

ioChanMgr

mml

pom

Additional information:

System patch CSCOgs013 is superseded by the fixes provided in system patch CSCOgs014. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCdx61723—NOA Cause14 32 Digit and Overdecadic for Spain/Italy/Belgium Featurette—This featurette implements the mapping of LNP parameters on three ITU protocols (Spanish, Italian, and Belgium ISUP). The parameters are:

1—Country specific NOA values

2—Cause 14 for QoR

3—32 and Overdecadic Digits support (Spain requires both; Italian already supports both, and Belgium ISUP already supports Overdecadics).

CSCOgs013

System patch CSCOgs013 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdx81270

1

engine

Reload RSIP doesnt recover BLK=GATEWAY CICs in PGW.

CSCdx79240

2

pxelogger

Not able to execute mml commands after running load test for 12 hours.

CSCdx79984

2

engine

GRS not acked after HW failure.

CSCdx80418

2

engine

SC cored when doing manual switch over.

CSCdx89870

2

engine

CQM for unequipped circuit fails UCIC response.

CSCdx93652

2

flovr

Crashing process can loop indefintely.


This patch provides updates to:

libpxelog.so

replicator

sagt

lib_cmg.so

lib_cxn.so

lib_eng.so

lib_rmg.so

engine.no_smartalloc

engine.smartalloc

mml

Additional information:

System patch CSCOgs012 is superseded by the fixes provided in system patch CSCOgs013. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOgs012

System patch CSCOgs012 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdx59012

2

engine

VSC releases CICs prior to receive GRA or CGUA.

CSCdx77379

3

engine

Timer T19 expired after CGBA received from SS7 network.


Additional information:

System patch CSCOgs011 is superseded by the fixes provided in system patch CSCOgs012. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOgs011

System patch CSCOgs011 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdx67988

1

engine

Excessive call failures stuck cics when sending multiple ISUP parameters.

CSCdx56882

2

engine-sj

SC cannot process call with NI2 segmented messages and engine=debug.

CSCdx77141

2

replicator

Replicator cores on startup—standalone only.


Additional information:

System patch CSCOgs010 is superseded by the fixes provided in system patch CSCOgs011. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOgs010

System patch CSCOgs010 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdx03812

2

iocm

EISUP links went to COOS afte failover&failback.

CSCdx38260

2

iocm

Dynamically deleted/modified NAS links do not work properly.

CSCdx17509

2

replicator

After bring hme interfaces down/up problems with switchover for 5 to 10 minutes.

CSCdx34803

2

replicator

While 10,000 calls are up on ACTIVE, .4% are not replicated to standby.

CSCdx15580

3

iocm

The perf counters generated by PGW are different than documented.

CSCdx19122

3

iocm

inb->foos denied for dynamically added ss7 links.

CSCdx15297

3

provision

Same peer port should not be allowed for ip links on naspaths on dif.

CSCdx46359

3

provision

GTD info not sent to NAS after gtd parameter changes.

CSCdx63327

4

mmlhelp

MML help needs to be updated.


Additional information:

System patch CSCOgs009 is superseded by the fixes provided in system patch CSCOgs010. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOgs009

System patch CSCOgs009 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdx61520

1

engine

Sust:Engine coring when blocking CICs.

CSCdx61749

1

provision

btnup 3.1KHz not able to associate profile with trunk group.

CSCdx63046

1

provision

Deviation in software caused unsuccessful merge.

CSCdx56882

2

engine-sj

SC cannot process call with NI2 segmented messages and engine=debug.

CSCdx59150

2

engine-sj

Engine core dump for SIP calls in debug mode.

CSCdx53255

3

engine

Engine dumps core after an mml sw-over on previous active PGW.

CSCdw91618

2

flovr

Slave not active until core file written on Master.

CSCdx19122

3

iocm

inb->foos denied for dynamically added ss7 links.

CSCdx48770

3

iocm

IOCM generates SW Fail alarm when mgcp link state set to OOS in VSC.

CSCdx52198

3

mml

Resultname /Resultsetname.

CSCdx33526

3

mmlhelp

Sust:rtrv-eqpt shows card INB but calls are still processed.

CSCdx51773

4

mml

SND commands in MML should be removed.


Additional information:

System patch CSCOgs008 is superseded by the fixes provided in system patch CSCOgs009. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOgs008

System patch CSCOgs008 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdx12388

2

mdl-in

Trigger.dat needs updating to support CONTIN and CONNECT cutnpaste.

CSCdx48492

2

mdl-sip

Multiple IP A records from DNS are not used when first fails.

CSCuk33572

2

mdl-sip

Normal call clearing forwards from SIP client has location 10.

CSCdx41413

3

dumper

cdrDmpr incorrectly tries to rm .cdr_xx with var/spool diff file sys.

CSCdx42143

3

ioccc7

Cannot use the same SS7 link for ISUP and TUP traffic.

CSCdx33524

3

mml

Sust:rtrv-eqpt shows card INB but calls are still processed.

CSCdx34340

3

mml

mml prov-rtrv:dchan by SVC field is not working as design.

CSCdx35644

3

mml

MML Help command is case sensitive.

CSCdx20208

3

other

MGCbackup failed if MGC stopped with a provsioning session open.

CSCdx38315

3

other

MGCbackup do not list all scheduled backups setup by different users.

CSCdx42730

3

procm

A few problems related to removing dangling channel controller.

CSCdx04293

3

provision

Cannot use same SLC in 2 linksets with same APC and different OPC.

CSCdx13123

3

provision

Provision allows two sip links to the same IP address on PGW2200.

CSCdx18088

3

provision

Max number of route list is 6 instead of 5 for conditional route.

CSCdx37984

3

provision

Provisioning should limit the number of RLM ports to 8.

CSCdx42119

3

provision

Provisioning should allow different sw-types on same SS7 IOCC.

CSCdw61819

6

other

Software Inventory Control.


Additional information:


Note Patches CSCOnn009 and CSCOgs008 are dependent on one another and must both be installed.


System patch CSCOgs007 is superseded by the fixes provided in system patch CSCOgs008. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCdw61819—Software Inventory Control—this featurette detects incompatible software versions residing on test systems in the various Cisco testing facilities. Each software release provides a file containing checksum information for all the libraries and executables being installed. The Software Inventory Control utility generates checksums on the production system then compares those checksums with the values in the installation master file. A discrepancy indicates that the software on the box does not match the software that was originally installed.

This featurette does not identify the source of a problem or the correct software to install. It does indicate if a problem exists prior to the testing of incompatible software.

CSCdx05822— ISDN Q931 3.1Khz Incorrectly Coded for BTNUP —this featurette extends the function of the existing defaultBC property to include BTNUP-based trunk groups. The property can be set to SPEECH or 3_1_KHZ. The default setting is SPEECH.

If the property is set to 3_1_KHZ, PGW converts the outgoing ISDN 3.1KHz (CAT3) call over the BTNUP TrunkGroup to an ISDN speech (CAT2) call. This property has no impact on outgoing ISDN data (CAT1) and speech (CAT2) calls over the BTNUP TrunkGroup.


Note CSCdx05822 was propagated forward with 9.1(5) patch CSCOgs011.


CSCOgs007

System patch CSCOgs007 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdx24991

2

engine

SC2200 core dumped when prov-add:files was done.

CSCdw84975

3

ioccc7

MTP-3 Changeback Declaration not implemented.

CSCdx33645

3

ioccpriip

Cannot support single NAS interface with dual local interface.


Additional information:

System patch CSCOgs006 is superseded by the fixes provided in system patch CSCOgs007. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOgs006

System patch CSCOgs006 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdx09580

2

engine

Segmented ISDN message sometimes interrupted with other messages.

CSCdw77330

3

mmlhelp

help:set-iplnk should be updated for nas links.

CSCdx14033

2

ioccsip

Standby shows SIP links IS STDBY after dynamic configuration.

CSCdx21171

4

ioccsip

siptool trace filter fails to work.

CSCdx07598

2

iocm

Dynamically readding dpc leaves the ss7 dest in INB.

CSCdw93244

2

iocm

Cannot bring both linksets with same DPC and different OPC in service.

CSCdx16832

2

ioccxgcp

mgcp links shows wrong status on standby.

CSCdx08951

3

iocm

Warm-Start Alarm in Active PGW.


Additional information:

System patch CSCOgs005 is superseded by the fixes provided in system patch CSCOgs006. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOgs005

System patch CSCOgs005 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdx10503

1

ioccsip

After failover SIP link goes to OOS CONF.

CSCdw91615

2

engine

Engine core after setting signaling service back IS.

CSCdw47478

2

engine-sj

SC renegotiates call from NAS when NI2+ message is segmented due to GTD.

CSCdx04824

2

engine-sj

ST:GSM update from SC not sent on all NFAS interfaces.

CSCdx13228

2

ioccsip

SIP calls are not checked for priority for more than one SIP link.

CSCdx13334

2

ioccsip

Second SIP link should show IS offduty.

CSCdx14153

2

provision

IOCM does not come to service after adding mgcp links dynamically.

CSCdx01749

3

ioccc7

After deleting an ss7-IOCC cannot do switch back.


Additional information:

System patch CSCOgs004 is superseded by the fixes provided in system patch CSCOgs005. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOgs004

System patch CSCOgs004 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdx11625

1

dumper

CDR Dumper creating files with duplicate sequence numbers.

CSCdx10739

1

engine

SS7 to SIP and SIP to SS7 calls not going through.

CSCdx10503

1

ioccsip

After failover SIP link goes to OOS CONF.


Additional information:

System patch CSCOgs003 is superseded by the fixes provided in system patch CSCOgs004. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOgs003

System patch CSCOgs003 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCuk32755

2

mdl-sip

SIP to UK-ISUP calls do not contain calling line identity.

CSCdw89597

2

iocm

Dynamic Reconfig fails when adding session set/lnk set.

CSCdw91579

2

mml

Profile does not work for SIP trunk.

CSCuk31923

2

provision

Calls to emergency numbers should have CPC 00001011.

CSCdw47295

2

replicator

Replicator link not recovering when restored after disruption.

CSCdw93220

3

measm

MeasCats.dat has invalid ID for H323 measurements.

CSCdw69233

3

mml

sta-dns-info command times out with null dns table.

CSCdw77330

3

mmlhfelp

help:set-iplnk should be updated for nas links.

CSCdw86713

3

provision

prov-add:files can not export ANUMDPSEL data.

CSCdw86745

3

toolkit

Toolkit: When option use current time is set the stop timelights up.

CSCuk32309

3

toolkit

MGC environment tool configures .stPort incorrectly for 9.2(2).

CSCuk32313

3

toolkit

MGC envirnonment tool configures *.platformid incorrectly.

CSCdw38322

3

userdoc

Default of isupTransparencyDisabled property should be Disabled.

CSCds07249

4

mdl-tools

Toolkit Call Translation has several mispelled words.


Additional information:

System patch CSCOgs002 is superseded by the fixes provided in system patch CSCOgs003. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

CSCOgs002

System patch CSCOgs002 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdw70162

1

mdl-sip

SIP to PSTN calls egress MGCP SDP causes Msoft Mess call failures.

CSCdw36636

3

userdoc

Circuit validation test fails.

CSCdw43093

3

iocm

Setting siplink to OOS is inconsistent.

CSCdw63397

3

mmlhelp

SC2200: MML help for stp-call is wrong.

CSCdw64921

3

mdl-tools

MDL trace shows incorrect info with simprint for SIP.

CSCdw67569

3

alrmm

IOChanMGR err: Unknown Alarm FORCE NODE RESTART.

CSCdw72155

3

provision

Database Migration Fails from 7.4(12) to 9.2(2).

CSCuk31908

2

mdl-eisup

SuppressCLIDigits parameter cannot be provisioned on EISUP trunk.

CSCdw75242

1

snmp

SNMP mishandles exceptional elements.

CSCdw71480

2

flovr

After isolating STANDBY SC STANDBY takes over as ACTIVE.

CSCdw75651

2

ioccsip

Sip link stays INB on standby system.

CSCdw69070

3

mmlhelp

MML help enhancement needed for rtrv-dns-info.

CSCdw69196

3

mmlhelp

MML help enhancement needed for sta-dns-purge.

CSCdw70233

3

mmlhelp

Incorrect MML help for dns parameter querytimeout cachesize.

CSCdw75676

3

ioccsip

rtrv-dns-info is not reporting status.

CSCdw70590

3

mmlhelp

sip trunkgrp type missing in mml help.

CSCdw77330

3

mmlhelp

help: set-iplnk should be updated for nas links.

CSCdw38322

3

userdoc

Default of isupTransparencyDisabled property should be Disabled.

CSCdw42876

3

engine-sj

1110 CDB missing SIP Tag 4203 in both call directions.

CSCdw85059

3

pkg

CSCdw57226 still in 9.2(2).


Additional information:

System patch CSCOgs001 is superseded by the fixes provided in system patch CSCOgs002. The superseded patch is removed when using the patch utility script to install a newer version of the patch.

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

The fix for CSCdw67569 adds a new alarm, FORCE NODE RESTART. Modified file: etc/CONFIG_LIB/newalarmCats.dat version /main/br_nssu_9main/br_nssu_9tech/br_nssu_92/br_nssu_922/1

To apply this fix, do one of the following:

copy etc/CONFIG_LIB/new/alarmCats.dat to etc, etc/active_link, and etc/prov_link

or

reprovision from new

CSCOgs001

System patch CSCOgs001 resolves the following DDTS tickets:

Identifier
Severity
Component
Description

CSCdw47478

2

engine-sj

SC renegotiates call from NAS when NI2+ mesg is segmented due to GTD.

CSCdw53360

2

engine

set-admin-state sends contradictory chan state messages to NAS and SS7.

CSCdv42989

3

engine

Provisioned CICs are shown as in-state to a gateway link in alarm.

CSCdw43400

3

provision

Could not identify the invalid CIC from prov-add:files error message.

CSCdw56252

3

flovr

GEN_WARN_FOVERD:Invalid message number.

CSCdw57234

3

provision

prov-exp could not export screeing data which has no dialplan.

CSCdw40702

3

install

ASCII CDR converter does not work.


Additional information:

Refer to the Patch Test Combinations section of this document to determine which protocol and system patches are needed.

This system patch includes a new protocol, Q767_SINGAPORE. Variant.dat has been updated and requires that both protocal patch CSCOnn001 and system patch CSCOgs001 are installed.

Supported SS7 Variants and ISUP Transparencies

Table 10 lists the ISUP transparency supported protocols:

Table 10 ISUP Transparency Supported Protocols

Q761 Variants
Q767 Variants
Other Protocols

Q761_Base

Q767_Base

ANSI

Singapore

Singapore

Thailand

Thailand


Known Issues and Operational Recommendations

This section contains information about known issues and the corresponding workarounds in the
Cisco MGC software release 9.2(2).


Note For more information about Cisco IOS issues and workarounds, see the Cisco IOS release notes for your platform.


Installation Patch Tool Removes Packages Before Checking to See If The System Is Down

When adding a new protocol patch to the system, the patch installation tool removes the current protocol patch, then checks to see if the system is running. If the system has not been stopped, it stops the tool, but does not add the current patch back on the system.

If you add a new protocol patch before stopping the system, you must then stop the system and then add the protocol patch to the system again.


Note For more information, refer to DDTS ticket number CSCec15748.


Using prov-cpy/prov-sync To Commit Configuration Changes on a Fault-Tolerant System

When using the prov-cpy/prov-sync combination to commit configuration changes on a fault-tolerant system the standby might not fully synchronize with the active which results in the second switchover failing. The following non-service affecting workarounds can be used if this problem occurs:

Use prov-dply, instead of the prov-cpy/prov-sync combination to commit each phase of provisioning on a fault-tolerant system. The prov-dply command ensures that both sides are completely synchronized.

After using the prov-cpy/prov-sync combination to commit configuration changes, stop and restart the standby. Restarting the standby resynchronizes all states correctly.


Note For more information refer to DDTS number CSCdw63484.


Do Not Use TimesTen Commands in PGW

PGW scripts should be used

Incorrect use of commands might result in database corruption.

TimesTen PGW scripts are located at:

/opt/CiscoMGC/local 3.

If a command is needed for which a script does not exist, you should open a ticket requesting a new script for that command.


Note For more information, refer to DDTS ticket number CSCdz78019.


Modifying the OPC of an SS7 Route

When prov-ed is used to modify the OPC of an SS7ROUTE or SS7PATH, the PGW software must be stopped and restarted before changes take affect. Stopping and restarting the system results in a service-affecting outage. To make a change without stopping and restarting the PGW, complete the following procedure:


Step 1 Start a provisioning session on the active machine.

Step 2 Use prov-dlt to remove the following components:

SS7ROUTE,

all associated trunks to the SS7PATH

SS7PATH

DPC

Step 3 Execute the prov-dply command.

Step 4 Start a second provisioning session on the active machine.

Step 5 Use prov-add to add the following components:

DPC

SS7PATH

all associated trunks to the SS7PATH

SS7ROUTE (with the new OPC and linkset changes)

Step 6 Execute the prov-dply command.


Migration of Dialplans Failed From 7.4(x) to 9.2(x)

The software upgrade from 7.4(x) to 9.3(x) involves upgrading the operating system (OS) from Solaris 2.6 to Solaris 2.8. The configuration and TimesTen databases are saved before the OS upgrade and then migrated to 9.3(x) as part of 9.3(x) installation. During migration the following error message is issued and the system does not come up in the standby state.

Migration dialplan file:0102.dialPlan:
Error message: error reading from /opt/CiscoMGC/etc/CONFIG_LIB/tmp_migrate_8.0//
digitAnalysis.dat
Error code: 5001
Error migrating dialPlan

If you receive this error during migration, refer to the Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide, Chapter 5, Upgrading to Cisco MGC Software Release 9.3(2), at the following url:

http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/swinstl/index.htm.


Note For more information refer to CSCdz30575.


CPU Timer Interval Is Not Disabled If CPUTimerInterval Parameter Is Set To 0

The XECfgParm.dat CPUTimerInterval parameter is not disabled when its value is set to 0.

Do Not Use the ifconfig UNIX Commands to Shut Down Ethernet Interfaces

During a failover on the master SC where both ethernet connections are lost, the failover correctly switches to the slave SC. However, after the ethernet connections are restored on the master, the slave SC does not return to standby mode.

Workaround:


Step 1 With the slave in Active mode, execute (as root) on the the Master:

/etc/init.d/CiscoMGC stop

Step 2 After the SC software has stopped, restart it using the following command:

/etc/init.d/CiscoMGC start

Step 3 To verify that the SC has entered the Standby state, return to MML and execute the following command:

rtrv-ne

Note The ifconfig UNIX commands should not be used to administratively down the ethernet interfaces while the MGC software is running. For more information on this issue, refer to CSCdy59730.


Conditional Routing Name Validation

In previous 9.2(2) releases, conditional routing name validation did not occur. Therefore, the potential that invalid conditional routing names were created exists.

As of patch CSCOgs021, conditional routing name validation occurs in release 9.2(2). Previously existing configurations should be checked to ensure that invalid names are not used. Conditional routing names should consist of 1-20 alphanumeric characters. If your conditional routing name is invalid, the routeAnalysis.dat file must be edited. Contact TAC so that the engineering team can be notified to have your information modified.


Caution If an invalid conditional routing name is used in release 9.2(2) and you attempt to upgrade to a newer release (9.3(2) and higher), the migration will fail because the validation of the conditional route name fails.


Note For more information on this issue, refer to CSCdy56160 and CSCdy58664.


Network Redundancy Between Dual Homed PGW and Single Homed NAS

The MGC provisioning rules have been modified to provide local redundancy on the PGW. You can now configure two IP addresses on the MGW (two ethernet interfaces on the SC side) to one IP address on a NAS. If one ethernet fails, the other ethernet can carry the traffic.

To support this configuration, the following modifications were made:

Provisioning—modified to allow you to configure sigChans with mutliple IP routes to the same destination.

IOCM—allows you to switchover to other IP routes if the primary route becomes unavailable.

IOCC—uses the remote IP address, port, and file descriptor to determine which sigChan a PDU belongs to.

Only one of the two IP routes assigned to the same destination and NETMASK is in the Solaris routing table at a time. If both interfaces are in-service, the I/O Channel Manger selects one of the two IP routes. If the ethernet interface associated with the IP route that is in the Solaris routing table fails, the I/O Channel Manager deletes that IP route from the Solaris routing table and puts the other IP route assigned to the same destination and NETMASK in the Solaris routing table. The original IP route is not restored when the ethernet interface associated with it recovers. The new IP route remains in the Solaris routing table unless the interface associated with it fails.

The following alarms are associated with this feature:

IP RTE FAIL— generated against an IPLNK or IPSESSION that is provisioned with a next hop address if the system fails to add the required route. This could be due to an invalid or conflicting parameter.

IP CONF RTE FAIL—generated when an IPLNK or IPSESSION is not using the route that it is configured to use. A conflicting route generated by another signal channel or by another process can cause this.

LIF FAIL—set by the I/O Channel Manager if it determines that the ethernet interface used by the IPSESSON or IPLNK object is not operational. It is cleared when the ethernet interface becomes operational. When set, the LIF FAIL alarm is accompanied by a log message of type GEN_ERR_IPINTF_FAIL that includes the provisioning name and operating system name of the interface that has failed. When cleared, the LIF FAIL alarm is accompanied by a log message of type GEN_INFO_IPINTF_RECOV that also includes the provisioning name and the operating system name of the interface.

An example of a provisioning name is IP_Addr1. An example of a operating system name is hme0. The error message also contains the cause of the failure. A cause of Link Down indicates that the interface has lost carrier. This can be caused by removing the cable or a failure at the ethernet switch. A cause of Admin Down indicates that the interface was taken down using the unix command ifconfig <interface name> down.


Note This configuration is supported in Cisco MGC Software Release 9.2(2) with system patch CSCOgs014 and protocol patch CSCOnn015 or later.


Suppress CLIDigits Parameter Cannot Be Provisioned on EISUP Trunk1

To prevent sending CLI digits to soft-phone applications that might ignore the CLI restriction indication and display the calling number the following workaround can be used:


Step 1 Start a new provisioning session.

Step 2 In the prov-link directory, edit the file propSet.dat file.

Step 3 Add a line after the last EISUP property name, for example:


xxxx  EISUP       *           SuppressCLIDigits     0              2   1  0

where xxxx is the number before the last EISUP property incremented by 1.

Step 4 Use the prov-ed command to set the SuppressCLIDigits value of the EISUP signaling path to 1.

Step 5 Deploy the configuration.


Switchover Might Take Five to Ten Minutes After Bringing Hme Interfaces Down

(CSCdx17509) When the ip links are bounced, but are in a current up state, the standby PGW has a rtrv-ne status of standby, NOT OOS. After attempting an MML>sw-over::confirm on the active unit, an MSO Refused, Warm Start-up in Progress error displays. This problem clears itself after 5 to 10 minutes.


Note This issue is resolved by applying CSCOgs010 or later system patches.


Support for Individual IOCC logPrio in XECfgParm.dat

A new template has been added to XECfgParm.dat that displays the valid process names for logPrio. These values allow you to turn on log priority for individual channel controllers.

The valid components for the logPrio parameter are based on the UNIX file names of the binary executables. The following are the valid component for logPrio:

EISUP

ISDNIP

ISDNL3

MGCP

SIP

SS7

TALI

almM

amDmpr

cfgM

ioChanMgr

engine

foverd

measMgr

mmdbd

mmSAgt

pom

procM

replicator

sagt

TCAP


Note The general parameter ioChanCtl (previously used to set the level for all channel controllers) has been removed.


2651 Approved for Use In the PGW 2200

For releases 7.4(12) and going forward, the 2651 has been approved for use in the PGW 2200. The 2651, used as an SLT, is ordered and shipped as a standard 2651. It ships with a non-SLT image. You must reload it with an SLT image prior to operating the device as an SLT.

2611s SLTs

Current images might need to be downloaded on 2611 SLTs prior to starting live service.

Caveats

This section describes resolved and open caveats for Cisco MGC software Release 9.2(2).

Resolved Caveats for Software Release 9.2(2)

Table 11 lists resolved caveats sorted by severity, then identifier, then component.

Table 11 Resolved Caveats for Software Release 9.2(2)  

Identifier
Severity
Component
Description

CSCdx79979

1

mdl-callctrl

MUTE CALL (mute and released calls after linked dialplan).

CSCdx81270

1

engine

Reload RSIP doesn't recover BLK=GATEWAY CICs in PGW.

CSCdy14230

1

mdl-connctrl

All calls fail on answer from PGW to HSI.

CSCdy66616

1

mml

Unable to prov more than 32 links error msg with valid batch file.

CSCdx55274

2

mdl-q767

Wrong Cause Value sent on ingress(SS7) side on ISUP SUS timer expiry.

CSCdx56882

2

engine-sj

SC cant process call with NI2 segmented messages and engine=debug.

CSCdx59012

2

engine

VSC releases CICs prior to receive GRA or CGUA.

CSCdx79984

2

engine

GRS not acked after HW failure.

CSCdx80418

2

engine

SC cored when doing manual switch over.

CSCdx84731

2

mdl-callctrl

call re-attempt at the same b channel for isdn nego resend-setup.

CSCdx85634

2

engine

Engine_smartall core dumps during 24 hour test.

CSCdx88061

2

ioccsip

Siplink always in service although hme interface is down.

CSCdx89870

2

engine

CQM for unequipped circuit fails UCIC response.

CSCdx93652

2

flovr

Crashing process can loop indefintely.

CSCdy02534

2

engine

Core dump while not able to export dialplans.

CSCdy11069

2

ioccsip

Need to add maddr parameter to Contact header - TEMPORARY.

CSCdy11883

2

ioccsip

Either hme down, no pgw TRYING response to INVITE.

CSCdy12278

2

ioccsip

PGW fails to recognise its own via in a comma seperated list.

CSCdy14868

2

provision

Modify nailed trunk SRCSVC field cause DSTTIMESLOT set to junk value.

CSCdy17792

2

mdl-sip

Forwarded call will disc after a 183 session progress.

CSCdy18222

2

engine

set-admin-state:lock causes CGB w/ immediate release sent to far end.

CSCdy29781

2

mdl-btnup

BTNUP, MGC sends two CCTF on clear at expiry of CSH Timer.

CSCdy30928

2

provision

prov-add:nailedtrnk cannt add nas dsttimeslot range 1-31 for E1 SPAN.

CSCdy36697

2

engine

Unable to modify SC config due to absence of SS7 route for some dpc.

CSCdy37584

2

mdl-q761

Engine process crash & ioCcConfig not able to write to IPC.

CSCdy44728

2

mdl-q761

pgw does not pass RGN and OCN for HKTA 2200 isup variant.

CSCdy53419

2

mdl-q761

Dropping call when nature of connection has echo control set to 1.

CSCdy57649

2

provision

Sukhoi:Provisioning is not blocked during Seamless upgrade.

CSCdy68963

2

engine

PGW sends wrong GRSA during HW failure.

CSCdy79280

2

mdl-analysis

Incomming prefix number not removed.

CSCdy81924

2

engine

Stuck CICs are created when the dpc recover from temporary outage.

CSCdz19032

2

protocol

PGW2200 can not recognize 3 bytes Release Cause Indicator.

CSCdz30575

2

upgrade

Migration of Dialplans failed from 7.4(x) to 9.2(x).

CSCuk34257

2

mdl-eisup

Post-answer CPG message not passed over EISUP.

CSCuk34258

2

mdl-q761

CPG message parameter discarded after transit over SS7.

CSCuk34269

2

mdl-q761

Transit of IAM containing CUG is rejected.

CSCuk34818

2

mdl-connctrl

Fax tone detect TG prop causes all H.323 calls to fail.

CSCuk34932

2

mdl-analysis

Use of dw2=99 negates any B-number digmodstring with patch gs9/nn009.

CSCuk36076

2

mdl-sip

Media not redirected when SIP re-invite received.

CSCuk36123

2

protocol

Incorrect behaviour on release collision causes hung cic.

CSCdx57865

3

mdl-sip

SIP drops plus character in bye messages.

CSCdv42989

3

engine

Provisioned CICs are shown as IS to a gateway link in alarm.

CSCdw81829

3

mdl-analysis

After switchover the call is not routed to the proper dialplan.

CSCdx08903

3

mdl-ansi-ss7

SC2200 does not accept CCR for remotely blocked CIC.

CSCdx15580

3

iocm

The perf counters generated by PGW are different than documented.

CSCdx38642

3

mdl

Kill-call and CDR problems [Want write TimeStamp according to XECfg].

CSCdx46359

3

provision

GTD - gtd info not sent to NAS after gtd param changes.

CSCdx62621

3

protocol

GTD - EBM support not operational when enabled per gateway.

CSCdx66443

3

mdl-callctrl

GTD - node B type behaviour with unrecognised IE - drop by LCM.

CSCdx68938

3

mdl-callctrl

VSC should send endpoint level DLCX when a 515 error response rcvd.

CSCdx71519

3

mdl-sip

BT:Ingress trunk group missing from CDR for SIP originated calls.

CSCdx72511

3

mmlhelp

docs need to more clearly define kill-call.

CSCdx78195

3

mdl-connctrl

On reception of vbd/vbdt the VSC response with wrong transaction id.

CSCdx78196

3

mdl-connctrl

On ft/mt notification VSC sends different codec string.

CSCdx84748

3

mdl-q767

Wrong cause code on ISUP SUS T2 timer expiry.

CSCdx92221

3

iocm

RTRV-RTE show incorrect state after TFP message.

CSCdx94208

3

mdl-q767

Q.767: several incorrect CauseCodes mappings (2nd edition).

CSCdx94403

3

engine

When controller is down CGB with immediate release to be sent.

CSCdy00998

3

mdl-connctrl

When MDCX for ft/mt notification is NACKed DLCX is sent one side.

CSCdy04602

3

mdl

Incorrect BCI in the Connect message with Q767-RUSS.

CSCdy07603

3

provision

Invalid cic are allowed in prov-add:nailedtrnk w/SPANSIZE specified.

CSCdy08356

3

engine

Incorrect release cause code in CDR record.

CSCdy10708

3

mmlhelp

docs need to describe transient state query-cic.

CSCdy11856

3

mdl-sip

Call Forward pstn->ata->pstn hme0 unplugged with CSPS2.0.1.4.

CSCdy12998

3

mdl-q761

Q761_BELG_BCOM - hop count support required for certification.

CSCdy17818

3

engdoc

IPCkind [r] in services.dat but not referenced in Data Dictionary.

CSCdy18138

3

engdoc

Alarm categories missing from 9.2(X) Data Dictionary EDCS-119626.

CSCdy20661

3

mdl-q761

PCI on egress should be present when on ingress.

CSCdy20914

3

mdl-ansi-ss7

COT always fail if Tone is returned before LPA.

CSCdy20931

3

mdl-ansi-ss7

If Initial IAM_w_COT fails subsequent COT fails as well.

CSCdy21573

3

engine

SVC=Notset is set in IPLNK configuration.

CSCdy24943

3

mdl-q721

Change request in Brazilian TUP to send charge in ACMs.

CSCdy31675

3

mdl-pri

Some HLC characteristics are not validated - calls fail.

CSCdy32910

3

mdl-btnup

BTNUP - ITUReasonCode being over written in CDR by Second REL.

CSCdy37745

3

mdl-q761

HKTA_2202 - restriction about noa Calling party removed.

CSCdy38088

3

mdl-q761

CPG should be accepted before ACM.

CSCdy38844

3

mml

MML core dumps on prov-export.

CSCdy40382

3

mdl-q761

PCI generate should be transit interpretation.

CSCdy42418

3

engine

object ptr rmgBearChan is NULL is added to platform.log after call.

CSCdy46777

3

engine

blk-cic not operational - no CGB sent out.

CSCdy62767

3

mdl-cdr

TAG 4106 FirstREL_TM is missing on CDB-Tag 1110.

CSCdy82535

3

provision

Invalid route priority not detected in provisioning.

CSCdy84847

3

mdl-ni2

BCI and OBI are changed on the Ingress Side of the call.

CSCdy85209

3

engine

Incorrect clear cause.

CSCdz08306

3

mdl-q721

CIC status mismatch problem.

CSCdz11836

3

engine

SC need to synchronize bearer channel status.

CSCdz27504

3

procm

PGW OOS due to IPLINK de-provision.

CSCuk24004

3

mdl-q761

VSC doesn't transit connected number info and discards call history.

CSCuk35488

3

mdl-sip

Incorrect MAPPING of SS7 CPG to SIP.

CSCuk35748

3

mdl-sip

PGW needs to ACK 487 subsequent to the CANCEL.

CSCuk35763

3

mdl-q767

T9 not read from trunk group properties.

CSCuk36578

3

mdl

SS7 Release msg mapped incorrectly to NI2+.


Open Caveats for Software Release 9.2(2)

Contact your Cisco representative to obtain status on software problem reports (SPRs). For more information on IOS caveats, see the IOS release notes for your platform. Table 12 is sorted by severity, then identifier, then component.

Table 12 Open Caveats for Software Release 9.2(2) 

Identifier
Severity
Component
Description
Explanation/Workaround

CSCdx14471

2

mdl

SC assumes end-to-end ISUP when building and originating SS7 message.

On the PGW2200 running software version 9.2(2) in a SS7 Interconnect for Voice Gateway solutions, if a call originates from a signaling type other than R2 or SS7, the PGW2200 processes the incoming NI2 SETUP from the NAS and sends out an IAM to the SS7 switch with both the originating_access_ISDN and ISUP_used_all_the_way parameters equal to 1.

CSCdx20455

2

provision

SIP:rttrnkgrp entry with type=9 mess up rttrnkgrp&siprttrnkgrp table.

Added a rttrnkgrp entry with type=9 and then tried to modify it to different type (type=7) or delete it, mml did not allow modification and returned SIP related error message.

Did prov-rtrv:rttrnkgrp:"all" and prov-rtrv:siprttrnkgrp:"all". Rttrnkgrp entry with type=9 did not show in rttrnkgrp tables but showed in Siprttrnkgrp tables.

Workaround: delete the entry using prov-dlt:sigrttrnkgrp command instead of Prov-dlt:rttrnkgrp command.

CSCdx84731

2

engine

Call reattempt at the same b channel for isdn nego resend-setup.

Workaround: None.

CSCdx85634

2

engine

Engine_smartall core dumps during 24 hour test.

On the Cisco SS7 Interconnect for Voice Gateways Solution the engine process running on the active SC2200 might fail and generate a core dump while proccessing calls and cause a failover to the standby SC2200.

Workaround: None.

CSCdx88061

2

ioccsip

Siplink shows as always in service although hme interface is down.

With two SIPLNKs configured, the primary one will always be in service even if the associated hme has gone down due to cable or switch failure.

CSCdx94735

2

flovr

Switchover takes too long when active process crashes.

When a process on the active system crashes, failover does not happen until the core file is produced. If the engine is the process that crashes, the core file can take over a minute to produce, which leaves the node without an active platform for over a minute.

CSCdy02534

2

engine

Core dump while not able to export dialplans.

When deploying a new set of configurations that had major dialplan changes (dialplan additions and removals), it was not possible to do a prov-exp. The call scenarios that used these dialplans all worked.


Obtaining Documentation

The following sections provide sources for obtaining documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following sites:

http://www.cisco.com

http://www-china.cisco.com

http://www-europe.cisco.com

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.

Ordering Documentation

Cisco documentation is available in the following ways:

Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace:

http://www.cisco.com/en/US/partner/ordering/index.shtml

Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

http://www.cisco.com/go/subscription

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).

Documentation Feedback

If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.

You can e-mail your comments to bug-doc@cisco.com.

To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:

Attn Document Resource Connection
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.

Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.

Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.

To access Cisco.com, go to the following website:

http://www.cisco.com

Technical Assistance Center

The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.

Contacting TAC by Using the Cisco TAC Website

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:

http://www.cisco.com/tac

P3 and P4 level problems are defined as follows:

P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.

In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.

To register for Cisco.com, go to the following website:

http://www.cisco.com/register/

If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:

http://www.cisco.com/tac/caseopen

Contacting TAC by Telephone

If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

P1 and P2 level problems are defined as follows:

P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.

P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.