|
|
These release notes describe the features and caveats for Release 1.3 of the Cisco SS7 Interconnect for Voice Gateways Solution. The following sections list the contents of this document and describe the solution and its components.
These release notes describe the following topics:
The Cisco SS7 Interconnect for Voice Gateways Solution is a distributed system that provides SS7 connectivity for Voice-over-IP (VoIP) media gateways by using the Cisco Media Gateway Controller (also referred to as the Cisco SC2200) and the media gateways as a bridge from the H.323 IP network to the PSTN network. This solution interacts over the IP network with other Cisco H.323 VoIP media gateways. In addition, the Cisco SS7 Interconnect for Voice Gateways Solution can interoperate with H.323 endpoints, using non-SS7 signaling such as ISDN PRI and channelized T1/E1.
Figure 1 illustrates where the Cisco SS7 Interconnect for Voice Gateways Solution is located when it is dropped into a PSTN to offload calls. By placing the solution as close to the ingress switch as possible, voice and data traffic ties up fewer PSTN resources. The direct connection of the Cisco SS7 Interconnect for Voice Gateways Solution to the SS7 network provides advantages such as faster call setup and teardown, and SS7's look-ahead capabilities for rerouting to avoid downed network nodes and links.
| Component Type | Product Name | Flash Memory Required | DRAM Memory Required | Other Hardware Requirements |
|---|---|---|---|---|
See Release Notes for Cisco Media Gateway Controller Software Release 7.4(12) |
||||
See Installing CMNM |
||||
|
Table 2 lists the required versions of Cisco IOS and other software for the components supported by the Cisco SS7 Interconnect for Voice Gateways Solution. This table includes links to the Software Center, where you can download the software you need to upgrade your solution to Release 1.3.
 |
Note You need a CCO account to download the software listed in Table 2. |
 |
Caution The December 10, 2001, software release is listed here for reference purposes only. This release was obsoleted because of security concerns. Cisco Systems recommends that you upgrade your components to the software versions listed in the April 18, 2002, column. See Cisco Security Advisory for details |
| Component | Release 1.3 December 10, 2001 |
Release 1.3 IOS/MGCS Patch Update April 18, 2002 |
Release 1.3 IOS/MGCS Patch Update August 12, 2002 |
|---|---|---|---|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
| 1Access to this release of Cisco IOS is restricted. To obtain this release, please send email to tv13_5850_xb4@cisco.com. |
Table 3 lists the features that have been added to Release 1.3 of the Cisco SS7 Interconnect for Voice Gateways Solution.
| Feature | Supported Platform | Minimum Cisco IOS Version Required |
Reference Documentation |
|---|---|---|---|
SS7 Interconnect for Access Servers and Voice Gateways Solutions Media Gateway Guide |
|||
Release Notes for Cisco Signaling Link Terminal for Cisco IOS Release 12.2 XA |
|||
Support for Cisco Media Gateway Controller Node Manager (CMNM) |
|||
SS7 Interconnect for Voice Gateways Solution Provisioning Guide |
|||
| 1Access to this release of Cisco IOS is restricted. To obtain this release, please send email to tv13_5850_xb4@cisco.com. |
Caveats describe unexpected behavior in the Cisco SS7 Interconnect for Voice Gateways Solution. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious. To review caveats that affect the individual components of the Cisco SS7 Interconnect for Voice Gateways Solution, refer to the following online release notes:
Cisco AS5850s configured for handover-split mode operate under the following limitations:
Use the redundancy handover peer-resources busyout-period command when instructing the active RSC to release control of the slots usually controlled by the standby RSC. This is to avoid dsp timeout event errors caused by the sudden disruption of active calls that are using the DSP resources on the relinquished slots.
This section describes possibly unexpected behavior by Release 1.3 of the Cisco SS7 Interconnect for Voice Gateways Solution.
If an SS7 destination point code sends a release with cause values 0x3F (service or option not available, unspecified) or 0x51, the media gateway controller will change this cause value to 0x1F (normal, unspecified). There is no workaround.
If an SS7 release message is sent with cause codes 0x29, 0x2A, or 0x6F by a SS7 destination point code, the Cisco Media Gateway Controller will change the cause code to 0x2C (Request circuit/channel not available). There is no workaround.
A setting in XECfgParm.dat, *.SysScreeningCheck, has a default value of "false". If screening is configured on the Cisco SC2200 and assigned to an SS7 path, all calls will be rejected by the Cisco SC2200. The workaround for this problem is to modify the XECfgParm.dat file and change this value to "true". After changing the XECfgParm.dat file the MGC software must be restarted. This can be accomplished in a redundant configuration by forcing two manual switchovers.
During a failover on the master SC where both ethernet connections are lost, the failover correctly switches to the slave SC. However, once the ethernet connections are restored on the master, the SC does not return to Standby mode. The workaround is as follows:
With the slave in Active mode, execute (as root) on the Master:
After the SC software has stopped, restart it using the following command:
To verify that the SC has entered the Standby state, return to mml and execute the following command:
In MGC software release 7.4(12), the command set-admin-state:<NASPATH>:reset does not work. There is not workaround.
After dynamically modifying trunk files, the command prov-sync may cause the SC to switch over. There is no workaround.
After an SS7 DPC failure, calls may hang in the Cisco SC2200. As a workaround, enter the sta-aud command. For further details on this procedure, refer to Release Notes for Cisco Media Gateway Controller Software Release 7.4(11).
When configuring AAA broadcast for the purpose of introducing a second RADIUS accounting server, the order of entry of the server groups will determine whether calls pass authorization or not.
On the Cisco AS5300, AS5350, AS5400, and AS5800 in a Cisco SS7 Interconnect for Voice Gateways solution, if isdn negotiate-bchan resend-setup is configured under the serial interface for the NFAS group, this will cause a renegotiation of the channel if the channel used by the NAS on egress calls is unavailable for some reason in the SS7 network (glare, COT failure, etc.). The CDR that is generated by the NAS in this particular scenario will contain the value of the original channel in the cisco-vsa-port-string field, instead of the new renegotiated value. There is no workaround.
The ExtCOT parameter, used when provisioning sigsvcprop on the Cisco SC2200, is case sensitive. When configuring COT, be sure to specify Loop (with an upper-case L) or Transponder (with an upper-case T).
On a Cisco AS5400 in a Cisco SS7 Interconnect for Voice Gateways solution, a manual COT test may fail. This problem is seen when the following configuration modem inout under line x/xx x/yyy is not in place.
The workaround is to use the following configuration:
When the Cisco AS5800 carries simultaneous egress and ingress calls, it selects blocked channels to terminate egress calls. This problem has been observed in 122-9.4.PI4 load.
All the channels of controller t1 1/0/0 were blocked from the Cisco SC2200 and controllers t1 1/0/1 to 1/0/8 were used for terminating calls. Controllers 1/1/0 to 1/1/9 were also up and in unblocked condition. Egress traffic was running for long time at 2 cps rate and there was 99.9% CCR. After some time, controllers 1/1/0 to 1/1/9 were used for ingress traffic at 1 cps rate. This has caused 5800 to select the blocked channels of controller 1/0/0 to terminate the egress calls. Since these channels were blocked, the Cisco SC2200 re-negotiates the channel-id. The sh isdn service command shows controller 1/0/0 is blocked by the Cisco SC2200.
SS7--->SC2200--->AS5300----H.323---->AS5300----CAS
when one of the controllers is down at the egress gateway, the active calls are released with cause value 34- No circuit Available- to the ingress SS7 side. Sending cause value 34 is not correct in this scenario, because the call is already answered and may be active for several minutes. If the egress side is SS7, cause code 41 is sent. Because of sending cause code 34, most probably these calls will not be billed also.
On the Cisco gateway running Cisco IOS Release 12.2(10.6)T, if a T1 or E1 goes down while calls are active, the calls will be correctly released but with the incorrect release cause code (16, normal call clearing). They should be released with cause 41, Temporary Failure. There is no workaround.
When the controller T3 card is hot swapped, the controller T3 never comes up until the framing type is changed.
The Cisco AS5850 was configured in handover split mode. RSC6 and RSC7 were both up and running calls. The controller 12/0 was controlled by RSC7 and was set up to egress ss7 calls and physically loopbacked externally. While calls were being terminated, the controller 12/0 was pulled from slot and then pushed back in. Controller T3 12/0 did not come up, whereas controllers t1 12/0:1 to 12/0:28 all came up. Calls to RSC7 could be terminated even though controller t3 12/0 was down.
The box is power recycled and both RSC6 and RSC7 came up. Controller 12/0 came up momentarily and the next second went down. All controllers belonging to 12/0 came up. The framing type was set to m23 and I changed to c-bit. After changing the framing type, the controller 12/0 has come up and all associated t1 also. But show call res voice stats shows no free DS0 resources and the right half of the AS5850's resources become unavailable.
After shut and no shut on the rlm g 2, the DS0 resources become available.
On the Cisco AS5xx0 family of routers, 10 to 15% of COT tests may fail when the gateway is terminating transponder COT. This does not affect COT tests when the gateway is terminating Loop COT.
The workaround is to upgrade to SPE v7.17 or greater. First check www.cisco.com for np.7.17.spe:
http://www.cisco.com/cgi-bin/tablebuild.pl/nextport-spe
If version 7.17 or later is not yet available, e-mail xu-nextport@cisco.com with details of your problem. A special SPE image can be downloaded to resolve this issue. Someone on the mail alias will provide you with details for accessing the file and how to download it.
Customers using Cisco Access Servers (such as Cisco AS5400 or Cisco AS5300) in the Cisco SS7 Interconnect for Voice Gateways solution may find that the radius CDR generated for CAS signaling-terminated calls do not show the DS0 number of "cisco-vsa-port-string" and "cisco-avpair" fields correctly and always set it to 0.
For information on troubleshooting procedures for the Cisco SS7 Interconnect for Voice Gateways Solution, refer to the Cisco MGC Software Release 7 Operations, Maintenance, and Troubleshooting Guide.
Consult the following online documentation for information about hardware installation and system requirements for the Cisco SS7 Interconnect for Voice Gateways Solution.
Platform-specific release notes are available for the following components:
The following sections provide sources for obtaining documentation from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at the following sites:
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 as an annual subscription.
Cisco documentation is available in the following ways:
http://www.cisco.com/cgi-bin/order/order_root.pl
http://www.cisco.com/go/subscription
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, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
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 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:
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.
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:
P3 and P4 level problems are defined as follows:
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
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:
Posted: Mon Feb 24 13:00:51 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
