THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT

NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE

PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR

APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION

PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO

LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB???s public domain version of the UNIX operating system. All rights reserved. Copyright ?? 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED

???AS IS??? WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED,

INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND

NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL

DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR

INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

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

Cisco VISM Installation and Configuration Guide

Copyright ?? 2004, Cisco Systems, Inc.

All rights reserved.

Contents

Contents

Contents

Configuring PNNI for AAL1/AAL2 SVCs 4-31

Configuring the ATM Network Side 4-31

Configuring PVC Connections for All Operating Modes 4-32

Configuring VoIP Switching/Trunking Operating Mode Parameters 4-34

Configuring AAL2 Trunking Operating Mode Parameters 4-36

Configuring Switched AAL2 PVC Operating Mode Parameters 4-38

Contents

Contents

I N D E X

Figures

T A B L E S

Tables

Preface

This preface describes the objectives, audience, organization, and conventions of the Cisco VISM Installation and Configuration Guide.

Objectives

This document describes the features, functions, installation, operation, and command line interface of Cisco Voice Interworking Service Module (VISM) Release 3.0.

Audience

This document is intended for the following personnel:

???Technicians responsible for installing VISM cards on the Cisco MGX 8230, MGX 8250, and MGX 8850 shelf.

???Network administrators responsible for configuring the Cisco MGX 8850 shelf.

Cisco recommends that installers be familiar with electronic circuitry and wiring practices and have experience as an electronic or electromechanical technician. Installers and network administrators should also be familiar with Cisco switches and routers, T1 and E1 voice lines, and Cisco wide area networks. Cisco also recommends that you have a system administrator present who is familiar with your network and UNIX servers during the initial installation of a Cisco MGX 8000 Series platform.

Document Organization

This document contains the following chapters:

???Chapter 1, ???Overview of the VISM and VISM-PR Cards,??? provides a general introduction to VISM and describes the hardware and software modules, and installation procedures.

???Chapter 2, ???Telephony Applications Using VISM,??? describes VISM applications for a variety of voice networking situations.

???Chapter 3, ???VISM Functional Description,??? describes VISM???s functional operation.

???Chapter 4, ???Configuring VISM Features,??? describes the initial mandatory configuration procedures for using VISM cards in each of the operating modes.

Preface

Related Documentation

???Chapter 5, ???CLI Commands,??? describes the syntax and semantics of each VISM command line interface command.

???Chapter 6, ???Troubleshooting Tips,??? describes VISM troubleshooting tools and techniques.

???Appendix A, ???VISM and VISM-PR Card Clocking Options,??? describes clocking configuration for both the VISM card and MGX 8000 Series platform PXM cards.

???Appendix B, ???VISM and VISM-PR???3.0 Specifications,??? describes the specifications of VISM Release 3.0.

Related Documentation

The following sections describe documentation you may need to reference as you use the VISM product.

Cisco MGX 8850 (PXM45) Multiservice Switch Release 3

The documentation for the installation and operation of the MGX 8850 Multiservice Switch for Release 3 is listed in Table 1.

Table 1 Cisco MGX 8850 (PXM45) Multiservice Switch Release 3 Documentation

Preface

Related Documentation

Table 1 Cisco MGX 8850 (PXM45) Multiservice Switch Release 3 Documentation (continued)

MGX 8850 (PXM1) Multiservice Switch Release 1.2.10

The documentation for the installation and operation of the MGX 8850 (PXM1) Multiservice Switch is listed in Table 2.

Preface

Related Documentation

MGX 8250 Edge Concentrator Release 1.2.10

The documentation for the installation and operation of the MGX 8250 Edge Concentrator is listed in Table 3.

MGX 8230 Edge Concentrator Release 1.2.10

The documentation for the installation and operation of the MGX 8230 Edge Concentrator is listed in Table 4.

Preface

Conventions

Conventions

This publication uses the following conventions to describe commands:

???Bold type???indicates command names and user entry text.

???Italic type???indicates arguments for which you supply values.

???| |???vertical bars indicate optional arguments.

This publication uses the following conventions to describe examples:

???Courier font???indicates terminal sessions and system display information.

???Courier bold font???indicates user entry.

Preface

Obtaining Documentation

Note Means reader take note. Notes contain helpful suggestions or references to materials not contained in this manual.

Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation on the World Wide Web at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

International Cisco websites can be accessed from this URL:

http://www.cisco.com/public/countries_languages.shtml

Ordering Documentation

You can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

???Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:

http://www.cisco.com/en/US/partner/ordering/index.shtml

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

Documentation Feedback

You can submit e-mail comments about technical documentation to bug-doc@cisco.com.

Preface

Obtaining Technical Assistance

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems

Attn: Customer Document Ordering

170 West Tasman Drive

San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour-a-day, award-winning technical support services, online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for technical assistance. If you do not hold a valid Cisco service contract, please contact your reseller.

Cisco TAC Website

The Cisco TAC website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365 days a year. The Cisco TAC website is located at this URL:

http://www.cisco.com/tac

Accessing all the tools on the Cisco TAC website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:

http://tools.cisco.com/RPF/register/register.do

Opening a TAC Case

Using the online TAC Case Open Tool is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using the recommended resources, your case will be assigned to a Cisco TAC engineer. The online TAC Case Open Tool is located at this URL:

http://www.cisco.com/tac/caseopen

For P1 or P2 cases (P1 and P2 cases are those in which your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.

To open a case by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)

EMEA: +32 2 704 55 55

USA: 1 800 553-2447

For a complete listing of Cisco TAC contacts, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

Preface

Obtaining Additional Publications and Information

TAC Case Priority Definitions

To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.

Priority 1 (P1)???Your network is ???down??? or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Priority 2 (P2)???Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Priority 3 (P3)???Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Priority 4 (P4)???You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

???Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Go to this URL to visit the company store:

http://www.cisco.com/go/marketplace/

???The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://cisco.com/univercd/cc/td/doc/pcat/

???Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

http://www.ciscopress.com

???Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

???iQ Magazine is the Cisco bimonthly publication that delivers the latest information about Internet business strategies for executives. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

Preface

Obtaining Additional Publications and Information

???Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

???Training???Cisco offers world-class networking training. Current offerings in network training are listed at this URL:

http://www.cisco.com/en/US/learning/index.html

Preface

Obtaining Additional Publications and Information

C H A P T E R 1

Overview of the VISM and VISM-PR Cards

This chapter provides a general introduction to VISM and VISM-PR and describes the hardware and software modules, and installation procedures. The following topics are described:

??????VISM and VISM-PR Card Types??? section on page 1-1

??????VISM and VISM-PR Card Physical Characteristics??? section on page 1-5

??????VISM and VISM-PR Card Features??? section on page 1-6

??????Installing VISM Hardware and Software??? section on page 1-13

??????Software Upgrades??? section on page 1-20

Note The term VISM is used to refer to the product software???either for the VISM card or for the VISM-PR card. The terms VISM and VISM-PR are used when discussing hardware only.

The VISM card, in combination with a Cisco MGX 8000 Series platform, enables telephone calls on conventional time-division multiplexed (TDM) voice circuits to be transported over an Asynchronous Transfer Mode (ATM) packet-switched and VoIP networks. The VISM card is a single height card designed to operate in the following platforms:

???Cisco MGX 8850 Release 1, wide area switch

???Cisco MGX 8250, edge concentrator

???Cisco MGX 8230, edge concentrator

Note VISM is not supported on the Cisco MGX 8260 switch.

VISM and VISM-PR Card Types

VISM and VISM-PR cards are installed in Cisco MGX 8000 Series switches as front cards and their associated back cards???card sets. There are two types of VISM front cards (see Figure 1-1):

???AX-VISM-8T1???Supports up to eight T1 lines carrying digitized voice

???AX-VISM-8E1???Supports up to eight E1 lines carrying digitized voice

Chapter 1 Overview of the VISM and VISM-PR Cards

VISM and VISM-PR Card Physical Characteristics

VISM and VISM-PR Card Service Types

VISM cards are configured with the following service types:

???Constant bit rate (CBR)

Note CBR is not supported with a combination of a PXM1 with either an RPM or external router.

???Variable bit rate real time, VBR (RT)

???VBR non-real time (NRT)

VISM-PR card connections with the RPM-PR card requires the VBR (NRT) 3 service type on the PXM1E and PXM45 platforms.

If you are using a VISM-PR card in combination with a PXM1E, PXM45, or RPM-PR card, you must use the VBR (NRT) 3 selection when adding a connection.

The following connection service types can be configured with VISM 3.0 and higher:

???VBR (RT) 2

???VBR (RT) 3

???VBR (NRT) 2

VISM and VISM-PR Card Physical Characteristics

VISM cards are equipped with the following:

???Eight T1 or E1 ports

???Digital signal processors (DSPs)

???High-level data link control (HDLC) framer

???Broadband interface to the packet network

VISM Card Architecture

VISM card architecture provides the following:

???Flexibility that allows the incorporation of new or improved technology as it becomes available.

???Application flexibility that allows VISM to be used in a range of situations that provide interoperability with a wide variety of equipment types.

???Modularity that allows equipment to be purchased and installed as it is needed for scalability.

Chapter 1 Overview of the VISM and VISM-PR Cards

VISM and VISM-PR Card Features

???Voice over ATM (VoATM) using AAL2 cells???No Logical Link Control/Subnetwork Access Protocol (LLC/SNAP) encapsulation.

Note Multiplexing is not supported for AAL2 SVCs.

???VoIP using AAL5 cells to RFC 1889.

???Extended Superframe (ESF) framing with or without cyclic redundancy check (CRC).

???Pulse code modulation (PCM) A/Mu law codecs.

???Programmable 24, 32, 48, 64, 80, 96, 112, 128 ms tail delay near end ECAN.

???Voice compression with the following standards:

???G.711

???G.726-16k

???G.726-24k

???G.726-32k

???G.726-40k

???G.729a

???G.729ab

???G.723.1-H

???G.723.1a-H

???G.723.1-L

???G.723.1a-L

Note The G.723.1 codecs are not supported in combination with the VISM card. The G.723.1 codecs are supported with the VISM-PR card.

???Nx64 clear channel (N = 1 only) support.

???Voice activity detection (VAD) and comfort noise generation (CNG) using variable threshold energy (Cisco proprietary).

???Call agent Simple Gateway Control Protocol (SGCP) Version 1.0, 1.1, 1.5, SGCP 1.1+, 1.5, and Media Gateway Control Protocol (MGCP) 0.1 and 1.0.

???Backhauling channel associated signaling (CAS) signaling to a call agent using xGCP (backhauling can be accomplished with any supported SGCP and MGCP protocol).

???Backhauling Primary Rate Interface (PRI) signaling via Reliable User Datagram Protocol (RUDP) to a call agent.

???Common channel signaling (CCS) transport across an AAL5 trunk.

???Fax and modem VoIP bearer transmissions.

???Dual (redundant) virtual circuits across the packet network.

???Full continuity testing (COT). Supports origination and terminating loopback and transponder COT between VISM and the central office on the TDM side.

???Loop timing, which can be used as the master clock for the entire MGX 8000 Series platform and local clock.

Chapter 1 Overview of the VISM and VISM-PR Cards

VISM and VISM-PR Card Features

???Line loopback (DS1) toward the TDM lines.

???Channel loopback (DS0) toward both the TDM lines and the ATM network.

???Transmission and reception of bit error rate tester (BERT) signals over loopbacked lines.

???Redundant alarm indication signal (RAI) and alarm indication signal (AIS) alarms.

???Extracting a DS0 CCS channel and directing it to the TDM signaling function.

???1:N cold redundancy using subrate multiplexing (SRM)-3T3 (bulk mode support for T1 lines only) and SRM-E (for OC3) capabilities. Calls do not persist during switchover.

???Graceful shutdown of ongoing voice calls when the VISM is taken out of service for maintenance or other reasons. Forced shutdown is also supported.

Caution A forced shutdown of the VISM or VISM-PR card may result in dropped calls.

Redundancy and Bulk Distribution

Redundancy for VISM cards with or without bulk distribution can be provided through the Service Redundancy Module (SRM) and SRM-E. Redundancy for VISM is also provided by Media Gateway Controller (MGC) redundancy groups. VISM redundancy is cold redundancy in which ongoing calls do not persist during switchover.

Note SRM-E is supported with PXM1 and PXM1E cards only.

Redundancy with bulk distribution requires a spare VISM card to be installed. The system uses the three T3 ports of the SRM back card instead of the normal T1 lines on the VISM back cards. VISM cards in bulk distribution mode do not require back cards.

The TDM voice data transmitted or received over the T3 ports are distributed to the VISM card as if they had been received over VISM T1 back card ports in the normal manner. This feature reduces the number of physical lines required to support VISM, but requires external equipment to multiplex and demultiplex the T1 data onto the T3 lines.

With or without bulk distribution, redundancy allows for the spare VISM card to automatically take over the functions of a failed VISM card. When the failed card is repaired, switching back to the repaired card is not automatic. You must manually change the repaired card back to the active state with the command line interface. See Chapter 4, ???Configuring VISM Features.???

Note 1:1 redundancy using Y-cables is not supported by VISM.

Redundancy can also be configured at the ATM permanent virtual circuits (PVCs) level. Two separate PVCs can be set up, each using a different PXM physical port and each routed to a separate router. Configure one PVC as active and the other as standby. Both PVCs are monitored by heartbeat OAM F5 loopback cells every 200 ms. If three consecutive OAM cells are lost, the PVC fails, and only the remaining PVC is active. A PVC will recover automatically when five consecutive OAM cells are received while the PVC remains in standby mode (no automatic fallback to active state is provided).

Control and bearer PVCs can be set up with a redundant PVC.

Chapter 1 Overview of the VISM and VISM-PR Cards

VISM and VISM-PR Card Features

Operating Modes

The VISM/VISM-PR card performs in the following operating modes:

???Voice over IP (VoIP) switching/trunking

???Switched AAL1 switched virtual circuits (SVCs)

???Switched AAL2 SVC

???Switched AAL2 PVC???this mode is not supported in VISM Release 3.0

???AAL2 trunking

???VoIP and switched ATM AAL1 SVC

The VISM/VISM-PR card, in order to support the operating modes, supports connections to three major interfaces:

???Voice TDM network

???ATM network

???Call agent???signaling (either CAS or CCS but not both) and call control

In VoIP switching, switched AAL2 PVC, AAL1 SVC, and AAL2 SVC modes, all three of these interfaces are always present and active. In AAL2 trunking mode, the interface to the call agent interface is not present and the only active interfaces are to the TDM network and the ATM network.

The operating modes, combined with features you configure, are used by VISM cards in a wide variety of telephony applications. For example:

???Provide many of the functions of a tandem (Class 4) switch. VISM can be used to replace, or partially offload, a Tandem switch by directing calls over a packet network rather than the conventional voice TDM network.

???Concentrate voice and data user services onto a single broadband circuit for transmission over the packet network. In this application, VISM performs as a front end to a voice gateway.

???The VISM/MGX combination is used to concentrate voice (and fax/modem voiceband data) user services over a preprovisioned AAL2 trunk. VISM passes bearer and signaling data across a packet network and does not perform call setup and teardown functions.

VoIP Switching and Switched AAL2 PVC Operating Modes

In VoIP switching mode and switched AAL2 PVC mode, VISM operates under the control of a call agent to set up and tear down calls. When a call is set up, VISM transports voice payloads over an ATM network to the called station destination. VISM performs either as a voice gateway or as a multiservice access front end to a voice gateway.

Note This document refers to the device that provides the interface between VISM and the telephone Signaling System 7 (SS7) as a call agent. Other terms that describe the same device are Virtual Switch Controller, Media Gateway Controller, and Gatekeeper.

Chapter 1 Overview of the VISM and VISM-PR Cards

VISM and VISM-PR Card Features

Figure 1-6 shows the major functional blocks and interfaces for the VoIP switching and switched AAL2 PVC operating modes.

Figure 1-6 VISM Block Diagram for VoIP Switching and Switched AAL2 PVC Operating Modes

The CAS signaling path on the TDM side is embedded in the voice stream but is separated at the bearer processing function. The CAS signaling then joins the CCS signaling path for CAS/CCS processing and is backhauled to the call agent. The path between the call agent and bearer processing, via a connection handling function, is for call setup and teardown.

Voice TDM Network Interface

The voice payload path is shown as a solid line along the bottom of Figure 1-6. All external TDM streams arrive and depart on the T1/E1 lines. Depending on the application, these streams consist of voice bearer channels (with or without CAS signaling) and separate CCS channels (if CCS signaling is used). The TDM line handling function provides the physical layer interface, which includes framing, line codes, clocking, loopbacks, physical alarms, etc. Bearer channels, including CAS, are sent to the bearer processing function. CCS channels are sent to the CAS/CCS processing function.

Further processing of the bearer channels is performed by the DSPs. This processing provides ECAN, compression, A/Mu law conversion, silence suppression, and fax/modem handling. If CAS signaling is present, signaling bits are extracted at the DSP stage and sent to the CAS/CCS processing function.

ATM Network Interface

The ATM processing function receives the processed DS0 voice streams and prepares them for transport over a packet network. The voice streams are divided into specific sample periods (for example, 5 ms or 10 ms) and formatted into service specific convergence sublayer (SSCS) packets appropriate for the method of transport over the ATM network. The available transport methods are VoIP (using AAL5) and voice over AAL2. Processing of the ATM packets further segments the voice payload into ATM cells for transport over the network using a SONET port on the PXM card.

Cisco VISM Installation and Configuration Guide

Chapter 1 Overview of the VISM and VISM-PR Cards

VISM and VISM-PR Card Features

Call Agent Interface

The call agent interface consists of CAS signaling or CCS signaling and call control. The path between the call agent and bearer processing, via a connection handling function, is for call setup and teardown.

The CAS signaling path on the TDM side is embedded in the voice stream (bearer DS0s) and is separated at the bearer processing function. The CAS signaling (robbed bits, digits, and tones) is passed to the CAS/CCS processing function where it is passed (backhauled) to the call agent under the control of the call agent. The mechanism for communicating between VISM and the call agent is a gateway control protocol:

???MGCP

???SGCP

???SRCP

The separate CCS signaling path channels are passed to the CAS/CCS processing function and backhauled to the call agent. The CCS signaling is transported as ISDN Q.931 messages both on the TDM side and on the call agent side. On the TDM side, the messages are carried in the Q.921 layer protocol (which terminates at the VISM card). On the call agent side, communication with the call agent consists of Q.931 messages encapsulated in RUDP/UDP/IP packets. The Q.931 connection is terminated at the call agent and not at the VISM card.

The call control path uses MGCP, SGCP, and SRCP for call setup and teardown. Because signaling and call control are so intertwined, both call control and CAS use the same path and protocol for the VISM card to call agent communications.

AAL2 Trunking Operating Mode

In the AAL2 trunking operating mode, the VISM card serves as an access to one or more trunks to preprovisioned locations. VISM may be used at both ends of the trunk, or at one end with a compatible device at the other. In AAL2 trunking mode, VISM plays no part in call setup and teardown. Other network elements handle call control while VISM merely handles voice transport over the trunks. Figure 1-7 shows the major functional blocks for the AAL2 trunking operating mode.

The AAL2 trunking mode is less complex than the VoIP switching and AAL2 PVC switched modes because there is no call control involved???and no need for a call agent.

Cisco VISM Installation and Configuration Guide

Chapter 1 Overview of the VISM and VISM-PR Cards

VISM and VISM-PR Card Features

The voice bearer path is treated in the same manner as in the VoIP switching and AAL2 PVC modes, except that only preprovisioned AAL2 PVCs are available for transport of voice over the trunks. The CAS signaling data is transported over the ATM network in the same AAL2 trunk as Type 3 messages. The CCS signaling data is transported over the ATM network in a separate AAL5 PVC.

VoIP Trunking Operating Mode

The Voice over IP (VoIP) trunking feature allows the VISM to connect to the PBX, or central office digital systems, using T1/E1 digital interfaces and converts the TDM bit stream into RTP packets, after ECAN and compression, and transports it over the IP network.

No call agent is required for setting up and tearing down calls. You must configure the DS0 circuits. The connection between VISM and the first router will be ATM after which it will be IP only. VISM and the router can have one or multiple PVCs to transport the data. You have the option to configure PVC for bearer or control. If the PVC is configured as bearer and no control PVC exists, then PRI signal traffic and bearer traffic will go through this PVC. If you configure separate PVCs for control and bearer, PRI signaling will go through control traffic only. You can modify some of the connection parameters after it is added.

CAS is transported to the far end using a Cisco proprietary format (not NSEs). PRI is transported over RUDP to the far end once the trunk is provisioned between the originating and terminating VISM.

PRI transport is handled in a way identical to PRI backhaul except that the PRI traffic is sent to remote gateway instead of a call agent. You can configure one line for PRI trunking and another line for PRI backhauling.

You must provision the LAPD trunk when using this feature. You must configure a line number, remote gateway IP address, local UDP port, and remote gateway UDP port, and then open a trunk. You must then configure the D-channel as a trunk or backhaul:

???To configure the D channel as trunk, use the addlapdtrunk command prior to the addlapd command. If the addlapd command has been previously executed for that line, the command is rejected.

Note Two D channels on one line are not supported.

???To configure the D channel as backhaul, use the addses command prior to the addlapd command. If you do not configure either trunk or session, the addlapd command is rejected.

AAL1/AAL2 SVC Operating Mode

Release 3.0(0) supports the AAL1 and AAL2 switched virtual circuit (SVC) operating modes for VISM-PR cards. VoAAL1 SVC is supported with the G.711 codec and clear channel.

Note VAD is not supported in combination with AAL1 SVCs. CAS is not supported in combination with SVCs.

Chapter 1 Overview of the VISM and VISM-PR Cards

Installing VISM Hardware and Software

VoAAL2 SVC is supported with the G.711, G.726, G.729a, and G.729ab codecs and profiles 1, 2, 3, 7, 8, 100, 101, 110, and 200.

Note The AAL1/AAL2 SVC operating modes require you to use a PXM1E or PXM45 in your MGX 8000 Series switch chassis.

Installing VISM Hardware and Software

You can install VISM cards in the following configurations:

???Install a VISM front card and a back card as a pair. The front and back cards must occupy the same slot.

???Install a VISM front card with no back card. The MGX 8000 Series bulk distribution feature allows this configuration. Access to and from the TDM lines is performed by the Service Resource Module (SRM) and the MGX 8000 Series distribution bus.

Note VISM cards in bulk distribution mode do not require back cards.

??? Install a VISM front card as a redundant card with a redundant back card in the same slot.

Note VISM T1 front cards require T1 back cards and E1 front cards require E1 back cards. Ensure that your configuration meets this requirement.

In each of these configurations, connections to the packet network are made through the MGX 8000 Series cellbus and an OC-3 port located on the MGX 8000 Series PXM card. Refer to the ???VISM and VISM-PR Card Physical Characteristics??? section on page 1-5 for more information on front and back cards.

Installing VISM Cards in MGX 8000 Series Chassis

VISM front and back cards can be installed in the following MGX 8000 Series platforms with these basic guidelines:

???Cisco MGX 8850 Release 1???Up to 24 slots can be used for VISM cards.

???Cisco MGX 8250???Up to 24 slots can be used for VISM cards.

???Cisco MGX 8230???Up to eight slots can be used for VISM cards.

The VISM card can be used with the Processor Module-1 (PXM1) card.

Installing VISM-PR Cards in MGX 8000 Series Chassis

VISM-PR front and back cards can be installed in the following MGX 8000 Series platforms with these basic guidelines:

???MGX 8250 and MGX 8850???Up to 24 slots can be used for VISM-PR cards.

???MGX 8230???Up to 8 slots can be used for VISM-PR cards.

Chapter 1 Overview of the VISM and VISM-PR Cards

Installing VISM Hardware and Software

The VISM-PR card can be used with the following Processor Module cards:

???PXM1

???PXM1E

???PXM45

You must install an additional fan tray spacer at the bottom of your MGX 8000 Series switch chassis directly above the intake plenum if you are using the VISM-PR card in combination with the PXM45 card. Refer to the Cisco MGX 8850 Hardware Installation Guide, Release 3 for step-by-step instructions to install a fan tray.

MGX 8850 and MGX 8250 Chassis

VISM and VISM-PR card installation in a Cisco MGX 8850 or MGX 8250 platform consists of installing one front card and one back card (if not using the bulk distribution feature) in either the upper or lower shelf of the chassis. You can use slots 1 to 6, 9 to 14, 17 to 22, and 25 to 30 to install VISM cards (see Figure 1-8).

Figure 1-8 Available Chassis Slots for VISM Cards in the MGX 8850 and MGX 8250???Front View

Note If you use all the available slots, you can configure the MGX 8850 and MGX 8250 with up to 24 VISM cards. However, the two lower shelf cellbuses can each sustain a bandwidth of one OC-3/STM-1 link. This bandwidth limits the number of E1 ports on the lower shelf, when using the G.711 codec, to 78, which limits the number of VISM cards to 10.

Cisco VISM Installation and Configuration Guide

Chapter 1 Overview of the VISM and VISM-PR Cards

Installing VISM Hardware and Software

MGX 8230 Chassis

VISM card installation in a Cisco MGX 8230 platform consists of installing one front card and one back card (if not using the bulk distribution feature) in either a left or right shelf slot. You can use slots 3 to 6, and 10 to 13 to install VISM cards (see Figure 1-9). If you use all the available slots, you can configure the MGX 8230 with up to eight VISM cards.

Figure 1-9 Available Chassis Slots for VISM Cards in the Cisco MGX 8230???Front View

Installing VISM and VISM-PR Front and Back Cards

This section describes the following hardware installation procedures:

1.Installing a VISM or VISM-PR Front Card

2.Installing a VISM Back Card

3.Connecting Cables to Cards

Installing a VISM or VISM-PR Front Card

Complete the following instructions to install a VISM or VISM-PR front card:

Step 1 Position the rear card guides over the appropriate slot in the chassis.

Step 2 Gently slide the card all the way into the slot and press the insertion/extractor lever until it snaps into the vertical (MGX 8250 or MGX 8850) or horizontal (MGX 8230) position.

Caution The card should slide in and out with only slight friction on the EMI gaskets on the adjacent board. Do not use force. Investigate any binding.

Cisco VISM Installation and Configuration Guide

Chapter 1 Overview of the VISM and VISM-PR Cards

Installing VISM Hardware and Software

Installing a VISM Back Card

Complete the following instructions to install a VISM back card:

Step 1 Ensure that the two extractor levers are at the ???in??? position.

When you insert the card into the slot, the levers should be vertical or horizontal along the line of the back card.

Step 2 Position the rear card guides over the appropriate slot in the chassis.

Step 3 Gently slide the card all the way into the slot.

Step 4 Tighten the two captive screws on the back card???s faceplate.

Step 5 Tighten the upper and lower screws to prevent misalignment of the card.

Note Do not overtighten the screws. Tighten them only enough to secure the card.

Connecting Cables to Cards

After you install the VISM front and back cards, connect the T1 or E1 cables to the RJ-48 or SMB connectors on the back cards. The T1 and E1 cables connect the eight ports on the back cards to the voice T1 or E1 lines. The T1 lines use RJ-48 connectors. The E1 lines use either RJ-48 or SMB connectors.

Note In all text references to cables, ???transmit??? refers to a cable used for data moving away from the VISM card, and ???receive??? refers to a cable used for data moving toward the VISM card.

Cabling for RJ-48 Connectors on T1 and E1 Ports

For T1 and E1 ports that connect through an RJ-48 connector, each connector has:

???Transmit TIP (TTIP) pin

???Transmit RING (TRNG) pin

???Receive TIP (RTIP) pin

???Receive RING (RRNG) pin

???Two pins for shielded ground

Chapter 1 Overview of the VISM and VISM-PR Cards

Installing VISM Hardware and Software

Step 3 Pull both of the extractor levers out to the horizontal position.

This action starts the removal of the card.

Step 4 Gently pull the card out of the chassis.

Applying Power to the VISM Card

You apply power to a VISM card by installing it in an already running MGX 8000 Series platform, or by applying power to a chassis that has a previously installed VISM card. When power is applied, the VISM card performs extensive testing and initialization functions. If the card has already been configured, the initialization downloads the configuration data from the disk on the PXM. This process takes approximately two minutes, during which the LED indicator blinks. When the Active LED becomes solid green, the card is in the Active state and is ready to be configured (if necessary) and able to process data.

Installing VISM Software Upgrades

VISM Release 3.0 provides a graceful upgrade procedure from Release 1.5 and higher. The existing VISM configuration is preserved throughout the upgrade procedure, provided that the following conditions are met:

???The Cisco MGX 8000 Series platform must be configured with at least two VISM cards in a redundant configuration. Refer to the add redundancy, addred, command in the Cisco MGX 8850, MGX 8250, and MGX 8230 command reference guides for details.

???The VISM cards must be running VISM 2.0 and be configured to the desired configuration.

???The VISM Release 3.0 software must have been already downloaded to the Cisco MGX shelf. Refer to Release Notes for Cisco Voice Interworking Services Module Release 3.0(0) for details.

???Cisco recommends an upgrade in the backup boot to version 3.0.

Complete the following steps to upgrade the VISM software. In the following procedure, old-rev refers to the firmware before the upgrade (2.0) and new-rev refers to the firmware after the upgrade (3.0).

Note If the VISM card you are upgrading is part of a nonredundant configuration, complete Step 1 to Step 4 only.

Step 1 Log in to the active PXM card (slot 7 or 8).

Step 2 Save the existing configuration as a contingency plan by entering:

savesmcnf <SM slot#>

where:

SM slot# is the slot number of the active VISM card.

This command saves the existing configuration to the C:\CNF directory. This file can be used during the downgrade procedure, if necessary.

Chapter 1 Overview of the VISM and VISM-PR Cards

Installing VISM Hardware and Software

Step 3 Execute the PXM install command for the backup boot image:

install bt sm <SM slot#> <new bb rev>

where:

SM slot# is the slot number of the active card, and new bb rev is the version number of the new backup boot image.

This command downloads the backup boot image to the flash in the VISM card slot you specified. The new backup boot image takes effect upon the next card reset.

Step 4 Execute the PXM install command:

install sm <SM slot#> <new-rev>

where:

SM slot# is the slot number of the VISM card that was active before the upgrade process started, and new-rev is the file name of the new firmware (for example, vism_8t1e1_002.001.000.000.fw).

This command causes the standby VISM card to reset and be placed in the hold state, running the new-rev firmware. The active VISM card is unaffected by this command. At this point the primary firmware is still the old-rev and the secondary firmware is new-rev.

Step 5 Execute the PXM newrev command:

newrev sm <SM slot#> <new-rev>

where:

SM slot# is the slot number of the VISM card that was active before the upgrade process started, and new-rev is the filename of the new firmware.

This command causes the standby VISM card to become the active VISM card running the new-rev firmware. The previously active VISM card is placed in the hold state, becoming the new standby VISM card, and is still running the old-rev firmware. The primary and secondary firmware switches with the new-rev becoming the primary firmware.

Step 6 Execute the PXM commit command:

commit sm <SMslot#> <new-rev>

where:

SM slot# is the slot number of the new standby VISM card and new-rev is the filename of the new firmware.

This command causes both VISM cards to run the new-rev firmware. After a short time, the cards switch automatically so that the originally active VISM card becomes the active card and the originally standby VISM card becomes the standby card. The two VISM cards are now back to their original condition except that both cards are now running the new-rev firmware.

Step 7 Log in to the active VISM card and use the display commands (dspendpts, dspcasvar, etc.) to confirm that the configuration has been preserved through the upgrade process.

Cisco recommends that you further verify the configuration by making some minor modifications to the configuration, checking that the changes have been executed correctly, and then changing the configuration back again.

See Appendix B, ???VISM and VISM-PR???3.0 Specifications??? for more information about the VISM and VISM-PR card specifications.

Chapter 1 Overview of the VISM and VISM-PR Cards

Software Upgrades

Software Upgrades

VISM/VISM-PR Release 3.0 provides a graceful upgrade procedure for the following releases:.

???From VISM 1.5 to VISM 3.0

???From VISM 2.1 to VISM 3.0

???From VISM 2.2 to VISM 3.0

Caution Installing VISM software upgrades from VISM Release 2.2 with CALEA to VISM Release 3.0 without CALEA is not graceful.

Prerequisites

To ensure that the VISM/VISM-PR configuration is preserved throughout the upgrade procedure, you must complete the prerequisites listed in this section.

Before starting the graceful upgrade procedure, complete the following prerequisites:

???Configure your MGX 8000 Series shelf with at least two VISM cards in a redundant configuration.

For more information on adding redundancy, refer to the add redundancy, addred, command in the Cisco MGX 8250, Cisco MGX 8230, and Cisco MGX 8850 PXM1-based Command Reference documentation and the Cisco MGX 8830 and MGX 8850 PXM1E/ PXM45-based Command Reference documentation.

???Ensure that the VISM/VISM-PR cards are running at least Release 2.1.

???Download software Release 3.0 for VISM/VISM-PR to the MGX 8000 Series shelf.

???If you are using the CALEA feature, ensure that you have the version of VISM/VISM-PR software that supports CALEA.

VISM/VISM-PR Upgrades with PXM1

This section describes the procedures for upgrading VISM/VISM-PR software when the

VISM/VISM-PR is used with a PXM1 card.

Download VISM/VISM-PR Boot Code and Firmware to PXM1

To download the VISM/VISM-PR boot code and firmware to the PXM1 card, use TFTP.

Step 1 Log in to your TFTP server.

Step 2 Download the bootcode and firmware images from the Cisco website.

Step 3 Download the selected revision of service module boot code into the service module.

a.tftp <node_name or IP address>

b.bin

c.put <backup boot> POPEYE@SM_1_0.BT

d.quit

Chapter 1 Overview of the VISM and VISM-PR Cards

Software Upgrades

Step 4 Download the selected firmware file.

To upgrade all VISM cards, proceed to Step 4c. To upgrade an individual VISM card, proceed to Step 4d.

a.tftp <node_name or IP address>

b.bin

c.put <FW file> POPEYE@SM_1_0.FW quit

d.put <FW file> POPEYE@SM_1_<slot number of card to upgrade>.FW quit

Note Do not enter two put commands in the same TFTP session.

Step 5 Proceed to the ???Upgrade VISM/VISM-PR Firmware with PXM1 Card??? section on page 1-21 to install the download.

Upgrade VISM/VISM-PR Firmware with PXM1 Card

Software Release 3.0 is for VISM and VISM-PR cards. Ensure that the VISM and VISM-PR cards have the minimum boot code version of vism_8t1e1_VI8_BT_3.1.00.fw.

The following versions of VISM software Release 3.0 are available:

???003.000.000.000???without CALEA

???003.050.000.000???with CALEA

In this procedure the following conditions apply:

???If two VISM or VISM-PR cards are part of a redundancy group, initially the primary card is in the active state, and the secondary card is in the standby state.

???Old-rev refers to the firmware, Release 2.2 and prior.

???New-rev refers to the firmware after the upgrade, Release 3.0.

Perform the firmware upgrade on the VISM or VISM-PR cards. Do not remove the VISM cards and replace them with VISM-PR cards at this time.

Step 1 Log in to the active PXM1 card (slot 7 or 8).

Step 2 Save the existing configuration as a contingency plan by entering:

savesmcnf <SM slot#>

This command saves the existing configuration in the C:CNF directory. This file can be used during the downgrade procedure, if necessary.

Step 3 Execute the PXM install command:

install sm <SM slot#> <new-rev>

where:

SM slot# is the slot number of the primary VISM or VISM-PR card and new-rev is the file name of the new firmware (for example, vism_8t1e1_003.000.000.000.fw).

Chapter 1 Overview of the VISM and VISM-PR Cards

Software Upgrades

This command causes the secondary VISM or VISM-PR card to reset and come up in the standby state, running the new-rev firmware. The primary VISM or VISM-PR card is unaffected by this command.

Step 4 Execute the PXM newrev command:

newrev sm <SM slot#> <new-rev>

where:

SM slot# is the slot number of the primary VISM or VISM-PR card and new-rev is the filename of the new firmware.

This command causes the primary VISM or VISM-PR card to reset and the secondary VISM or VISM-PR card to become active and running the new-rev firmware.

Step 5 Execute the PXM commit command:

commit sm <SM slot#> <new-rev>

where:

SM slot# is the slot number of the primary VISM or VISM-PR card and new-rev is the filename of the new firmware.

The two VISM or VISM-PR cards are now back to their original condition except that both cards are now running the new-rev firmware.

Step 6 Log in to the active VISM or VISM-PR card and use the display commands (for example, dspendpts, dspcasvar, and so forth) to confirm that the configuration has been preserved through the upgrade process.

Note For more than one primary VISM or VISM-PR card in a redundancy group, ensure that the secondary card is in the standby state and repeat Step 4 and Step 5 for each VISM card in the redundancy group.

It is also recommended that you perform the following verifications:

???Make minor modifications to the configuration.

???Check that the changes have been executed correctly.

???Change the configuration back again.

Note If the VISM or VISM-PR card is not part of a redundancy group, complete Step 1 to Step 3.

For more information about the VISM and VISM-PR card specifications, see ???VISM and

VISM-PR???3.0 Specifications??? section on page B-1.

Chapter 1 Overview of the VISM and VISM-PR Cards

Software Upgrades

Boot Code Upgrade Procedure with PXM1 Cards

Complete the following steps to upgrade the new backup boot code when you are using PXM1 cards in your MGX 8230, MGX 8250, and MGX 8850 chassis:

Note This procedure re-programs the VISM boot code for previous VISMs using the VISM runtime image version 1.0 to 2.0.

Step 1 Telnet to MGX shelf and cc to the VISM card.

Note VISM must be in the active state in order to update the VISM boot code.

Step 2 Access the server where the VISM boot code resides and TFTP the VISM boot code to the VISM card:

a.Type tftp <IP address of the MGX shelf>

b.Type bin at the tftp prompt.

Caution Ensure that you perform Step 2b. If you to not perform Step 2b. the boot code is corrupted and not recoverable.

c. Type install [bt] [sm <slot>] <version> at the PXM prompt.

Caution Do not touch the VISM card until the status comes back ('Sent xxx bytes in yyy seconds'). Failure to follow this recommendation corrupts the boot code, which cannot be recovered.

When the boot code is being written to PROM, you will see comments displayed at the VISM prompt. This behavior is normal and expected.

Step 3 Use the resetcd command for VISM from the PXM card for the latest boot take effect.

Step 4 Type the version command to verify the correct boot code.

Note Step 4 is optional.

You have completed upgrading the new VISM backup boot code.

VISM-PR Upgrades with PXM1E and PXM45

This section describes the procedures for upgrading VISM-PR software when the VISM-PR is used with a PXM1E or PXM45 card.

Chapter 1 Overview of the VISM and VISM-PR Cards

Software Upgrades

Download VISM-PR Boot Code and Firmware to PXM1E and PXM45

To download the VISM-PR boot code and firmware to the PXM1E or PXM45 card, use FTP.

Step 1 Access the image on the Cisco Web site.

Step 2 To download the image, enter the ftp command. ftp node-ip

where node-ip is the IP address of the node to which you want to download the image.

Step 3 Enter your user name and password.

Step 4 Enter bin.

Step 5 Access the appropriate directory.

cd C:FW

Step 6 Download the image to your C:FW directory. put image-version

where image-version is the downloaded image from Step 1.

Step 7 To exit the download procedure, enter bye.

Upgrade VISM-PR Firmware with PXM1E and PXM45 Cards

Ensure that the VISM-PR cards have the minimum boot code version of vism_8t1e1_VI8_BT_3.1.00.fw. The following versions of VISM-PR software Release 3.0 are available:

???003.000.000.000???without CALEA

???003.050.000.000???with CALEA

Perform the firmware upgrade on the VISM-PR cards.

Step 1 Log in to the active PXM1E or PXM45 card.

Step 2 Ensure that the card is in the redundant mode, where the active card is the primary card.

Step 3 To save the existing configuration as a contingency plan, enter the saveallcnf command.

Step 4 To load the new software, enter the loadrev command. loadrev sm-primary-slot-num new-rev

where sm-primary-slot-num is the slot number of the VISM-PR card in which you want to install the new software; and new-rev is the new firmware version number for the VISM-PR software.

Caution Temporary traffic loss occurs.

Step 5 To execute the download, enter the runrev command. runrev sm-primary-slot-num new-rev

Caution Temporary traffic loss occurs.

Chapter 1 Overview of the VISM and VISM-PR Cards

Software Upgrades

Step 6 To commit the new download to the VISM-PR card, enter the commitrev command.

commitrev sm-primary-slot-num new-rev

You have completed the steps. Proceed to the Boot Code Upgrade Procedure with PXM1E and PXM45 Cards, page 1-25.

Boot Code Upgrade Procedure with PXM1E and PXM45 Cards

Complete the following steps to upgrade the new backup boot code when you are using PXM1E or PXM45 cards in your MGX 8000 Series chassis:

Step 1 Complete the steps in the VISM-PR Upgrades with PXM1E and PXM45, page 1-23 section.

Step 2 Log in to the PXM1E or PXM45 card.

Step 3 Use the burnboot sm-primary-slot-num new-rev command, where sm-primary-slot-num is the slot number of the VISM-PR card you want to upgrade and new-rev is the firmware version number of the new VISM software, to upgrade the VISM-PR boot code.

The VISM-PR card automatically resets and becomes active with the latest boot code image. You have completed the boot code upgrade procedure.

VISM/VISM-PR Downgrade Procedure

Use this procedure to downgrade VISM software from software Release 3.0 to an earlier VISM release. By following the downgrade procedure described here, the configurations are retained after the downgrade.

Note The configurations that existed with old-rev firmware should have been saved earlier. You cannot downgrade from VISM-PR to VISM.

Complete the following steps to downgrade the VISM software from software Release 3.0 for

VISM/VISM-PR to Release 2.2, 2.1, 2.0, or 1.5:

Step 1 If the VISM card is in a redundancy group, remove the redundancy.

delred <SM slot#>

Step 2 Download the old-rev firmware onto the MGX shelf.

Step 3 Execute the PXM clrsmcnf command:

clrsmcnf <SM slot#>

where:

SM slot# is the slot number of the VISM card to be downgraded.

The VISM card resets on executing this command. Wait for the card to come active.

Chapter 1 Overview of the VISM and VISM-PR Cards

Software Upgrades

Step 4 Execute the PXM restoresmcnf command:

restoresmcnf -f <filename> -s <SM slot#>

where:

The filename is the name of the old configuration file that was saved while the old-rev firmware was running. The file can be found in the C:CNF directory on the MGX shelf.

The SM slot# is the slot number of the VISM card to be downgraded.

The VISM card resets again. When the card becomes active, it has the old-rev firmware running with the old configuration.

Step 5 Reconfigure redundancy group, if required.

VISM to VISM-PR Hardware Upgrade

Complete the following steps to upgrade your system from VISM cards to VISM-PR cards.

Caution You must install the redundant (standby) VISM-PR card first. Failure to follow this recommendation results in traffic loss. In addition, do not remove an active VISM card from your chassis. Ensure that you configure an active VISM card to the standby state before you remove it and replace it with a VISM-PR card.

Step 1 Remove the redundant (standby) VISM card from your chassis.

Step 2 Install a VISM-PR card in the slot you removed the VISM card from in Step 1.

Step 3 Administratively configure the VISM-PR card you installed in Step 2 as primary (active).

Step 4 Remove the now redundant VISM card from your chassis.

Step 5 Install a VISM-PR card in the slot you removed the VISM card from in Step 4.

Step 6 Log in to the redundant (secondary) VISM-PR card and execute the dspcd command. Verify that the output from the dspcd command lists the card type under FunctionModuleType as a VISM-PR card. If the card type still indicates the VISM card, execute the resetcd slot-num command from the PXM and repeat the dspcd command to insure that the correct card type is shown.

Step 7 Log in to the active VISM-PR card and execute the dspcd command. Verify that the output from the dspcd command lists the card type under FunctionModuleType as a VISM-PR card. If the card type still indicates the VISM card, execute the resetcd slot-num command from the PXM and repeat the dspcd command to insure that the correct card type is shown.

Step 8 If you have no other VISM cards in your chassis, you have completed the hardware upgrade procedure; do not proceed to Step 9. If you have more VISM cards in your chassis, proceed to Step 9.

Step 9 Remove a standby VISM card from your chassis.

Step 10 Install a VISM-PR card in the slot you removed the VISM card from in Step 9.

Step 11 Repeat Step 9 and Step 10 to remove any remaining VISM cards in your chassis and replace them with VISM-PR cards.

Step 12 Repeat Step 6 and Step 7 on the remaining VISM-PR cards to insure the correct card type is shown.

C H A P T E R 3

VISM Functional Description

The functions performed by VISM are described in the following sections:

??????TDM Line-Handling Function??? section on page 3-2

??????Bearer Processing Function??? section on page 3-3

??????Signaling Function??? section on page 3-5

??????ATM Voice Data Processing Function??? section on page 3-11

??????Call Control Function??? section on page 3-15

??????Embedded VISM Management Function??? section on page 3-19

Figure 3-1 shows the functional blocks of VISM. Items with single asterisks indicate VoIP switching and switched AAL2 PVC functions. Items with double asterisks indicate AAL2 trunking functions. Items without asterisks indicate VoIP switching, switched AAL2 PVC, and AAL2 trunking functions.

Chapter 3 VISM Functional Description

Bearer Processing Function

Bearer Processing Function

The bearer processing function processes raw bearer DS0 streams from the T1/E1 lines in preparation for packetization and segmentation and reassembly (SAR) processing on the ATM side. Most of the bearer processing is performed by the VISM daughter card???s DSPs.

The main processing categories are:

???Echo cancellation, voice compression, and A/Mu law conversion

???Voice activity detection and silence suppression

???Fax and modem handling

???Jitter control

???CAS handling

Echo Cancellation, Voice Compression, A/Mu Law Conversion

Bearer DS0 streams are received from the T1/E1 line function, and each is assigned to a DSP configured for echo cancellation (ECAN). You can configure the following ECAN parameters:

???Residual echo control

???Maximum tail in milliseconds (up to 128 ms)

???Fax and modem tone detection

If voice compression is required, the ECAN voice streams are assigned to a second DSP configured with the required codec. Available compression schemes are:

???G.711 64 kbps (A/Mu law, user configurable)

???G.726-16k

???G.726-24k

???G.726-32k

???G.726-40k

???G.729a

???G.729ab

???G.723.1-H

???G.723.1a-H

???G.723.1-L

???G.723.1a-L

VISM allows the use of codec templates in which the user selects a template instead of specifying each allowable codec individually. VISM supports the following codec templates:

???Template 1???Supports clear channel, G.711a, G.711u, G.729a, G.729ab, G.726-16k, G.726-24k, G.726-32k, and G.726-40k codecs.

???Template 2???Supports clear channel, G.711a, and G.711u codecs.

Chapter 3 VISM Functional Description

Bearer Processing Function

???Template 3???Supports G.711u, G.711a, G.726-16k, G.726-24k, G.726-32k, G.726-40k, G.729a, and G.729ab codecs, clear channel.

???Template 4???Supports G.711u, G.711a, G. 726-16k, G.726-24k, G.726-32k, G.726-40k, G.729a, G.729ab, G.723.1-H, G.723.1a-H, G.723.1-L, G.723.1a-L codecs and clear channel.

Within each template, you can specify a preference order for each codec. At call setup time, the codec to be used from the configured template is either specified by the call agent or negotiated between the calling and called VISM cards. If the codec is negotiated, the most preferred codec that both VISM cards can support is selected.

For each codec, VISM supports various packetization periods as described in Table 3-1.

Table 3-1 Supported Codecs and Packetization Periods

Voice Activity Detection and Silence Suppression

You can configure the VISM card DSPs to monitor the TDM voice stream for voice activity. If the voice activity detection (VAD) feature is enabled and no voice activity (silence) is detected for more than a specified period of time, typically 250 ms, the silent voice samples are suppressed. During periods of silence, parameters defining background noises transmit periodically. You can configure the remote VISM to use the background noise information to generate comfort noise at the called end while silence suppression is in operation.

Fax and Modem Tone Detection

You can configure the VISM card DSPs to detect the modem or fax tones on the data lines. For VoIP operating mode, the action is specified using command line interface (CLI) commands. Refer to Chapter 5, ???CLI Commands,??? for more information on CLI commands. For AAL2 connections, the action is specified in the AAL2 profile. Generally, when a modem or fax tone is detected, VAD and ECAN are turned off and codec is changed to the specified type (for example G.711 or clear channel).

Note If the codec is already set to clear channel, the DSP cannot detect any tones???fax and modem tones are not detected.

Chapter 3 VISM Functional Description

Signaling Function

Jitter Control

The VISM card uses voice buffers on the DSP to reduce jitter on outgoing voice streams. Jitter control operates in the following modes:

???Fixed???Allows you to configure a fixed buffer size in the range 0 to 100 ms. This mode is used when latency jitter is nearly constant. This is the default mode for G.711u/a and clear channel codecs, with a 100-ms buffer size.

???Adaptive???Allows you to configure a starting buffer size, but adapts the size of the buffer according to the jitter. Use this mode when latency jitter varies greatly. This is the default mode for all codecs other than G.711u/a and clear channel.

CAS Handling

In applications using CAS, you can configure the VISM card DSPs to monitor incoming traffic and extract the following CAS signaling information:

???ABCD bits

???Digits

???Tones

You can configure VISM to handle various CAS variations such as immediate start, wink start, ground start. The extracted CAS signaling information is sent to the TDM signaling function.

Signaling Function

All TDM signaling enters and exits VISM on the T1/E1 lines and is directed to the signaling function. CAS signaling information is received from the bearer processing function, described in the ???Bearer Processing Function??? section on page 3-3. CCS signaling information arrives directly from the TDM line handling function, described in the ???TDM Line-Handling Function??? section on page 3-2.

VISM depends on a combination of the following two features to determine how it handles signaling:

???Operating mode:

???VoIP switching/trunking

???Switched AAL2 PVC

???AAL2 trunking

???AAL1 SVC

???AAL2 SVC

???AAL1/VoIP (for TDM grooming)

???Signaling type:

???CAS

???CCS

Signaling enters from the T1/E1 lines and, depending upon the mode and the type of signaling, is processed for the correct protocol and directed to either the call agent or the ATM trunks (see Figure 3-2).

Chapter 3 VISM Functional Description

Signaling Function

5.When the call agent receives the dialed number, it uses the dial plan to communicate with the remote call agent to set up the call.

6.The call is terminated when either the called or calling party goes on-hook.

CCS Processing in Switched AAL2 PVC Operating Mode

In the switched AAL2 PVC operating mode, CCS signaling can be configured to pass (backhaul) CCS signals between the user PBXs and the call agents.

You can configure T1 and E1 lines for CCS signaling. You must specify a particular DS0 as an Integrated Services Digital Network (ISDN) D channel to carry the Primary Rate Interface (PRI) signaling. Signaling from the private branch exchange (PBX) is received on the D channel as level 3 Q.931 messages encapsulated in the information field of level 2 Q.921 LAPD information frames.

The Q.921 link is terminated at the VISM, and on the call agent side, a Redundant User Datagram Protocol/User Datagram Protocol/Internet Protocol (RUDP/UDP/IP) connection is used to carry level 3 Q.931 signaling between VISM and the call agent. This link to the call agent flows through an intermediate router. From VISM to the router, the RUDP/UDP/IP packets are segmented and transported as AAL5 ATM cells.

The function of the VISM PRI/backhaul feature is to pass the Q.931 messages between the PBX and the call agent.

VISM handles all Q.921 frame types. For information type frames, the process is described in the following list:

1.VISM extracts the Q.931 frame.

2.VISM then places it in an RUDP datagram.

3.The RUDP datagram is encapsulated in UDP and IP packets (using the IP address and a specified port number of the destination call agent).

4.The SAR section of VISM segments the IP message into AAL5 ATM cells for transport to the call agent via an edge router.

In CCS processing, communication between VISM and the call agent involves both call control information using xGCP protocols and CCS signaling using Q.931 protocol. Both are transported using the AAL5 ATM connection.

Signaling from the call agent to the PBX is handled in the same manner but in reverse:

1.Signaling from the call agent is stripped of its RUDP/UDP/IP headers and trailers.

2.Signaling is then encapsulated into Q.921 information type frames for transmission to the user???s PBX.

VISM is not involved with the signaling content but acts as an interface between the PBX and the call agent.

Chapter 3 VISM Functional Description

ATM Voice Data Processing Function

Use the CLI PRI/backhaul commands to do the following:

???Create and delete session sets

???Create, delete, configure, and display sessions and sessions groups

???Create, delete, configure, and display D channels for CCS

???Display PRI/backhaul statistics

Refer to Chapter 5, ???CLI Commands,??? for more information on CLI commands.

CAS Processing in AAL2 Trunking Operating Mode

CAS signaling is extracted from the voice data and is transported across the packet network in AAL2 trunking operating mode. The signaling is transported across the same trunk (VC) and the same channel identifier (CID) as its associated voice stream, using AAL2 Type 3 messages in accordance with ITU-T I.366.2. The messages are used for CAS (A,B,C, and D) robbed bits, fax/modem tones, and digits and are transported with triple redundancy.

CCS Processing in AAL2 Trunking Operating Mode

CCS signaling is maintained as Q.931 messages and transported across the packet network using an AAL5 PVC in AAL2 trunking operating mode. The local and remote ends of the PVC are the same as those for the AAL2 PVC trunk carrying the associated voice data.

ATM Voice Data Processing Function

The VISM DSPs process incoming voice data (for compression, ECAN, etc.) and then the data is prepared for transport over the ATM network. Voice samples are processed into ATM packets and then into ATM cells in preparation for transport. VISM then transports the cells to Voice over ATM (VoATM) networks with the following supported operating modes:

???VoIP

???Switched AAL2 PVC

???AAL2 trunking

???AAL1 SVC

Transporting Voice Cells with VoIP

The VoIP switching operating mode processes voice cells in the following order to transport them over ATM networks:

1.Formatted into Real-Time Transport Protocol (RTP) packets.

Note RTP allows time-stamping of the voice samples, which permits dejittering of the samples transmitted to the destination TDM line.

2.Encapsulated in a UDP packet.

Chapter 3 VISM Functional Description

ATM Voice Data Processing Function

To improve reliability, VISM supports two independent OC-3 interfaces, each connected to a separate edge router and each with its own PVC. One PVC is designated the primary PVC and the other the secondary PVC. The primary circuit is used unless it fails, in which case VISM switches automatically to the secondary circuit. Switchover may cause a temporary 250-ms delay on the lines.

VISM communicates with the packet network about transmitting the voice payload by using the SONET OC-3 port on the MGX 8000 series platform PXM card. Voice payload samples are formatted and sent across the MGX 8000 series platform cellbus and onto the SONET connection.

Transporting Voice Cells with Switched AAL2 PVC

The switched AAL2 PVC operating mode transports voice cells with up to 64 PVCs. Multiple calls can share a single AAL2 connection simultaneously using a CID. Each PVC is assigned a virtual connection circuit identifier (VCCI). The VCCI/CID to endpoint/DS1/DS0 binding is made dynamically by the call agent as part of the call setup procedure. However, you can permanently set the binding???which makes VISM operate as if it were in AAL2 trunking operating mode.

The AAL2 PVC supports AAL2 profiles and mid-call upspeeds. Codec changes can be supported if they are within the agreed upon profile. The following AAL2 profiles are supported:

???Custom profile 100

???Custom profile 101

???Custom profile 110

???ITU-T I.366.2 profile 1

???ITU-T I.366.2 profile 2

???ITU-T I.366.2 profile 7

???ITU-T I.366.2 profile 8

Chapter 3 VISM Functional Description

Call Control Function

xGCP Extensions for AAL2 Switched PVC and AAL2 SVC Operating Modes

VISM supports the following extensions to the xGCP protocols for AAL2 switched and AAL2 SVC applications:

???A new AAL2 Type 3 message type (coded ???010001???) for telephone signal events (TSEs). The following are TSEs:

???ECAN off

???Request audible ring tone

???Ack continuity test

???Request stop audible tone

???Request continuity test

???An extended naming structure to include ATM endpoints. An ATM endpoint enables the following to be included in the definition of an endpoint:

???ATM address

???virtual path identifier (VPI)

???VCI

???VCCI

???CID

???An extended list of connection events in MGCP, known as an ATM Package. These events are:

???Setup complete (for AAL2 CID path)

???Setup failed (for AAL2 CID path)

???Enable CAS via type 3 packets

???Introduction of a Profile Type in call setup commands to describe encoding techniques.

Endpoint Service States

Endpoints exist in one of two service states???in-service (IS) and out-of-service (OOS). The state of an endpoint is determined by user configuration commands and line alarm conditions. When an endpoint is added, it automatically assumes the state of the line.

When endpoints are taken OOS, the transition can be graceful or forced. If graceful, no new connections are permitted while ongoing connections are allowed to terminate normally. If forced, no new connections are permitted and all ongoing connections are terminated immediately.

You can also bring an endpoint to the IS and OOS states with the following commands, which operate either on a line-by-line basis or on the entire VISM card:

???cnflnis???Configure a line as IS

???cnflnoos???Configure a line as OOS

???cnfgwis???Configure a VISM card as IS

???cnfgwoos???Configure a VISM card as OOS

These commands allow you to specify either a graceful or forced transition.

Chapter 3 VISM Functional Description

Call Control Function

If an alarm condition on a line is raised, all endpoints on the line are brought into a forced transition to OOS. An automatic return to IS is performed when the alarm is cleared, unless a specific OOS command is executed in the meantime.

Restart In Progress Command

The call agent is kept informed of the state of all endpoints with the xGCP Restart In Progress (RSIP) command. The following minimum requirements must be met for this process to operate:

???At least one call agent must be configured using the add media gateway controller (addmgc) command.

???A protocol must be added for each media gateway controller using the add media gateway group entry command (addmgcgrpentry) command.

The VISM card issues an RSIP command in the following situations:

???One or more endpoints are added or deleted with the following commands:

???addendpt

???addendpts

???delendpt

???delendpts

???A line is configured as IS or OOS with one of the following commands:

???cnflnis

???cnflnoos

???The VISM card (gateway) is configured as IS or OOS with one of the following commands:

???cnfgwis

???cnfgwoos

???The VISM card is powered up or reset.

Note In this case, the RSIP is delayed by a random amount (up to a configurable maximum duration) to avoid an avalanche of RSIPs arriving at the call agent when an entire MGX 8000 series platform with multiple VISM cards is powered up or reset.

When the states of multiple endpoints are changed simultaneously, the VISM card minimizes the number of RSIP commands through the use of the wildcard ( * ) convention of naming endpoints.

When an RSIP is sent to call agents, VISM expects an acknowledgment. If no acknowledgment is received after a timeout period, the RSIP is sent again. This process is repeated a number of times, after which, if no acknowledgment is received, an acknowledgment is assumed. You can configure both the timeout period and the number of retries with the cnfxgcpretry command.

Chapter 3 VISM Functional Description

Embedded VISM Management Function

Connection Admission Control

The VISM connection admission control (CAC) feature calculates the effect of a new call on the bandwidth utilization of the ATM PVC before a new call is either admitted or rejected.

Each call requires a connection between two endpoints and requires a certain amount of bandwidth. Bandwidth is expressed as cells per second (cps) and depends upon the following:

???Encapsulation method

???Coding/compression method

???Enabled/disabled VAD

CAC maintains a table of all currently active calls and their bandwidth requirements. When a new call is requested, CAC calculates the total bandwidth requirements of all the current calls and adds the bandwidth required by the newly requested call. The new total is then compared with the preprovisioned bandwidth (cps) of the ATM PVC.

If the new bandwidth total exceeds the preprovisioned bandwidth of the PVC, the call request is rejected. If the new bandwidth total is less than or equal to the preprovisioned bandwidth of the PVC, the call is accepted.

You can specify the values of the following VAD parameters in the CAC algorithm:

???Over-subscription drop ratio

???Voice duty cycle

VAD parameter specification allows the CAC algorithm to take into account the bandwidth savings of VAD and improves the CAC decision-making process. You can specify the values of these parameters at the card level and at the logical channel level. The default condition is for CAC to be enabled.

Embedded VISM Management Function

VISM management tools allow you to do the following:

???Configure VISM features

???Provision connections

???Display VISM configurations

???Display VISM statistics

Use any of the following tools to manage and configure the VISM card:

???CLI???See Chapter 4, ???Configuring VISM Features,??? for a description of how to configure VISM using the CLI. See Chapter 5, ???CLI Commands,??? for a description of the syntax for each CLI command.

???Third-party Simple Network Management Protocol (SNMP) manager???Permits you to display and manipulate the individual MIB objects.

???Cisco WAN Manager (CWM) program???Provides a graphics-based interface on a UNIX workstation.

Chapter 3 VISM Functional Description

Embedded VISM Management Function

Figure 3-12 shows an example of a CWM VISM Card Config screen with the card elements displayed.

Figure 3-12 VISM Card Config Screen???Card Elements Display

Chapter 3 VISM Functional Description

Embedded VISM Management Function

Figure 3-13 shows an example of a CWM VISM Card Config screen with the VISM features displayed.

Figure 3-13 VISM Card Config Screen???VISM Features Display

Refer to the WAN CiscoView for the MGX 8250 for more information on using CWM.

All three VISM management tools allow you to access and manipulate the VISM Management Information Bases (MIBs) that contain all VISM configuration settings, operating modes, and statistics.

Chapter 3 VISM Functional Description

Embedded VISM Management Function

C H A P T E R 4

Configuring VISM Features

The command line interface (CLI) is a DOS-like interface used to configure VISM cards. This chapter describes the following:

??????Using the Command Line Interface??? section on page 4-1

??????Connecting to Cisco MGX 8000 Series Platforms??? section on page 4-2

??????Configuring VISM Features??? section on page 4-6

Using the Command Line Interface

CLI commands may be followed by a string of required or optional argument identifiers and argument values. The entire string, from the command to the last argument value, is referred to as a command line. Spaces are used to separate all elements in a command line. Type the command, any necessary argument identifiers and argument values, then press Enter.

Note You must press the Enter key at the end of all CLI command lines to complete the command.

For example, the Add Endpoint command, addendpt, adds an endpoint to VISM and has three required arguments. An endpoint defines one end of a connection. The addendpt command format is as follows:

addendpt endpt-num ds1-num ds0-num

When you type a command, use argument values to represent the arguments. For example, to add an endpoint with number 10 on DS1 number 4 and DS0 number 3, the command line is as follows:

addendpt 10 4 3

Some commands require you to type an argument identifier before the argument value. For example, the Clear Alarm command, clralm, requires you to enter an identifier, -ds1, before the argument value. The clralm command format is as follows:

clralm -ds1 line-num

To clear alarms on line 4, the command line is as follows:

clralm -ds1 4

Chapter 4 Configuring VISM Features

Connecting to Cisco MGX 8000 Series Platforms

VISM Command Attributes

Use the information in Table 4-1 to determine the log file attributes, VISM card state requirements for command use, and personnel privileges for all VISM commands.

Table 4-1 VISM Command Attributes???Log File, Card State, and Privilege Level

1. The text shown represents the complete CLI command name.

Note For a complete description of the CLI commands in this chapter, see Chapter 5, ???CLI Commands.???

Connecting to Cisco MGX 8000 Series Platforms

The VISM card operates in the following MGX 8000 Series platforms:

???Cisco MGX 8850 Release 1, wide area switch

???Cisco MGX 8250, edge concentrator

???Cisco MGX 8230, edge concentrator

Each platform contains a Processor Module (PXM) back card (see Figure 4-1). Connect your CLI command administration terminal or workstation to the PXM back card???s control port???locally or remotely through a modem.

Note The MGX 8000 Series platform PXM back card contains all connections for managing VISM cards. The VISM card itself has no physical management ports.

Chapter 4 Configuring VISM Features

Connecting to Cisco MGX 8000 Series Platforms

Note The default user name is cisco. You may change this username after your initial login is complete. Consult the system administrator for valid user names.

The password prompt is displayed:

password:

Step 3 Type your password and press Enter.

For security, the password is displayed as asterisks:

password: *****

Note The default password is cisco. You may change this password after your initial login is complete. Consult the system administrator for valid passwords.

The following prompt is displayed:

card number [7]:

Step 4 If you know the VISM card slot number of the card you want to configure, proceed to Step 5. If you do not know the VISM card slot number of the card you want to configure, proceed to Step 6.

Step 5 Type the VISM card slot number and press Enter.

The VISM card prompt is displayed. See the ???VISM Card Prompt??? section on page 4-5 for more information. You have completed logging in to the PXM and VISM cards and can now perform the mandatory initial VISM card configuration. Proceed to the ???Initial VISM Configuration??? section on page 4-6.

Step 6 Type the slot number of the active PXM card (either 7 or 8) and press Enter.

The PXM card prompt is displayed:

NODENAME.1.7.PXM.a >

Step 7 Type the dspcds command to display available card types and press Enter.

A list of available card types and associated states is displayed for the MGX 8000 Series platform with which you are connected. The display is similar to the following:

NODENAME.1.7.PXM.a > dspcds

Chapter 4 Configuring VISM Features

Connecting to Cisco MGX 8000 Series Platforms

NODENAME.1.7.PXM.a >

Step 8 Identify, from the list displayed in Step 7, the slot number of the VISM card you want to configure.

Step 9 Type the cc command (to change card), the VISM card slot number identified in Step 8, and press Enter.

The VISM card prompt is displayed. See the ???VISM Card Prompt??? section on page 4-5 for more information.

You have completed logging in to the PXM and VISM cards and can now perform the mandatory initial VISM card configuration. Proceed to the ???Initial VISM Configuration??? section on page 4-6.

VISM Card Prompt

The VISM card prompt is displayed when you successfully log in to a VISM card and has the following format:

NODENAME.1.9.VISM8.a

The VISM card prompt contains the following data:

???Name of the MGX 8000 Series platform to which you are connected

???Number of the shelf???always 1

???Slot number

???Card type

???Card state???active (a) or standby (s)

Logging Out of VISM and PXM Cards

Enter one of the following commands to log out of the VISM and PXM cards:

???bye

???logout

Chapter 4 Configuring VISM Features

Configuring VISM Features

Configuring VISM Features

The CLI allows you to configure all features and functions of VISM. Configure mandatory commands when you require argument values that are different from the default. Configure optional commands when necessary.

Perform the following tasks with CLI commands to enable your VISM card applications:

1.Perform the mandatory initial VISM configuration.

2.Perform the initial card-level configuration.

3.Configure the TDM side.

4.Configure bearer processing.

Note Configure one type of signaling???CAS or CCS???for each application.

5.Configure the ATM network side.

6.Configure the call agent interface.

Note If you are using a VoIP or an AAL2 trunking application, do not configure a call agent interface.

Initial VISM Configuration

You must execute a sequence of mandatory commands, specific to your operating mode, to make the VISM card fully operational. The mandatory commands for each operating mode are listed in Table 4-2 in order of execution. The remainder of this chapter assists you with using these commands, and commands specific to your operating system.

Chapter 4 Configuring VISM Features

Configuring VISM Features

Table 4-2 Mandatory Initial VISM Configuration Command Sequence for All Operating Modes

Chapter 4 Configuring VISM Features

Configuring VISM Features

Table 4-2 Mandatory Initial VISM Configuration Command Sequence for All Operating Modes (continued)

1.The cnfvismmode command may be mandatory or optional, depending upon the operating mode with which the VISM card is seen as displayed on your terminal. A VISM card that is not configured is initially displayed in the VoIP operating mode. Subsequent accesses to the VISM card result in the card being displayed in the VoIP operating mode or in the operating mode you have last configured for the card. If the card is displayed as being in the wrong operating mode, the cnfvismmode command is mandatory to change the operating mode. Use the dspvismparam command to verify the VISM card???s current operating mode.

Initial Card Level Configuration

You must complete the following configuration tasks when you initially configure your VISM card.

1.Configure the operating mode.

2.Allocate resources.

3.Configure the connection admission control (CAC).

4.Bring VISM into service.

Configuring the Operating Mode

Complete the following steps to configure the correct operating mode for your VISM card immediately after power is applied:

Step 1 Type the dspvismparam command and press Enter to determine the current VISM operating mode.

Note A new VISM card (one that has not been configured) is displayed by default in VoIP operating mode.

The operating mode of the VISM card is displayed in the first line of the VISM card parameter list.

Step 2 If the VISM card operating mode displayed in Step 1 is correct for your application, proceed to the ???Allocating Resources??? section on page 4-9. If the VISM card operating mode displayed in Step 1 is not correct for your application, proceed to Step 3.

Chapter 4 Configuring VISM Features

Configuring VISM Features

Step 3 Type the cnfvismmode command, an oper-mode argument value, and press Enter to configure the VISM operating mode. Specify the oper-mode argument with one of the following values:

???1 = VoIP switching/VoIP trunking

???2 = AAL2 trunking

???3 = Switched AAL1 SVC

???7 = Switched AAL2 SVC

???8 = Switched AAL2 PVC???this mode is not supported in VISM Release 3.0

???9 = VoIP and Switched ATM AAL1 SVC

You have completed configuring the operating mode for your VISM card. Proceed to the ???Allocating Resources??? section on page 4-9.

Allocating Resources

Complete the following steps to allocate resources???virtual ports, controller resources, and codec templates???to your VISM card.

Step 1 Type the addport command and press Enter to add a virtual port to your VISM card.

This command adds an ATM port on a VISM. There are no arguments for this command. When you add the ATM port, the bandwidth, VPI range, and VCI range are determined. The VPI range is a single VPI value, the slot ID. The added port is not detected by the controller until you create a resource partition (refer to Step 2). The VISM ATM port is pseudo physical.

Step 2 Type the addrscprtn command, the control-id argument value 1, and press Enter to specify the controller resources.

Note Always specify the control-id argument value as 1.

A port can be controlled by more than one controller (for example PNNI and PAR), but supports only one controller at a time. VISM can create one resource partition for each controller in a non-overlapping way. The controller number you specify associates a resource partition to a controller. All resources of a port are associated with the resource partition you specify. When you add a resource partition, the associated controller detects the port as limited by the resource partition.

Step 3 Type the cnfcodectmpl command, a template-num argument value, and press Enter to specify the codec template used with your VISM card. Specify the template-num argument with one of the following values:

???1 = G.711u, G.711a, G.726-16K, G.726-24K, G.726-32K, G.726-40K, G.729a, and G.729ab codecs, and clear channel

Note Template 1 is not supported for the VoIP operating mode.

???2 = G.711u and G.711a uncompressed codecs, and clear channel

Chapter 4 Configuring VISM Features

Configuring VISM Features

???3 = G.711u, G.711a, G.726-16k, G.726-24k, G.726-32k, G.726-40k, G.729a, and G.729ab codecs and clear channel

Note Codec template number 3 = template number 1 with T.38 support added. Maximum channels = 120.

???4 = G.711u, G.711a, G. 726-16k, G.726-24k, G.726-32k, G.726-40k, G.729a, G.729ab, G.723.1-H, G.723.1a-H, G.723.1-L, G.723.1a-L codecs and clear channel

Note Template 4 supports a maximum of 64 channels for VISM, and a maximum of 144 channels for VISM-PR. The G.723.1 codecs are not supported for the VISM card.

You have completed allocating resources to your VISM card. Proceed to the ???Configuring Connection Admission Control??? section on page 4-10.

Configuring Connection Admission Control

Complete the following steps, which allow you to:

???Enable or disable CAC.

???Define CAC parameters.

???Configure voiceband data policies for fax/modem carrier loss and fax/modem CAC failure events.

Step 1 Type the cnfcac command, a cac-enable argument value, and press Enter to enable or disable CAC on your VISM card. Specify the argument with one of the following values:

???1 = On

???2 = Off

Note If your application does not require CAC, specify the cac-enable argument as value 2 in Step 1 and proceed to the ???Placing the VISM Card In Service??? section on page 4-11.

Step 2 Type the cnfcacparams command, vad-duty-cycle and vad-tol argument values, and press Enter to configure card level CAC parameter values for VAD tolerance and duty cycle, which are used in CAC algorithms. Specify the arguments with the following values:

???vad-duty-cycle: In the range from 1 to 99 (default = 61)

???vad-tol: In the range from 0 to 10000 (default = 100)

Step 3 Type the cnfconcacparams command, lcn, vad-tol, and vad-duty-cycle argument values, and press Enter to configure values for VAD tolerance and duty cycle, which are used in the CAC algorithms, for a specified logical connection number (PVC). Specify the arguments with the following values:

???lcn: In the range from 131 to 510

???vad-tol: In the range from 1 to 10000 (default = 100)

???vad-duty-cycle: In the range from 1 to 99 (default = 61)

Chapter 4 Configuring VISM Features

Configuring VISM Features

Step 4 Type the cnfvbdpol command, carrier-loss-pol and cac-reject-pol argument values, and press Enter to specify card level default policies for a fax/modem carrier loss and a fax/modem CAC failure. Specify the arguments with the following values:

???carrier-loss-pol:

???1 = Revert to the previous codec.

???2 = Maintain the upspeed codec.

???cac-reject-pol:

???1 = Delete the connection.

???2 = Maintain the connection and revert to the previous codec.

You have completed configuring CAC on your VISM card. Proceed to the ???Placing the VISM Card In Service??? section on page 4-11.

Placing the VISM Card In Service

Type the cnfgwis command and press Enter to place the VISM card in service. The VISM card prompt terminates with an a to indicate the in-service state:

NODENAME.1.9.VISM8.a

Placing the VISM Card Out of Service

Type the cnfgwoos command, a oos-method argument value, and press Enter to place the VISM card out of service. Specify the oos-method argument with one of the following values:

???2???Forceful

???3???Graceful

The VISM card prompt terminates with an s to indicate the out-of-service (standby) state:

NODENAME.1.9.VISM8.s

Configuring the TDM Side

You must perform the following tasks to configure the TDM side of your networking application:

1.Configure T1 and E1 lines.

2.Configure VISM card clocking.

3.Configure DS0 channels.

Configuring T1 and E1 Lines

This section deals with the configuration of the eight physical T1/E1 ports on the VISM back card or, if bulk distribution is used, the equivalent ports being fed from the Service Resource Module (SRM) card.

Chapter 4 Configuring VISM Features

Configuring VISM Features

Complete the following steps to:

???Add and configure your eight T1 or E1 line ports on the VISM back card.

???Add and configure your eight T1 and E1 line ports on the SRM card if your application requires bulk distribution.

Note You can configure the DS0s on a line after a line is added and configured.

Step 1 Type the addln command, a line-num argument value, and press Enter to add a line to your VISM card. Specify the line-num argument value in the range 1 to 8.

The VISM card prompt and line number are displayed.

Step 2 Type the cnfln command, line-num, line-code, line-length, clock-source, line-type, and loopback-detection argument values, and press Enter to specify the operating parameters for the line added in Step 1. Specify the arguments with the following values:

???line-num: In the range from 1 to 8

???line-code:

???2 = B8ZS for T1 lines

???3 = HDB3 for E1 lines

???4 = AMI for T1 or E1 lines

???line-length:

???8 = AX-SMB-8E1 and AX-R-SMB-8E1 back card types

???9 = AX-RJ48-8E1 and AX-R-RJ48-8E1 back card types

???10 to 15 = T1 back cards, where 10 = 0 to 131 ft, 11 = 131 to 162 ft, 12 = 262 to 393 ft, 13 = 393 to 524 ft, 14 = 524 to 655 ft, and 15 = over 655 ft

???clock-source:

???1 = Loop clock

???2 = Local clock

???line-type:

???1 = DSx1ESF

???2 = DSx1D4

???3 = E1

???4 = E1CRC

???5 = E1MF

???6 = E1MFCRC

???7 = E1 Clear

???8 =

???9 =

???loopback-detection:

???1 = Disabled

???2 = Enabled

Chapter 4 Configuring VISM Features

Configuring VISM Features

Step 3 Type the cnfalm command, argument identifiers and argument values???-ds1 line-num -red red-sev -rai rai-sev -neu ne-alarm-up -ned ne-alarm-down -net ne-alarm-thresh -feu fe-alarm-up -fed fe-alarm-down -fet fe-alarm-thresh???and press Enter to configure a line for alarm condition handling. Specify the arguments with the following values:

???-ds1 line-num: In the range from 1 to 8

???-red red-sev:

???1 = Minor

???2 = Major

???-rai rai-sev:

???1 = Minor

???2 = Major

???-neu ne-alarm-up: In the range from 1 to 65535

???-ned ne-alarm-down: In the range from 1 to 65535

???-net ne-alarm-thresh: In the range from 1 to 65535

???-feu fe-alarm-up: In the range from 1 to 65535

???-fed fe-alarm-down: In the range from 1 to 65535

???-fet fe-alarm-thresh: In the range from 1 to 65535

Step 4 Type the cnflnsig command, line-num and line-signal-type argument values, and press Enter to configure the signaling mode for the specified line. Specify the line-num and line-signal-type arguments with the following values:

???line-num: In the range from 1 to 8

???line-signal-type:

???1 = CAS

???2 = CCS

???3 = No signaling

Note If you choose CAS signaling for a VISM/VISM-PR E1 line, the supported operating modes are AAL2 trunking and VoIP trunking.

Step 5 Type the cnftrunkcond command, line-num and trunk-cond-enable argument values, and press Enter to enable or disable trunk line conditioning on a line. Specify the arguments with the following values:

???line-num: In the range from 1 to 8

???trunk-cond-enable:

???1 = On

???2 = Off

If you enable trunk line conditioning, VISM conditions the affected DS0 when an alarm indication signal (AIS) is detected on the ATM side. Trunk line conditioning consists of transmitting an idle code pattern for 2.5 seconds followed by the seized code specified in the cnfcascode command.

Note This command is not allowed if endpoints or CCS channels are enabled on the line.

Chapter 4 Configuring VISM Features

Configuring VISM Features

Step 6 Type the addlnloop command, a line-num argument value, and press Enter to set a specified line to the local loopback state. Specify the line-num argument in the range from 1 to 8.

Use the dellnloop command to remove the local loopback state on a VISM line.

Note The VISM CLI has no command for setting a line to the remote loopback state. Use the cnfbert command on the PXM card to set a line to the remote loopback state.

You have completed configuring T1 and E1 lines for your VISM card. Proceed to the ???Placing T1 and E1 Lines In Service??? section on page 4-14.

Placing T1 and E1 Lines In Service

Type the cnflnis command, a line-num argument value, and press Enter to place a T1 or E1 line in service. Specify the line-num argument in the range from 1 to 8.

Note If the VISM card is rebooted, this information configuration using this command is lost.

Placing T1 and E1 Lines Out of Service

Type the cnflnoos command, line-num and oos-method argument values, and press Enter to place a T1 or E1 line out of service. Specify the arguments with the following values:

???line-num: In the range from 1 to 8

???oos-method:

???2 = Forceful

???3 = Graceful

Configuring the PXM and VISM Cards Clocking Source

Complete the following steps to configure the clocking source on your PXM and VISM cards.

Note Refer to Appendix A, ???VISM and VISM-PR Card Clocking Options,??? and the ???Expanded Clock Source Selection??? section on page 4-69 for additional instructions on using the commands and specifying argument values to configure the clocking source on your PXM and VISM cards.

Step 1 Examine the entire configuration of the MGX 8000 Series platform to determine the single clock source.

The type of equipment connected to the VISM T1 or E1 lines may dictate this choice. If the selected clock source is from one of the VISM T1 or E1 lines, that line must be connected to port 1 of the VISM back card. See Figure 1-3 on page 1-4 for more information on VISM back cards and port locations.

Chapter 4 Configuring VISM Features

Configuring VISM Features

Step 2 Type the cnfclksrc command, slot-num.port-num, and clk-type argument values, and press Enter to configure the PXM card clock source. Specify the arguments with the following values:

???slot-num.port-num:

???slot-num = 7 or 8, port-num = 1 to n.

Note Ensure that you type the period with no spaces on either side, between the slot-num argument value and the port-num argument value.

???clk-type argument values:

???P = Primary

???S = Secondary

???N = Null (no external clocking source; use the PXM card???s internal crystal) Specify the cnfclksrc command argument values according to the following rules:

???If the clock source is the external BITS clock (a T1 or E1 port on the PXM back card), specify the configuration as:

cnfclksrc 7.35 P

Note Type 7 for the slot number regardless of the PXM card???s location in the chassis. Type 35 for the port number???the BITS port is always port 35.

??? If the clock source is an external signal on one of the PXM OC3 ports, specify the configuration as:

cnfclksrc 7.n P

Note Type 7 for the slot number regardless of the PXM card???s location in the chassis. The n port parameter value is the OC3 port number in the range 1 to 4.

???If the clock source is the PXM???s internal crystal and no other clock source has been specified, do not configure the clock source. The crystal is the automatic default.

???If you want to change the clocking source from external to the PXM card???s internal crystal, specify the configuration as:

cnfclksrc 7.X N

Note Type 7 for the slot number regardless of the PXM card???s location in the chassis. The X argument value is the either 35 or the OC3 port number, depending upon which is the currently specified source. The null port number argument value cancels the previous configuration and returns the clocking source to the default internal crystal.

??? If the clock source is from a line on a VISM card, specify the configuration as:

cnfclksrc y.1 P

Chapter 4 Configuring VISM Features

Configuring VISM Features

Note The y argument value is the actual slot number of the VISM card. Always type 1 for port argument value, which represents the line number in this configuration. VISM-PR cards do not have this requirement.

Step 3 Type the cnfln command, the line-num, line-code, line-length, clock-source, line-type, and loop-detection argument values, and press Enter to configure the clocking option defined in Step 2 on your VISM card. Specify the arguments with the following values:

???line-num: In the range from 1 to 8

???line-code:

???2 = B8ZS for T1

???3 = HDB3 for E1

???4 = AMI for T1 or E1

???line-length:

???8 = E1 lines with AX-SMB-8E1 and AX-R-SMB-8E1 back card types

???9 = E1 lines with AX-RJ48-8E1 and AX-R-RJ48-8E1 back card types

???In the range from 10 to 15 = T1 lines

???clock-source:

???1 = Loop clock???clocking from the T1 or E1 line

Note If the clocking source is from a line on your VISM card, you must configure that line???which must be line 1???as loop clock. Configure all remaining lines on all remaining VISM cards as local.

??? 2 = Local???clocking from the PXM card

Note You must configure all lines on all VISM cards as local if the clocking source to the

VISM cards is from the PXM card.

???line-type:

???1 = DSx1ESF

???2 = DSx1D4

???3 = E1

???4 = E1CRC

???5 = E1MF

???6 = E1MFCRC

???7 = E1 clear

???loop-detection:

???1 = Disabled

???2 = Enabled

Chapter 4 Configuring VISM Features

Configuring VISM Features

Note You must include all argument values when using the cnfln command; however, the line-num and clock-source are the only relevant arguments for configuring the clocking source on your VISM cards.

You have completed configuring the clocking source for your PXM and VISM cards. Proceed to the ???Configuring DS0 Channels??? section on page 4-17.

Configuring the PXM1E or PXM45 Card as Clocking Source

Use the cnfncdpclksrc command to configure the PXM1E or PXM45 card as the primary clock source.

Use the following commands to display and verify your configuration:

???dspncdpclkinfo

???dspncdpclksrc

Refer to the ???Related Documentation??? section on page xiv for the appropriate document to use the commands in this section.

Configuring DS0 Channels

You are now ready to configure the 24 (T1) or 31 (E1) DS0 channels on the VISM card???s T1 or E1 lines. Table 4-3 describes the VISM/VISM-PR DS0 density when the cards are used in combination with the supported codecs.

Table 4-3 VISM/VISM-PR DS0 Density with Codec Support

You must complete the following tasks to configure a DS0 channel:

1.Add and configure DS1 line and DS0 endpoints.

2.Configure CCS or CAS signaling.

Chapter 4 Configuring VISM Features

Configuring VISM Features

Add and Configure DS1 Lines and DS0 Endpoints

Complete the following steps to add and configure a DS1 line and DS0 endpoints:

Step 1 Type the addendpt command, endpt-num, ds1-num, and ds0-num argument values, and press Enter to add a DS1 line and a DS0 endpoint. This step ensures that a call with a specified endpoint is tied to a specific line and channel. Specify the arguments with the following values.

Note If you choose CAS signaling for a VISM/VISM-PR E1 line, the supported operating modes are AAL2 trunking and VoIP trunking.

???endpt-num:

???For template number 1:

For VISM, in the range from 1 to 145

For VISM-PR T1, in the range from 1 to 192 For VISM-PR E1, in the range from 1 to 248

???For template number 2:

For VISM T1, in the range from 1 to 192 For VISM E1, in the range from 1 to 248

???For template number 3:

For VISM, in the range from 1 to 120

For VISM-PR T1, in the range from 1 to 192 For VISM-PR E1, in the range from 1 to 248

???For template number 4:

For VISM-PR, in the range from 1 to 144

???ds1-num: The physical line number in the range 1 to 8

???ds0-num:

???For T1 lines, from 1 to 24

???For non-CAS E1 lines, from 1 to 31

???For CAS E1 lines, from 1 to 15 and 17 to 31

Note You must specify DS0 16 for E1 lines if your application requires CAS signaling.

Step 2 Type the addendpts command, start-endpt, start-line-num, start-ds0-num, and endpt-quantity argument values, and press Enter to add a number of endpoints in one command. Specify the arguments with the following values:

???start-endpt:

???For template number 1:

For VISM, in the range from 1 to 145

For VISM-PR T1, in the range from 1 to 192 For VISM-PR E1, in the range from 1 to 248

Chapter 4 Configuring VISM Features

Configuring VISM Features

???For template number 2:

For VISM T1, in the range from 1 to 192 For VISM E1, in the range from 1 to 248

???For template number 3:

For VISM, in the range from 1 to 120

For VISM-PR T1, in the range from 1 to 192 For VISM-PR E1, in the range from 1 to 248

???For template number 4:

For VISM-PR, in the range from 1 to 144

???start-line-num (DS1 line): In the range from 1 to 8

???start-ds0-num (DS0 channel):

???For T1 lines, from 1 to 24

???For non-CAS E1 lines, from 1 to 31

???For CAS E1 lines, from 1 to 15 and 17 to 31

???endpt-quantity:

???For template number 1:

For VISM, in the range from 1 to 145

For VISM-PR T1, in the range from 1 to 192 For VISM-PR E1, in the range from 1 to 248

???For template number 2:

For VISM T1, in the range from 1 to 192 For VISM E1, in the range from 1 to 248

???For template number 3:

For VISM, in the range from 1 to 120

For VISM-PR T1, in the range from 1 to 192 For VISM-PR E1, in the range from 1 to 248

???For template number 4:

For VISM-PR, in the range from 1 to 144

Step 3 Type the addendptloop command, an endpt-num argument value, and press Enter to place a specific endpoint???and so a specific DS1/DS0???into the loopback state in the TDM direction. Specify the endpt-num argument value from the following ranges:

???For template number 1:

???For VISM, in the range from 1 to 145

???For VISM-PR T1, in the range from 1 to 192

???For VISM-PR E1, in the range from 1 to 248

???For template number 2:

???For VISM T1, in the range from 1 to 192

???For VISM E1, in the range from 1 to 248

Chapter 4 Configuring VISM Features

Configuring VISM Features

???For template number 3:

???For VISM, in the range from 1 to 120

???For VISM-PR T1, in the range from 1 to 192

???For VISM-PR E1, in the range from 1 to 248

???For template number 4:

???For VISM-PR, in the range from 1 to 144

Step 4 Type the cnfds0loop command, line-num, ds0-num, and loopback-type argument values, and press Enter to place a specific DS1/DS0 into one of three loopback states. Specify the arguments with the following values:

???line-num: In the range from 1 to 8

???ds0-num:

???In the range from 1 to 31 for E1 lines

???In the range from 1 to 24 for T1 lines

???loopback-type:

???1 = No loopback

???2 = Remote loopback

???3 = Local loopback

You have completed adding and configuring a DS1 line and DS0 endpoints. Proceed to one of the following sections:

??????Configuring TDM Side Signaling for Applications Using CCS??? section on page 4-20.

??????Configuring TDM Side Signaling for Applications Using CAS??? section on page 4-23.

Configuring TDM Side Signaling for Applications Using CCS

Note If your application requires CAS signaling, proceed to the ???Configuring TDM Side Signaling for Applications Using CAS??? section on page 4-23.

CCS signaling uses a dedicated channel on a DS1 line to carry the signaling for the other channels on the line. You must identify the signaling channel to the VISM card. CCS signaling is used for the following operating modes:

???VoIP trunking.

???AAL2 trunking???Signaling is transported across the trunk as Q.931 messages in ATM cells using AAL5.

???Switched AAL2 PVC???Signaling is backhauled to the call agent using Q.921 frames on the TDM side and RUDP/UDP/IP/Q.2931 on the call agent side.

Chapter 4 Configuring VISM Features

Configuring VISM Features

Complete the following steps to add and configure CCS signaling:

Step 1 Type the addccs command, line-num, ds0-num, and lcn argument values, and press Enter to add a CCS channel to your VISM card. Specify the arguments with the following values:

???line-num: In the range from 1 to 8

???ds0-num:

???In the range from 1 to 24 for T1

???In the range from 1 to 31 for E1

???lcn: In the range from 131 to 510

Step 2 If you are configuring CCS for the AAL2 trunking operating mode, the CCS configuration is complete. Proceed to the ???Configuring Bearer Processing??? section on page 4-27. If you are configuring CCS for the VoIP switching operating mode, you must create a Q.921 link access protocol for the D channel (LAPD) link for the channel and specify its argument values. Proceed to Step 3.

Step 3 Type the addlapd command, line-num, ds0-num, |lapd-side| and |lapd-app-type| argument values, and press Enter to add an ISDN PRI channel on a DS1/DS0.

Specify the arguments with the following values:

???line-num: Type the value used in Step 1.

???ds0-num: Type the value used in Step 1.

???|lapd-side|:

???1 = Network (default)

???2 = User

???|lapd-app-type|:

???1 = PRI (default)

???2 = GR-303 (currently unsupported)

Step 4 Type the cnflapdtype command, line-num, ds0-num, and lapd-type argument values, and press Enter to specify the LAPD stack type. Specify the arguments with the following values:

???line-num: Type the value used in Step 1.

???ds0-num: Type the value used in Step 1.

???lapd-type:

???1 = ITU

???3 = ATT5ESSPRA

???4 = ATT4ESS

???6 = NTDMS100PRA

???7 = VN2 or 3

???8 = INSNet

???9 = TR6MPC

???10 = TR6PBX

???12 = AUSP

???13 = NIL

???14 = SSETSI

Chapter 4 Configuring VISM Features

Configuring VISM Features

???15 = BC303TMC

???16 = BC303CSC

???17 = NTDMS250

???18 = Bellcore

???19 = NI2

Step 5 Type the cnflapdwinsize command, line-num, ds0-num, and iframe-num argument values, and press Enter to specify the LAPD window size. The iframe-num value is the maximum number of outstanding I-frames that can be accumulated before sending an acknowledgment. Specify the arguments with the following values:

???line-num: Type the value used in Step 1.

???ds0-num: Type the value used in Step 1.

???iframe-num: In the range from 1 to 127

Step 6 Type the cnflapdretrans command, line-num, ds0-num, and n200 argument values, and press Enter to specify the maximum allowable frame retransmissions. Specify the arguments with the following values:

??? line-num: Type the value used in Step 1.

??? ds0-num: Type the value used in Step 1.

??? n200: In the range from 1 to 10

Step 7 Type the cnflapdtimer command, line-num, ds0-num, frame-trans-time, and frame-exchange-time argument values, and press Enter to specify the two LAPD timers. Specify the arguments with the following values:

???line-num: Type the value used in Step 1.

???ds0-num: Type the value used in Step 1.

???frame-trans-time (time, at the end of which, a frame transmission can be initiated):

???1000 to 1023000 for PRI (specify in increments of 50 ms)

???100 to 350 for GR-303 (specify in increments of 50 ms)

Note The specified value for frame-trans-time must be less than the specified value for frame-exchange-time.

???frame-exchange-time (maximum time allowed without frames being exchanged) argument values:

???1000 to 1023000 for PRI (specify in increments of 10000 ms)

???10000 to 300000 for GR-303 (specify in increments of 10000 ms)

You have completed adding and configuring CCS. Proceed to the ???Configuring Bearer Processing??? section on page 4-27.

Chapter 4 Configuring VISM Features

Configuring VISM Features

Configuring TDM Side Signaling for Applications Using CAS

Note If your application requires CCS, see the ???Configuring TDM Side Signaling for Applications Using CCS??? section on page 4-20.

CAS signaling is used for the following operating modes:

???VoIP trunking.

???VoIP switching???TDM side signaling is translated in xGCP messages to the call agent.

???AAL2 trunking???Signaling is transported across the trunk as Q.931 messages in AAL2 cells using AAL5.

???Switched AAL2 PVC???Signaling is backhauled to the call agent using xGCP on the TDM side and Reliable User Datagram Protocol (RUDP)/User Datagram Protocol (UDP)/IP/Q.2931 on the call agent side.

Complete the following steps to add and configure CAS signaling.

Note If you choose CAS signaling for a VISM/VISM-PR E1 line, the supported operating modes are AAL2 trunking and VoIP trunking. In addition Step 1 through Step 8 and Step 11 through Step 13 are used only in the VoIP switching and switched AAL2 PVC operating modes.

Step 1 Type the cnfcasparamsource command, endpt-num and cas-source argument values, and press Enter to configure the source of CAS-related timer parameters for a specified endpoint. Specify the arguments with the following values:

???endpt-num:

???For template number 1:

For VISM, in the range from 1 to 145

For VISM-PR T1, in the range from 1 to 192 For VISM-PR E1, in the range from 1 to 248

???For template number 2:

For VISM T1, in the range from 1 to 192 For VISM E1, in the range from 1 to 248

???For template number 3:

For VISM, in the range from 1 to 120

For VISM-PR T1, in the range from 1 to 192 For VISM-PR E1, in the range from 1 to 248

???For template number 4:

For VISM-PR, in the range from 1 to 144

???cas-source:

???1 = CAS application file

???2 = Current VISM MIB file

Chapter 4 Configuring VISM Features

Configuring VISM Features

Note The cnfcasparamsource command permits different CAS-related timer values for different endpoints, but all are associated with the same CAS variant.

Step 2 Type the cnfcasonhooktime command, endpt-num and onhooktime argument values, and press Enter to specify the minimum time an on hook-pattern must be present to be recognized as an on-hook signal. Specify the arguments with the following values:

??? endpt-num: Type the value used in Step 1.

??? onhooktime: In the range from 10 to 1000

Step 3 Type the cnfcasoffhooktime command, endpt-num and offhooktime argument values, and press Enter to specify the minimum time an off-hook pattern must be present to be recognized as an off-hook signal. Specify the arguments with the following values:

??? endpt-num: Type the value used in Step 1.

??? offhooktime: In the range from 10 to 1000

Step 4 Type the cnfcaswinktime command, endpt-num, min-make-time, max-make-time, and min-break-time argument values, and press Enter to specify the minimum and maximum make times and the minimum break time. A wink begins with an on-hook pattern, goes to off-hook, and returns to on-hook. Specify the arguments with the following values:

???endpt-num: Type the value used in Step 1.

???min-make-time: In the range from 10 to 1000

???max-make-time: In the range from 10 to 3000

???min-break-time: In the range from 10 to 1000

Note All three make and break duration time argument values must be observed for the signaling sequence to be recognized as a wink.

Step 5 Type the cnfcasglaretime command, endpt-num and glaretime argument values, and press Enter to specify the glare time. Specify the arguments with the following values:

???endpt-num: Type the value used in Step 1.

???glaretime: In the range from 10 to 1000

Step 6 Type the cnfcasguardtime command, endpt-num and guardtime argument values, and press Enter to specify the guard time. Specify the arguments with the following values:

???endpt-num: Type the value used in Step 1.

???guardtime argument values:

???In the range from 10 to 1000

Step 7 Type the cnfcasdialdelay command, endpt-num and dial-delay argument values and press Enter to configure the CAS dial delay (wait time).

Dial delay is the time that VISM waits before sending dialing digits after sending an off-hook event.

Note The cnfcasdialdelay command applies to immediate start protocols only.

Specify the arguments with the following values:

Chapter 4 Configuring VISM Features

Configuring VISM Features

???endpt-num: Type the value used in Step 1.

???dial-delay: In the range from 10 to 1000

Step 8 To configure CAS for the switched AAL2 PVC operating mode, proceed to Step 11. To configure CAS for the AAL2 trunking operating mode, proceed to Step 9.

Step 9 Type the cnfcascode command, endpt-num, |endpt-num|, idle-code, and seized-code argument values and press Enter to specify the idle and seized codes for one or more endpoints. Specify the arguments with the following values:

???endpt-num: Type the value used in Step 1.

Note If the |endpt-num| optional argument value is used in combination with this argument, the endpt-num argument value is the first endpoint in a consecutive range of endpoints.

???|endpt-num|:

???For template number 1:

For VISM, in the range from 1 to 145

For VISM-PR T1, in the range from 1 to 192 For VISM-PR E1, in the range from 1 to 248

???For template number 2:

For VISM T1, in the range from 1 to 192 For VISM E1, in the range from 1 to 248

???For template number 3:

For VISM, in the range from 1 to 120

For VISM-PR T1, in the range from 1 to 192 For VISM-PR E1, in the range from 1 to 248

???For template number 4:

For VISM-PR, in the range from 1 to 144

Note The |endpt-num| optional argument value indicates the last endpoint in a consecutive range of endpoints.

???idle-code (4-bit idle code): In the range from 0 to 15 represents the four A, B, C, and D signaling as bits 3, 2, 1, and 0 respectively with bit 3 the most significant.

???seized-code (4-bit seized code): In the range from 0 to 15 represents the four A, B, C, and D signaling as bits 3, 2, 1, and 0 respectively with bit 3 the most significant.

Chapter 4 Configuring VISM Features

Configuring VISM Features

Step 10 Type the cnfds0localcas command, line-num, ds0-num, local-cas-enable, and local-cas-pattern argument values, and press Enter to configure a local CAS bit pattern for a T1 line and DS0.

Note The cnfds0localcas command is not allowed if the line is E1 or not enabled, or the DS0 is in a remote loop state, or if the line signaling type is CAS.

Specify the arguments with the following values:

???line-num: 1 to 8 (T1 lines only)

???ds0-num: 1 to 24

???local-cas-enable:

???1 = Enable

???2 = Disable

???local-cas-pattern: In the range from 1 (default) to 15

Note If the local-cas-enable argument value = 1, you must specify a local-cas-pattern argument value.

Step 11 Type the addcasvar command, var-name, file-name and |source| argument values, and press Enter to add a CAS variant to your VISM card.

Note A file containing the CAS variant information must be downloaded to your MGX 8000 Series PXM card using a separate application (TFTP) before you can execute this command.

Specify the arguments with the following values:

???var-name (name of the CAS variant): A text string of 1 to 64 alphanumeric characters.

???file-name:

???wink_did_dod.o = wink start

???ground_start.o = ground start

???wink_did_dod_mf.o = wink start multifrequency

???q50.o = Q.50

???fgd_ea_incoming.o = for endpoints connected to an end office

???fgd_ea_outgoing.o = for endpoints connected to an access carrier

???fgd_os_e911.o = for endpoints connected to FDG OSS (Feature group D operator services system.

???loop_start.o = loop start

???delay_did_dod.o = dial delay, DTMF

???delay_did_dod_mf.o = dial delay, MF

???immed_did_dod.o = immediate start

???immed_did_dod_mf.o = immediate start, MF

???In the range from 1 to 32 alphanumeric characters???user configured files only.

Chapter 4 Configuring VISM Features

Configuring VISM Features

???|source| (CAS variant file location):

???1 = Unspecified. If TFTP domain is configured, the location is the TFTP server. If not found in the TFTP server, the file is treated as built-in.

???2 = User configured (built-in) file location.

???3 = External???resides on the TFTP server.

Step 12 Type the cnfcasvar command, var-name, country-code, partial-time, critical-time, and interdigit-timeout argument values, and press Enter to configure a CAS variant and CAS timing parameters for the variant added in Step 11. Specify the arguments with the following values:

???var-name: Type the value used in Step 11.

???country-code: The two-character country code of the variant.

???partial-time (partial dial time): In the range from 10 to 10000, in increments of 10 seconds.

???critical-time (critical timing): In the range from 0 to 10000, in increments of 10 seconds.

???interdigit-timeout (interdigit timeout for MF digits): In the range from 1 to 10 seconds.

Step 13 Type the cnfcasendpt command, endpt-num and var-name argument values, and press Enter to associate an endpoint with a CAS variant. Specify the arguments with the following values:

???endpt-num: Type a value used in Step 9.

???var-name: Type the value used in Step 11.

You have completed adding and configuring CAS signaling. Proceed to the ???Configuring Bearer Processing??? section on page 4-27.

Configuring Bearer Processing

Processing of the bearer payload takes place either upon receipt of the payload from a T1 or E1 line or prior to transmission over a T1 or E1 line. You must complete the following tasks to configure bearer processing:

1.Configure codecs.

2.Configure ECAN.

3.Configure jitter.

Configuring Codecs

Complete the following steps to assign and configure a codec template:

Step 1 Type the cnfcodectmpl command, a template-num argument value, and press Enter to specify a codec template. Specify the template-num argument value from the following:

???1 = G.711u, G.711a, G.726-16k, G.726-24k, G.726-32k, G.726-40k, G.729a, and G.729ab codecs, and clear channel

Note Template 1 is not supported for the VoIP operating mode.

Chapter 4 Configuring VISM Features

Configuring VISM Features

??? 2 = G.711u and G.711a codecs, and clear channel

Note The cnfcodectmpl command is included in the ???Allocating Resources??? section on page 4-9 but is included here for your convenience.

???3 = G.711u, G.711a, G.726-16k, G.726-24k, G.726-32k, G.726-40k, G.729a, and G.729ab codecs, clear channel, and T.38 fax transfer

???4 = G.711u, G.711a, G. 726-16k, G.726-24k, G.726-32k, G.726-40k, G.729a, G.729ab, G.723.1-H, G.723.1a-H, G.723.1-L, G.723.1a-L codecs and clear channel

Step 2 Type the cnfcodecparams command, codec-type, codec-pkt-period, |preference, codec-string, and iana-type| argument values, and press Enter to specify various codec parameters for use in the VoIP operating mode.

The packetization period is defined in three separate commands depending upon the ATM method used:

???Use the cnfcodecparams command for VoIP switching applications. Complete this step.

???Use the addcid command for AAL2 trunking applications. See the ???Configuring AAL2 Trunking Operating Mode Parameters??? section on page 4-36.

???Use the addrtpcon command for AAL2 trunking applications.

???Use the cnfprofelemvoice command for switched AAL2 PVC applications. See the ???Configuring Switched AAL2 PVC Operating Mode Parameters??? section on page 4-38.

Specify the arguments with the following values:

???codec-type: In the range from 1 to 14.

???codec-pkt-period:

???10

???20

???30

???40

???60

???preference:

???0 = Ignore preference

???In the range from 1 (highest) to 13 (lowest).

???codec-string: In the range from 1 to 20 ASCII characters.

???iana-type (IANA registered codec type): In the range from 0 to 96.

Step 3 Type the cnfcodecneg command, the codec-priority argument value, and press Enter to specify a codec preference order when there are several codec lists???from the call agent local connection option (LCO) list, local MIB, or a list received from the remote gateway in the session description protocol (SDP) data. Specify the codec-priority argument value with one of the following:

???1 = LCO list, remote SDP data list, local MIB

???2 = LCO list, local MIB, remote SDP data list

???3 = Remote SDP data list, LCO list, local MIB

???4 = Remote SDP data list, local MIB, LCO list

Chapter 4 Configuring VISM Features

Configuring VISM Features

???5 = Local MIB, LCO list, remote SDP data list

???6 = Local MIB, remote SDP data list, LCO list

You have completed assigning and configuring the codec template. Proceed to the ???Configuring ECAN??? section on page 4-29.

Configuring ECAN

Complete the following steps to enable and configure echo cancellation (ECAN) on a line-by-line basis:

Step 1 Type the cnfecanenable command, line-num and ecan-enable argument values, and press Enter to enable (or disable) ECAN for a line. Specify the arguments with the following values:

???line-num: In the range from 1 to 8.

???ecan-enable:

???1 = Disable

???2 = Enable

Step 2 Type the cnfecanrec command, line-num and res-echo-control argument values, and press Enter to set the residual echo control. Specify the arguments with the following values:

???line-num: Type the value used in Step 1.

???res-echo-control:

???1 = Cancel only

???2 = Suppress residual

???4 = Comfort noise

Step 3 Type the cnfecantail command, line-num and max-ecan-tail argument values, and press Enter to specify the ECAN algorithm???s maximum tail length. Specify the arguments with the following values:

???line-num: Type the value used in Step 1.

???max-ecan-tail (defined in milliseconds):

???24

???32

???48

???64

???80

???96

???112

???128

Chapter 4 Configuring VISM Features

Configuring VISM Features

Step 4 Type the cnferl command, the echo-ret-loss argument value, and press Enter to specify the ECAN algorithm???s return echo loss applied by ECAN DSPs, in decibels. Specify the echo-ret-loss argument with one of the following values:

???echo-ret-loss:

???1 = 0 dB

???2 = 3 dB

???3 = 6 dB

???4 = 1 dB

Step 5 Type the cnfconvbdpol command, lcn, carrier-loss-pol, and cac-reject-pol argument values, and press Enter to specify the fax/modem upspeed connection admission control (CAC) failure and carrier loss policies for a channel. Specify the arguments with the following values:

???lcn (logical channel number): In the range from 131 to 510.

???carrier-loss-pol (carrier loss policy):

???1 = Revert to the previous codec

???2 = Maintain the upspeed codec

???3 = Unspecified

???cac-reject-pol (CAC rejection policy):

???1 = Delete the connection

???2 = Maintain the connection

???3 = Unspecified

You have completed enabling and configuring ECAN on your lines. Proceed to the ???Configuring Jitter??? section on page 4-30.

Configuring Jitter

You can dejitter the voice payload to improve the quality of the egress voice stream.

Note If your application uses the AAL2 trunking operation mode, you cannot change the jitter parameters while the CIDs are active.

Complete the following steps to specify and configure jitter mode:

Step 1 Type the cnfjtrmode command, the jitter-mode argument value, and press Enter to set the jitter mode. Specify the jitter-mode argument with one of the following values:

???1 = Fixed buffer size; recommended value if the jitter amount is expected to be constant or near constant.

???2 = Adaptive; you specify a starting buffer size and VISM adapts the buffer size to handle jitter.

Step 2 If you chose a fixed buffer size in Step 1, you have completed configuring jitter. Proceed to the ???Configuring the ATM Network Side??? section on page 4-31. If you chose an adaptive buffer size in Step 1, proceed to Step 3.

Chapter 4 Configuring VISM Features

Configuring VISM Features

Step 3 Type the cnfjtrinitdelay command, the jitter-buffer-size argument value, and press Enter to specify the starting buffer size. Specify the jitter-buffer-size argument (defined in bytes) with a value from one of the following ranges:

???For template numbers 1, 3, and 4, in the range from 0 to 100 in increments of 10.

???For template number 2, in the range from 0 to 100 in increments of 5.

You have completed configuring jitter. Proceed to the ???Configuring the ATM Network Side??? section on page 4-31.

Configuring PNNI for AAL1/AAL2 SVCs

Use the cnfpncon command to configure Private Network-to-Network Interface (PNNI) priority routing for AAL1/AAL2 switched virtual circuits (SVCs). Refer to Chapter 5, ???CLI Commands,??? for more information on using the cnfpncon command.

Configuring the ATM Network Side

Configuring the ATM network side consists of setting up ATM PVCs across the network and providing the mechanism by which calls are routed over the correct PVC. The PVC configuration depends on the VISM operating mode you require for your application.

???The Voice over IP switching operating mode requires you to set up an AAL5 PVC between the VISM card and the PXM card, and then to an edge router. A single PVC is set up (a secondary PVC may also be set up for redundancy). The PVC is used for bearer voice traffic and gateway protocol communication between VISM and the call agent. The router extracts the IP frames from the ATM cells and routes the frames accordingly.

???The AAL2 trunking operating mode requires you to set up as many as 64 AAL2 PVCs connected to each remote location supported by the network. The PVCs carry voice traffic and optional CAS signaling.

Each PVC is set up as three segments consisting of two local segments and one network segment. The local segments are set up between the two VISM cards (one at the end of the PVC) and their respective PXM cards. The network segment is set up between the two PXM cards across the network. Refer to the Cisco MGX 8250 and MGX 8230 Release l installation and configuration guides for more information.

In AAL2 trunking operating mode, you must bind endpoints to specific DS0s using the addendpoint(s) commands. You must also create CIDs (connection identifiers) for each PVC that binds the endpoints to the CID and a PVC. This ensures that calls arriving at a specific DS0 are automatically routed to the preconfigured CID and PVC over nailed-down trunks. There is no switched or call agent involvement.

Chapter 4 Configuring VISM Features

Configuring VISM Features

???The switched AAL2 PVC operating mode requires you to set up as many as 64 AAL2 PVCs connected to each remote location supported by the network. The PVCs carry voice traffic across the ATM network.

Each PVC is set up as three segments consisting of two local segments and one network segment. The local segments are set up between the two VISM cards (one at the end of the PVC) and their respective PXM cards. The network segment is set up between the two PXM cards across the network. Refer to the Cisco MGX 8850 Release 1 installation and configuration guides for more information.

In switched AAL2 PVC operating mode, you must bind endpoints to specific DS0s using the addendpoint(s) commands. You must also create VCCIs (virtual circuit connection identifiers), which identify each PVC and associate each PVC with a specific remote ATM address. At call setup time, the call agent informs VISM which VCCI to use for the call and instructs VISM to set up a CID for transport across the VCCI. This ensures that the binding of a DS0 to a CID and PVC is dynamic by using of the called address.

Configuring PVC Connections for All Operating Modes

Complete the following steps to configure PVC connections for all operating modes:

Step 1 Type the addcon command, local-vci, pref-level, pvc-conn-type, conn-app, peak-cell-rate, conn-type, |remote-conn-id, service-type, sus-cell-rate, and max-burst-rate| argument values, and press Enter to add an ATM PVC between the VISM card and the MGX 8000 Series platform PXM card. Specify the addcon command arguments with the following values:

???local-vci: In the range from 131 to 510.

???pref-level:

???1 = Primary

???2 = Secondary (for redundancy)

???pvc-conn-type:

???1 = AAL5

???2 = AAL2

???3 = AAL1

???conn-app:

???1 = Control

???2 = Bearer

???3 = Signaling

???peak-cell-rate (defined as cells per second):

???In the range from 1 to 80000 for VoIP bearer.

???In the range from 1 to 20000 for VoIP control.

???In the range from 1 to 50000 for AAL2 T1.

???In the range from 1 to 60000 for AAL2 E1.

???In the range from 1 to 400 for AAL2 signaling (trunking).

???In the range from 1 to 90000 for AAL5 bearer.

???In the range from 1 to 10000 for AAL5 control.

Chapter 4 Configuring VISM Features

Configuring VISM Features

???conn-type (type of connection):

???1 = Master

???2 = Slave (default)

???|remote-conn-id| (remote connection identifier):

???Type the value in the following format: nodename.slot.port.vpi.vci

Note Use the optional |remote-conn-id| argument only if you selected the conn-type argument value of 1 (master).

???|service-type|:

???1 = Constant bit rate (CBR)

???2 = Variable bit rate real time, VBR (RT)

???3 = Variable bit rate non-real time, VBR (NRT)

???4 = VBR (RT) 3

???5 = VBR (RT) 2

???6 = VBR (NRT) 2

???7 = VBR (NRT) 3

???|sus-cell-rate| (sustainable cell rate):

???In the range from 1 to the value you specified for the peak-cell-rate argument.

???|max-burst-rate| (maximum number of cells transmitted at the peak cell rate):

???In the range from 1 to 10 times the value you specified for the sus-cell-rate argument.

Step 2 Type the cnfcon command, lcn, peak-cell-rate, service-type, sus-cell-rate, and max-burst-rate argument values and press Enter if you need to refine the configuration parameters of the connection added in Step 1 and identify the connection by the logical channel number. Specify the arguments with the following values:

???lcn: Type the value you entered for the local-vci argument in Step 1.

???peak-cell-rate (defined as cells per second):

???In the range from 1 to 80000 for VoIP bearer.

???In the range from 1 to 20000 for VoIP control.

???In the range from 1 to 50000 for AAL2 T1.

???In the range from 1 to 60000 for AAL2 E1.

???In the range from 1 to 400 for AAL2 signaling (trunking).

???In the range from 1 to 90000 for AAL5 bearer.

???In the range from 1 to 10000 for AAL5 control.

Note The peak-cell-rate argument value cannot be changed if the calls or connections for signaling and control are active.

Chapter 4 Configuring VISM Features

Configuring VISM Features

???service-type:

???1 = Constant bit rate (CBR)

???2 = Variable bit rate real time???VBR (RT)

???3 = Variable bit rate non-real time???VBR (NRT)

???4 = VBR (RT) 3

???5 = VBR (RT) 2

???6 = VBR (NRT) 2

???7 = VBR (NRT) 3

???sus-cell-rate (sustained cell rate, defined as cells per second):

???In the range from 15 to the value you specified for the peak-cell-rate argument.

???max-burst-rate (maximum burst rate, defined as cells per second):

???In the range from 1 to 10 times the value you specified for the sus-cell-rate argument.

Step 3 Type the addconloop command, the lcn argument value, and press Enter to set a loopback on a VISM PVC with the loopback in the direction of cellbus. Specify the lcn argument value with a value in the range from 131 to 510.

Note You can use the delconloop command to remove a loopback on a VISM PVC.

You have completed configuring PVC connections. Proceed to one of the following sections, as appropriate:

???Configuring VoIP Switching/Trunking Operating Mode Parameters, page 4-34.

???Configuring AAL2 Trunking Operating Mode Parameters, page 4-36.

???Configuring Switched AAL2 PVC Operating Mode Parameters, page 4-38.

Configuring VoIP Switching/Trunking Operating Mode Parameters

Complete the following steps to configure VoIP switching operating mode parameters:

Step 1 Type the cnfconprotect command, lcn, protect-enable, lock-state, and second-lcn argument values, and press Enter to configure primary and secondary PVCs to provide protection in the event of a PVC failure. Specify the argument with the following values:

???lcn: In the range from 131 to 510.

???protect-enable:

???1 = On

???2 = Off

???lock-state:

???1 = Unlock

???2 = Lock

???second-lcn (secondary LCN): In the range from 131 to 510.

Chapter 4 Configuring VISM Features

Configuring VISM Features

Step 2 Type the cnfdeftos command, control-prec, control-tos, |bearer-prec|, and |bearer-tos| argument values, and press Enter to configure the type of service for both control and bearer IP packets.

Note If you do not execute the cnfdeftos command, card level default values are used.

Specify the arguments with the following values:

???control-prec: In the range from 0 to 7 (default = 3)

???control-tos (type of service for control packets):

???0 (default)

???1

???2

???4

???8

???bearer-prec: In the range from 0 to 7 (default = 5)

???bearer-tos (type of service for bearer packets):

???0 (default)

???1

???2

???4

???8

Note The bearer-prec and bearer-tos arguments are used during call setup in cases where values are not supplied by a call agent.

Step 3 Type the cnfvoiptransparams command, dtmf-trans, cas-trans, and |event-neg-enable|, |event-neg-pol|, and |sid-type| argument values, and press Enter to configure the VoIP transportation characteristics across the network. Specify the arguments with the following values:

???dtmf-trans (DTMF tones relayed to the other endpoint):

???1 = On

???2 = Off

???cas-trans (CAS bits relayed to the other endpoint):

???1 = On

???2 = Off

???event-neg-enable (Optional):

???1 = On

???2 = Off

Chapter 4 Configuring VISM Features

Configuring VISM Features

???event-neg-pol (Optional; event negotiation policy):

???1 = None

???2 = Proprietary (default)

???3 = All

???sid-type (Optional; SID payload type): In the range from 0 to 255 (default = 13)

You have completed configuring the VoIP switching operating mode parameters. Proceed to the ???Configuring the Call Agent Interface??? section on page 4-44.

Configuring AAL2 Trunking Operating Mode Parameters

Complete the following steps to configure AAL2 trunking operating mode parameters:

Step 1 Type the addcid command, endpt-num, lcn, cid-num, codec-type, profile-type, profile-num, |vad-enable, vad-init-timer, ecan-enable, type-3-red, cas-trans, dtmf-trans, idle-code-sup, and pkt-period| argument values, and press Enter to add a channel identifier (CID) to an AAL2 PVC.

The CID is a mechanism within AAL2 that allows multiple calls to be transported across a single AAL2 PVC. The addcid command binds an endpoint to a logical channel (PVC). Specify the arguments with the following values:

???endpt-num (endpoint to be related to the LCN/CID pair being added):

???For template number 1:

For VISM, in the range from 1 to 145

For VISM-PR T1, in the range from 1 to 192 For VISM-PR E1, in the range from 1 to 248

???For template number 2:

For VISM T1, in the range from 1 to 192 For VISM E1, in the range from 1 to 248

???For template number 3:

For VISM, in the range from 1 to 120

For VISM-PR T1, in the range from 1 to 192 For VISM-PR E1, in the range from 1 to 248

???For template number 4:

For VISM-PR, in the range from 1 to 144

???lcn (LCN of the LCN/CID pair): In the range from 131 to 510.

???cid-num (CID of the LCN/CID pair): In the range from 8 to 255.

???codec-type:

???1 = G.711u

???2 = G.711a

???3 = G.726-32k

???4 = G.729a

Chapter 4 Configuring VISM Features

Configuring VISM Features

???5 = G.729ab

???6 = Clear channel (VAD must be off)

???7 = G.726-16k

???8 = G.726-24k

???9 = G.726-40k

???11 = G.723-H

???12 = G.723a-H

???13 = G.723.1-L

???14 = G.723.1a-L

???profile-type (used for the CID):

???1 = International Telecommunication Union (ITU) I.366.2

???3 = Custom

???profile-num:

???1 = for the ITU profile

???2 = for the ITU profile

???3 = for the ITU profile

???7 = for the ITU profile

???8 = for the ITU profile

???12 = for the ITU profile

???100 = for custom profiles

???101 = for custom profiles

???110 = for custom profiles

???200 = for custom profiles

???vad-enable:

???1 = On

???2 = Off

???vad-init-timer (holdover timer; in milliseconds): In the range from 250 to 65535 (default = 250)

???ecan-enable:

???1 = On (default)

???2 = Off

???type-3-red (triple redundancy protection for CAS type 3 packets):

???1 = On

???2 = Off

???cas-trans:

???1 = On (default)

???2 = Off

Chapter 4 Configuring VISM Features

Configuring VISM Features

???dtmf-trans (DTMF tone transport as AAL2 type 3 packets):

???1 = On (default)

???2 = Off

Note The dtmf-trans argument value must be set to 1 (on) when the codec-type is configured for codecs other than G.711 and G.726.

???idle-code-sup (idle code suppression):

???1 = On

???2 = Off

???pkt-period (defined in milliseconds):

???10

The pkt-period argument requires you to configure packetization in the following ways for the other two operating modes:

???Use the cnfcodedecparams for the VoIP operating mode.

???Use the cnfprofelemvoice command for the switched AAL2 PVC operating mode. See the ???Configuring Switched AAL2 PVC Operating Mode Parameters??? section on page 4-38 for more information.

Step 2 Type the cnfaal2subcellmuxing command, the mux-enable argument value, and press Enter to enable or disable subcell multiplexing. Specify the mux-enable argument with one of the following values:

???1 = On

???2 = Off

You have completed configuring the AAL2 trunking operating mode parameters.

Configuring Switched AAL2 PVC Operating Mode Parameters

Note The switched AAL2 PVC operating mode is not supported in VISM Release 3.0.

You must complete the following tasks to configure the switched AAL2 PVC operating mode parameters:

1.Configure a virtual circuit connection identifier (VCCI).

2.Modify the AAL2 PVC profile table.

Note Modifying the AAL2 PVC profile table is not mandatory.

3.Configure AAL2 PVC parameters.

Chapter 4 Configuring VISM Features

Configuring VISM Features

Configuring a Virtual Circuit Connection Identifier

Complete the following steps to configure a VCCI for the switched AAL2 PVC operating mode:

Step 1 Type the cnfconvcci command, lcn, vcci-num, addr-type, and |fe-addr| argument values, and press Enter to create a new VCCI with an associated logical channel number and a remote ATM address. Specify the arguments with the following values:

???lcn: In the range from 131 to 510.

???vcci-num: In the range from 0 to 65535.

???addr-type (address type):

???1 = Not applicable

???2 = Network service access point (NSAP); a 20-byte hexadecimal address

???3 = E.164 public network addressing; a 1- to 15-byte decimal address

???4 = Gateway ID; a 1- to 64-byte ASCII character address

???5 = Unspecified

???|fe-addr|: The actual remote address

Step 2 Repeat Step 1, as needed, to configure VCCIs on other LCNs.

You have completed configuring VCCIs for the switched AAL2 PVC operating mode. Proceed to the ???Modifying the AAL2 PVC Operating Mode Profile Table??? section on page 4-39.

Modifying the AAL2 PVC Operating Mode Profile Table

A profile table is associated with each AAL2 operating mode. This profile table specifies the encoding format, which tells the card how to interpret the packets.

You can use the dspaal2profile command to see the values for a profile type. Example 4-1 shows the default values for ITU profile type 1.

Example 4-1 Default Values for ITU Profile 1

nodename.1.28.VISM8.a > dspaal2profile 1 1

Table 4-4 describes the fields shown in the display.

Table 4-4 dspaal2profile Field Descriptions

Chapter 4 Configuring VISM Features

Configuring VISM Features

Chapter 4 Configuring VISM Features

Configuring VISM Features

Table 4-5 AAL2 Operating Mode Profiles (continued)

Complete the following steps to assign a profile preference and to modify the packet period and SID values of the profile table, as necessary.

Note Modifying the AAL2 PVC profile table is not mandatory. Proceed to the ???Configuring AAL2 PVC Parameters??? section on page 4-43 if the values shown in Table 4-5 are correct for your application and configuration requirements.

Step 1 Type the cnfprofparams command, profile-type, profile-num, and profile-pref argument values, and press Enter to specify the preference for a given profile during call setup profile negotiation. Specify the arguments with the following values:

???profile-type:

???1 = ITU

???3 = Custom

???profile-num:

???1 = for the ITU profile

???2 = for the ITU profile

???3 = for the ITU profile

???7 = for the ITU profile

???8 = for the ITU profile

???12 = for the ITU profile

???100 = for custom profiles

???101 = for custom profiles

???110 = for custom profiles

???200 = for custom profiles

???profile-pref:

???0 = No preference; excludes a profile from negotiation

???In the range from 1 (highest) to 9 (lowest)

Chapter 4 Configuring VISM Features

Configuring VISM Features

Step 2 Type the cnfprofelemvoice command, profile-type, profile-num, codec-type, pvoice-pkt-period, and sid argument values, and press Enter to configure the voice profile element for a specified profile. Specify the arguments with the following values:

???profile-type: Refer to the options listed in Step 1.

???profile-num: Refer to the options listed in Step 1.

???codec-type argument values:

???1 = G.711u

???2 = G.711a

???3 = G.726-32k

???4 = G.729a

???5 = G.729ab

???6 = Clear channel (VAD must be off)

???7 = G.726-16k

???8 = G.726-24k

???9 = G.726-40k

???11 = G.723.1-H

???12 = G.723.1a-H

???13 = G.723.1-L

???14 = G.723.1a-L

???pvoice-pkt-period (defined in milliseconds):

???5

???10

???20

???30

???40

???60

???sid:

???1 = VAD off

???2 = VAD on

???3 = SID generic

???4 = SID 729

???5 = SID 723

Step 3 Type the cnfprofelemvbd command, profile-type, profile-num, codec-type, and vbd-pkt-period argument values, and press Enter to configure the voiceband data element for a specified profile. Specify the arguments with the following values:

???profile-type???Refer to the options listed in Step 1.

???profile-num???Refer to the options listed in Step 1.

???vbd-codec-type???Refer to the options listed in Step 2.

???vbd-pkt-period (defined in milliseconds):

Chapter 4 Configuring VISM Features

Configuring VISM Features

???5

???10

???30

Step 4 Type the cnfprofneg command, the codec-priority argument value, and press Enter to specify the priority preference order for the profile lists. Profiles can be from the call agent local connection option (LCO) list, local MIB, or a list received from the remote gateway in the session descriptor protocol (SDP) data. Specify the codec-priority argument value with one of the following:

???1 = LCO list, remote SDP data list, local MIB

???2 = LCO list, local MIB, remote SDP data list

???3 = Remote SDP data list, LCO list, local MIB

???4 = Remote SDP data list, local MIB, LCO list

???5 = Local MIB, LCO list, remote SDP data list

???6 = Local MIB, remote SDP data list, LCO list

You have completed modifying the switched AAL2 PVC operating mode profile table. Proceed to the ???Configuring AAL2 PVC Parameters??? section on page 4-43.

Configuring AAL2 PVC Parameters

Complete the following steps to configure AAL2 PVC parameters:

Step 1 Type the cnfaal2timerparams command, vad-init-timer and cid-fill-timer argument values, and press Enter to configure the holdover and maximum wait time arguments. Specify the arguments with the following values:

???vad-init-timer (defined in milliseconds): In the range from 250 to 65535.

???cid-fill-timer (defined in milliseconds): In the range from 5 to 100.

The vad-init-timer is the holdover time before activating silence suppression. The cid-fill-timer is the maximum waiting time for filling up the cell when the next packet is not ready.

Step 2 Type the cnfaal2transparams command, dtmf-trans, cas-bits-trans, and type-3-red argument values, and press Enter to enable or disable three parameters regarding the transport of CAS signaling.

???dtmf-trans (transportation of DTMF digits):

???1 = On

???2 = Off

???cas-bits-trans (transportation of CAS bits):

???1 = On

???2 = Off

???type-3-red (transportation of AAL2 Type 3 redundancy packets):

???1 = On

???2 = Off