|
|
These release notes describe the features and caveats for the Cisco Telephony Controller software Release 7.3(15)D. The following sections list the contents of this document and describes the system and software.
 |
Note In Release 7.4, the name of the software has been changed to the Cisco Media Gateway Controller (MGC) software. The documentation that applies to both software Release 7.3 and Release 7.4 uses the term MGC to refer to the software. |
The Cisco Telephony Controller software is part of several solutions that perform call processing, protocol conversion, and call switching and routing functions. It runs on a Sun Microsystems host server and is a component of:
In these solutions, the combination of software and host server is called the Cisco SC2200 Signaling Controller, or SC host. The Cisco SC2200 interconnects Cisco network access servers (NASs) to a circuit-switched time-division multiplexing (TDM) network. Cisco Signaling Link Terminals (SLTs) are used to terminate Signaling System 7 (SS7) and pass signaling information to the SC host. Data and voice calls are then routed over the IP network. The combination of SC host and Cisco SLTs is also referred to as the SC zone.
The Cisco SC2200 is available in several continuous-service or simplex configurations. Supported platforms include:
The following software is required to run the Cisco Media Gateway Controller software on the Sun Enterprise 450, Sun Netra t 112x, and Sun Netra t 140x platforms:
Table 1 shows the host minimum server hardware requirements.
 |
Caution Before using the minimum hardware configuration, consult with your Cisco representative to determine the hardware and software requirements that will give you the best results based on your network configuration, proposed traffic, and desired processing power. In particular, B-number analysis or screening, long call hold times, and SCP queries might require additional hardware resources. |
|
Note For the Cisco SS7 Interconnect for Access Servers Solution to work properly you need 4 GB of swap space. |
| Component | Sun Netra t 1120/1125 | Sun Netra t 1400/1405 | Sun E4501 |
|---|---|---|---|
Processor | 2 - 300 MHz | 2 - 440 MHz2 | 2 - 300 MHz |
Disk drive | 1- 9 GB3 | 1 - 9 GB3 | 1- 9 GB3 |
CD-ROM drive | 1 | 1 | 1 |
DAT 3-drive | Optional | Optional | Optional |
RAM | 1 GB4 | 1 GB5 | 1 GB6 |
Table 2 shows the interface options.
| Interface Options | Sun Netra t 1120/1125 | Sun Netra t 1400/1405 | Sun E4501 |
|---|---|---|---|
ITK E1/T1 card2 | Supported | Not supported | Supported |
PTI V.35 card | Supported | Not supported | Supported |
Sun Ethernet 1-port card | Required | Required | Required |
Cisco SLT | Supported | Supported | Supported |
|
Note We recommend that you use the Cisco SLT to terminate signaling. ITK T1/E1 and PTI V.35 cards are no longer orderable. |
Table 3 shows the ancillary hardware requirements. In addition to the items listed, your solution might use the following:
| Component | Sun Netra t 1120/1125 | Sun Netra t 1400/1405 | Sun E450 | ||
|---|---|---|---|---|---|
Dataprobe ARU | Supported
| Not supported | Supported; not required if alarm functions are not necessary | ||
Dataprobe A/B switch | Required with use of ITK T1/E1 or PTI V.35 card1 | Not supported | Required with use of ITK T1/E1 or PTI V.35 card1 | ||
Asynch extension | Optional for simplex configurations; required with use of Dataprobe A/B switch | Not supported | Optional for simplex configurations; required with use of Dataprobe A/B switch |
| 1Call preservation upon switchover is not supported with the A/B switch. |
For Cisco IOS memory requirements, see the Cisco IOS release notes listed in Table 4.
| NAS | Release Notes | ||
|---|---|---|---|
Cisco AS52001 | http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5200/ios52/index.htm
| ||
Cisco AS5300 | http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/iosrn/index.htm | ||
Cisco AS58002 | http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5800/58_iosrn/index.htm
|
Solution software requirements are detailed in the following tables:
|
Note For more information about Cisco IOS software, see the Cisco IOS release notes for your platform at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/relnote/index.htm |
|
Note For more information about portware and IOS software releases, see the compatibility matrixes at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/mod_info/cm/mca12prt.htm |
|
Note The Cisco SS7 Interconnect for Voice Gateways Solution requires a Cisco AS5300 running Cisco IOS 12.1(2)T. |
Component | Required Software Release | Required Firmware (If Applicable) |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Component | Required Software Release | Required Firmware (VCware) (If Applicable) |
|---|---|---|
|
|
|
|
|
|
|
|
|
Your solution can use one or more local-area network (LAN) switches from the Cisco Catalyst Switch family with the Catalyst software, Release 12.0(3x)W5(9), to connect the SC hosts to the MGWs or to the Cisco SLTs.
|
Note A LAN switch is not provided with the Cisco SC2200. |
The features listed in Table 7 are supported in Release 7.3 of the Cisco Telephony Controller Software.
| Feature | Purpose |
|---|---|
NAS resource and call congestion management | The SC can monitor resource usage for various NASs and direct calls according to load. |
Provides a reliable IP link between signaling controllers and NASs with Redundant Link Manager (RLM) | No single point of failure in connection between NAS and signaling controller. |
Directly connects access servers to PSTN in a peer-to-peer interconnect |
|
Intelligent Network (IN) triggers |
|
Dial outsourcing | The SC and NAS can be provisioned by telephone service providers and local exchange carriers. Calls can be directed to NASs belonging to various ISPs. |
The SC features parallel advances in Cisco Dial, ISDN, and routing platforms | Realize the vision of open packet telephony and new world network architectures. |
Facility-associated signaling provided by the Cisco SLTs |
|
Resource management |
|
Introduces services such as wholesale dial, VPDNs, and virtual modem pooling |
|
Supports colocated and distributed access servers |
|
Investment in Cisco equipment protected. | |
Terminates and originates switching-system functions |
|
Provides software upgrade of:
|
|
|
|
| Meet PSTN requirements to create new service opportunities. |
Table 8 provides an overview of the scalability and performance features for Release 7.3.
| Feature | Benefit |
|---|---|
|
|
The following enhancements have been made to MML and the TCM:
Table 9 provides an overview of the management components of the SC.
| Management Component | Description |
|---|---|
Telephony Controller Manager (TCM) and Dial Provisioning Plan (DPP) | The TCM is a graphical user interface (GUI) that uses SNMP to configure and provision your network. You can access the TCM remotely, using X-window terminals, and manage all of the SC hosts in your network with a single TCM system. DPP is used to format the dial plan and routing data for deployment on the SC. Dial plan and routing data is defined in a flat file. The DPP parses this information to generate the configuration files for deployment on the SC. |
Alarms | The SC supports a comprehensive set of 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. |
Performance Measurement | You can obtain a variety of usage statistics from the SC. The data is recorded real-time and is written to a file. You can specify the statistics to be collected and the time intervals for collection and writing to the file. Each performance measurement record includes:
|
Accounting | Every call that passes through the SC produces call detail information, which includes:
Call detail records are written to a spool file that is automatically closed at defined intervals or when the file exceeds a specified size. You can also specify when to retrieve or send closed files to processing systems. |
The Cisco IOS software installed on the network access servers (NASs) provides an array of network management components (described in Table 10) that are designed to meet the needs of today's large, complex networks.
These management features do the following:
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.
| Management component | Description |
|---|---|
SNMP and RMON Support | NASs can be fully managed by means of the Simple Network Management Protocol (SNMP) and imbedded Remote Monitoring (RMON) capabilities:
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 overloaded conditions and congestion in real time. |
Network management systems | The NASs both support CLI and the CiscoView GUI for comprehensive, flexible network management. CiscoView provides dynamic status, statistics, and comprehensive configuration information for Cisco switches, routers, NASs, Cisco SLTs, concentrators, and adapters. It displays a graphical view of Cisco devices, provides configuring and monitoring functions, and offers basic troubleshooting. |
Modem management | Cisco offers two types of modems: basic and managed. Managed modems offer superior reporting and statistics in the CiscoView application, including troubleshooting and monitoring modem connections on individual or groups of modems. You can manage modems using the same tools you use to manage the rest of the network. In addition, managed modems provide an out-of-band management feature that allows you to reduce problem detection and resolution time when you are working at a remote site. Through out-of-band management, you can view real-time information (for current or previous calls) such as modem modulation scheme, modem protocol, modem EIA/TIA-232 signal states, modem transmit and receive states, and analog signal-to-noise ratios. |
The Session Manager software, running on the Cisco SLT, manages the communication sessions between two SC hosts. The session manager:
The Cisco Media Gateway Controller software supports the following telephony protocols:
Table 11 lists the solutions using the Cisco Telephony Controller Release 7.3(15)D software; and the table also lists the hardware and software that these solutions require.
| Solution Name | Hardware | Software |
|---|---|---|
Cisco SS7 Interconnect for Access Servers Solution |
|
|
Cisco SS7 Interconnect for Voice Gateways Solution |
|
|
Before you install the Cisco Media Gateway Controller software, consult the following related documentation for information about hardware installation and system requirements:
After you install the Cisco Media Gateway Controller software, consult the following related documentation for information on configuring and provisioning your system:
This section contains information and procedures you can use to remove, upgrade, and install theCisco Telephony Controller software. It also contains information about software patches.
The Cisco Telephony Controller software is provided to customers on CD. It can also be downloaded by Cisco Systems. The Cisco Telephony Controller software, including software patches, can be installed directly from the CD.
If you are installing software Release 7.3(x) for the first time, refer to the Cisco Media Gateway Controller Software Release 7 Installation and Configuration Guide for instructions.
If you are upgrading from the Cisco SS7 Dial Access Solution Release 2.0 (software Release 4) to the Cisco SS7 Interconnect for Access Servers Solution (software Release 7.3[x]), refer to the Cisco SS7 Interconnect for Access Servers Solution Upgrade Guide for instructions.
|
Note These documents are shipped with your software in hard copy and electronic format on CD. Always check CCO for the latest version of the documentation. |
If you are upgrading from a previous release of 7.3(x) to Release 7.3(15)D, and you have a configuration with an active and a standby host, follow these steps:
Step 2 Stop the software by entering the /etc/init.d/transpath stop command.
Step 3 Back up and remove the CDRs using the rm /opt/TransPath/var/spool/* command.
Step 4 Uninstall the software by performing the following steps:
a. Insert the Cisco Telephony Controller software Version 7 CD-ROM into the CD-ROM drive.
b. Type each of the following commands at the # prompt and press Enter:
cd /cdrom/cdrom0 ./uninstall.sh
 |
TimeSaver If you do not accept the unattended removal, the system prompts you before removing each package individually. |
c. Type y (yes) and press Enter to accept the unattended package removal.
Uninstallation log can be found in /tmp/uninstall.log.
Step 5 Enter the following command:
cd /etc
Step 6 Open the group file with your editor.
Step 7 Make sure that the transpath group is removed. This group must be removed in order to accept default software installation later.
Step 8 Save any changes to the group file and close it.
|
Caution If you are trying to maintain calls during an upgrade of a redundant system and you want to preserve your configuration, verify that in /opt/TransPath/etc/XECfgParm.dat the pom.dataSync parameter is set to false. |
Step 9 Install the software by typing each of the following commands at the # prompt and pressing Enter:
cd /cdrom/cdrom0 ./install.sh Base directory for Media Gateway Controller (default /opt/MGC) [?,q]
Step 10 Press Enter to accept the default base directory path.
Install Cisco Telephony Controller Manager (TCM) package? [n] [y,n,?,q] y
Step 11 Enter y (yes) to install the TCM package (Optional. If you do not want to install the TCM package, skip to Step 13).
Base directory for TCM (default /opt/VSCprov/bin) [?,q]
Step 12 Press Enter to accept the default base directory path.
Use supplied admin file for unattended install? [n] [y,n,?,q] y
Step 13 Type y (yes) and press Enter to use the supplied administrative file to perform an unattended package installation. This process installs all the packages automatically. The initial installation takes approximately one hour.
|
TimeSaver If you do not accept the unattended installation, the system prompts you before installing each package individually. |
Step 14 When prompted, enter y (yes) and press Enter to install the CSCOgu000 utilities package. You will see prompts asking you to enter a user and group ID. When asked:
a. Press Enter to accept the default user ID (20000) at the system prompt.
b. Press Enter to accept the default group ID (20000) at the system prompt.
You can specify a user ID or a group ID. If the ID you specify already exists on the system, either the corresponding ID is reused, or you are prompted to enter another ID.
|
Caution No validation is performed on the IDs you enter. If you enter an invalid ID, the utilities package does not add any accounts. |
The system returns a message that the CSCOgu000 utilities package is successfully installed.
Depending on your configuration, the remaining application packages either install without interruption, or you are asked to reboot your system.
 |
Tips 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). |
Step 15 If you are prompted to reboot, perform the following steps:
a. Type the following command and press Enter:
a. After the reboot finishes, restart install.sh to install the remaining packages. To restart install.sh, type each of the following commands at the # prompt and press Enter:
Step 16 If your system uses IT Telekommunikations AG (ITK, now Digi International AG) cards (not for use with the Cisco SS7 Interconnect for Voice Gateways Solution), you must install the CSCOgd001 ITK drivers package manually using the pkgadd command:
pkgadd -d packagename
After you install the package, the system reboots automatically.
Step 17 Check the end of log file /tmp/install.log for errors
Step 18 Start the software with the /etc/init.d/transpath start command.
Step 19 Log on to the active host and perform Step 2 through Step 18. This switches call processing to the standby host (which has already been upgraded) and it becomes the active host.
Step 20 Log on to the current active host (which was the first machine you upgraded) and set the pom.dataSync parameter in the XECfgParm.dat file to true.
Software Release 7.3(15)D has three patches, CSCOgp079.pkg, CSCOgp080.pkg, and CSCOgp082.pkg at this time that are included on the CD and are automatically installed when you install the software using normal installation procedures.
If you later receive patches that need to be manually added, use the following procedure (unless otherwise stated in the release notes for the patch):
Step 2 To stop the Cisco Telephony Controller software, enter the following command:
# /etc/init.d/transpath stop
Step 3 At the UNIX prompt, change to the directory containing the software patch to be installed and enter:
pkgadd -d CSCOgpN where N is the patch number (for example, 075)
Step 4 Follow the on-screen prompts. Answer y to each prompt that requires a response.
Step 5 Repeat Step 3 and Step 4 for each patch.
Step 6 Restart your system.
This patch package provides bug fixes to devtest for the 7.3(15)D software release. The included updated executable files are copied into the /opt/TransPath/bin directory. A copy of the old versions of the files is saved in the /opt/TransPath/patch/CSCOgp079/bin directory.
Before installing this patch, you must shut down the VSC application, because the affected programs are part of the running system.
You must type as root "pkgadd -d CSCOgp079.pkg" specifying the directory in which the package is currently residing.
Following the upgrade, you must execute a config-lib command to save the production data to library, Doing so causes the /opt/TransPath/etc directory to be updated.
During installation the following directory is created and the files that are to be replaced as part of this package are backed up to the patch directories:
/opt/TransPath/patch/CSCOgp079/bin
This patch package provides showstopper or test-stopper bug fixes to devtest for the 7.3(15) software release. The patch provides the following:
ETS_300_356.so
ISUPV2_FRENCH.so
ISUPV2_GERMAN.so
ISUPV2_JAPAN.so
ISUPV2_NTT.so
ISUPV2_SPANISH.so
ISUPV2_SWISS.so
ISUPV3.so
ISUPV3_UK.so
Q761_ARGENTINA.so
Q761_AUSTRL.so
Q761_BASE.so
Q761_CHINA.so
Q761_JAPAN.so
Q761_SINGAPORE.so
ETS_300_356.mdo
ISUPV2_FRENCH.mdo
ISUPV2_GERMAN.mdo
ISUPV2_JAPAN.mdo
ISUPV2_NTT.mdo
ISUPV2_SPANISH.mdo
ISUPV2_SWISS.mdo
ISUPV3.mdo
ISUPV3_UK.mdo
Q761_ARGENTINA.mdo
Q761_AUSTRL.mdo
Q761_BASE.mdo
Q761_CHINA.mdo
Q761_JAPAN.mdo
Q761_SINGAPORE.mdo
The executable files will be updated in the /opt/TransPath/bin directory. A copy of the old versions of the files will be saved in the /opt/TransPath/patch/CSCOgp080/bin directory.
This patch package provides showstopper or test-stopper bug fixes to devtest for the 7.3(15)D software release. The patch provides the following:
The included updated executable files are copied into the /opt/TransPath/bin directory. A copy of the old versions of the files is saved in the /opt/TransPath/patch/CSCOgp082/bin directory.
The included updated binary, .dat, library, protocol, and script files are copied into the following directories depending upon the type of files being delivered:
During patch installation the following directories are created, depending on the type of files being patched, and the files that are being replaced are backed up in these directories and renamed with a .old extension:
Before installing this patch, you must shut down the Cisco MGC application, because the affected programs are part of the running system. In order to ensure that the MGC application has been shut down, execute the following command:
sudo /etc/init.d/transpath stop
Once the Cisco MGC application has been shut down, you should verify the currently installed software load to ensure that the patch being installed is compatible with and meant for the software currently installed. One way to do this is to run the following command:
sudo pkgparam CSCOgu000
Now that the MGC application has been shut down and the software load has been verified, you can begin to install the patch.
From the directory in which the package is currently residing, the user must type as root:
pkgadd -d CSCOgp082.pkg
Once done, you can follow the online instructions.
This section contains information about known issues and the corresponding workarounds in the Cisco Media Gateway Controller software Release 7.3(15)D.
|
Note For more information about Cisco IOS issues and workarounds, see the Cisco IOS release notes for your platform. |
For the Cisco SS7 Interconnect for Access Servers Solution, the active and standby system platforms must use matching hardware. For example, a Sun Netra 1120 cannot be used as a peer to a Sun E450. A Sun Netra 1120 can be used as a peer only to a Sun Netra 1120. A Sun E450 can be used only as a peer to a Sun E450.
The format of call detail record (CDR) files has changed in Release 7. CDR files are now generated in a binary format and are composed of call detail blocks (CDBs). CDBs contain statistics taken at various points in a call. CDR files are generated at regular intervals based on file size, call records, or a specified number of minutes.
|
Note You can configure the Cisco Media Gateway Controller software to generate CDRs in an ASCII format, if necessary. For more information, see the Cisco Media Gateway Controller Software Release 7 Installation and Configuration Guide. |
You can change the following settings by opening the dmprSink.dat file (located in /opt/TransPath/etc/dmprSink.dat) with a text editor, such as vi:
For information about CDBs and the fields in CDR files, see the Cisco Media Gateway Controller Software Release 7 Reference Guide and the Cisco Media Gateway Controller Software Release 7 Operations, Maintenance, and Troubleshooting Guide.
If you use the Sun Enterprise Volume Manager software to mirror your system and you set the system to a future date, you must reinstall the Sun Solaris operating system to reset the current date. If you change the setting from a future date back to the present date without reinstalling Sun Solaris, your system will not operate.
Circuit group operations on Non-Facility Associated Signaling (NFAS) spans are functional, but note the following behavior in a configuration where Circuit Identification Codes (CICs) 1 through 23 map to channels 1 through 23 on NAS span 0, and CIC 24 maps to channel 1 on NAS span 1:
When two NAS spans are disconnected, the SC receives two group service messages from the NAS:
When two NAS spans are reconnected simultaneously, two identical group service messages are received by the network management system. These messages indicate that the channels on span 0 and span 1 are in-service. The SC sends out the circuit group unblocked (CGU) message, starting from CIC 1 with a range of 23. This includes CIC 24, because the group service message indicates that channel 1 on span 1 is in-service. The SC sends a second CGU starting from CIC 25, because CIC 24 is noted in the first CGU.
The documentation accompanying the Cisco AS5200 Universal Access Server specifies memory requirements incorrectly. The correct requirements are 16 MB RAM (minimum) and 8 MB Flash memory (minimum).
Cisco AS5800 modem boards require at least 64 megabytes of memory per board. The part number for the correct modem board is MEM=200/NPE-64MB=.
The Cisco SLT is designed to be colocated with the Cisco SC2200, and interconnected via a local area IP network. Remote connectivity between the Cisco SLT and Cisco SC2200 is currently not supported.
If your configuration uses an 8-port connector as a serial connection for switchover, you must enable the read-write permissions for the connection. The permissions file is located at /devices/pci@1f,2000. With root access, use the chmod command to change the setting from crw---------- to crw-rw-rw-.
The expected throughput data rate on an SS7 link configured to run at 64 kbps is approximately 53 kpbs, allowing for link overhead for flags, bit stuffing, and sequence numbering. However, when you are using a 64-kpbs link on the IT Telekommunikations AG (ITK, now Digi International AG) cards, the uplink data rate is approximately 40 kbps and the downlink data rate is approximately 52 kbps.
MICA modems do not include a near-end echo canceller, so they do not function correctly on circuits with excessive near-end echo (greater than -60 dBm, for example -33 dBm.) Typical observed results are poor or no V.34 or PCM connects on long distance calls. With a short round-trip delay, the near-end and far-end echoes might overlap and the modem's far-end echo canceller might cancel both.
Workaround: Reengineer the line to the MICA modem to eliminate any near-end echo (for example, remove any near-end A/D conversion), or replace the MICA modem with a Microcom modem. Microcom modems (3.1.30 fw) function correctly and establish solid, if not exceptionally fast, V.34 connections in the range 19.2 to 24 kbps range. Also, setting a modem cap with s29 = 4 (for example, V.22bis and below) causes incoming calls to succeed.
While an MML command is processing, if you continue to enter input or press Enter repeatedly, you might cause MML to stop functioning.
When you reboot a trunking gateway, you might see several version messages exchanged between the SC and the media gateway (MGW) during synchronization. This behavior does not affect system performance or PRI initialization.
When there is a peak load on the system, do not query all CICs using the rtrv-tc:all or rtrv-cic command, and do not perform a dynamic reconfiguration of the system (for example, do not add or delete NASs).
Launching such a query under peak load might cause the system to enter an Overload Light Condition, leading to dropping of calls and possible system failure. (CSCdr35619)
When the standby SC host starts, its SNMP configuration is not synchronized with the active host by the process manager in the Telephony Controller software. As a result, any SNMP changes must be made to both the active and standby hosts. Also, for any changes made to the standby unit that require software reinstallation, verify that the sysName, sysContact, and sysLocation fields are the same on both the active and standby hosts.
Pressing Ctrl-C several times in rapid succession (for example, to stop an unintentionally displayed large response to an rtrv command), causes a core dump. (CSCdm75485)
Switchover for the Cisco SS7 Interconnect for Access Servers Solution is supported for a maximum of of 25,000 connected calls on the Netra 11xx platform. Switchover is not supported if there are 25,001 or more connected calls. (CSCdr24989)
This section describes issues and caveats for Cisco Media Gateway Controller software
Release 7.3(15)D.
Contact your Cisco representative to obtain current status on problem reports. You should also check the latest online version of this document on CCO for the most up-to-date information on caveats and workarounds.
For more information on Cisco IOS caveats, see the Cisco IOS release notes for your platform.
The list of issues and caveats is sorted by severity, then identifier, then component.
|
Note For sustainable runs, we recommend that all log priority processes be set to Error. |
| Identifier | Severity | Component | Description | Explanation/Workaround |
|---|---|---|---|---|
CSCdp98448 | 2 | Switchover | Cisco SS7 Interconnect for Access Servers Solution: Active should not switchover if the standby is not in standby state | If your SC is provisioned for redundancy, it is possible for the active system to switch over to the standby system that is not in a standby state. This would cause a clean switchover to be unsuccessful, and calls to be dropped. Workaround—Ensure that the standby system goes into standby state after any switchover and always check the state of the standby unit prior to performing a manual switchover of system controllers. |
CSCdr45009 | 2 | Engine | Cisco SS7 Interconnect for Access Servers Solution: With 50,000 calls in progress, core dump occurred between 6 and 36 hours | System instability might result when a near-maximum call load (50,000 calls) is maintained for an extended duration of 6 to 36 hours. |
CSCdr49278 | 2 | IOCM | Cisco SS7 Interconnect for Voice Gateways Solution: Cannot restore SS7 Destination after dynamic reconfiguration of ss7path | Updating the Customer Group ID (custgrpid) ss7path parameter results in all the nailed trunks (CICs) associated with the ss7path becoming unassociated with the ss7path. The nailed trunks can be reassociated with the ss7path if you restart the SC. Workaround—Provision the ss7path with the correct custgrpid value when bringing up the SC for the first time. |
CSCdr66401 | 2 | MGC | SC 2200 cannot be brought into a standby state in failover configuration, using the sw-over command. | When the prov-sync command is used, the slave attempts to synchronize all configurations stored in the /opt/TransPath/CONFIG_LIB directory with the master. An extremely large number of configurations cause the process to timeout and fail. Failure of the prov-sync command leaves the standby MGC without any service and the SC 2200 cannot be brought into a standby state in a failover configuration. Workaround—Limit the storage of configurations to 64 or less in the /opt/TransPath/etc/CONFIG_LIB directory on the the MGC. |
CSCdr31626 | 3 | iocm | Links went OOS CONF after adding c7iplnk with existing dpc | This only occurs if 1. There is an initial configuration at startup with SS7 components EXCEPT SS7 links. 2. The SS7 links are added dynamically. The workaround is to delete SS7 components such as SS7 pointcode, linkset, and routes and add them back with SS7 links. |
CSCdr31777 | 3 | Engine | After switchover, system marks CICs 1, 25, 49, and 73 as busy | This condition stops calls from being made on those CICs. |
CSCdr47558 | 3 | Provision | Cannot enter 0 as the first value of a point code | You cannot provision a "0" as the first value in a point code (for example, 0.1.1). Workaround—Use a placeholder value when you are provisioning the point code. After you commit or deploy your configuration, use a text editor such as vi to modify the dpc.dat file in the /opt/TransPath/etc directory and replace the placeholder value with the "0." |
CSCdr50855 CSCdp91898 | 3 | IOCM | The alarm "IOCM standby warm start" is displayed on the standby SC host | When you issue the MML command rtrv-alms on the SC in switchover mode on the standby system, the IOCM-01 process might be in a state of "Standby warm Start." This alarm is cosmetic and does not impact call processing. |
CSCdp25007 | 3 | Engine | The reset-cic command does not send out proper range in GRS after overlapping blocks | The incorrect range is sent in GRS. This occurs only when no circuit group blocking acknowledgement (CGBA) is returned in response to CGB and the reset-cic MML command is issued. This rarely occurs in the field. Workaround—Do not issue the reset-cic MML command when the SC is used for a CGBA. |
CSCdr21222 | 3 | Provision | Wrong SC host ID for standby host when using the rtrv-ne command | The SC does not display the correct platform ID when you are using the rtrv-ne MML command. This does not impact system performance. Use the machine name at the prompt to differentiate the two SC host servers. |
CSCdr28253 | 3 | pxelogger | The platform.log messages for engine are always debug level | Not available. |
CSCdr29116 | 3 | IOCM | Second c7iplnk could not come up after modifying Cisco SLT IP address | If the Cisco SLT is provisioned for two c7iplnks, the second link should come up after dynamic reconfiguration by changing the IP address of the Cisco SLT. Workaround—Delete and add the links again. Make sure you delete all of the links in the linkset before adding them again. |
CSCdr29901 | 3 | Engine | When using the rtrv-tc:all command, component is not found | The MML command rtrv-tc:all reports that the first NAS within your configuration is not configured because the component is not found. All other NASs within your configuration are reported properly. Workaround—To view the CIC status on the first NAS, enter the command: rtrv-tc:nasname where nasname is the name of your first NAS. |
CSCdr30076 | 3 | Provision | The prov-cpy command failed on the Cisco SS7 Interconnect for Access Servers Solution for the chkPtPort parameter in the XECfgParm.dat file | This is an intermittent error. There is no workaround at this time. |
CSCdr31576 | 3 | IOCM | Modifying one NAS IP caused both NAS links in same RLM group to have busy (INB) status | If the NAS IP address has been changed, do not try to modify the IP address on the SC using dynamic reconfiguration. It causes all PRI IP links for this NAS to go to install busy (INB) and not work. Workaround—Delete the NAS links and add them again. |
CSCdr31759 | 3 | procM | Processes on new standby can bounce | The standby processes can bounce if:
Workaround—After a software upgrade in a high-availability or continuous-service configuration, you must initially set pom.dataSync = false on the standby that has been upgraded with the latest software. Set dataSync = true on the standby if it has the same version of software as the active host. Other workarounds:
|
CSCdr32081 | 3 | procM | Circular error message generated by the process manager | You can experience an error message such as the following: ProcessManager (PID 19520) <Error> procMDataMgr: dependency between MMDB-01 and ENGG-01 appears circular and will be ignored This message does not affect call processing. |
CSCdr32218 CSCdr46714 | 3 | Planning | Implement ACL parameter in ISUP release message. | Prior to implementing ACL parameters in the Integrated Services Digital Network (ISDN) User Part (ISUP), the optional Automatic Congestion Level (ACL) parameter was not included in the (ISUP) release messages. The system does not indicate to the adjacent switches in the PSTN that it is experiencing congestion. If the SC is congested because too much traffic is being presented by adjacent signaling points, congestion might continue to occur. Workaround—No workaround is needed; when the ACL parameter is present, it provides improved handling of local signaling point congestion. See CSCdr46714. |
CSCdr33480 | 3 | IOCM | Dynamic reconfiguration: Destination went OOS LINS after restart | After dynamic reconfiguration, you can use the MML command set-dest to put a destination in-service. The link comes up first after the MML command, but the links do not come to IS after restart. Workaround—Break the set-dest command into two steps; for example: set-dest-state:nassrv1:OOS set-dest-state:nassrv1:IS |
CSCdr34494 | 3 | Provision | Standby host would not restart if peer session is in use | If the provisioning session is in use by MML or TCM on an active SC host, the standby does not restart. Workaround—Stop the provisioning session on the active SC host. |
CSCdr34549 | 3 | Engine | The "auditLoop start size" error message needs to be downgraded | The engine debugging message "auditLoop start size" is set incorrectly to Error level. This message is not an error-level message, and the condition does not impact performance in a significant way. |
CSCdr34562 | 3 | MML | Cisco SS7 Interconnect for Access Servers Solution: The rtrv-cic and rtrv-tc commands are missing one entry on the display | Workaround—See CSCdr29901. |
CSCdr34806 | 3 | Provision | Cisco SS7 Interconnect for Access Servers Solution: It takes about 20 seconds to delete a single CIC using the prov-dlt command | Deleting multiple CICs using the prov-dlt MML command might be time-consuming. Workaround—Edit the bearer channel (bearChan.dat) file and import it. |
CSCdr34858 | 3 | Engine | Cisco SS7 Interconnect for Voice Gateways Solution: SC not sending CGUB message after adding NAS gateway | SS7 GRS messages are not sent when CICs are put in-service for the first time. Workaround—Manually send GRS messages with the following MML command: reset-cic:point code: |
CSCdr36502 | 3 | Engine | Cisco SS7 Interconnect for Access Servers Solution: Dynamic delete caused extra entry missing in rtrv-dest:all | You might experience a reporting defect when using the prov-dlt MML command. The prov-dlt command removes some NASs that were not specified by the command from your display output. The unspecified NASs do not lose call-processing ability, and they can be displayed by means of the rtrv-dest:nasname MML command. |
CSCdr36820 | 3 | Provision | The prov-dply command still updated data files after the command failed | If there is a data synchronization problem between the active and standby SC hosts, the prov-dply command fails. However, the data files are still updated on the active but not the standby host. Workaround—Correct the connection problem between the active and standby SC hosts first, and then try prov-dply again to update the data files on the standby host. |
CSCdr40040 | 3 | Provision | Memory leak while adding number to database using the numan-add command | Workaround—Do not use the numan-add command to add numbers to the database. Use the file import MML command to a large number of phone numbers, or exit the MML session after adding some numbers and start the MML session again. |
CSCdr40862 | 3 | SNMP | SNMP MIB measurement counters are not replicated from Active to Standby nodes. | SNMP MIB measurements are valid only on the Active node. They are not replicated on the Standby node. |
CSCdr34858 | 3 | Engine | The SS7 GRS messages are not sent when CICs are put in service for the first time. The work around is to manually send GRS messages with the following mml command . | Workaround—Manually send the GRS messages with the MML command <CmdBold>reset-cic: |
Table 13 lists software problem reports (SPRs) that have been placed in the resolved state as a result of this software release. This list is sorted by severity, then identifier, then component.
| Identifier | Severity | Component | Description |
|---|---|---|---|
CSCdp53521 | 2 | Provision | Migration error migrating channel controllers (ITK) |
CSCdp67654 | 2 | IOCCC7 | AIN: Cannot send queries after a few thousand calls (Trillium error) |
CSCdr35891 | 2 | Engine | Cisco SS7 Interconnect for Access Servers Solution: Core dump from engine after recycling INET and NAS under 25,000 calls |
CSCdr45467 | 2 | Engine | If GRS is enabled, GRS is always sent during a switchover |
CSCdm87390 | 3 | SNMP | SNMP-AGT name inconsistent between operational MIB and trap |
CSCdp63670 | 3 | IOCM | Add hysteresis to state changes on NAS/SC interface |
CSCdp90319 | 3 | Protocol | Release mapping problem with customer-specific number 1 |
CSCdr11753 | 3 | Protocol | Cisco SS7 Interconnect for Voice Gateways Solution: Reselect outgoing NI2 B-channel to recover from glare |
CSCdr16771 | 3 | SNMP | SNMP IAM counter is reset after CollectTime interval expires |
CSCdr25400 | 3 | Provision | Cisco SS7 Interconnect for Access Servers Solution: Times Ten Data Manager error of DeadlockDetect failed 1 |
CSCdr29652 | 3 | Provision | Times Ten migration failed during software Release 4 to software Release 7 upgrade |
CSCdr43340 | 3 | Engine | Need to increase queue size of Group Service Message (GSM) |
You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.
Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).
Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.
Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online 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.
CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, 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 CCO to obtain additional personalized information and services. Registered users can order products, check on the status of an order and view benefits specific to their relationships with Cisco.
You can access CCO in the following ways:
You can e-mail questions about using CCO to cco-team@cisco.com.
The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.
To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.
To contact by e-mail, use one of the following:
Language | E-mail Address |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.
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
We appreciate you comments.
We appreciate and value your comments.
Posted: Mon Sep 11 08:45:30 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.