 Feedback
|
Table Of Contents
Release Notes for the Cisco PGW 2200 Softswitch Release 9.8(1)
Cisco PGW 2200 Softswitch Software Compatibility Matrix
Host Minimum Server Requirements
Media Gateway Hardware Requirements
Cisco PGW 2200 Softswitch Management
Display Name and Connected Number Interworking
Enhanced Clear Channel Codec Support
Enhanced Generic Number Handling
Inter-CUCM SIP Trunk Service Transparency for MWI, KPML, and COLP
ISUP and SIP-I Interworking for DPNSS CBWF Relay
Licensing Features for the Cisco PGW 2200 Softswitch
MLPP Local Handling in ISUP, PRI, and SIP
MLPP Relay in PRI to SIP/ISUP Interworking
MLPP Support for ISUP and SIP Interworking and SIP to SIP Transparency
Nortel Release Link Trunk (RLT) Support
Secure Real-time Transport Protocol Support
Support for Tel URI in SIP Diversion Header
Support of SIP P-Headers for 3GPP
Suppression of Redirecting Number and Information
TCP Transport for SIP Phase II
Release 9.8(1) Patch 4 and Earlier
Release 9.8(1) Patch 5 and Later
Installing and Upgrading the Softwareon
Important Notices and Statements
Additional Cautions and Notes for Patch 5 and Later
Using the Patch Upgrade Procedure
Resolved Caveats Listed by Patch Number
Open Defect in 9.8(1)S15P15 Release
SNMP Returns Wrong Status for Physical E1000G Interfaces
Known Issues and Operational Recommendations
System File vars.pm Error After Migration from Release 9.7(3) to Release 9.8(1)
The Hostagt Process Sometimes Takes Up High CPU (Nearly 50%)
Obtaining Documentation and Submitting a Service Request
Release Notes for the Cisco PGW 2200 Softswitch Release 9.8(1)
Revised: February 15, 2013
The Cisco PGW 2200 Softswitch 9.8(1) release provides new features and significant performance improvements. These release notes describe the features and caveats for release 9.8(1).
Contents
•
Resolved Caveats Listed by Patch Number
•
•
Introduction
The Cisco PGW 2200 Softswitch is a next generation carrier-grade class 4 (transit) softswitch that has been deployed by over 600 service providers and enterprises.
The Cisco PGW 2200 Softswitch Release 9.8(1) expands current softswitch capabilities and introduces signaling path border element (SBE) into its feature portfolio. The session border controller (SBC) was introduced to replace the back-to-back media gateway pairs and allow native IP interconnects between VoIP networks. SBC functions can be broadly divided into two logical subelements: signaling path border element (SBE) and data path border element (DBE). The SBE provides signaling functions such as protocol interworking (for example, H.323 to SIP), identity and topology hiding, and call admission control (CAC). The DBE provides media-related functions such as deep packet inspection and modification, media relay, and firewall support under SBE control. To date, the SBE and DBE logical elements have generally been realized within a single, physical SBC device. This model is referred to as unified SBC as shown in Figure 1.
Figure 1 The Unified SBC Model
However, many carriers are finding that as their voice networks grow, the challenges of managing the networks grow proportionately. Service providers today want the option to decouple SBC data-path functions from signaling functions. They want to be able to distribute SBE functions in the network separately from the DBE element to simplify management, operations, and troubleshooting. In this distributed model, communication between the SBE and DBE takes place over a well-defined standard, such as ITU-T H.248 adopted in IP Multimedia Subsystem (IMS), which allows a multiplatform implementation of the SBE and DBE elements in the network. The distributed approach to SBCs is in alignment with the directional approach of IMS, ITU, and Telecoms and Internet converged Services and Protocols for Advanced Networks (TISPAN) architectures where the SBE functionality can be provided by a variety of different elements and applications in the network. Figure 2 shows a SBE deployment with a variety of different network elements.
Figure 2 Distributing the SBE and DBE Functions of Session Border Control
A flexible network component with integrated SBC supports both the unified and the distributed model. Networks continually grow and evolve, and a multimedia IP transport network that scales adequately today with a unified SBC will outgrow the unified model and necessitates a distributed approach. Operators want SBCs that can grow with their networks—they do not want to make capital-intensive complete equipment upgrades of in-service network elements. The Release 9.8 can cater to such market requirements, behaving as the centralized SBE and interworking with Cisco and potentially non-Cisco DBE via standard H.248 interfaces. The benefits of such architecture consists of:
•
•
•
•
Platform Support
For a list of supported platforms see the following documents:
•
•
Software Required
For a list of software requirements, see Chapter 1, "Preparing for Sun Solaris Operating System and Cisco PGW 2200 Softswitch Software Installation", of Cisco PGW 2200 Softswitch Release 9.8 Software Installation and Configuration Guide at the following URL:
http://www.cisco.com/en/US/products/hw/vcallcon/ps2027/tsd_products_support_series_home.html
Caution
Cisco PGW 2200 Softswitch Software Compatibility Matrix
Table 1 provides compatibility matrix for Cisco PGW 2200 Softswitch software Release 9.8(1) and other Cisco products.
Table 1 Cisco PGW 2200 Softswitch Software Compatibility Matrix
Cisco PGW Node
Call control
Cisco PGW 2200 Softswitch
Cisco PGW 2200 Softswitch Release 9.8(1)
—
—
HSI (H.323)
Release 4.3(2), with latest patch
ITP-L1
—
Cisco 2811 ITP-L, Cisco 2651 ITP-L
Cisco IOS Version 12.4(15)SW
iITP-L2
—
Cisco AS5400 Integrated ITP-L
Cisco IOS Version 12.4(7e)
Ethernet Switch/Router
—
Cisco Catalyst 2900XL
Current Release
—
Cisco Catalyst 5500
Current Release
—
Cisco Catalyst 6500
Current Release
CUCM3
IP PBX and
key switchCUCM
Version 7.1.34 , Version 6.0.1, Version 5.1.2, Version 4.2
CME5
—
CME
Cisco IOS version 12.4(19)
Cisco Unity
—
Cisco Unity
Version 4.0
CUBE6
—
Cisco 2811
Cisco IOS Version 12.4(15)SW
ICM7
—
Cisco IPCC ICM
Version 7.2
ITP8
—
Cisco ITP 2651
Cisco ITP 2811
Cisco IOS Version 12.4(15)SW
Cisco IOS Version 12.4(15)SW
Media Gateways (MGCP-controlled for PSTN trunking)
—
Cisco AS5350XM
Cisco IOS Version 12.4(7)SW
—
Cisco AS5400XM
Cisco IOS Version 12.4(19)SW
—
Cisco AS5850
Cisco IOS Version 12.4
—
Cisco AS5850 with STM1 module
Cisco IOS Version 12.4
—
Cisco MGX 8880 Media Gateway (VISM)
VISM 3.3.xx
—
Cisco MGX 8880 Media Gateway (Cisco VXSM)
VXSM 5.4
Media Gateways (MGCP-controlled for PBX access)
—
Cisco 2651XM, Cisco 36xx, Cisco 37xx
Cisco IOS Version 12.4(19)
—
BRI backhaul: Cisco 1721, Cisco 1751, Cisco 1751v, Cisco 1761,
Cisco 1761v 2612Cisco IOS Version 12.4(19)
—
PRI/Q.931 backhaul for call agents:
Cisco 2691Cisco IOS Version 12.3(7)T1
Media Gateways (Megaco-controlled for IP-IP gateway)
—
Cisco GSR 12K SBC
Version 3.7.0
—
Cisco ASR 1000 Series SBC
Cisco IOS 12.2(33)XNA
—
Cisco MGX 8880 Media Gateway (Cisco VXSM)
VXSM 5.5
Firewall
—
Cisco PIX 515, 525, or 535 Security Appliance
Cisco PIX Security Appliance Version 7.0
Network Management
—
Cisco BAMS9
Version 3.30 with latest patch
—
Cisco MNM10
Version 2.8(1). For correlation of the MNM patches with the Cisco PGW 2200 Softswitch patches, see
http://www.cisco.com/en/US/docs/net_mgmt/mnm/2.8.1/release/notes/CMNM_rn.html
—
Cisco VSPT
Version 2.8(1). For correlation of the VSPT patches with the Cisco PGW 2200 Softswitch patches, see
http://www.cisco.com/en/US/docs/net_mgmt/vspt/2.8/release/notes/vspt281.html
—
CTM11 for MGX 8880 Media Gateway management
Version 8.0
—
CiscoWorks LMS12 for IOS and Catalyst devices
Version 2.5.1
Optional Software
—
Cisco IPM13
Version 2.3
—
CIC14
Version 3.5
1 ITP-L = IP Transfer Point LinkExtender
2 iITP-L = integrated IP Transfer Point LinkExtender
3 CUCM = Cisco Unified Communications Manager
4 Compatibility between the CUCM Release 7.1.3 and the Cisco PGW 2200 Release 9.8.1 started with Cisco PGW 2200 Release 9.8.1 Patch S7P7 (Patch Level 7).
5 CME = Cisco Unified Communications Manager Express
6 CUBE = Cisco Unified Border Element
7 ICM = Cisco Unified Intelligent Contact Management
8 ITP = IP transfer point
9 BAMS = Billing and Measurement Server
10 MNM = MGC Node Manager
11 CTM = Cisco Transport Manager
12 LMS = LAN Management Solution
13 IPM = Internetwork Performance Monitor
14 CIC = Cisco Info Center
Required Swap Space
The Cisco PGW 2200 Softswitch software needs to partition 4 GB of swap space. The Cisco Solaris 10 Operating System Jumpstart Disk used to install the solaris system automatically sets up the swap space. Setting swap space at installation is recommended; however, you can change swap space at a later date by adding a swap file or repartitioning the swap space using the format menu (for example, reassigning how many cylinders are in each partition). The swap space requirement is determined by the amount of traffic. As traffic increases, use the MML command rtrv-ne-health to observe the amount of swap space that is being used; you can decide to increase the swap space if more is needed.
Note
Host Hardware Requirements
This section describes the hardware requirements for the Cisco PGW 2200 Softswitch software.
Host Minimum Server Requirements
See Cisco PGW 2200 Softswitch Hardware Installation Guide—Releases 7 and 9 for the host minimum hardware requirements. Before using the minimum hardware configuration, consult with your Cisco representative to determine the hardware that gives you the best performance results based on your network configuration, proposed traffic, and desired processing power.
Media Gateway Hardware Requirements
Table 2 lists URLs for release notes that document media gateways.
Table 2 Media Gateway Release Notes Locations
MGX 8880 Voice Interworking Service Module
http://www.cisco.com/en/US/products/hw/gatecont/ps3869/prod_release_notes_list.html
MGX 8000 Voice Gateway
http://www.cisco.com/en/US/products/hw/gatecont/ps3869/prod_release_notes_list.html
AS5350 Universal Gateway
http://www.cisco.com/en/US/docs/ios/12_1/12_1xq/release/notes/rn5350xq.html
AS5400 Universal Gateway
http://www.cisco.com/en/US/docs/ios/12_1/12_1xd/release/notes/rn5400xd.html
AS5850 Universal Gateway
http://www.cisco.com/en/US/docs/ios/12_1/12_1xv/release/notes/rn5850xv.html
LAN Switch
Your application might use one or more LAN switches from the Cisco Catalyst Switch family to connect the Cisco PGW 2200 Softswitch host to the media gateways (MGWs) and to the Cisco IP Transfer Point LinkExtenders (ITP-Ls) or Cisco IP Transfer Points (ITPs).
Note
Note
Supported Features
Table 3 lists features that were inherited from earlier releases of the Cisco PGW 2200 Softswitch software and are still supported in Release 9.8(1).
Table 3 Supported Features in Release 9.8(1)
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 ANI1 authorization
Adds security and prevents fraudulent use of the network.
Support for toll-free and 8XX numbers through the SCP2
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 COT3 support
Provides verification of the voice path.
Support for ISDN direct-access lines
Allows direct line access to the Cisco PGW 2200 Softswitch.
Support for E-ISUP inter-MGC signaling
Provides scalable and flexible service.
Support for advanced call routing
Provides scalable and flexible service.
Support for MGCP 1.0
Allows the Cisco PGW 2200 Softswitch to control media gateway connections.
Support for carrier-grade QoS4
Replaces the need for traditional TDM equipment.
Support for SS7-to-SS7, SS7-to-ISDN, SS7-to-SIP, SS7-to-H.323, ISDN-to-SIP, ISDN-to-H.323, ISDN-to-ISDN, DPNSS-H323, and DPNSS-SS7 call types
Provides scalable and flexible service.
Support for voice-band telephony
Provides scalable and flexible service.
Support for ISDN data calls
Provides scalable and flexible service.
Support for real-time fax relay
Provides scalable and flexible service.
Support for modem passthrough
Provides scalable and flexible service.
Support for Cisco media gateways
Protects investment in Cisco equipment.
Provides a reliable IP link between Cisco PGW 2200 Softswitch and access servers with RUDP5
No single point of failure in the connection between media gateways and the Cisco PGW 2200 Softswitch.
Call detail records for PSTN billing
Meets carrier-grade PSTN requirements for moving existing voice revenue streams to the packet environment and for creating new voice service opportunities. Provides a CDR viewer for viewing billing records.
Facility associated signaling provided by the Cisco SLTs (T1/E1 WIC, optional with SS7)
•
•
High Availability platform
Established calls are maintained when there is a switchover from the active Cisco PGW 2200 Softswitch host to its paired standby host.
Sun Solaris 10
•
•
•
•
•
•
•
Quasi-associated or fully associated signaling
Ready for international markets.
Complete continuity check (two-wire and four-wire)
Meets interconnect requirements.
NEBS8 Level 3 compliant
Telco-ready.
Several simplex or high availability platform options
Cost-effective options.
1 ANI = automatic number identification
2 SCP = service control point
3 COT = continuity test
4 QoS = quality of service
5 RUDP = Reliable User Datagram Protocol
6 DPCs = destination point codes
7 OPCs = originating point codes
8 NEBS = Network Equipment-Building System
Cisco PGW 2200 Softswitch Management
Table 4 provides an overview of the management components of the Cisco PGW 2200 Softswitch.
New Features in This Release
This section describes new features introduced in Cisco PGW 2200 Softswitch Release 9.8(1).
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Display Name and Connected Number Interworking
This feature introduces a comprehensive structure for handling the parameters associated with the following features for calls between ISUP and SIP endpoints:
•
•
•
•
These parameters allow the Cisco PGW 2200 Softswitch to support interworking between ISUP and SIP networks for basic call features, call forwarding features, and call transfer feature. Call forwarding feature includes Call Forwarding Unconditional (CFUC), Call Forwarding No Answer (CFNA), and Call Forwarding Busy (CFB).
The Display Name and Connected Number Interworking feature also enables the Cisco PGW 2200 Softswitch to handle display name and number identity interworking between PBX and SIP for basic calls, call forwarding, and call transfer.
CLIP/COLP provides call control and security functions for residential telephone users. In addition, display name is part of the calling line identity (CLI). Using CLI information within networks enhances the existing support for call processing, billing, emergency call handling, customer care, operator assistance services and advanced services.
With this feature, the Cisco PGW 2200 Softswitch can map display name and connected number between SIP and ISUP, and between SIP and QSIG. It also supports the prefix modification for connected number, redirection number, and transferred number.
This feature provides the following benefits:
•
Note
•
•
This feature has the following limitations:
•
•
Note
Domain-Based Routing
This feature enhances the Cisco PGW 2200 Softswitch analysis and routing functions to allow the Cisco PGW 2200 Softswitch to route calls based on user and domain names. These changes allow the Cisco PGW 2200 Softswitch to simultaneously route calls using E.164 numbers, domain names, user names, or a combination of E.164 and non-E.164 data.
Domain-based routing also introduces domain-based call screening functions and translation tables to map E.164 numbers to domain and user names and vice versa.
Note
Enhanced Clear Channel Codec Support
The clear channel codec guarantees bit integrity of a digital signal 0 (DS-0) transferred through a gateway. It supports the transporting of nonvoice circuit data sessions through a VoIP network. It enables the VoIP networks to transport data calls.
Before the introduction of this feature, the Cisco PGW 2200 Softswitch supported the clear channel codec for TDM-to-SIP data calls. That is, the Cisco PGW 2200 Softswitch could handle data calls that originated from the TDM side and ended on the Session Initiation Protocol (SIP) side.
The Enhanced Clear Channel Codec Support feature completes clear channel codec support to SIP-to-TDM data calls. Based on incoming SIP messages and user configurations, the Cisco PGW 2200 Softswitch sends certain clear channel codecs to gateways and sets the transmission medium requirement (TMR) value for data calls properly. With this feature, users can make TDM data calls through the SIP network. In addition, users can customize clear channel codecs that media gateways use for data calls.
Note
Enhanced Generic Number Handling
The Enhanced Generic Number Handling feature enables the Cisco PGW 2200 Softswitch to pass a Generic Number field into a SIP INVITE message when it receives an ISUP IAM message (United Kingdom variant—ISUPV3_UK) that includes a Number Qualifier field, and that field contains the value "intra-nw-use".
Note
The Cisco PGW 2200 Softswitch performs this message conversion when it determines that it must set up a call between an ISUP network on the originating side and a SIP network on the destination side. In this case, the Cisco PGW 2200 Softswitch ignores the contents of the Generic Number field in the ISUP IAM message and forwards the calling number to a device on the SIP network side.
Note
Enhanced Video Support
The Enhanced Video Support feature expands video capabilities on the Cisco PGW 2200 Softswitch. Before the introduction of this feature, the Cisco PGW 2200 Softswitch handled Session Initiation Protocol (SIP) video calls in a basic way. It was not possible to hold or transfer SIP video calls, and you did not have control of media streams for SIP video calls. Working together with data border elements (DBEs) (Cisco ASR 1000 DBE), the Cisco PGW 2200 Softswitch now handles SIP video calls more comprehensively:
•
–
–
–
–
–
•
•
•
•
Note
Generic Call Tagging
The Generic Call Tagging feature enables a service provider to configure the Cisco PGW 2200 Softswitch to perform additional routing operations beyond the pre-existing manner of route selection. If you apply a generic call tag in Pre-analysis, A-number analysis, or B-number analysis, the Cisco PGW 2200 Softswitch can perform another level of route selection defined by the tag, which extends the route selection algorithms for certain calls. This feature enables you to refine route selection.
When you use the Generic Call Tagging feature, you influence the progression of call route selection:
Dial Plan—You must configure a new dial plan result called CALL_TAG, which you can configure to be present for the Pre-analysis, A-number analysis, or B-number analysis stages of routing analysis. The Cisco PGW 2200 Softswitch processes the CALL_TAG result type by associating it with a data word, in which you provide a name for a particular tag list.
The identity you specify for a tag list must be an alphanumeric character string (upper or lower case) of a maximum of 32 characters. There is no limit to the number of name or value pairs (or just tags without values) that you can contain in a tag list. If you specify a tag name without a value, the Cisco PGW 2200 Softswitch supplies the default value "true".
Tag List Table—Cisco PGW 2200 Softswitch constructs a tag list table with which it can decide whether a particular trunk group can service a call based on the presence of a tag. By constructing a tag list table, you can "blacklist" (or skip) any number of trunk groups from servicing calls that bear particular tags.
Routing Analysis—When the Cisco PGW 2200 Softswitch reaches the point in route analysis at which it must select a trunk group to service a call, it consults the tag list table to find a trunk group that is allowed to service the call.
To implement the Generic Call Tagging feature, you must perform the following procedures.
1.
2.
3.
4.
The Generic Call Tagging feature enables you to use your own naming conventions to suit your location and purposes. The primary intent is to associate tags with particular trunk groups. This enables you to designate the trunk groups over which you wish to route certain calls. You can associate a tag with a trunk group to prevent the trunk group from routing a call that requires handling defined by the tag. This effectively blacklists the trunk group from routing calls of a designated type. For example, you could prevent some trunk groups from routing a call that requires fax transmission.
Note
H.248 Protocol-Phase 2
H.248 Protocol-Phase 2 enables the Cisco PGW 2200 Softswitch to perform media anchoring on ingress or egress border gateways for IP traffic. This feature includes a simple service policy decision module (SPDM), which determines whether a session border element (SBE) should perform media anchoring and, if so, identifies which border gateway performs the media anchoring based on service requirements. The border gateway control interface conforms to the ITU-SG16/IETF specification of the H.248 protocol and an additional optional package.
H.248-Phase 2 gives the Cisco PGW 2200 Softswitch the capacity to anchor media on ingress or egress border gateways for IP traffic, no matter whether a call is TDM to IP, IP to TDM, or IP to IP. With H.248-Phase 2, the Session Border Element (SBE) engine can select border gateways in gateway pools, and, through the use of H.248, instruct these border gateways to anchor the Realtime Transport Protocol (RTP) or Real Time Conferencing Protocol (RTCP) media streams.
Note
Inter-CUCM SIP Trunk Service Transparency for MWI, KPML, and COLP
The Inter-CUCM SIP Trunk Service Transparency for MWI, KPML, and COLP feature enables the Cisco PGW 2200 Softswitch to handle out of dialog/in dialog SUBSCRIBE and NOTIFY messages, in addition to the existing support for INVITE message. With this feature, Cisco PGW 2200 Softswitch can transparently transit the following information in Back to Back User Agent (B2BUA) mode:
•
•
•
The details of these messages are described in the following sections.
Message Waiting Indication
This feature enables the Cisco PGW 2200 Softswitch to interwork with the Cisco Unity, which sends voicemail MWI by unsolicited NOTIFY. With this feature, Cisco PGW 2200 Softswitch can relay unsolicited MWI information and the responses in MWI flows. These responses include:
•
•
•
•
•
•
•
•
Note
The Cisco PGW 2200 Softswitch performs the following actions to support the MWI status relaying:
•
•
•
SIP Key Press Stimulus Package
The Cisco PGW 2200 Softswitch supports SIP messaging for Dual Tone Multi-Frequency (DTMF) that takes place between a Signaling Connection Control Part (SCCP) phone hosted by a Cisco Unified Call Manager (CUCM) and a SIP gateway via a SIP trunk. DTMF support is implemented by the bidirectional subscriptions for DTMF notification between the CUCM and the SIP gateway. NOTIFY messages are exchanged when a digit is pressed from the called and calling party phones. After the call is released, the CUCM and the SIP gateway terminate both local and remote KPML subscriptions. CUCM sends a 489-Bad Event message to the Cisco PGW 2200 Softswitch or receives the same message from the Cisco PGW 2200 Softswitch.
The Cisco PGW 2200 Softswitch relays KPML payload (in XML form) in SIP messages SUBSCRIBE/NOTIFY in B2BUA mode. These KPML requests are passed in-dialog. Cisco PGW 2200 Softswitch is also able to relay the responses possible in KPML flows, such as 200 Ok, 480 Temporarily Unavailable, 404 Not Found, 503 Service Unavailable, 403 Forbidden, 481 Subscription does not exist, 489 Bad Event, and 202 Accepted. Cisco PGW 2200 Softswitch does not parse the message contents and allows KPML event.
Connected Line Presentation
Connected Line Presentation (COLP) is a service that provides caller with the identity to which he connected. For example if someone dials 01234 567890, but the call is diverted to another number, COLP provides the identity of the person that is actually connected to. The identity is typically the telephone number of the connected party.
This feature enables the Cisco PGW 2200 Softswitch to send PAID and Remote-Party-ID headers of UPDATE in B2BUA mode. The Cisco PGW 2200 Softswitch relays display name and user part of the URI in PAID and Remote-Party-ID headers in SIP messages, such as UPDATE,180 Ringing, and 200 OK.
Note
ISUP and SIP-I Interworking for DPNSS CBWF Relay
The ISUP and SIP-I Interworking for DPNSS CBWF Relay feature allows a user who receives a busy signal, such as extension busy or network congestion, to request an automatic callback when trying to make a call through a private network.
A calling party can register for the feature with the originating PBX that requests the terminating PBX to monitor the called extension. When the called extension and the transmission path across the network become free, the user who invoked the feature is notified by a ring tone that the called extension is available. The user can then call back, and a call is set up from the user to the extension that is free.
With this feature, the Cisco PGW 2200 Softswitch can transparently relay DPNSS signaling encapsulated in ISUP signaling to SIP-I and vice versa. The Cisco PGW 2200 Softswitch neither controls nor has the knowledge of the DPNSS call states and message flows, and takes decisions pertaining to call setup, processing, and release purely from the ISUP-to-SIP-I interworking perspective and vice versa. This feature supports the protocol interworking of ISUP (UK ISUP version 3 variant) with SIP-I (encapsulating UK ISUP version 3 variant) carrying DPNSS signaling for CBWF and vice versa.
Note
Licensing Features for the Cisco PGW 2200 Softswitch
The Cisco PGW 2200 Softswitch release 9.8(1) introduces licensing control for TimesTen in-memory database and the Session Border Element (SBE) interface or IP-IP Gateway. The TimesTen license keeps track of the Number Portability and Full Number Translations. The SBE interface license is needed when Cisco PGW 2200 Softswitch is used as an SBE in the Cisco Session Border Controller solution.
Note
MLPP Local Handling in ISUP, PRI, and SIP
This feature describes the local handling functionalities for MLPP in protocol ISUP, PRI, and SIP. The PGW 2200 Softswitch handles the pre-emption of calls as the MLLP's supplementary service. A new value, 2, is set to the existing property MlppSupport in order to enable local handling support for MLPP.
Note
MLPP Relay in PRI to SIP/ISUP Interworking
The MLPP Relay in PRI to SIP/ISUP Interworking feature for the Cisco PGW 2200 Softswitch supports MLPP for PRI-PRI and PRI-SIP/ISUP interworking without local handling and vice versa. With this feature, Cisco PGW 2200 Softswitch interoperates PRI with SIP peers such as CUCM and switches interoperating with SS7 in the customer deployment/PSTN to facilitate PRI-SIP and PRI-ISUP prioritized call handling transparently.
Note
MLPP Support for ISUP and SIP Interworking and SIP to SIP Transparency
This feature enables the Cisco PGW 2200 Softswitch to support Multilevel Precedence and Preemption (MLPP), which permits validated users to place priority calls. Precedence assigns a priority level to a call. Preemption refers to a process that terminates a call of lower priority, which is using a device that is targeted by a call of higher priority. Precedence assures that a higher-priority call can access the target device.
The implementation of MLPP defined by this feature only supports the relay of prioritized call signaling information in Back to Back User Agent (B2BUA) mode for SIP-to-SIP calls. This feature also enables the Cisco PGW 2200 Softswitch to map call signaling information for SIP-to-ISUP calls and for ISUP-to-SIP calls.
Note
Note
Nortel Release Link Trunk (RLT) Support
The Nortel Release Link Trunk (RLT) Support feature extends the existing RLT mechanism on the Cisco PGW 2200 Softswitch. Cisco PGW 2200 Softswitch can release a call when it receives a SIP REFER message. This feature allows you to optimize trunk facilities because SS7 circuits are released after call bridging or redirection occurs. With this feature, Cisco PGW 2200 Softswitch can interwork with the switches that are configured to accept RLT message sequences.
Note
QSIG Tunneling over SIP
The Cisco Unified Communications Manager (CUCM) clusters are used to interwork directly by tunneling QSIG for callback scenarios. With this feature, interworking among CUCMs can be enhanced by tunneling QSIG over the Session Initiation Protocol (SIP) through Cisco PGW 2200 Softswitch, which acts as a transit switch.
The QSIG Tunneling over SIP feature provides a new interface for QSIG Tunneling over SIP protocol in Cisco PGW 2200 Softswitch for callback scenarios. This feature enables transparent interworking between Call Managers by tunneling the QSIG information in the SIP messages.
Applying this feature, Cisco PGW 2200 Softswitch will interwork with the Call Managers (single-cluster or multiple-cluster configurations) on SIP interfaces as a transit switch.
Note
Secure Real-time Transport Protocol Support
The Secure Real-time Transport Protocol Support feature enables the Cisco PGW 2200 Softswitch to handle MGCP-based TDM and SIP calls that have media authentication and encryption of the Secure Real-time Transport Protocol (SRTP). This feature adds security to media traffic in your network. The Cisco PGW 2200 Softswitch can fall back from SRTP to non-secure Real-time Transport Protocol (RTP).
Note
Note
SIP Profiles
This feature introduces new service profiles for SIP, EISUP, and other protocols. Service profiles improve provisioning and security for the Cisco PGW 2200 Softswitch by allowing you to create a customized set of call properties and assign it to a call trunk group.
This feature includes four new profile types:
•
•
•
•
Note
SIP-I Protocol
This feature, SIP-I (SIP with encapsulated ISUP), is an ITU-defined SIP extension which allows IP networks to provide services that are supported by ISUP networks, for example, malicious call identification. The feature allows the Cisco PGW 2200 Softswitch to interwork between SIP-I and ISUP, and also to interwork between SIP-I and other protocols such as SIP, H.323, PRI, and QSIG. Where PSTN services are required in IP networks, SIP trunks with SIP-I support can be the preferred method for supplying these services, because the ISUP content is encapsulated in SIP message headers.
The Cisco PGW 2200 Softswitch supports ITU, ANSI, German, UK, Finnish ISUP, and
Russian (CSCsv88752) encapsulated in SIP-I messages, which allows a high degree of interworking for many services across a SIP-I configured link.You can provision the closest base or the closest country-specific SIP-I variant if you are using SIP-I for other ISUP variants. The service interoperability level between SIP-I and other protocols such as SIP, H.323, PRI, and QSIG, is lower than the interoperability level between SIP-I and ISUP, but is nearly equivalent to the interoperability level between those protocols and ISUP today.The SIP-I Protocol feature is useful in a next-generation network (NGN) emulation model, where the Cisco PGW 2200 Softswitch, working with the Cisco BTS 10200 Softswitch in a SIP solution, communicates with other NGNs using SIP-I. This new feature is also useful for bridging existing PSTN networks without TDM interconnections being required.
Russian SIP-I support was added in CSCsv88752.
Note
Support for Tel URI in SIP Diversion Header
Diversion information in incoming SIP messages, such as INVITE and 3xx, may have tel URI. Currently, the Cisco PGW 2200 Softswitch supports only the SIP URI in the Diversion header. The Suppression of Redirecting Number and Information feature enables the Cisco PGW 2200 Softswitch to relay the Diversion headers received with incoming SIP requests or responses to the outgoing SIP network. If multiple Diversion headers are present, the Cisco PGW 2200 Softswitch relays information pertaining to all the Diversion headers to the outgoing SIP network. The Cisco PGW 2200 Softswitch will also parse and handle the tel-URI-formatted Diversion headers in the SIP.
Note
Support of PAID Tel URI
The Support of PAID Tel URI feature enables the Cisco PGW 2200 Softswitch to parse the Telephone Uniform Resource Identifier (tel URI) information, and pass it from the P-Asserted-Identity (PAID) header to Calling Line Identification (CLI) of ISUP message.
Before this feature, when the Cisco PGW 2200 Softswitch received a PAID header from SIP, it stored the SIP URI of the PAID and used it to build the calling party number. Tel URI in PAID header was ignored.
With this feature, when both tel URI and SIP URI are present in the message, the Cisco PGW 2200 Softswitch uses the tel URI in preference to SIP URI. If a SIP INVITE message contains multiple PAID headers, the Cisco PGW 2200 Softswitch uses the first Tel URI of PAID header.
The following examples shows an incoming PAID header with tel URI:
P-Asserted-Identity: "ego ego"<tel:+4533591161>The Cisco PGW 2200 Softswitch does not support the instance where other parameters are present in the tel URI. For example, PGW does not support the following type of Tel URI in PAID:
tel: +1-800-234-5678;cic=2345The Support of PAID Tel URI feature addresses the support of tel URI in PAID header for SIP-to-ISUP calls and ISUP-to-SIP calls. Calls originated from EISUP side and terminated on SIP side are also supported. All the variants of ISUP and the protocols that ISUP uses, including EISUP, are supported. This feature is not applicable to SIP-SIP calls. That is, the Cisco PGW 2200 Softswitch does not parse tel URI in SIP-SIP calls. Except for the URI, no other parameters are supported for this feature. The Cisco PGW 2200 Softswitch does not support Tel URI of any form in any of the SIP headers.
Note
Support of SIP P-Headers for 3GPP
The Support of SIP P-Headers for 3GPP feature extends handling capabilities of SIP P-headers on the Cisco PGW 2200 Softswitch. The Cisco PGW 2200 Softswitch supports three more SIP P-headers for Third Generation Partnership Project (3GPP):
•
•
•
This feature enables service providers to correlate charging and access network information across multiple entities within a user-defined trusted zone. Service providers can use these two types of information saved as call detailed records (CDRs) for further analysis and actions.
In a typical deployment, the Cisco PGW 2200 Softswitch interworks voice services between two IP Multimedia Subsystem (IMS) core networks. It also interworks voice service among PSTN networks and IMS core networks. Each Cisco PGW 2200 Softswitch pair functions as a Breakout Gateway Control Function (BGCF) server or a Media Gateway Controller Function (MGCF) server.
This feature provides the following benefits:
•
•
•
The Support of SIP P-Headers for 3GPP feature has the following restrictions and limitations:
•
–
–
•
Note
Suppression of Redirecting Number and Information
When a call that is made from the ISUP (ETS_300_356) to the Session Initiation Protocol (SIP) is redirected to the ISUP (ETS_300_356), the following information is sent in Initial Address Messages (IAM) or Address Complete Messages (ACM):
•
•
•
•
•
The Suppression of Redirecting Number and Information feature enables the optional suppression of the above parameters in IAMs and ACMs. In incoming messages, these parameters are parsed and processed for all existing call logics. The decision about suppression is taken when encoding or packing the ISUP messages in the outgoing direction of the Cisco PGW 2200 Softswitch. The ISUP trunk group properties are used to configure the suppression.
Note
TCP Transport for SIP Phase II
The TCP Transport for SIP Phase I feature introduced support for multiple transport protocols on the PGW 2200 Softswitch in Release 9.7(3). This feature extends the benefits of TCP Transport for SIP Phase I by adding more flexible configuration options for the UDP and TCP transport protocols.
This feature provides the following benefits:
•
•
•
•
•
Note
TG Advance
In the current instance of normal Trunk group (TG) advance, if the number of advances meets or exceeds the *.MaxNumTGAdvances value defined in XECfgParm.dat, the failure cause is set to Temporary Failure, and the treated cause code that started the reattempt cycle will not be passed to the originating side. The cause code will always be Temporary Failure, no matter what the terminating call release cause code is.
With the introduction of the TG Advance feature, the release cause code is passed transparently to the originating side in case of a failure from a terminating call leg.
Note
Installation Notes
This section contains information and procedures you can use to remove, upgrade, or install the Cisco PGW 2200 Softswitch software. It also contains information about software patches.
Acquiring the Software
The Cisco PGW 2200 Softswitch software is provided to users on CD. Before installing the software, check the solution release notes and the web for the most current patch level. If the information on the CD matches the information provided on the web and in the solution release notes, you can install the software and patches directly from the CD.
If the web information is more current, complete the following procedure to obtain software patches from Cisco.com.
Release 9.8(1) Patch 4 and Earlier
Software files for Patch 4 and earlier are located in the following directories.
Note
Media Gateway Controller 9.8(1) Sparc Version:
http://www.cisco.com/pcgi-bin/tablebuild.pl/mgc-981-sparc
Media Gateway Controller 9.8(1) Opteron Version:
http://www.cisco.com/pcgi-bin/tablebuild.pl/mgc-981-opteron
Release 9.8(1) Patch 5 and Later
Use the following procedure to locate the software files for Patch 5 and later:
Step 1
The Download Software page displays.
Step 2
A login box displays.
Step 3
After authentication, a list of Voice and Unified Communications products displays.
Step 4
1.
2.
3.
4.
Step 5
Step 6
Caution
Installing and Upgrading the Softwareon
Read all notices and statements in this section.
Important Notices and Statements
Note
Note
Note
Caution
Caution
Caution
Caution
Perform the following procedure to ensure that DTMF propagation works when upgrading to Release 9.8(1).
•
•
•
•
Tip
Additional Cautions and Notes for Patch 5 and Later
All the cautions and notes in this section apply to Patch 5 and later.
Caution
Caution
Caution
Note
Using the Patch Upgrade Procedure
To install software patches, use the procedure provided in the technical note Patch Upgrade Procedure for Cisco PGW 2200 Softswitch Release 9.6 and Later.
The protocol packaging has been improved so that you need only load and install protocols that you require. Previously, the entire protocol suite was packaged and delivered as a unit. With the improved packaging protocol:
•
•
The same number of packages available with the initial release still exists; however, they have a new nomenclature that is required for support of patching later in the release life cycle. You have the option to install only the packages containing required protocols.
The protocol packages are labeled CSCOnnvvv:
nn—Indicates the specific protocols you need for your environment.
vvv—Indicates the version level of the patch.
For example, at the time of the release you are given protocol patch CSCO01000.pkg. The 01 indicates a specific protocol applicable to your environment; 000 indicates the revision level. The next time a set of protocol patches is built, the 000 is incremented by 1 (001).
Caution
Note
Note
Be sure that you have downloaded the latest patch file as explained in the "Release 9.8(1) Patch 5 and Later" section. Navigate to the /opt/SW/SxxPxx directory (for example, /opt/SW/S5P5), and copy the packages you want to apply into your local directory (/opt/SW/SxxPxx) for installation.
The installation script requires one of the following options:
•
•
•
–
–
•
–
–
The following shows a sample output of option 2, patch all, which automatically searches the current directory and the installed system to determine the most recent available patch located in /opt/SW/SxxPxx, for example, /opt/SW/S5P5 (protocol and system), and automatically updates the system with that patch level:
bash-3.00# ./patch allNote:From Release 9.8(1), PGW may change TimesTen database schema during patch application, please make sure(1) TimesTen database has been backed up before applying the patch(2) TimesTen replication has been stopped before applying the patch(3) TimesTen daemon keeps running during patch applicationHave these preconditons all been met? [y] [y,n,?,q] yThe following patches are about to be removed from your system:CSCO00004CSCO01004CSCO02004CSCO10004CSCO20004CSCO30004CSCO31004CSCO32004CSCO33004CSCO40004CSCO41004CSCO42004CSCO50004CSCO60004CSCO70004CSCO71004CSCO80004CSCOgs004The following patch(es) are about to be added to your system from the local directory:CSCO00005.pkgCSCO01005.pkgCSCO02005.pkgCSCO10005.pkgCSCO20005.pkgCSCO30005.pkgCSCO31005.pkgCSCO32005.pkgCSCO33005.pkgCSCO40005.pkgCSCO41005.pkgCSCO42005.pkgCSCO50005.pkgCSCO60005.pkgCSCO70005.pkgCSCO71005.pkgCSCO80005.pkgCSCOgs005.pkgAre you sure this add/remove scenario is correct? [y] [y,n,?,q]System Level Equivalency
Table 5 provides the system level equivalency for each protocol patch. For example, after you install CSCOnn006, Release 9.8(1) is equivalent to Release 9.7(3) patch level CSCOnn025 (contains all patches and features included in Release 9.7(3) up to patch CSCOnn025).
Table 6 provides the system level equivalency for each system patch. For example, after installing CSCOgs006, release 9.8(1) is equivalent to release 9.7(3) patch level CSCOgs025 (contains all patches and features included in release 9.7(3) up to patch CSCOgs025).
Patch Test Combinations
Table 7 provides a list of the patch combinations that were used during testing. Use this list to determine which protocol and system patches should be installed before you run the Cisco PGW 2200 Softswitch software. It does not matter which patch (protocol or system) is installed first.
Resolved Caveats Listed by Patch Number
This section lists the caveats resolved in each patch.
Release 9.8(1) S18P18
Release 9.8(1) S18P18 resolves the following caveats:
Release 9.8(1) S17P17
Release 9.8(1) S17P17 resolves the following caveats:
Release 9.8(1) S16P16
Release 9.8(1) S16P16 resolves the following caveats:
Release 9.8(1) S15P15
Release 9.8(1) S15P15 resolves the following caveats:
Open Defect in 9.8(1)S15P15 Release
New defect
CSCts66527
3
mdl-sip
MLPP local handling doesnot work when mlppsupport is set.
Legacy Defect
Release 9.8(1) S14P14
Release 9.8(1) S14P14 resolves the following caveats:
Release 9.8(1) S13P13
Release 9.8(1) S13P13 resolves the following caveats:
Release 9.8(1) S12P12
Release 9.8(1) S12P12 resolves the following caveats:
CSCOnn011
Patch CSCOnn011 resolves the following caveats:
SNMP Returns Wrong Status for Physical E1000G Interfaces
The SNMP returns wrong status for physical E1000G interfaces procedure is used to check the status of the physical E1000G interfaces on the Cisco PGW 2200 Softswitch. The following procedure should only be used by customers who need to check the status of the physical E1000G interfaces.
To check the status of the physical E1000G interfaces, use the following procedure:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
CSCOnn010
Patch CSCOnn010 resolves the following caveats:
CSCOnn009
Patch CSCOnn009 resolves the following caveats:
CSCOnn008
Patch CSCOnn008 resolves the following caveats:
CSCOnn007
Patch CSCOnn007 resolves the following caveats:
CSCOnn006
Patch CSCOnn006 resolves the following caveats:
CSCOnn005
Patch CSCOnn005 resolves the following caveats:
CSCOnn004
Patch CSCOnn004 resolves the following caveats:
CSCOnn003
Patch CSCOnn003 resolves the following caveats:
CSCOnn002
Patch CSCOnn002 resolves the following caveats:
CSCOnn001
Patch CSCOnn001 resolves the following caveats:
CSCOgs011
Patch CSCOgs011 resolves the following caveats:
CSCth60266
2
engine
Terminations/CICs gets unavailable at MGX VXSM after PGW 2200 switchover
CSCOgs010
Patch CSCOgs010 resolves the following caveats:
CSCOgs009
Patch CSCOgs009 resolves the following caveats:
CSCOgs008
Patch CSCOgs008 resolves the following caveats. See the "Patch Test Combinations" section of this document to determine which protocol and system patches are needed.
CSCOgs007
Patch CSCOgs007 resolves the following caveats. See the "Patch Test Combinations" section of this document to determine which protocol and system patches are needed.
CSCOgs006
Patch CSCOgs006 resolves the following caveats. See the "Patch Test Combinations" section of this document to determine which protocol and system patches are needed.
CSCOgs005
Patch CSCOgs005 resolves the following caveats. See the "Patch Test Combinations" section of this document to determine which protocol and system patches are needed.
CSCOgs004
Patch CSCOgs004 resolves the following caveats. See the "Patch Test Combinations" section of this document to determine which protocol and system patches are needed.
CSCOgs003
Patch CSCOgs003 resolves the following caveats. See the "Patch Test Combinations" section of this document to determine which protocol and system patches are needed.
CSCOgs002
Patch CSCOgs002 resolves the following caveats. See the "Patch Test Combinations" section of this document to determine which protocol and system patches are needed.
CSCOgs001
Patch CSCOgs001 resolves the following caveats. See the "Patch Test Combinations" section of this document to determine which protocol and system patches are needed.
Protocols Supported
Table 8 lists the protocols supported by the Cisco PGW 2200 Softswitch. In this table, Switch Type refers to variations in the switch implementation of a particular protocol. Switch Type 0 means that there is no switch-specific implementation.
Table 8 Supported Protocol Variants
ANSISS7_2K
SS7-ANSI
0
ANSISS7_92
SS7-ANSI
0
ANSISS7_C2
SS7-ANSI
20
ANSISS7_C3
SS7-ANSI
0
ANSISS7_E1
SS7-ANSI
23
ANSISS7_STANDARD
SS7-ANSI
0
ANSISS7_STANDARD_SIPI
SIP-I
0
ATT_41459
ISDNPRI
17
ATT_41459_C2
ISDNPRI
17
BELL_1268
ISDNPRI
22
BELL_1268_C2
ISDNPRI
22
BTNUP_BTNR167
SS7-UK
5
BTNUP_IUP
SS7-UK
5
DPNSS_BTNR188
DPNSS
26
dummy
AVM
0
dummy
H248
0
dummy
LI
0
dummy
MGCP
0
dummy
RA
0
dummy
SGCP
0
dummy
TCAPOverIP
0
dummy
VSI
0
EISUP
EISUP
0
ETS_300_102
ISDNPRI
27
ETS_300_102_C2
ISDNPRI
27
ETS_300_121
SS7-ITU
0
ETS_300_172
ISDNPRI
29
ETS_300_356
SS7-ITU
0
GR317
SS7-ANSI
0
HONGKONG
SS7-ITU
0
IETF_SIP
SIP
0
ISUPV1_POLI
SS7-ITU
0
ISUPV2_AUSTRIAN
SS7-ITU
0
ISUPV2_AUSTRIAN_C2
SS7-ITU
0
ISUPV2_CZECH
SS7-ITU
0
ISUPV2_DUTCH
SS7-ITU
0
ISUPV2_FINNISH96
SS7-ITU
0
ISUPV2_FINNISH96 _SIPI
SIP-I
0
ISUPV2_FRENCH
SS7-ITU
0
ISUPV2_GERMAN1
SS7-ITU
0
ISUPV2_GERMAN_SIPI
SIP-I
0
ISUPV2_ISRAEL
SS7-ITU
40
ISUPV2_JAPAN
SS7-JAPAN
10
ISUPV2_JAPAN_C2
SS7-JAPAN
0
ISUPV2_NORWEGIAN
SS7-ITU
0
ISUPV2_POLISH
SS7-ITU
0
ISUPV2_SPANISH
SS7-ITU
0
ISUPV2_SPANISH_C2
SS7-ITU
0
ISUPV2_SWISS
SS7-ITU
0
ISUPV2_SWISS_C2
SS7-ITU
0
ISUPV2_VIETNAM
SS7-ITU
0
ISUPV3
SS7-ITU
0
ISUPV3_FRENCH
SS7-ITU
0
ISUPV3_UK
SS7-UK
0
ISUPV3_UK_C2
SS7-UK
15
ISUPV3_UK_C3
SS7-UK
0
ISUPV3_UK_C4
SS7-UK
15
ISUPV3_UK_SIPI
SIP-I
0
Q721_BASE
SS7-ITU
5
Q721_BRAZILIAN
SS7-ITU
5
Q721_BRAZILIAN_C2
SS7-ITU
5
Q721_CHINA
SS7-CHINA
5
Q721_FRENCH
SS7-ITU
5
Q721_PHILLIPINE
SS7-ITU
5
Q761_97VER_BASE
SS7-ITU
0
Q761_97VER_RUSS
SS7-ITU
0
Q761_97VER_RUSS_C2
SS7-ITU
0
Q761_97VER_RUSS_SIPI
SIP-I
0
Q761_99VER_AUSTRL_C3
SS7-ITU
0
Q761_99VER_BASE
SS7-ITU
0
Q761_99VER_BASE_SIPI
SIP-I
0
Q761_ARGENTINA
SS7-ITU
0
Q761_ARGENTINA_C2
SS7-ITU
0
Q761_AUSTRL
SS7-ITU
0
Q761_AUSTRL_C2
SS7-ITU
0
Q761_BASE
SS7-ITU
0
Q761_BELG
SS7-ITU
0
Q761_BELG_97VER
SS7-ITU
0
Q761_CHILE
SS7-ITU
0
Q761_CHINA
SS7-CHINA
0
Q761_CHINA_C2
SS7-CHINA
0
Q761_DANISH
SS7-ITU
0
Q761_GERMAN2
SS7-ITU
0
Q761_INDIA
SS7-ITU
0
Q761_KOREAN
SS7-ITU
0
Q761_MALAYSIAN
SS7-ITU
0
Q761_NEWZEALAND
SS7-ITU
0
Q761_PERU
SS7-ITU
0
Q761_PORTUGAL
SS7-ITU
0
Q761_SINGAPORE
SS7-ITU
0
Q761_SINGAPORE_C2
SS7-ITU
0
Q761_TAIWAN
SS7-ITU
0
Q761_THAILAND
SS7-ITU
0
Q767_AUSTRALIA
SS7-ITU
0
Q767_BASE
SS7-ITU
0
Q767_BRAZIL
SS7-ITU
0
Q767_BRAZIL_C2
SS7-ITU
0
Q767_COLOMBIA
SS7-ITU
0
Q767_GUATEMALA
SS7-ITU
0
Q767_INDONESIA
SS7-ITU
0
Q767_ITAL
SS7-ITU
0
Q767_ITAL_C2
SS7-ITU
0
Q767_MEXICAN
SS7-ITU
0
Q767_NIGERIAN
SS7-ITU
0
Q767_RUSS
SS7-ITU
0
Q767_RUSS_C2
SS7-ITU
0
Q767_SINGAPORE
SS7-ITU
0
Q767_SPAN
SS7-ITU
0
Q767_SWED
SS7-ITU
0
Q767_TURKISH
SS7-ITU
0
Q931
ISDNPRI
27
Q931_AUSTRALIA
ISDNPRI
19
Q931_SINGAPORE
ISDNPRI
27
QBE
CTI-QBE
0
1 ISUPV2_GERMAN has ETS_300_356 as the base variant and GERMAN as the country variant.
2 Q761_GERMAN has Q761 as the base variant, SIEMENS as the country variant, and MOBILCOM as the customer variant.
Known Issues and Operational Recommendations
This section contains information about known issues and the corresponding workarounds in the
Cisco PGW 2200 Softswitch software release 9.8(1).
Note
System File vars.pm Error After Migration from Release 9.7(3) to Release 9.8(1)
After you have migrated from Cisco PGW 2200 Softswitch Release 9.7(3) CSCOgs027/CSCOnn027 to Release 9.8(1) CSCOgs007/CSCOnn007 and later, there is an error in the /opt/CiscoMGC/lib/perl5/5.00503/vars.pm file after installation.
The following line shows line 17 of vars.pm after installation:
if ($sym =~ tr/A-Za-Z_0-9//c) {Correct line 17 should be:
if ($sym =~ tr/A-Za-z_0-9//c) {The workaround for this known issue is to manually change line 17 of vars.pm file from "if ($sym =~ tr/A-Za-Z_0-9//c) {" to "if ($sym =~ tr/A-Za-z_0-9//c) {" and save the file. The CDETS number for this issue is CSCtf30543.
The Hostagt Process Sometimes Takes Up High CPU (Nearly 50%)
You could do following things to resolve this problem:
•
•
Note
http://www.cisco.com/cisco/software/type.html?mdfid=277708611&flowid=5334
Caveats
Use the Bug Toolkit to query caveats. The tool is located at the following URL:
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl
Related Documentation
This document contains information that is related to SoftwareRelease 9.8(1). The documents that contain additional information related to the Cisco PGW 2200 Softswitch are at the following URL:
http://www.cisco.com/en/US/products/hw/vcallcon/ps2027/tsd_products_support_series_home.html
You can find the Cisco PGW 2200 Softswitch documentation map at the following URL:
http://www.cisco.com/en/US/products/hw/vcallcon/ps2027/products_documentation_roadmaps_list.html
Before Installation
Before installing the Cisco PGW 2200 Softswitch software, consult the following related documentation for information about hardware installation and system requirements:
•
•
•
•
•
After Installation
After installing the Cisco PGW 2200 Softswitch software, consult the following related documentation for information on configuring and provisioning your system:
•
•
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
©2008-2012 Cisco Systems, Inc. All rights reserved.
