cc/td/doc/product/access/multicon
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Release Notes for Cisco MC3810 for
Cisco IOS Release 11.3(1)MA

Release Notes for Cisco MC3810 for
Cisco IOS Release 11.3(1)MA

December 14, 1998

These release notes describe the features and caveats for Cisco IOS Release 11.3(1)MA, up to and including Release 11.3(1)MA7. This special release applies only to the Cisco MC3810 multiservice access concentrator.

Use these release notes in conjunction with the Release Notes for Cisco IOS Release 11.3 located on Cisco Connection Online (CCO) and the Documentation CD-ROM. For more information, see the "Cisco Connection Online" section and the "Documentation CD-ROM" section.

Note Release 11.3(1)MA7 is the final maintenance release for this software version.

Contents

These release notes discuss the following topics:

System Requirements

This section describes the system requirements for Cisco IOS Release 11.3 (1) MA and includes the following sections:

Memory Requirements

Table 1 lists the software product numbers and minimum memory requirements for the Cisco MC3810 multiservice concentrator using Cisco IOS Release 11.3(1)MA.


Table 1:
Feature Set Image Name1 Required Flash Memory Required DRAM

Cisco MC3810 IOS IP/IPX/AT/IBM/VOICE

SF381BSV-XX.X.X

SW381BSV-XX.X.X=

4 MB

32 MB

Cisco MC3810 IOS IP/IPX/IBM/ATM

SF381MH-XX.X.X

SW381MH-XX.X.X=

4 MB

32 MB

Cisco MC3810 IOS IP/IPX/AT/IBM/ATM/VOICE

SF381BSHV-XX.X.X

SW381BSHV-XX.X.X=

4 MB

32 MB

1Substitute the release number for XX.X.X in the product number. For example, SF381M-XX.X.X is equivalent to SF381M-11.3.1M.
Memory Requirements for Cisco MC3810

Hardware Supported

Cisco IOS Release 11.3(1)MA supports the following platform:

Determining Your Cisco IOS Software Release

To determine the version of Cisco IOS software currently running on your Cisco MC3810, log in to the concentrator and enter the show version EXEC command. The following is sample output from the show version command. The version number is indicated on the second line as shown below.

Cisco Internetwork Operating System Software
IOS (tm) MC3810 Software (MC3810-JS-L), Version 11.3(1), RELEASE SOFTWARE

Additional command output lines include more information such as processor revision numbers, memory amounts, hardware IDs, and partition information.

Feature Set Table

To determine what features are available with each feature set, see Table 2. The table summarizes what features you can use when running a specific feature set on the Cisco MC3810 for Cisco IOS Release 11.3(1)MA6. The feature set table uses the following terms to identify features:


Table 2: Cisco IOS Feature Set for the Cisco MC3810
Feature Sets
Features IP/IPX/ AT/IBM/ Voice 11.3 1M IP/IPX/ IBM/ATM 11.3 1M IP/IPX/ AT/IBM/ ATM/Voice 11.3 1M
ATM Access

UNI 3.11

No

Yes

Yes

Traffic Shaping

No

Yes

Yes

rtVBR, nrtVBR, CBR, uBR

No

Yes

Yes

Structured CES2

No

Yes

Yes

RFC 1483

No

Yes

Yes

IBM Support

APPN

No

No

No

APPN High-Performance Routing

No

No

No

APPN MIB Enhancements

No

No

No

APPN over Ethernet LAN Emulation

No

No

No

APPN Scalability Enhancements

No

No

No

BAN for SNA Frame Relay Support

Yes

Yes

Yes

Bisync

No

No

No

Caching and Filtering

Yes

Yes

Yes

DLSw+

Yes

Yes

Yes

DLSw (RFC 1795)

Yes

Yes

Yes

DLSw Version 2 (RFC 1266)

Yes

Yes

Yes

Downstream PU Concentration (DSPU)

Yes

Yes

Yes

Frame Relay SNA Support (RFC 1490)

Yes

Yes

Yes

NCIA

No

No

No

NetView Native Service Point

Yes

Yes

Yes

QLLC

No

No

No

Polled Async (ADT)

No

No

No

Response Time Reporter

No

No

No

SDLC Integration

Yes

Yes

Yes

SDLC Transport (STUN)

Yes

Yes

Yes

SDLC-to-LAN Conversion (SDLLC)

Yes

Yes

Yes

SNA and NetBIOS WAN Optimization

No

No

No

SRB/RSRB

No

No

No

SRT

No

No

No

SRTLB

Yes

Yes

Yes

TG/COS

No

No

No

TN3270

No

No

No

TN3270 LU Nailing

No

No

No

TN3270 Server Enhancements

No

No

No

Integrated Voice

Analog Signaling

Yes

No

Yes

Multiflex Trunk

Yes

Yes

Yes

E1 CAS Signaling3

Yes

No

Yes

T1 CAS Signaling

Yes

No

Yes

Voice Activity Detection

Yes

No

Yes

Voice over ATM

No

No

Yes

Voice over Frame Relay

Yes

No

Yes

Voice over HDLC

Yes

No

Yes

Local Dialing

Yes

No

Yes

Remote Dialing

Yes

No

Yes

PLAR

Yes

No

Yes

Pass-Through Voice

Yes

No

Yes

Off-net Dialing

Yes

No

Yes

On-net/Off-net Call Rerouting

Yes

No

Yes

Multiple Ring Tones

Yes

No

Yes

Gain Control

Yes

No

Yes

IP Routing

BGP

Yes

Yes

Yes

BGP4

Yes

Yes

Yes

EGP

Yes

Yes

Yes

Enhanced IGRP

Yes

Yes

Yes

Enhanced IGRP Optimizations

Yes

Yes

Yes

ES-IS

No

No

No

IGRP

Yes

Yes

Yes

IS-IS

No

No

No

Named IP Access Control List

Yes

Yes

Yes

Network Address Translation (NAT)

No

No

No

NHRP

Yes

Yes

Yes

OSPF

Yes

Yes

Yes

OSPF Not-So-
Stubby-Areas (NSSA)

Yes

Yes

Yes

OSPF On-Demand Circuit (RFC 1793)

Yes

Yes

Yes

PIM

Yes

Yes

Yes

Policy-Based Routing

Yes

Yes

Yes

RIP

Yes

Yes

Yes

RIP Version 2

Yes

Yes

Yes

LAN Support

Apollo Domain

No

No

No

AppleTalk Phase 2

Yes

No

Yes

Banyan VINES

No

No

No

Concurrent Routing and Bridging

Yes

Yes

Yes

DECnet IV

No

No

No

DECnet V

No

No

No

GRE

Yes

Yes

Yes

Integrated Routing and Bridging (IRB)

Yes

Yes

Yes

IP

Yes

Yes

Yes

LAN Extension Host

No

No

No

Multiring

No

No

No

Novell IPX

Yes

Yes

Yes

OSI

No

No

No

Source-Route Bridging

No

No

No

Transparent and Translational Bridging

Yes

Yes

Yes

VLANs (ISL & IEEE 802.10)

No

No

No

XNS

No

No

No

Management

AutoInstall

Yes

Yes

Yes

Automatic Modem Configuration

Yes

Yes

Yes

HTTP Server

Yes

Yes

Yes

Cisco IOS File System4

Yes

Yes

Yes

RMON Events and Alarms

Yes

Yes

Yes

RMON Full

No

No

No

SNMP

Yes

Yes

Yes

Telnet

Yes

Yes

Yes

Multimedia and Quality of Service

Generic Traffic Shaping

Yes

Yes

Yes

Random Early Detection (RED)

Yes

Yes

Yes

RSVP

Yes

Yes

Yes

Other Routing

AURP

Yes

No

Yes

IPX RIP

Yes

Yes

Yes

NLSP

Yes

Yes

Yes

RTMP

Yes

No

Yes

SMRP

Yes

No

Yes

SRTP

No

No

No

Protocol Translation

LAT

No

No

No

PPP

No

No

No

Rlogin

No

No

No

Telnet

No

No

No

TN3270

No

No

No

X.25

No

No

No

Remote Node

ARAP 1.0/2.0

Yes

No

Yes

Asynchronous Master Interfaces

No

No

No

ATCP

No

No

No

CPPP

No

No

No

CSLIP

No

No

No

DHCP

No

No

No

IP Pooling

No

No

No

IPX and ARAP on Virtual Async Interfaces

No

No

No

IPXCP

No

No

No

MacIP

No

No

No

NASI

No

No

No

NetBEUI over PPP

No

No

No

PPP

Yes

Yes

Yes

SLIP

Yes

Yes

Yes

Security

Access Lists

Yes

Yes

Yes

Access Security

Yes

Yes

Yes

Extended Access Lists

Yes

Yes

Yes

Kerberized Login

No

No

No

Kerberos V Client Support

No

No

No

Lock and Key

No

No

No

Mac Security for Hubs

Yes

Yes

Yes

Md5 Routing Authentication

No

No

No

Network Layer Encryption (40-bit or Export Controlled 56-bit DES)

No

No

No

RADIUS

No

No

No

Router Authentication

No

No

No

TACACS+

Yes

Yes

Yes

Terminal Services

LAT

No

No

No

Rlogin

No

No

No

Telnet

No

No

No

TN3270

No

No

No

X.25 PAD

No

No

No

XRemote

No

No

No

WAN Optimization

Bandwidth-on-demand

No

No

No

Custom and Priority Queuing

Yes

Yes

Yes

Dial Backup

No

No

No

Dial-on-demand

No

No

No

Header, Link and Payload Compression

Yes

Yes

Yes

Snapshot Routing

Yes

Yes

Yes

Weighted Fair Queuing

Yes

Yes

Yes

WAN Services

ATM LAN Emulation: Decnet Routing and Banyan Vines Support

No

No

No

ATM LAN Emulation: (HSRP and SSRP)

No

No

No

ATM: Rate Queues for SVC per Subinterface

No

No

No

ATM: UNI 3.1 Signaling For ATM

No

No

No

Combinet Packet Protocol (CPP)

No

No

No

Dialer Profiles

No

No

No

Frame Relay Compression (Frf.9)

Yes

Yes

Yes

Frame Relay SVCs Support (DTE)

No

No

No

Frame Relay Traffic Shaping

Yes

Yes

Yes

Frame Relay Switching

Yes

Yes

Yes

Frame Relay Uni

Yes

Yes

Yes

Frame Relay-ATM Interworking

No

Yes

Yes

Half Bridge/Half Router for CPP and PPP

No

No

No

HDLC

Yes

Yes

Yes

IPXWAN 2.0

Yes

Yes

Yes

ISDN

No

No

No

ISDN Advice of Charge

No

No

No

ISDN Caller ID Callback

No

No

No

ISDN NFAS

No

No

No

Leased-Line ISDN at 128 kbps

No

No

No

Multichassis Multilink PPP (MMP)

No

No

No

PPP

Yes

Yes

Yes

SMDS

No

No

No

Switched 56

No

No

No

Virtual Private Dial-up Network (VPDN)

No

No

No

X.25

No

No

No

X.25 Enhancements

No

No

No

X.25 on ISDN

No

No

No

X.25 Switching between PVCs and SVCs

No

No

No

1ATM PVCs only. SVCs are not supported.
2Voice signaling on CES is not available.
3Includes T1 CAS protocols, plus UK Standard CAS (Mercury protocol) and CEPT standard E&M.
4Cisco IOS File System is offered in Release 11.3 (1)MA.

Cisco IOS File System

To make file management easier, the Cisco MC3810 provides a complete file system for software images, message files, and reports. The standard Flash memory size is 4 MB, and an 8-MB option is available. The 8-MB version can hold 2 code images simultaneously for fail-safe upgrades.

Network Management

Management and configuration of the Cisco MC3810 should be familiar to the Cisco IOS user and compatible with existing management systems. As such, it provides a superset of the Cisco command-line interface (CLI). The Cisco MC3810 can be managed by standard Cisco management platforms and facilities. The Cisco MC3810 can be managed by CiscoView in addition to the native remote login facilities provided by Telnet and rlogin. Three types of configuration interfaces are provided:

The HTTP-based interface allows configuration from any Web browser such as Netscape Navigator or Microsoft Internet Explorer. The SNMP MIB allows management of the Cisco MC3810 from SNMP managers (for example, HP OpenView).

New and Changed Information

The following sections list the new features supported by the Cisco MC3810 in Cisco IOS Release 11.3(1)MA.

New Features in Cisco IOS Release 11.3(1)MA7

There are no new features in Cisco IOS Release 11.3(1)MA7. However, one enhancement has been added in this release.

Enhancement Added in Release 11.3(1)MA7

The following enhancement has been added in Cisco IOS Release 11.3(1)MA7.

Fancy Queuing on Frame Relay or Cisco HDLC

In previous releases, when the voice-encap option was configured on Frame Relay or Cisco HDLC, all fancy queuing (such as weighted fair queuing, custom queuing, and priority queuing) on the interface was disabled, and queuing was handled on a first-come first-served (FCFS) basis. In this release, new enhancements have been made to support fancy queuing on Frame Relay and Cisco HDLC.

A new interface command, frag-pre-queuing, has been added that allows you to set the queuing to be performed after the data segmentation. The command is available for Frame Relay interfaces only. The syntax for this new command is the following:
frag-pre-queuing
no frag-pre-queuing
By default, this command is enabled, which allows only FCFS queuing at the interface level. If you enter no frag-pre-queuing, can configure weighted fair queuing, custom queuing, or priority queuing at the interface level. Note that if you enter no frag-pre-queuing, you still must explicitly configure the fancy queuing type on the interface.
For HDLC encapsulation, the queuing now takes place after segmentation when the voice-encap option is entered. Weighted fair queuing, custom queuing, and priority queuing are now supported on an interface configured for Cisco HDLC.

New Features in Cisco IOS Release 11.3(1)MA6

There are no new features in Cisco IOS Release 11.3(1)MA6.

New Features in Cisco IOS Release 11.3(1)MA5a

There are no new features in Cisco IOS Release 11.3(1)MA5a. This special release version fixes the following caveat:

When the voice port on the AVM is configured for a-law companding and saved into NVRAM, and then the Cisco MC3810 is rebooted, the voice-port driver is not set to a-law companding. If the compand-type command is then reset to a-law, the change is then reflected on the voice-port driver. This caveat has been fixed in this release.

New Features in Cisco IOS Release 11.3(1)MA5

This section describes the new feature and enhancements in Cisco IOS Release 11.3(1) MA5.

Facility Data Link Support Feature

Cisco IOS Release 11.3(1)MA5 supports Facility Data Link for the T1 controller. Using the new fdl controller command, you can configure the T1 controller to support either the ANSI T1.403 standard or the AT&T TR54016 standard, or both. The fdl command applies only if the framing format for the controller is set to Extended SuperFrame (ESF). The syntax for the fdl command is as follows:
fdl {ansi | att | both}

Enhancements Added in Release 11.3(1)MA5

The following enhancements have been added in Cisco IOS Release 11.3(1)MA5.

Off-Premises Extension Support for PLAR

Cisco IOS Release 11.3(1)MA5 supports an enhanced PLAR feature for off-premises extension (OPX). Using this feature, the local voice port provides a local response before the remote voice port receives an answer. A new voice-port configuration command, connection plar-opx-ringrelay, has been added to support this feature. The following is the syntax for this command:

connection plar-opx-ringrelay string
Configurable Guard Time for FXO Voice Ports

In previous releases, an FXO port that had been released required a minimum of three seconds after release before it could be seized again. In this case, when the FXS port attempted to reseize the same FXO port in a very short time, silence was returned to the caller followed by a tone. This guard time was previously restricted to 600 milliseconds. In Cisco IOS Release 11.3(1)MA5, the timing guard-out voice-port command has been added to configure the guard-out duration. The following is the syntax for the timing guard-out command:

timing guard-out value

where the value ranges from 300-3000 milliseconds. The default is 2000 milliseconds.

G.726 32K ADPCM and G.711 PCM Support

The codec voice-port command has been enhanced to add support for G.725 32K ADPCM and G.711 PCM CODECs. The following is the new syntax for the codec command:

codec {729r8 | g729ar8 | g726r32 | g711alaw | g711ulaw}

The default value is g.729ar8.

PLAR Confirmation Tone Disable

In previous releases, when a voice port was configured for PLAR to draw dial tone from a remote PBX, a caller would hear a two-beep confirmation tone when picking up the handset and before hearing the dial tone. In Cisco IOS Release 11.3(1)MA5, this confirmation tone can now be disabled using the new voice confirmation-tone-disable voice-port configuration command. This command has no options or keywords.

New Features in Cisco IOS Release 11.3(1)MA4

This section describes the new features and enhancements in Cisco IOS Release 11.3(1) MA4.

AppleTalk Support

Cisco IOS Release 11.3(1)MA4 supports standard AppleTalk functionality on the Cisco MC3810. For information on AppleTalk configuration, refer to the Cisco IOS Release 11.3 manual Network Protocols Configuration Guide, Part 2, available on CCO at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios113ed/113ed_cr/np2_c/index.htm

For information on AppleTalk commands, refer to the Network Protocols Command Reference, Part 2, available on CCO at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios113ed/113ed_cr/np2_r/index.htm

Enhancements Added in Release 11.3(1)MA4

The following enhancements have been added in Cisco IOS Release 11.3(1)MA4:

Serial Port Clear-Channel Encapsulation Enhancement

You can now enable the UIO (serial) interface to support clear-channel encapsulation in DTE mode. The correct modem signals are now supported. When the interface is in shutdown state, the modem signals are disabled. When the interface is active and a cross-connect is set up, the modem control signals are enabled when controller T1/E1 0 is up, and disabled when controller T1/E1 0 is down.

Dial Peer Hunt Group Enhancement

In previous releases, when there was a hunt for a dial peer and there were several equal-length matches, the preference order was inconsistent in deciding which dial peer to choose, depending on where the call had originated. In Cisco IOS Release 11.3(1)MA4, this has been fixed so that dial peers are hunted and matched in the following order:

    1. The highest preference, as set with the preference dial-peer command.

    2. The dial peer with the longest match. For example, if one dial peer has a destination pattern of 338234, and a second dial peer has a destination pattern of 338...., the first dial peer will be chosen because the destination pattern has a longer match than the second dial peer.

    3. All POTS dial peers are searched before dial peers across the WAN (Voice over Frame Relay or Voice over ATM dial peers).

    4. Dial peers selected in the order in which they were defined.

Cisco MIB Support Enhancement

Support for OLD-CISCO-FLASH MIB and CISCO-FLASH-MIB has been added.

New Features in Cisco IOS Release 11.3(1)MA3

This section describes the new features released in Cisco IOS Release 11.3(1)MA3.

Pulse Dialing

As of Release 11.3(1)MA3, the Cisco MC3810 supports pulse dialing with the following commands: dial-type pulse, timing pulse, and timing pulse-interdigit. These commands are documented in the Cisco MC3810 Multiservice Access Concentrator Software Configuration Guide and the Cisco MC3810 Multiservice Concentrator Command Reference Guide.

Multichassis Hunt Groups

The hunt group support has been enhanced to route an incoming call to another configured outgoing trunk if it fails to terminate locally because all ports are busy, or if the intended outgoing trunk is down or congested. Using multichassis hunt groups, the Cisco MC3810 can hunt between both local dial peers and network dial peers on the terminating or tandem Cisco MC3810. The system hunts among local dial peers first, and then hunts to the network dial peers. Preference order defined with the preference command applies only within the peer group, so all local peers will be searched first, even if a network peer exists with a higher preference.

A/B/C/D Bit Conditioning

Release 11.3(1)MA3 supports three new voice-port commands: condition, ignore, and define. These commands are applicable to the digital voice module (DVM) only. The commands allow the Cisco MC3810 to recognize different "ABCD bit" combinations as on-hook and off-hook signals from the PABX. For example, when connected to the NEC PABX, the A and B bits are reversed, or "inverted," relative to most North American digital FXS interfaces. The condition command can also be used as a troubleshooting aid or installation aid to turn down circuits. Cisco IOS Release 11.3(1)MA3 supports configuration of the ABCD signaling bits as follows:

condition {tx-a-bit | tx-b-bit | tx-c-bit | tx-d-bit} {rx-a-bit | rx-b-bit | rx-c-bit | rx-d-bit}
{on | off | invert}
ignore {rx-a-bit | rx-b-bit | rx-c-bit | rx-d-bit}
define {Tx-bits | Rx-bits} {seize | idle} {0000 | 0001 | 0010 | 0011 | 0100 | 0101 |
0110 | 0111 | 1000 | 1001 | 1010 | 1011 | 1100 | 1101 | 1110 | 1111}

Be careful when using the show commands in conjunction with these new commands. The show voice port command reports at the protocol level while the show controller command reports at the driver level. The driver does not know about any bit manipulation using the condition, ignore, and define commands.

Call Routing Enhancements

The following new call routing enhancements have been added to Cisco IOS Release 11.3(1) MA3:

Digit Forwarding

In previous releases, the Cisco MC3810 that terminated a voice call would only forward digits that exactly matched the destination pattern or matched the wildcard matched digits. For example, if you set the destination pattern to 3.... and you dialed 31234, the digits "1234" would be forwarded.

Beginning with Cisco IOS Release 11.3(1)MA3, you can now control how many digits are forwarded to the telephony interface. A new dial-peer configuration command, forward-digits, is supported in Cisco IOS Release 11.3(1) MA3:

forward-digits [num-digit | all]
where num-digit ranges from 0 to 32, and indicates how many right-justified digits to forward. If this command is not used, then only the digits that exceed the pattern are forwarded.
Voice Default Route

In previous releases, you could not set a voice default route using all wildcards. For example, when setting the destination pattern of a dial peer, you had to configure the voice default route with at least one leading digit, such as 8...., in the string. In the Cisco IOS 11.3(1)MA3 release, you can now set a default voice route using all wildcards with the destination pattern command. For example, if you enter the following command:

destination-pattern ....

the voice default route will be any four-digit string. In this case, when a call dials four digits, and the system does not find an exact match, the system will send the voice call to the first session target mapped to a four-digit string.

The following restrictions apply to a voice default route:

Japan and Australia Call Progress Tones

The following support for Japan and Australia Call Progress Tones has been added:

Dial-Out Delay

The default dial-out delay of E&M immediate signal type has been changed to 300 milliseconds and is country independent. The following syntax allows the user to change the value of the dialout delay:

timing dialout-delay delay

where delay is from 100 to 5000 milliseconds. The default delay is 300 milliseconds.

E&M Immediate-Start and Delay-Start

E&M MELCAS (CEPT) immediate-start and delay-start are now supported.

Debug Voice Command Enhancements

The debug voice all command shows call progress events as they occur. Because a lot of debug information is generated, it might be difficult to explicitly turn off the debug. As a result, the following additions and changes have been made:

debug voice all [voiceport] [duration]
where duration ranges from 5 to 64000 seconds. The default duration is 20 seconds if no voiceport is entered, or 600 seconds if a voiceport is entered.

Important Notes

This section describes important notes regarding use of the Cisco MC3810 to connect with the Public Switched Telephone Network (PSTN).

Connections to a PSTN

Be careful when connecting switched voice ports on the Cisco MC3810 directly to the PSTN because improper configurations can expose the corporate network to telephone fraud.

Switched Access from the PSTN

The Cisco MC3810 has the capability to connect a user from the PSTN directly to the corporate wide-area telephone network. As a telephone switch, the Cisco MC3810 can be configured to switch the user to any location in that network, even remote locations that are connected again to another PSTN. However, the Cisco MC3810 does not provide any mechanism to restrict where users can call after they are connected. Without proper network design, this condition could result in the unauthorized use of the corporate network for making calls at the corporation's expense. To prevent this from occurring, Cisco does not recommend connecting a switched voice interface on the Cisco MC3810 directly to the PSTN. Instead, it should be connected to a PBX that implements a security scheme that prevents unauthorized use.

Non-Switched Calls

The opportunity for illicit use does not exist for non-switched call types such as pass-through connections. Pass-through calls create a path to only a single location specified by the network administrator. For example, a pass-through connection might be used to pass a trunk from a PBX to the PSTN. In this case, the trunk on the PBX will always pass straight through the Cisco MC3810 to the PSTN. As a result, the necessary security is provided by the PBX.

Caveats

This section contains open and resolved caveats for Cisco IOS Release 11.3(1)MA only.

If you have an account with CCO, you can use Bug Navigator II to find caveats of any severity for any release. Bug Navigator II is at http://www.cisco.com/support/bugtools, or from CCO, select Software & Support: Technical Support: Bug Toolkit II.

Caveats for Release 11.3(1)MA7

This section describes possibly unexpected behavior by Cisco IOS Release 11.3(1)MA7. This section describes only severity 1 and 2 caveats. Caveats are organized into the following categories:

ATM

The debug atm packet command does not display the voice traffic.
The value for the Peer maxvcibits entry may appear incorrect in the display from a show atm ilmi-stats command if the interface is shutdown then set to no shutdown.

Basic System Services

After entering a fsck flash: command, it can take up to one minute before the system displays any information on the results of the command.
After entering a copy flash: source-filename flash: destination-filename command, it can take up to 3 minutes before the system displays any information on the results of the command.
This is normal operation and should not be interpreted as a failure of the system requiring a restart or any other action.
Serial ports on the Cisco MC3810 when configured for SDLC may report input abort errors when the clock rate is greater than 38400. This does not effect performance as the errors are not typically input aborts. This is cosmetic and does not result in retransmitted frames. There is no performance impact as a result of this situation.

Frame Relay

In a configuration for Frame Relay operation with traffic-shaping enabled, the display from a show frame pvc command indicates that "Shaping adapts to BECN" however, this is not supported in the first release of the Cisco MC3810.
When an fr-atm interworking interface is deleted, a show frame-relay lmi or pvc command for that interface will display statistics for the deleted interface. The statistics are no longer valid.
The no frame-relay cir, no frame-relay be and no frame-relay bc commands do not set the parameter to its default.
A Cisco MC3810 serving as a Frame Relay switch does not change the status of the DLCI upon shutting down the interface. This yields incorrect status to the connecting device.
When upgrading a Cisco MC3810 with a large number of Frame Relay PVCs to Cisco IOS Release 11.3(1)MA5 or above, the console may display memory allocation failures due to an insufficient buffer pool of 1680 bytes.

Network Management

An SNMP browser will always receive the value FALSE in response to a crfExtCircuitCreateType query.

Voice Support

There may be an issue with a second call being placed to a station that is currently in call_setup or connected. This only appears where the call is being forwarded via an intermediate router.

Caveats for Release 11.3(1)MA6

This section describes possibly unexpected behavior by Cisco IOS Release 11.3(1)MA6. This section describes only severity 1 and 2 caveats. Caveats are organized into the following categories:

Basic System Services

After performing the ping command to a host that is not currently in the route table and getting a successful response, the ARP table is not updated and a show arp will not include the new host in the display.
There is no workaround.
There might be an issue with a second call being placed to a station that is currently in call_setup or connected. This only appears where the call is being forwarded via an intermediate router.
In a test bed with Cisco MC3810 multiservice access concentrators connected back-to-back over Frame Relay, it was observed once that one of the routers reloaded. The stack analysis might point to LMI timeouts.
When doing CES ATM on the serial interface, there is a problem with how we are determining when the interface should be declared down.
After doing an snmpset of dialCtlPeerCfgTrapEnable variable to enable on a port, cannot reestablish call through the port. Snmpset back to disable does not recover it.
Workaround: reboot the router.
A FATAL ERROR can be cleared by removing the + sign from the prefix command.
The Cisco MC3810 has a TDM group configured on the E1 controller. When a crossconnect is configured using the TDM group on controller E1, the incorrect timeslots are assigned.

Wide-Area Networking

The no frame-relay cir, no frame-relay be, and no frame-relay bc commands do not set the parameter to its default.
A Cisco MC3810 serving as a Frame Relay switch does not change the status of the DLCI upon shutting down the interface. This yields incorrect status to the connecting device.

Caveats for Release 11.3(1)MA5

This section describes possibly unexpected behavior by Cisco IOS Release 11.3(1)MA5. This section describes only severity 1 and 2 caveats. Caveats are organized into the following categories:

Serial Ports

Serial ports on the Cisco MC3810 configured for SDLC might report input abort errors when the clock rate is greater than 38400. This does not affect performance as the errors are not typically input aborts. This is cosmetic and does not result in retransmitted frames. There is no performance impact because of this.

Frame Relay-ATM Interworking

Turning on VC shaping for Frame Relay-ATM Interworking PVCs might degrade the throughput of large packets. Removing VC shaping will allow large packets throughput to reach the link bandwidth.

Caveats for Release 11.3(1)MA4

This section describes possibly unexpected behavior by Cisco IOS Release 11.3(1)MA4. This section describes only severity 1 and 2 caveats. Caveats are organized into the following categories:

Note The caveats in this section originally applied to Release 11.3(1)MA3 and are duplicated in the caveats section for Release 11.3(1)MA3.

Voice Support

Under some conditions, a fax call placed into a Lucent PBX and then sent over a T1 digital line to a Cisco MC3810, and then across a network trunk to a remote Cisco MC3810 and then out an FXS port to a remote fax does not operate correctly. The same configuration has been tested and works consistently with PBXs from other vendors. Also, the reverse direction from the remote Cisco MC3810 to the one attached to the Lucent PBX works. Fax traffic originating on a Cisco MC3810 and terminating on a Lucent PBX works consistently.
A problem might occur passing digits out the FXO port with VAD enabled on the FXS port going to a handset. Turning VAD off circumvents this problem.
When a port is configured for PLAR operation, FXO type, it will go off-hook as soon as the incoming call is detected. The port will then attempt to set up a call across the network to the configured destination port. Because the local port had gone off-hook immediately, the calling device interprets that as a completion of the call, and proceeds, but if the remote destination is busy or unreachable, then the call fails, returns to on-hook, and the call is terminated. The calling device sees this sequence as a call-completion followed quickly by a call-termination. There is no workaround. The calling device must be able to handle this situation.

Frame Relay

In a configuration with generic traffic-shaping enabled on an interface with only data PVCs defined, if you reconfigure the interface to add voice-PVCs and use Frame Relay traffic-shaping and delete the generic traffic-shaping configuration, the system will generate a CPU-exception: "FORCE_CRASH(8c00e4)" followed by a software forced reload when traffic begins to flow on the voice PVC.
The workaround is to completely unconfigure the interface before adding the voice PVC configuration with traffic-shaping. The traffic-shape rate bit-rate [burst-size] [excess-burst-size] command should not be used in the same configuration as the frame-relay traffic-shaping command; they are mutually exclusive and will cause problems if used together. The preferred command for Frame Relay operation is the frame-relay traffic-shaping command.

Caveats for Release 11.3(1)MA3

This section describes possibly unexpected behavior by Cisco IOS Release 11.3(1)MA3. This section describes only severity 1 and 2 caveats. Caveats are organized into the following categories:

Note All the caveats listed in this section are resolved in Release 11.3(1)MA4 except CSCdj76205, CSCdj89486, CSCdk01296, and CSCdk02924.

IP Routing

Under some conditions, the show ip bgp command crashes when routes are displayed.

DLSw

In a configuration with DLSw traffic routed across a pair of Cisco MC3810 nodes, when DLSw is configured using the dlsw bridge-group command, the remote Cisco MC3810 suffers a software-forced crash (0xB9980) and reloads.

Serial Ports

You cannot Telnet to or ping an adjacent Cisco MC3810 concentrator over a serial WAN interface when transparent bridging (with the no ip routing command set) is configured on "multiple" interfaces. Note: If transparent bridging is configured only on the connecting serial interfaces, TCP\IP connectivity works. The problem occurs when multiple interfaces are configured with transparent bridging and an IP address.

Voice Support

After a call is set up, the initial few input dial tone digits will not be properly echo-cancelled; after that, the echo cancellation works correctly.
Under some conditions, a fax call placed into a Lucent PBX and then sent over a T1 digital line to a Cisco MC3810 and then across a network trunk to a remote Cisco MC3810 and then out an FXS port to a remote fax does not operate correctly. The same configuration has been tested and works consistently with PBXs from other vendors. Also, the reverse direction from the remote Cisco MC3810 to the one attached to the Lucent PBX works. Fax traffic originating on a Cisco MC3810 and terminating on a Lucent PBX works consistently.
When the clock rate 20000000 ces command is entered, the system reloads.
The router has problems distinguishing dial-plan numbers of different lengths with common overlapping digits. In the scenario below, the router translates the +111 as +11. As a result, when trying to place a call to +111, the call always fails, as shown in the following configuration:
dial-peer voice 11 pots
 destination-pattern +111
 port 1/1
!
dial-peer voice 16 pots
 destination-pattern +11
 port 1/6
In Release 11.3 (1) MA3 the framing format for E1 trunks on both sides of a configuration must match. For example, both sides must be either configured as CRC4 or no-CRC4.
When the MFT is configured for 56 kbps, a maximum of 14 contiguous time slots and a maximum of 10 noncontiguous timeslots can be configured into a channel group. The time slots can be in continuous or non-continuous fashion in order to meet your application. All time slots of a channel group shall be of identical data length, either 8 bit (64K) or 7 bit (56K). If the data length is 7 bit (56k), the following configuration limitation exists. If the configuration violates the limitation, the error message "%Insufficient resources to create channel group" is displayed. If the data length is 7 bit (56k) and the time slot assignment is continuous, the system can support up to 14 time slots. For example, you would enter the following command:
    channel-group 1 timeslots 2-15 speed 56
If the data length is 7 bit (56k) and the time slot assignment is noncontiguous, the system can support up to 10 time slots. For example, you would enter the following command:
    channel-group 2 timeslots 3,5,7,9,15-20 speed 56
If the data length is 8 bit (64k), no configuration limitation exists.
A problem might occur passing digits out the FXO port with VAD enabled on the FXS port going to a handset. Turning VAD off circumvents this problem.
When an FXO port is configured for PLAR operation, it will go off-hook as soon as the incoming call is detected. The port will then attempt to set up a call across the network to the configured destination port. Since the local port had gone off-hook immediately, the calling device interprets an off-hook condition on the FXO port as a completion of the call and proceeds. But if the remote destination is busy or unreachable and the call fails, the local port returns to on-hook and the call is terminated. The calling device sees this sequence as a call completion followed quickly by a call-termination. There is no workaround. The calling device must be able to handle this situation.
In a configuration with a DVM in E1 mode, the transmitted signaling bits displayed by the show controller command do not reflect the actual bits transmitted. Additionally, a show voice port command indicates that the default defined E&M idle and seized patterns are different from the bit patterns that are actually transmitted on the voice port.

Frame Relay

In a configuration with generic traffic-shaping enabled on an interface with only data PVCs defined, if you reconfigure the interface to add voice-PVCs and use Frame Relay traffic-shaping and delete the generic traffic-shaping configuration, the system will generate a CPU-exception: "FORCE_CRASH(8c00e4)" followed by a software forced reload when traffic begins to flow on the voice PVC.
The workaround is to completely unconfigure the interface before adding the voice PVC configuration with traffic-shaping. The traffic-shape rate bit-rate [burst-size] [excess-burst-size] command should not be used in the same configuration as the frame-relay traffic-shaping command; they are mutually exclusive and will cause problems if used together. The preferred command for Frame Relay operation is the frame-relay traffic-shaping command.
In a configuration with CLEAR CHANNEL as a DTE, the RTS control signal is set low regardless of the state of the circuit. This might cause failure to transfer data from the attached device.

ATM

After configuring IPX on an interface that is configured for "ATM CES" encapsulation, the router experiences the following errors:
ASSERTION FAILED: file "../src-m860/pquicc_driver_lib.c", line 301
ASSERTION FAILED: file "../src-m860/pquicc_driver_lib.c", line 301
ASSERTION FAILED: file "../src-m860/pquicc_driver_lib.c", line 301
An ATM CES encapsulation is not compatible with IPX and should not be configured that way.

Documentation Updates

This section addresses updates in the Cisco MC3810 Multiservice Access Concentrator Software Configuration Guide and the Cisco MC3810 Multiservice Concentrator Command Reference Guide and provides information that was not available before this guide was printed.

Important Documentation Notes for Cisco MC3810 Software Configuration Guide (78-4856-02)

The version of the Cisco MC3810 Multiservice Access Concentrator Software Configuration Guide (78-4856-02) that was shipped with the Cisco MC3810 beginning in November, 1998 includes documentation for features not supported in the Cisco IOS Release 11.3(1)MA.

Note If the printed version of the Cisco MC3810 Multiservice Access Concentrator Software Configuration Guide you are using has the part number 78-4856-01, then this section does not apply. Proceed to the "Updates to the Cisco MC3810 Software Configuration Guide" section.

If you are running this version of software, please note the following sections of this manual that are not supported, or are different from your software version:

Updates to the Cisco MC3810 Software Configuration Guide

This section describes updates to the Cisco MC3810 Multiservice Concentrator Software Configuration Guide.

Note This section only applies if the manual you are using has the part number 78-4856-01. If your part number is 78-4856-02, see the section "Important Documentation Notes for Cisco MC3810 Software Configuration Guide (78-4856-02)" section.

Add the following information to Chapter 10, "Other Frame Relay and ATM Voice Configuration Considerations."

Configuring a Voice Tie-Line

The current Cisco MC3810 implementation of tie-line is best described as "store-and-forward" of digits, especially when a Cisco MC3810 acts as a transparent device tie-line connected between PBXes. There is no busy signal at the circuit level from the Cisco MC3810 when a PBX seizes a line, but the Cisco MC3810 fails to seize a line on the far end. Instead, the Cisco MC3810 directly connected to the PBX will wink back immediately to the PBX and collect digits and forward to the remote end. In this case, when the Cisco MC3810 fails to establish a call, the PBX will not be able to reroute. Nevertheless, this implementation behaves just as any other tie-line applications if a Cisco MC3810 is installed to behave as a PBX.

Figure 1 shows an example of a tie-line configuration. The Frame Relay DLCI in the example is 3.


Figure 1: Voice Tie-Line Configuration


To configure a voice tie-line on Cisco MC3810 1, enter the following commands:

voice-port 1/1		
connection tie-line 20
 
dial-peer voice 200 vofr
 destination-pattern 20.....
 session-target Serial2 3
 
dial-peer voice 10 pots 
 destination-pattern 10
 port 1/1

To configure a voice tie-line on Cisco MC3810 2, enter the following commands:

voice-port 1/3
connection tie-line 10
 
dial-peer voice 100 vofr
 destination-pattern 10.....
 session-target Serial2 3
 
dial-peer voice 20 pots
 destination-pattern 20
 port 1/3

Excess Digits Playout and Digit Collection

Excess digits are defined as received digits that are beyond the length of the destination pattern on a terminating Cisco MC3810. A terminating Cisco MC3810 will forward excess digits to the telephony interface. For example, if the digits "123456789" are matched on a terminating Cisco MC3810 with a destination pattern of "1.....," the "6789" are excess digits and will be forwarded.

A Cisco MC3810 that is originating a call will only collect digits up to the length of a defined destination pattern. When a number is dialed that is longer than the destination pattern, after the last digit in the destination pattern is dialed, the call is immediately placed, and the additional digits are not collected by the Cisco MC3810.

For example, if the digits "123456789" are dialed on an originating Cisco MC3810 with a destination pattern of 1...., then "6789" are not collected. The call is placed immediately after the digit "5" is dialed. The additional digits "6789" are not collected, but are passed through the audio path.

In configurations where a telephone on an FXS port on the Cisco MC3810 is connected to the PSTN through an FXO port on the same Cisco MC3810, additional steps are necessary to enable a call to go through. Because the uncollected excess digits are passed through the audio path, the excess digits might not go through if the audio path is not ready when the excess digit is dialed. When dialing a destination pattern in this situation, pause and wait for a second dial tone before dialing the excess digits. This will give the audio path time to accept the excess digits.

Forward Digits and Voice Default Route

Prior to Cisco IOS Release 11.3(1)MA3, extra digits playout, tie-line emulation, and on-net to off-net switchover were the only conditions that caused digits to be forwarded to a telephony interface on the Cisco MC3810. Voice default routing for fixed-length dial plans was not previously available. To use the Cisco MC3810 with larger PBX configurations, the forward digits and voice default routing features have been added in Release 11.3(1)MA3.

Figure 2 shows an example of routing voice calls through a PBX using forward digits. In the configuration, the Cisco MC3810-t and Cisco MC3810-T are tandem nodes, and are required to support forwarding digits so that calls from Cisco MC3810 numbers 0, 5, or 9 can make a call to extension "8208."


Figure 2: Routing Voice Calls among Cisco MC3810s through a PBX


On the two tandem nodes, the forward-digits command is required. This command specifies to forward all digits matched with the destination "8..." to the appropriate port. For a call from Cisco MC3810-0 to reach extension 8208, the call must first route through Cisco MC3810-T, which plays out the digits "8208" to the voice port connected to the PBX. The PBX then routes the voice call to Cisco MC3810-t. On the tandem nodes, although the forward-digits all command is used, the forward-digits 4 command can also be used in this example. The following are the dial-peer configurations on each Cisco MC3810 required for this configuration:

For Cisco MC3810-t:

dial-peer voice 8 pots
destination-pattern 8208
session-target s0 1

dial-peer voice 1000 pots
destination-pattern 8...
forward-digits 4
port 1/1

dial-peer voice 9999 pots
destination-pattern ....
forward-digits all
port 1/1

For Cisco MC3810-T:

dial-peer voice 1 vofr
destination-pattern 8200
session-target s0 1

dial-peer voice 6 vofr
destination-pattern 8205
session-target s0 6

dial-peer voice 10 vofr
destination-pattern 8209
session-target s0 10

dial-peer voice 1 pots
destination-pattern 8...
forward-digits all
port 1/1

For Cisco MC3810-0:

dial-peer voice 1 pots
destination-pattern 8200
port 1/1

dial-peer voice 1000 vofr
destination-pattern8...
session-target s0 1

For Cisco MC3810-5:

dial-peer voice 5 pots
destination-pattern 8205
port 1/1

dial-peer voice 1000 vofr
destination-pattern 8...
session-target s0-1

For Cisco MC3810-9:

dial-peer voice 9 pots
destination-pattern 8209
port 1/1

dial-peer voice 1000 vofr
destination-pattern 8...
session-target s0 1

The concept of default voice routes is also shown in Figure 2 and in the configuration. In the example, the configurations for the destination dial plans "8..." in both the tandem nodes are voice default routes because all voice calls dialed that start with 8 followed by three digits will either match on 8208 or end up with 8...., which is the last-resort voice route used by Cisco MC3810-t if no other route is discovered.

Updates to the Cisco MC3810 Command Reference Guide

This section addresses errors and updates to the Cisco MC3810 Multiservice Concentrator Command Reference Guide and provides information that was not available before the guide was printed.

codec (voice port)

The codec command has been updated in Cisco IOS Release 11.3(1)MA5 to add new options. Replace the description of the codec command with the following:

To configure voice compression on the Cisco MC3810 voice port, use the codec voice port configuration command. Use the no form of this command to restore the default value.

codec {g729r8 | g729ar8 | g726r32 | g711alaw | g711ulaw}
Syntax Description

g729r8

Specifies G.729, 8k CSA-CELP.

g729ar8

Specifies G.729, 8k CSA-CELP Annex A.

g726r32

Specifies G.726 32K ADPCM.

g711alaw

Specifies G.711 64K PCM A-Law.

g711ulaw

Specifies G.711 64K PCM U-Law.

Default

g729ar8

Command Mode

Voice port configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3(1)MA.

The g729ar8 compression mode can support a maximum of 24 simultaneously active on-net voice calls on the Cisco MC3810 while the g729r8 value can only support a maximum of 12. Both compression modes have a nominal data rate of 8 kbps.

The g726r32 compression mode has a nominal data rate of 32 kbps. The g711alaw and g711ulaw compression modes have a nominal data rate of 64 kbps.

This command applies to both analog and digital voice ports on the Cisco MC3810.

Example

The following example configures voice port 1/1 on the Cisco MC3810 to support g729r8 compression:

voice port 1/1
codec g729r8

connection

The connection command has been updated in Cisco IOS Release 11.3(1)MA5 to add the plar-opx-ringrelay option. Replace the description of the connection command with the following:

To specify a connection mode for a voice port, use the connection voice-port configuration command. Use the no form of this command to disable the selected connection mode.

connection {plar | tie-line | plar-opx-ringrelay} string
no connection {plar | tie-line | plar-opx-ringrelay} string
Syntax Description

plar

Specifies a Private Line Auto Ringdown (PLAR) connection. PLAR is handled by associating a peer directly with an interface; when an interface goes off-hook, the peer is used to set up the second call leg and conference them together without the caller having to dial any digits.

tie-line

(Specific to the Cisco MC3810) Specifies a tie-line connection to a private branch exchange (PBX).

plar-opx-ringrelay

(Specific to the Cisco MC3810) Specifies support for PLAR off-premises extension (OPX) ring relay.

string

Specifies the destination telephone number. Valid entries are any series of digits that specify the E.164 telephone number.

Default

No connection

Command Mode

Voice-port configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3(1)T.

Use the connection command to specify a connection mode for a specific interface. Use the connection plar command to specify a PLAR interface. The string you configure for this command is used as the called number for all calls coming in over this connection. The destination peer is determined by the called number.

If the connection command is not configured, the standard session application outputs a dial tone when the interface goes off-hook until enough digits are collected to match a dial peer and complete the call.

The connection tie-line command is used on the Cisco MC3810 to replace a trunk line between two PBXes. In this situation, it allows you to reflect a network failure back to the origination point before calls are set up.

The connection plar-opx-ringrelay command is used on the Cisco MC3810 to support PLAR off-premises extension (OPX). Using this option, the local voice port provides a local response before the remote voice port receives an answer. This option was added in Cisco IOS Release 11.3(1) MA5.

The connection trunk command option has been removed.

Example

The following example selects tie-line as the connection mode on the Cisco MC3810, with a destination telephone number of 555-9262:

voice-port 1/1
connection tie-line 5559262

timing guard-out

A new command has been added to Cisco IOS Release 11.3(1)MA5. Add the following command to Chapter 9, "Voice Port Configuration Commands".

To configure the guard-out duration of an FXO voice port, use the timing guard-out voice-port configuration command. To restore the default value, use the no form of this command.

timing guard-out value
no timing guard-out value
Syntax Description

value

Duration in milliseconds of the guard-out period. The range is from 300 to 3000 milliseconds.

Default

2000 milliseconds

Command Mode

Voice-port configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3(1)MA5.

voice confirmation-tone

A new command has been added to Cisco IOS Release 11.3(1)MA5. Add the following command to Chapter 9, "Voice Port Configuration Commands."

To disable the two-beep confirmation tone for PLAR connections drawing the dial tone from a remote PBX, use the voice confirmation-tone voice-port configuration command. To reenable the confirmation tone, use the no form of this command.

voice confirmation-tone
no voice confirmation-tone
Syntax Description

There are no arguments or keywords for this command.

Default

Voice confirmation-tone is enabled

Command Mode

Voice-port configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3 MA5.

timing percentbreak

A new command has been added to Cisco IOS Release 11.3(1)MA4. Add the following command to Chapter 9, "Voice Port Configuration Commands."

To configure the break period of a dialing pulse, use the timing percentbreak voice-port configuration command. To restore the default value, use the no form of this command.

timing percentbreak percent
no timing percentbreak percent
Syntax Description

percent

Percentage of the break period for a dialing pulse. The range is from 20% to 80%.

Default

50%

Command Mode

Voice-port configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3(1)MA4.

condition command

A new command has been added to Cisco IOS Release 11.3(1)MA3. Add the following command to Chapter 9, "Voice Port Configuration Commands."

To manipulate the signaling format bit-pattern for all voice signaling types, use the condition command. To remove the condition setting, use the no form of this command.

condition {tx-a-bit | tx-b-bit | tx-c-bit | tx-d-bit} {rx-a-bit | rx-b-bit | rx-c-bit | rx-d-bit}
{on | off | invert}
no condition {tx-a-bit | tx-b-bit | tx-c-bit | tx-d-bit} {rx-a-bit | rx-b-bit | rx-c-bit | rx-d-bit}
{on | off | invert}
Syntax Description

tx-a-bit

Transmit A bit.

tx-b-bit

Transmit B bit.

tx-c-bit

Transmit C bit.

tx-d-bit

Transmit D bit.

rx-a-bit

Receive A bit.

rx-b-bit

Receive B bit.

rx-c-bit

Receive C bit.

rx-d-bit

Receive D bit.

on

Force the bit state to be a 1.

off

Force the bit state to be a 0.

invert

Invert the state of the bits.

Default

No condition (for all transmit or receive A, B, C, and D bits)

Command Mode

Voice-port configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3(1)MA3.

Use the conditioning command to manipulate the bit patterns sent or received by the Cisco MC3810 to match expected patterns on a connected device. Be careful not to destroy the information content of the bit pattern. For example, forcing the A-bit on or off will prevent FXO interfaces from being able to generate both an on-hook and off-hook state.

define command

A new command has been added to Cisco IOS Release 11.3(1)MA3. Add the following command to Chapter 9, "Voice Port Configuration Commands."

To define the transmit and receive bits for E&M and E&M MELCAS voice signaling, use the define voice-port configuration command. To use the default setting, use the no form of this command.

define {Tx-bits | Rx-bits} {seize | idle} {0000 | 0001 | 0010 | 0011 | 0100 | 0101 |
0110 | 0111 | 1000 | 1001 | 1010 | 1011 | 1100 | 1101 | 1110 | 1111}
no define {Tx-bits | Rx-bits} {seize | idle} {0000 | 0001 | 0010 | 0011 | 0100 | 0101 |
0110 | 0111 | 1000 | 1001 | 1010 | 1011 | 1100 | 1101 | 1110 | 1111}
Syntax Description

Tx-bits

Transmit signaling bits.

Rx-bits

Receive signaling bits.

seize

Define the pattern that represents the seized state.

idle

Define the pattern that represents the idle state.

0000 through 1111

Define the appropriate bit pattern.

Default

The default is to use the preset signaling patterns as defined in ANSI and CEPT standards, as follows:

For E&M:

Tx-bits idle 0000 (0001 if on E1 trunk)
Tx-bits seize 1111
Rx-bits idle 0000
Rx-bits seize1111

For E&M MELCAS:

Tx-bits idle 1101
Tx-bits seize 0101
Rx-bits idle 1101
Rx-bits seize 0101

Command Mode

Voice-port configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3(1)MA3.

Use the define command to match the E&M bit patterns with the attached telephony device. Be careful not to define invalid configurations, such as all 0000 on E1, or identical seize and idle states. Use this command with the ignore command.

Related Commands

ignore

ignore command

A new command has been added to Cisco IOS Release 11.3(1)MA3. Add the following command to Chapter 9, "Voice Port Configuration Commands."

To specify the E&M or E&M MELCAS voice port to ignore specific receive bits, use the ignore voice-port configuration command.

ignore {rx-a-bit | rx-b-bit | rx-c-bit | rx-d-bit}
no ignore {rx-a-bit | rx-b-bit | rx-c-bit | rx-d-bit}
Syntax Description

rx-a-bit

Ignore the receive A bit.

rx-b-bit

Ignore the receive B bit.

rx-c-bit

Ignore the receive C bit.

rx-d-bit

Ignore the receive D bit.

Default

The default is mode dependent:

For E&M: 

no ignore rx-a-bit
ignore rx-b-bit, rx-c-bit, rx-d-bit

For E&M MELCAS:

no ignore rx-b-bit, rx-c-bit, rx-d-bit
Command Mode

Voice-port configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3(1)MA3.

Use this command with the define command.

Related Commands

define

forward-digits

A new command has been added to Cisco IOS Release 11.3(1)MA3. Add the following command to Chapter 10, "Dial Peer Configuration Commands."

To configure forward digits for voice calls, use the forward-digits dial-peer configuration command. The no form of this command cancels the setting.

forward-digits [num-digit | all]
no forward-digits [num-digit | all]
Syntax Description

num-digit

Number of digits to be forwarded. If the number of digits is longer than the length of a destination telephone number, the length of the destination number is used.

all

Forward all digits. If "all" is used, the length of the destination pattern will be used.

Default

No default.

Command Mode

Dial-peer configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3(1)MA3.

Forwarded digits are always right-justified so that extra leading digits are stripped.

controller command

The description of the controller command in Chapter 1, "Global Configuration Commands," states that the command first appeared in the Cisco IOS Release 11.3(1)MA. This is incorrect. The controller command first appeared in Cisco IOS Release 10.0.

destination-pattern command

On page 10-3, the syntax for the no destination pattern command should be no destination pattern string, with the string value required. In the syntax description for the destination-pattern command, replace the description of the string value with the following text:

string

Series of digits that specify the E.164 or private dialing plan telephone number. Valid entries are the digits 0 through 9, the letters A through D, and the comma (,) symbol.

dial-type pulse command

The dial-type pulse command was not supported in the earlier Cisco IOS Release 11.3(1)MA2. In Cisco IOS Release 11.3(1)MA3, this command is now supported.

loopback command

The description of the loopback command in Chapter 3, "T1/E1 Controller Commands," states that the command first appeared in the Cisco IOS MA release. This is incorrect. The loopback command first appeared in Cisco IOS Release 11.1.

timing pulse command

The timing pulse command was not supported in the earlier Cisco IOS Release 11.3(1)MA2. Beginning with Cisco IOS Release 11.3(1)MA3, this command is now supported.

timing pulse-interdigit command

The timing pulse-interdigit command was not supported in the earlier Cisco IOS Release 11.3(1) MA2. In the Cisco IOS Release 11.3(1)MA3, this command is now supported.

Related Documentation

The following sections describe the documentation available for the Cisco MC3810. Typically, these documents consists of hardware installation guides, software installation guides, Cisco IOS configuration and command references, system error messages, and feature modules, which are updates to the Cisco IOS documentation. Documentation is available as printed manuals or electronic documents, except for feature modules, which are available online only.

The most up-to-date documentation can be found on the Web on Cisco Connection Online (CCO) and on the latest Documentation CD-ROM. These electronic documents might contain updates and modification made after the paper documents were printed. For information on CCO, refer to the "Cisco Connection Online" section. For more information on the CD-ROM, refer to the "Documentation CD-ROM" section.

Hardware Documents

Hardware documentation for the Cisco MC3810 is listed in Table 3. These documents ship with the Cisco MC3810.

To access hardware documents on CCO, follow this path:

Products and Ordering: Cisco Documentation: Access Servers and Access Routers: Multiservice Access Concentrators

To access hardware documents on the Documentation CD-ROM, follow this path:

Cisco Product Documentation: Access Servers and Access Routers: Multiservice Access Concentrators


Table 3: Hardware Documents for the Cisco MC3810
Book Part Number Chapter Topics

Cisco MC3810 Multiservice Concentrator Hardware Installation Guide

78-4855-02

Overview of the Cisco MC3810
Planning Your Installation
Installing the Cisco MC3810
Powering Up the Cisco MC3810
Opening and Closing the Chassis

Cisco Redundant Power System Hardware Installation Guide

78-4097-02

Overview of the Cisco RPS
Installing the Cisco RPS
Connecting to External Devices
Connecting Cables

Software Documents

Software documentation for the Cisco MC3810 is listed in Table 4. These documents ship with the Cisco MC3810.

To access software documents on CCO, follow this path:

Products and Ordering: Cisco Documentation: Access Servers and Access Routers: Multiservice Access Concentrators: Cisco MC3810 Multiservice Concentrator Software

To access hardware documents on the Documentation CD-ROM, follow this path:

Cisco Product Documentation: Access Servers and Access Routers: Multiservice Access Concentrators: Cisco MC3810 Multiservice Concentrator Software


Table 4: Software Documents for Cisco MC3810
Book Part Number Chapter Topics

Cisco MC3810 Multiservice Access Concentrator Software Configuration Guide

78-4856-02

Cisco IOS Software Basic Skills
Initial Configuration
Serial Port and T1/E1 Trunk Configuration
Synchronized Clock Configuration
Voice over Frame Relay Configuration
Voice over ATM Configuration
Frame Relay-ATM Interworking Configuration
Voice over HDLC Configuration
PBX Signaling Format Configuration
Dial Plan Considerations
CDR Support Configuration
Voice Port Configuration
Video Support Configuration
Cisco MC3810-IGX Interworking Configuration
ROM Monitor Configuration
Planning Forms

Cisco MC3810 Multiservice Concentrator Software Command Reference Guide

78-4975-01

Global Configuration Commands
EXEC Commands
T1/E1 Controller Commands
Frame Relay Commands
Frame Relay-ATM Interworking Command
ATM Commands
HDLC Command
UIO Serial Port Commands
Voice Port Configuration Commands
Dial Peer Configuration Commands

For information on corrections and additions to the Cisco MC3810 Multiservice Access Concentrator Software Configuration Guide and to the Cisco MC3810 Multiservice Concentrator Command Reference Guide, see the "Documentation Updates" section.

Cisco IOS Documentation

Cisco IOS software documentation is listed in Table 5. Software documentation consists of the Cisco IOS configuration guides and command references and also includes several supporting documents. These documents are shipped with the Cisco MC3810 in electronic form on the Documentation CD-ROM, unless you specifically ordered the printed version of the documents.

To access software documents on CCO, follow this path:

Products and Ordering: Cisco Documentation: Cisco IOS SOftware Configuration: Cisco IOS Release 11.3

To access software documentation on the Documentation CD-ROM, follow this path:

Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 11.3


Table 5: Cisco IOS Software Documents
Books Part Numbers Chapter Topics

  • Configuration Fundamentals Configuration Guide

  • Configuration Fundamentals Command Reference

78-4728-01

78-4729-01

Configuration Fundamentals Overview
Cisco IOS User Interfaces
File Management
Interface Configuration
System Management

  • Network Protocols Configuration Guide, Part 1

  • Network Protocols Command Reference, Part 1

78-4736-01

78-4739-01

IP Addressing
IP Services
IP Routing Protocols

  • Network Protocols Configuration Guide, Part 2

  • Network Protocols Command Reference, Part 2

78-4737-01

78-4740-01

AppleTalk
Novell IPX

  • Network Protocols Configuration Guide, Part 3

  • Network Protocols Command Reference, Part 3

78-4738-01

78-4741-01

Apollo Domain
Banyan VINES
DECnet
ISO CLNS
XNS

  • Wide-Area Networking Configuration Guide

  • Wide-Area Networking Command Reference

78-4734-01

78-4735-01

ATM
Frame Relay
SMDS
X.25 and LAPB

  • Security Configuration Guide

  • Security Command Reference

78-4730-01

78-4731-01

AAA Security Services
Security Server Protocols
Traffic Filtering
Network Data Encryption
Passwords and Privileges
Neighbor Router Authentication
IP Security Options

  • Dial Solutions Configuration Guide

  • Dial Solutions Command Reference

78-4732-01

78-4733-01

Dial Business Solutions and Examples
Dial-In Port Setup
DDR and Dial Backup
Remote Node and Terminal Service
Cost-Control and Large-Scale Dial Solutions
VPDN

  • Cisco IOS Switching Services Configuration Guide

  • Cisco IOS Switching Services Command Reference

78-4756-01

78-4757-01

Switching Paths for IP Networks

  • Fast Switching

  • Autonomous Switching

  • NetFlow Switching

  • Optimum Switching

Virtual LAN (VLAN) Switching and Routing

  • Inter-Switch Link Protocol Encapsulation

  • IEEE 802.10 Encapsulation

  • LAN Emulation

  • Bridging and IBM Networking Configuration Guide

  • Bridging and IBM Networking Command Reference

78-4742-01

78-4743-01

Transparent Bridging
Source-Route Bridging
Remote Source-Route Bridging
DLSw+
STUN and BSTUN
LLC2 and SDLC
IBM Network Media Translation
DSPU and SNA Service Point
SNA Frame Relay Access Support
APPN
NCIA Client/Server Topologies
IBM Channel Attach

  • Cisco IOS Software Command Summary

  • System Error Messages

  • Debug Command Reference

78-4746-01

78-4747-01

78-4745-01

Note The Cisco Management Information Base (MIB) User Quick Reference publication is no longer being published. For the latest list of MIBs supported by Cisco, see the Cisco Network Management Toolkit on Cisco Connection Online. On CCO, use the following path Software and Support: Software Center: Network Management Products: Cisco Network Management Toolkit: Cisco MIBs.

Cisco Connection Online

Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.

Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

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





hometocprevnextglossaryfeedbacksearchhelp
Posted: Wed Mar 17 12:10:26 PST 1999
Copyright 1989-1999©Cisco Systems Inc.