These release notes describe new features and caveats in system Software Release 1.2.3 for the Cisco MGX 8260 Media Gateway. Use these release notes in conjunction with the documentation listed in the "Related Documentation" section.

Fax signals can be distorted by some compression algorithms, such as G.729 and G.726. This problem is fixed (for T1 only) in Software Release 1.2.3. Now when the MGX 8260 detects a fax signal, it performs the following actions:

A security key is required to transfer files to the MGX 8260 using the UNIX tftp function. To determine the appropriate MGX 8260 security key code, use the lskey command from the command line interface.

Before performing an upgrade, make sure you have a current backup of the configuration database. Back up the database using the dbbkup command from the command line interface.

Caution All modules must be upgraded to the new release of software during the upgrade process. Performing a partial upgrade (e.g., some, but not all BSCs, or some, but not all NSCs) could cause unexpected behaviors in MGX 8260 system operation.

Note This installation procedure describes only a graceful upgrade process from the software release indicated in the "System Software Upgrade Paths" section to the current release.

The upgrade process for redundant SCCs is graceful. It does not interrupt established calls, but can interrupt calls in the process of being established. When you invoke the upgrade process, the MGX 8260 upgrades and restarts the standby SCC. You then have the option to commit or cancel the upgrade. When you commit the software, the MGX 8260 switches to the standby SCC and then upgrades the other SCC.

Note Enter a 9 even if card 10 is active. This parameter refers to logical card 9. The active SCC is always logical card 9 regardless of its physical slot location.

In redundant configurations, the upgd command will reset the standby SCC. Wait until the standby SCC reboots and its console session shows a standby state. The standby SCC will now be running the new release of boot flash and software images.

On redundant systems, the upgdcmit command will switch over the two SCCs. The previously standby SCC (with its newly upgraded database and software image) is placed into active state and the previously active SCC is reset and boots up to standby state.

Warning You must execute either the upgdcmit command in Step 4b. or the upgdcancel command in Step 4a. If you do not execute one of these commands, database corruption will occur.

Step 5 Ensure that the previously active SCC has completed booting and is in standby state.

The upgrade process for redundant BSCs is graceful. It does not interrupt established calls, but can interrupt calls in the process of being established. When you invoke the upgrade process, the MGX 8260 upgrades and restarts the standby BSC. You then have the option to commit or cancel the upgrade. When you commit the software, the MGX 8260 switches to the standby BSC and then upgrades the other BSC.

In redundant configurations, the upgd command will reset the secondary BSC matched with the primary BSC you specified in <logicalSlotNumber>. The secondary BSC will now be running the new release of boot flash and software images.

Step 4 Ensure that the standby BSC has finished booting and is in the standby state.

If you have redundant BSCs installed, the upgdcmit command will switch over the two BSCs. The previously secondary BSC (with its newly upgraded database and software image) becomes the primary BSC, and the previously primary BSC becomes the secondary BSC.

Warning You must execute either the upgdcmit command in Step 5b. or the upgdcancel command in Step 5a. If you do not execute one of these commands, database corruption will occur.

Step 6 Ensure that the previously primary BSC has finished booting and is in the standby state.

The upgrade process for redundant NSCs is graceful. It does not interrupt established calls, but can interrupt calls in the process of being established. When you invoke the process, the MGX 8260 upgrades and restarts the standby NSC. You then have the option to commit or cancel the upgrade. When you commit the software, the MGX 8260 switches to the standby NSC and then upgrades the other NSC.

NSC redundancy follows an N:1 design, with one NSC providing redundancy for all remaining NSCs. Because of the shared nature of the redundant module, all NSC upgrades for MGX 8260 media gateways equipped with NSC redundancy must be performed sequentially in a particular order.

If your MGX 8260 includes NSCs, perform the following steps to upgrade NSC flash and software images:

Step 1 Upgrade the boot flash software on each NSC using the following command. Issue the command for each NSC, replacing the <physicalSlotNumber> with the appropriate number for your configuration.

Run tftp only from a UNIX workstation. Do not run scripts on Microsoft Windows NT.

CSCdr89536

During connection, DS3 modification should not be allowed

During a connection, it is possible to modify DS3 parameters. This should not be possible, as it can affect calls in progress.

N/A

CSCds67779

Documentation change to have ECAN and VAD default to off

ECAN and VAD default have been changed to OFF but the user documentation does not include this change as of Release 1.2.

N/A

CSCds70201

update user guide for new cli stopdisk

As of Release 1.2.1, a new CLI command, stopdisk, is available to provide a method to shut off hard disk access. This command is not yet included in the Cisco MGX 8260 Command Line Interface (CLI) Guide.

N/A

CSCds71682

typo in lsevt help message

If incorrect parameters are passed to the lsevt CLI command, the usage message describes the date as dd/mm/yyyy instead of mm/dd/yyyy.

When entering the lsevt CLI command, structure your command in the format mm/dd/yyyy.

CSCds79125

CLI - adddlsp; dlsapTEIAssign does not default to 2

According to the Cisco MGX 8260 Command Line Interface Guide, the default value for the addlsp dlsapTEIAssign parameter is 2. This is incorrect. The current default is 1.

N/A

CSCds79162

CLI - adddlsp; min for dlsap203Timer should be 20

According to the Cisco MGX 8260 Command Line Interface Guide, the minimum value for the addlsp dlsap203Timer parameter is 20. This is incorrect. Currently, this value can be as low as 10.

N/A

CSCdt00032

Cells are being dropped when there are 2300 connections

Cells are being dropped slowly when there are 2300 connections with 4 ethernet lines active. dspatm2stat shows ErrCrc increasing slowing. Also, if the user continues operations with 2300 connections, the database will somehow become corrupted and will result in MGCP reporting 540 on CRCX and 400 on MDCX with the very first endpoint.

N/A

CSCdt00517

DTMF mid-signal duration not working properly

DTMF mid-signal duration is not working correctly. A DTMF signal may not be detected if the signal duration is borderline.

N/A

CSCdt04637

Datapath distorts original tone from HPT1 tester

When a 404-Hz tone is sent through the bearer path, and switched over to Slot 6, the 404-Hz tone is replaced with a much higher frequency tone.

This problem is caused by bad NSC hardware. Contact the Cisco TAC for assistance.

CSCdt10260

BIP-8 bit does not report cell crash error in CbtPrintStatus function

Upon occurrence of cell bus BIP-8 problems, the cell bus controller (Cubit) driver on the SCC and NSC does not accurately report the problem. Furthermore, upon this specific error condition, the SCC/NSC is not switched over. The occurrence of cell bus BIP-8 problem itself can be intermittent due to defective hardware. This problem is associated with the occurrence of BIP-8 cell bus problems.

N/A

CSCdt13497

MRPC errors in event log and 502 responses to MGCP.

Some MGCP events in the event log are not explained in the user documentation.

N/A

CSCdt21007

BSC Environmental Monitoring Module (EMM) Reports Failed

The environmental monitoring module (EMM) reports created before and after resetting the BSC cards are different.

After changing the secondary clocking source, the Clock Source Card Type field displayed by lsclksrc shows the secondary clocking source rather than the current clocking source.

N/A

CSCdt31117

Misleading information on T1 lines in the documentation.

The MGX 8260 documentation for DS1/T1 lines states that the received direction is always set to robbed bit. This should be changed to state that the default signal mode for DS1/T1 lines in the receive direction is None, rather than robbed bit signaling.

N/A

CSCdt40426

NMS-IP addr of format xxx.xxx.xxx.0 broadcast to that subnet

IP addresses of the format xxx.xxx.xxx.0 are broadcast to IP addresses in that subnet. Unless this is intended, such as the manager IP address in the community string, then it is possible that the recipient host is not the intended target of the message. This problem is found in the email server IP configuration and the trap manager IP address configuration. These features are not intended for broadcast.

N/A

CSCdt56759

Tones not measured correctly with gain less than -38dBm in E1

N/A

N/A

CSCdt60334

E1MC: PSQM score is too high

E1 VoIP voice calls may have reduced quality. Workaround is to not use high compression codecs for voice calls.

Do not use high compression codecs for voice calls.

CSCdt62577

Need CLI to shut off RSIP generation

When the call agent does not generate traffic, the MGX 8260 eventually brings down the MGCP link and starts sending RSIPs.

None

CSCdt72583

DS1 Bert failure on repetitive patterns

During a Bert for DS1 on NSC, with repetitive patterns.
1) With error insertion, COMET sometimes will report error rate mismatch;
2) Without error insertion, COMET sometimes indicates that error bits are detected;
These cases are very likely to happen on patterns 3in24 and 1in16.

N/A

CSCdt75173

System Name is lost after resetnd or upgrade

N/A

N/A

CSCdt77965

clrndcnf may potentially lose trap mgr info if SCC switches over

When the node configuration is cleared, the trap Register RAM information is backed up in a temporary file. When the node rebuilds, this backup file is restored so that traps can be generated when the node is rebuilt. On normal operation, when the node configuration is cleared, when the Active card is reset, the same active card is assumed to still be the active one. However, in the SCC mastership arbitration, if the once ACTIVE card gives up mastership and the standby SCC takes over before the trap manager backup is restored, all trap manager information is gone. The Active SCC does not update the standby SCC trap register RAM information, which is the source of information for backing up the trap information.

Update the standby SCC's trap register RAM information. When clrndcnf is invoked, the standby SCC should also invoke the SnmpDbSave function so it can save its RAM information. If the SCC comes up as standby, it should not restore the backup. It should wait for updates from the Active card. If there is an ungraceful switchover and the standby SCC becomes active, it will restore the backup trap manager.

CSCdt83222

SCC switch over when adding inactive FastEthernet lines

When adding 4 new Fast Ethernet lines to the primary SCC, the SCC switches over. This should not occur when the Fast Ethernet lines on the secondary SCC are also down. In addition, when the two Fast Ethernet lines on the primary and secondary become active, the SCC also switches over.

N/A

CSCdt84087

TCG reports AAL1 add error

After a few switchovers, a few calls start failing due to Add Channel failure from RMG (possibly due to TCG failure).

N/A

CSCdt84298

Call Agent times out while waiting for COT notify from the MGX 8260

The call agent times out while waiting for a notification of continuity test result from the MGX 8260 when transponder continuity testing is requested on a endpoint before the terminating call is setup.

N/A

CSCdt87073

BSC s/o causes one of the ds3ln to remain in blinking yellow state

While performing graceful shutdown of the BSC, when a call is active, one of the DS3 lines goes to a permanent blinking yellow state.

N/A

CSCdt89367

Cannot add an ethernet line when OSPF and loopback ip are enabled

N/A

N/A

CSCdt89970

Standby NSC cannot be upgraded

When using the upgrade functions (upgd, upgdcmit) NSC modules in standby state but not set up as part of a redundant pair cannot be upgraded. Further, the nsc.fw file is not updated when the last NSC module is upgraded which causes any new NSC modules that are introduced into the system or previously upgraded NSC modules which are clear configured (clrcdcnf) to boot up on the pre-upgrade software version.

N/A

CSCdt90496

A unique/special tftp key should be added for sensitive files

Currently it is possible to tftp the pswd file out of the MGX 8260. This is a high security risk because any user can currently do this. A unique/secret tftp key (separate from that for normal files) needs to be added and applied against all sensitive/security related files on the system.

N/A

CSCdt91753

System Date accepting invalid values

The MGX 8260 allows invalid settings for system date and time. For example, February 31 is allowed.

N/A

CSCdt94852

FAX call failed sometimes on data transmission stage

Fax calls sometimes fail during data transmission stage. This problem is different from what has been addressed in resolved issue CSCdt59149 where the failure happens during negotiation stage.

N/A

CSCdt96988

COT transponder tests on each channel of BSC DS1 times out.

COT transponder tests may fail when the sctTimeout value in the COT tests is set to a small number, e.g. 100 ms.

N/A

CSCdu00119

D channels dropped during BSC switchover

N/A

N/A

CSCdu02910

Multiple NTFY sent by the MGX 8260

The NSC reports multiple instances of modem tone upon receipt of each MDCX message. This occurs when modemup-speed is set to G.711. This processing of the MDCX message by TCG will cause multiple instances of modem tone to be detected. As a result, MPC will then report multiple MT NTFY messages to the call agent.

N/A

CSCdu03079

Unrequested NFTY G/vbd sent by 8260

This problem occurs when the
MGX 8260 is configured to send fax/modem NTFY messages.When a modem call is made with FaxModemDetect enabled, 2 NTFY messages are sent from the MGX 8260, one with modem tone detection and a second with voice band detection.

Customers using release 1.2.2 or prior software should manually turn off the fax/modem reporting via the CLI command 'chmpc'. Customers using release 1.2.3 will have the fax/modem reporting configuration set to off as default.

CSCdu03115

All endpoints reset due to 1 unack message

Using G.726 32k codec selection, when a modem call with FaxModemDetect enabled, 2 MGCP NTFY messages are sent from the MGX 8260. One message is sent for modem tone detection and a second with voice band data detection. Eventually the repetition of this event results in all configured endpoints on the MGX 8260 to reset.

N/A

CSCdu04802

clrndinf dosent clear inband ip address

Clearing node config should clear inband ip, so the value would be at default again. This does not occur. When the clrndinf command is used, the inband ip address is not reset to the default.

N/A

CSCdu04944

updatefls CLI command should not require path for flashfile

The CLI updatefls command returns an error if the flashfile path is not also included in the command syntax.

N/A

CSCdu16859

Event log entry needed for system clock events.

An event log entry should be made whenever there is a status change to either the primary or secondary clock. Currently clock failures/recoveries are not recorded in the event log.

N/A

CSCdu18974

SCC resetcd boots all cards and fails them

When you reset the SCC card with a redundant SCC card, all cards in the chassis reboot and later fail. You then need to use the resetnd command to return to the normal mode.

N/A

CSCdu22897

DTMFmid high pitch tones after switchover

When switchover is performed, sometimes tones are discontinued and a high pitch tone is heard while the call connection is still active. If tones are resent, the high pitch tones stop, and the correct tones are received.

N/A

CSCdu23980

NSC Standby responds badly to swcd command

When the redundant NSC module is in active state and the swcd command is issued to return this module to Standby state (and reactive the primary NSC), the standby card boots to Failed state.

N/A

CSCdu24995

lsreds command inconsistent when rdndnt NSC in slot 16

The MGX 8260 does not display redundancy correctly (via lsreds command) when the redundant card is in the upper slots (11 - 16) and there is BSC redundancy as well as NSC redundancy.

N/A

CSCdu26624

Received functions of lsmacsapstat command do not work.

The received fields of the lsmacsapstat command do not display any received statistics. These fields include Received Frames, Received Bytes, and Received Queued.

N/A

CSCdu26823

Dchan display reports Arbitration scheme as passive when active set

The Macsap profile has a parameter called "Link Arbitration Setup Scheme". This parameter is set to either "active" or "passive". When set to "active", it should be reported as active when viewing the details of a Dchan that is using the specific Macsap profile. Instead, the Dchan detail reports the arbitration scheme as passive.

N/A

CSCdu30720

AddChan and/or DelChan take 2 secs.

This problem is for PRI calls only. Some calls are taking up to 2 seconds for call setup request. The normal setup time is 0.2 seconds. This problem only occurs during high PRI call rates, such as 30 calls per second.

None

CSCdu36092

Many performance alarm traps in event log but there is no alarm

During normal traffic load tests, many performance alarm traps fill up the event log, but there is no alarm.

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.

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).

If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.

You can e-mail your comments to bug-doc@cisco.com.

To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:

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.

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:

All other trademarks mentioned in this document or Web site 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. (0105R)