Table Of Contents
Configuring Video Applications
Video Applications Overview
Cisco Video Support by Platform
Cisco MC3810 Multiservice Concentrator
Cisco 2600 Series, 3600 Series, and 7200 Series Router and MC3810 Multiservice Concentrator
Cisco 3600 Series Router
Multimedia Conference Manager with Voice Gateway Image and RSVP to ATM SVC Mapping
ATM Nonreal-Time VBR SVC Support for Video
Video Applications Prerequisite Tasks and Restrictions
Video Applications Configuration Task List
Configuring Video in Pass-Through Mode
Configuring Video over ATM AAL1
Tuning Circuit Emulation Services Settings
Configuring Video over ATM PVCs and SVCs
Configuring Network Clocks and Controllers
Verifying Network Clock and Controller Configuration
Configuring Serial Interfaces to Support the Video Codec
Configuring ATM Interfaces to Support Video over PVCs and SVCs
Configuring Video Dial Peers
Verifying Video Dial-Peer Configuration
Troubleshooting Video over ATM SVCs and PVCs
Configuring the CES Clock
Configuring Structured CES
Configuring the Proxy and T.120
Configuring the Gatekeeper to Support Zone Bandwidth
Configuring RSVP-ATM QoS Interworking
Verifying RSVP-ATM QoS Interworking Configuration
Video Applications Configuration Examples
Video over ATM PVCs and SVCs Configuration Examples
CES Video Traffic on the Cisco MC3810 Multiservice Concentrator Configuration Example
Video Traffic on a Cisco 3600 Series Router Configuration Example
Cisco IP/VC 3510 Multipoint Control Unit with Cisco IOS Gatekeeper/Proxy Configuration Example
CES Clock Configuration Examples
Configuring Video Applications
This chapter describes how to configure video support. It contains the following sections:
•
Video Applications Overview
•Video Applications Prerequisite Tasks and Restrictions
•Video Applications Configuration Task List
•Video Applications Configuration Examples
Note This chapter does not describe how to configure Multimedia Conference Manager. For more information, see the "Configuring H.323 Gatekeepers and Proxies" chapter.
For a complete description of the video application commands used in this chapter, refer to the
Cisco IOS Voice, Video, and Fax Command Reference. To locate documentation for other commands that appear in this chapter, use the command reference master index or search online.
To identity the hardware platform or software image information mentioned in this appendix, use the Feature Navigator on Cisco.com to search for information about the feature or refer to the software release notes for a specific release. For more information, see the "Identifying Supported Platforms" section in the "Using Cisco IOS Software" chapter.
Video Applications Overview
This section contains the following subsections:
•Cisco Video Support by Platform
•Multimedia Conference Manager with Voice Gateway Image and RSVP to ATM SVC Mapping
•ATM Nonreal-Time VBR SVC Support for Video
Cisco Video Support by Platform
Cisco video support for various applications is listed by platform in the following sections:
•Cisco MC3810 Multiservice Concentrator
•Cisco 2600 Series, 3600 Series, and 7200 Series Router and MC3810 Multiservice Concentrator
•Cisco 3600 Series Router
Cisco MC3810 Multiservice Concentrator
The Cisco MC3810 multiservice concentrator supports video traffic within a data stream in the following ways:
•Video in pass-through mode—By this method, video traffic received from a video codec connected to a universal I/O serial port can be transported on a dedicated time slot between systems using the time-division multiplexing (TDM) functionality of the T1/E1 trunk.
•Video over ATM adaptation layer 1 (AAL1)—A serial stream from a video codec connected to a Cisco MC3810 on serial port 0 or 1 can be converted to ATM and transported across an ATM network using AAL1 circuit emulation services (CES) encapsulation.
•Video over ATM permanent virtual circuits (PVCs) and switched virtual circuits (SVCs)—A serial stream from a video codec connected to a Cisco MC3810 using the plug-in video dialing module (VDM) can be converted to ATM and transported across an ATM network using AAL1 CES encapsulation.
Note Before configuring your MC3810 multiservice concentrator to support video traffic, you must first configure the clock source for the Cisco MC3810 interfaces. For more information, refer to the "Configuring Synchronized Clocking" appendix.
Note Only V.35 cable is supported for video traffic over serial port 0 or 1.
Cisco 2600 Series, 3600 Series, and 7200 Series Router and MC3810 Multiservice Concentrator
Cisco 2600 series, 3600 series, and 7200 series routers and the MC3810 multiservice concentrator support Multimedia Conference Manager with voice gateway image and Resource Reservation Protocol (RSVP) to ATM SVC mapping. Multimedia Conference Manager delivers H.323 gatekeeper, proxy, and voice gateway solutions with routing as a single Cisco IOS image. In addition, Multimedia Conference Manager enables H.323 RSVP reservations to be mapped to ATM nonreal-time variable bit rate (nRTVBR) SVCs to guarantee quality of service (QoS) for video applications over ATM backbones.
Cisco 3600 Series Router
Circuit emulation is a service based on ATM Forum standards that allows communications to occur between AAL1 CES and ATM user network interfaces (UNIs), that is, between non-ATM telephony devices (such as classic PBXs or time-division multiplexers) and ATM devices (such as Cisco 3600 series routers). Thus, a Cisco 3600 series router equipped with an OC-3/STM-1 ATM CES network module offers a migration path from classic T1/E1 data communications service to emulated CES T1/E1 unstructured (clear channel) services or structured (N x 64) services in an ATM network.
The OC-3/STM-1 ATM CES network module uses the CES clock and passes the clocking information to the T1 and E1 controller and to the ATM interface.
For specific information regarding OC-3/STM-1 ATM CES network module configurations, refer to the Cisco IOS Wide-Area Networking Configuration Guide and the Cisco IOS Quality of Service Solutions Configuration Guide.
Multimedia Conference Manager with Voice Gateway Image and RSVP to ATM SVC Mapping
Multimedia Conference Manager with voice gateway image and RSVP to ATM SVC mapping is implemented on Cisco IOS software. Multimedia Conference Manager is supported on the Cisco 2600 series , 3600 series, and 7200 series routers and on the MC3810 multiservice concentrator.
Multimedia Conference Manager with voice gateway image and RSVP to ATM SVC mapping enables you to limit the H.323 traffic on the LAN and WAN; it provides user accounting for records based on the service use; it guarantees QoS for the H.323 traffic generated by applications such as Voice over IP (VoIP), data conferencing, and videoconferencing; and it guarantees the implementation of security for H.323 communications. In addition, this new and separate image also incorporates Cisco voice gateway and routing functionalities in the same image.
With voice gateway image and RSVP to ATM SVC mapping, you can stipulate bandwidth limits for each videoconferencing connection and an aggregate bandwidth limit for all videoconferencing sessions. This voice gateway image allows you to provide bandwidth limitation to the endpoints.
Additional benefits include the following:
•The proxy can forward T.120 connections, which enhances real-time data conferencing capabilities.
•The gatekeeper can perform load-balancing functionality for external H.323 Version 2 gateways.
•The gatekeeper supports call accounting for proxied calls. Proxied calls are recorded into call history to provide additional call detail information.
Multimedia Conference Manager is recommended for multiple Cisco CallManagers or CallManager cluster domains. Multimedia Conference Manager provides critical connection admission control (CAC) between domains to guarantee that the number of calls between locations does not exceed available bandwidth.
For more detailed information about Multimedia Conference Manager, see the "Configuring H.323 Gatekeepers and Proxies" chapter.
ATM Nonreal-Time VBR SVC Support for Video
ATM nonreal-time variable bit rate (nRTVBR) SVC service operates much like X.25 SVC service although ATM allows much higher throughput. Virtual circuits are created and released dynamically, providing user bandwidth on demand. This service requires a signaling protocol between the router and the switch. Each ATM node is required to establish a separate connection to every other node in the ATM network with which it needs to communicate. All such connections are established using a PVC or an SVC with an ATM signaling mechanism.
Using ATM nRTVBR SVC for video on an ATM backbone guarantees that video sessions will traverse that backbone with QoS features enabled. The Cisco IOS image takes H.323 RSVP reservations and maps them to ATM nRTVBR SVCs that are dynamically established and torn down when video sessions are established and terminated. End-to-end IP routing across the network backbone is no longer required to guarantee video QoS.
ATM nonreal-time nRTVBR SVC service is supported on the Cisco 2600 series, 3600 series, and 7200 series routers and on the MC3810 multiservice access server.
For more information on configuring ATM, refer to the Cisco IOS Wide-Area Networking Configuration Guide.
Video Applications Prerequisite Tasks and Restrictions
The following prerequisites and restrictions apply when using Multimedia Conference Manager with voice gateway image and RSVP to ATM SVC mapping:
•Permanent virtual pathways (PVPs) are supported only on OC-3 cards and DS3/E3 cards. Neither the T1-IMA cards nor the T1 interface on the Cisco MC3810 supports PVPs.
•T.120 proxy has been tested and proved to work with Microsoft NetMeeting 3.01. Based on testing, T.120 proxying does not work with VCON endpoints. T.120 proxy works only with endpoints that can connect to ports other than the default port of 1503. Microsoft NetMeeting 3.01 can do this, but VCON cannot.
•Some older H.323 endpoint implementations, especially those used in videoconferencing, may not be able to connect to an H.225 call setup port number other than 1720. If you have to use those endpoints with the H.323 gatekeeper proxy feature, consider using an image without the Cisco H.323 VoIP gateway (an -ix- image).
•For Multimedia Conference Manager with voice gateway image and RSVP to ATM SVC mapping to function properly, you must have 16 megabytes of Flash memory and 64 megabytes of DRAM memory. For the Cisco 3660 router and for the Cisco 7200 series router, 96 megabytes of DRAM are required.
Video Applications Configuration Task List
Video applications require different tasks. To configure video support, perform one of the following:
•Configuring Video in Pass-Through Mode
•Configuring Video over ATM AAL1
–Tuning Circuit Emulation Services Settings
•Configuring Video over ATM PVCs and SVCs
–Configuring Network Clocks and Controllers
–Configuring Serial Interfaces to Support the Video Codec
–Configuring ATM Interfaces to Support Video over PVCs and SVCs
–Configuring Video Dial Peers
–Troubleshooting Video over ATM SVCs and PVCs
•Configuring the CES Clock
•Configuring Structured CES
•Configuring the Proxy and T.120
•Configuring the Gatekeeper to Support Zone Bandwidth
•Configuring RSVP-ATM QoS Interworking
Configuring Video in Pass-Through Mode
Video in pass-through mode is supported on the Cisco MC3810 multiservice concentrator.
To configure support for video in pass-through mode, use the following commands beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# network-clock base-rate {56k | 64k}
|
Configures the network clock base rate. The default is 56 kbps.
|
Step 2
|
Router(config)# interface serial number {multipoint
| point-to-point}
|
Enters serial interface configuration mode for either serial port 0 or 1.
•multipoint—Assumes that there is a fully meshed network.
•point-to-point—Specifies that a video connection will be over a point-to-point network.
|
Step 3
|
Router(config-if)# encapsulation clear-channel
|
Configures the serial interface to be in clear-channel mode for pass-through traffic.
|
Step 4
|
Router(config-if)# clock rate network-clock rate
|
Configures the network clock speed for serial port 0 or 1 in DCE mode on the MC3810 multiservice access server. The rate argument is the network clock speed in bits per second. The range is from 56 kbps to 2048 kbps. The value entered should be a multiple of the value set for the network-clock base-rate command. The maximum rate supported is 2048 Mbps.
|
Step 5
|
Router(config-if)# exit
|
Exits interface configuration mode.
|
Step 6
|
Router(config)# controller t1 0
|
Enters controller configuration mode for controller T1 0.
|
Step 7
|
Router(config-controller)# tdm-group tdm-group-no
timeslot timeslot-list [type {e&m | fxs [loop-start
| ground-start] | fxo [loop-start |
ground-start] | fxs-melcas | fxo-melcas |
e&m-melcas}
|
Configures a list of time slots for creating clear channel groups (pass-through) for time-division multiplexing (TDM) cross-connect.
The keywords and arguments are as follows:
•tdm-group-no—Specifies the TDM group number.
•timeslot—Specifies the timeslot number.
•timeslot-list—Specifies the timeslot list. The valid range is from 1 to 24 for T1, and it is from 1 to 15 and 17 to 31 for E1.
•type—(Optional) (Valid only when the mode cas command is enabled.) Specifies the voice signaling type of the voice port. If configuring a TDM group for data traffic only, do not specify the type keyword.
Choose from one of the following options:
–e&m—Specifies E&M signaling.
–fxs—Specifies Foreign Exchange Office (FXO) signaling. (Optionally, you can also specify loop-start or ground-start.)
–fxo—Specifies Foreign Exchange Station (FXS) signaling. (Optionally, you can also specify loop-start or ground-start.)
–fxs-melcas—Specifies FXS Mercury Exchange Limited (MEL) Channel Associated Signaling (CAS).
–fxo-melcas—Specifies FXO MEL CAS.
•e&m-melcas—Specifies ear and mouth (E&M) MEL CAS.
|
Step 8
|
Router(config-controller)# exit
|
Exits controller configuration mode.
|
Step 9
|
Router(config)# cross-connect id controller-1
tdm-group-no-1 controller-2 tdm-group-no-2
|
Cross-connects two groups of digital signal level 0s (DS0s) from two controllers on the Cisco MC3810 or cross-connects the Universal I/O (UIO) serial port for pass-through traffic to a trunk controller.
Configures cross-connect pass-through from Universal I/O (UIO) serial port 0 or 1 to a controller. The arguments are as follows:
•id—Specifies the unique identification (ID) assigned to this cross-connection. The valid range is from 0 to 31.
•controller-1—Specifies the type of the first controller (T1 0, T1 1, or E1).
•tdm-group-no-1—Specifies the time-division multiplexing (TDM) group number assigned to the first controller.
•controller-2—Specifies the type of the second controller (T1, E1 0, or E1 1).
•tdm-group-no-2—Specifies the TDM group number assigned to the second controller.
|
Configuring Video over ATM AAL1
This section describes how to configure video over ATM AAL1 PVCs using CES. This functionality does not use the VDM, and SVCs are not supported. This section describes the video functionality supported on the MC3810 multiservice concentrator.
To configure video support over ATM AAL1 PVCs on a Cisco 3600 series router, see the "Configuring Structured CES" configuration task table in this chapter and refer to the Cisco IOS Wide-Area Networking Configuration Guide or the OC-3/STM-1 ATM Circuit Emulation Service Network Module.
To configure support for video streaming data over ATM AAL1 encapsulation using CES, use the following commands beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# network-clock base-rate {56k | 64k }
|
Configures the network clock base rate.
The keywords are as follows:
•56k—Sets the network clock to 56 kbps.
•64k—Sets the network clock to 64 kbps.
|
Step 2
|
Router(config)# controller {t1 | e1} 0
|
Selects T1/E1 controller 0. ATM is supported only on controller 0.
|
Step 3
|
Router(config-controller)# mode atm
|
Specifies that the controller will support ATM encapsulation and creates virtual ATM interface 0, which you will use to create the ATM permanent virtual circuits (PVCs).
|
Step 4
|
Router(config-controller)# exit
|
Exits controller configuration mode.
|
Step 5
|
Router(config)# interface atm 0 {multipoint |
point-to-point}
|
Enters interface configuration mode to configure ATM interface.
•0—Indicates the ATM port number. Because the ATM interface processor (AIP) and all ATM port adapters have a single ATM interface, the port number is always 0.
•multipoint | point-to-point—Specifies a multipoint or point-to-point subinterface.
|
Step 6
|
Router(config-if)# pvc [name] vpi/vci
[ilmi | qsaal | smds]
|
Creates an ATM permanent virtual circuit (PVC) and enters ATM PVC configuration mode.
The keywords and arguments are as follows:
•name—(Optional) Specifies the name of the PVC or map. The name can be as many as 16 characters long.
•vpi/—Specifies the ATM network VPI for the PVC that you named.
The ATM network VPI of this PVC is an 8-bit field in the header of the ATM cell. The vpi value is unique only on a single link, not throughout the ATM network, because it has local significance only. The vpi value must match that of the switch. Valid values are from 0 to 255, but the value is usually 0 for ILMI communications. If a value is not specified, the vpi value is set to 0.
Note You cannot set both vpi and vci to 0; if one is 0, the other cannot be 0.
•vci—Specifies the ATM network VCI for the PVC you named. The VCI is a 16-bit field in the header of the ATM cell. The VCI value is unique only on a single link, not throughout the ATM network, because it has only local significance. The vci value ranges from 0 to 1 less than the maximum value set for this interface by the atm vc-per-vp command.
Note Typically, the low vci values 0 to 31 are reserved for specific traffic (for example, F4 operations, administration, and maintenance [OAM]; SVC signaling; and ILMI). Do not use them for other PVCs.
|
| |
|
•ilmi—(Optional) Sets up communication with the ILMI; the associated vpi and vci values ordinarily are 0 and 16, respectively.
•qsaal—(Optional) Specifies a signaling-type PVC used for setting up or tearing down SVCs; the associated vpi and vci values ordinarily are 0 and 5, respectively.
•smds—(Optional) A signaling-type PVC used for setting up or tearing down SVCs; the associated vpi and vci values ordinarily are 0 and 5, respectively.
|
Step 7
|
Router(config-if-atm-pvc)# encapsulation aal1
|
Sets the PVC to support ATM adaptation layer 1 (AAL1) encapsulation for video.
|
Step 8
|
Router(config-if-atm-pvc)# cbr rate
|
Configures the CBR for the ATM circuit emulation service (CES) for an ATM PVC on the Cisco MC3810 multiservice concentrator. By default, the rate argument used is the value configured with the vc-class command. The valid rate is from 56 to 10,000 kbps. The formula to calculate the CBR is 1.14 times the clock rate on the serial port.
|
Step 9
|
Router(config-if-atm-pvc)# exit
|
Exits ATM PVC configuration mode.
|
Step 10
|
Router(config)# interface serial number {multipoint
| point-to-point}
|
Enters interface configuration mode for either serial port 0 or 1.
For a full explanation of the keywords and argument, see Step 2 in the "Configuring Video in Pass-Through Mode" configuration task table in this chapter.
|
Step 11
|
Router(config-if)# clock rate network-clock rate
|
Configures the network clock speed for serial ports 0 or 1 in data circuit-terminating equipment (DCE) mode on the Cisco MC3810 multiservice concentrator. The rate argument is the network clock speed in bits per second. The range is from 56 kbps to 2048 kbps. The value entered should be a multiple of the value set for the network-clock base-rate command. The maximum rate supported is 2048 Mbps.
|
Step 12
|
Router(config-if)# encapsulation atm-ces
|
Enables CES ATM encapsulation on the Cisco MC3810.
|
Step 13
|
Router(config-if)# ces connect atm-interface pvc
[name | [vpi/]vci]
|
Maps the CES service to the PVC.
The keywords and arguments are as follows:
•atm-interface—Specifies the number of the ATM interface. The only valid option on the
Cisco MC3810 multiservice concentrator is ATM0.
•pvc—Specifies that the connection is to an ATM PVC.
•name—(Optional) The name of the ATM PVC.
•vpi/—(Optional) The virtual path identifier value.
•vci—(Optional) The virtual channel identifier value.
|
Tuning Circuit Emulation Services Settings
Video streaming traffic over AAL1 uses CES. The default CES settings are sufficient for most configurations. However, you can tune the CES settings as needed.
To change the CES settings, use the following commands, beginning in interface configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config-if)# ces initial-delay bytes
|
Configures the maximum size of the CES circuit transmit buffer. The bytes argument specifies the size of the receive buffer of the CES circuit. The valid range is from 1 to 16,000 bytes. This command is used to accommodate cell jitter on the network. Bytes received from the ATM network are buffered by this amount before being sent to the CES port.
|
Step 2
|
Router(config-if)# ces partial-fill octet
|
Configures the number of user octets per cell for CES. The octet argument specifies the number of user octets per cell for the CES. Possible values of octet range from 0 to 47. Setting this number to zero disables partial cell fill and causes all cells to be completely filled before they are sent.
|
Configuring Video over ATM PVCs and SVCs
Video over ATM SVCs enables the Cisco MC3810 multiservice concentrator to provide dynamic and flexible videoconferencing system support. Using a plug-in VDM to provide an EIA/TIA-366 dialing interface to an H.320 video codec, the Cisco MC3810 automatically accepts dial-out requests from the video system. The codec connects to one of the Cisco MC3810 serial ports and also to the Cisco MC3810 EIA/TIA-366 dialup port.
This feature permits automatic PVC connections through a serial port. Each codec must place a call to the other videoconferencing system prior to the expiration of the video codec timeout period (set on the codec, usually 1 minute). Using a video dial map, each system reconciles the dialed number with a PVC that has already been configured, allowing fast connectivity.
This section describes the video functionality supported on the Cisco MC3810 and contains the following sections:
•Configuring Network Clocks and Controllers
•Verifying Network Clock and Controller Configuration
•Configuring Serial Interfaces to Support the Video Codec
•Verifying Serial Interface Configuration for Video Codecs
•Configuring ATM Interfaces to Support Video over PVCs and SVCs
•Verifying ATM Interface Configuration for Video over PVCs and SVCs
•Configuring Video Dial Peers
•Verifying Video Dial-Peer Configuration
•Troubleshooting Video over ATM SVCs and PVCs
Service providers, educational organizations, and enterprises can combine video streams and packet data on a single high-speed ATM link. A separate ATM access multiplexer is not needed. Features of the Cisco ATM SVC implementation include the following:
•AAL1 and CES encapsulation is used to transport video traffic to the destination using a single CBR virtual circuit that includes multiple ATM SVCs.
•The implementation adheres to the required features of the ATM Forum UNI specification, version 4.0, which simultaneously supports PVCs and SVCs.
•Video over ATM SVCs support codec speeds of 128, 384, 768, and 1152 kbps.
•The Cisco MC3810, responding to the design of many leading H.320-based video systems, receives the called-party information from the EIA/TIA-366 interface and then reconciles the dialed address with a standard 20-octet ATM network service access point (NSAP) address.
Figure 120 shows a sample ATM video application.
Figure 120 Sample ATM Video Application
Figure 121 shows how the physical interfaces interact with software, the codec, and video data to handle connectivity and video functionality. The VDM automatic calling equipment (ACE) provides the EIA/TIA-366 interface to the video codec, and one of the Cisco MC3810 serial interfaces connects to the video codec DTE interface. The Video Call Manager (ViCM) software manages video calls that travel over a T1 or E1 facility through the Cisco MC3810 multiflex trunk (MFT) interface.
Figure 121 Physical Interfaces and Their Functions
The following restrictions apply to video over ATM using SVCs:
•Point-to-point connectivity for ATM SVC video does not support tandem switching and network (local) hunting.
•You can connect only one video codec to a Cisco MC3810.
•For video SVCs, the ATM service class is not configurable. It is automatically set to CBR, which is the standard service class for video.
The following special hardware is required for this feature:
•A Cisco MC3810 video dialing module VDM and an MFT module for ATM network connectivity
•Two cables:
–A new Cisco serial V.35 DCE cable (product number 72-1721-01) that includes a ringing indicator (RI) conductor. This cable carries the video stream between the Cisco MC3810 and the video equipment. Videoconferencing equipment often uses the V.35 RI as the incoming call-alerting signal. Cisco standard serial V.35 cables do not include the RI conductor.
–A Cisco EIA/TIA-366 ACE cable (product number 72-1722-01) to connect the VDM to the videoconferencing equipment EIA/TIA-366 dialup DTE port.
For additional information about installation and other hardware considerations, refer to the Cisco MC3810 Multiservice Concentrator Hardware Installation Guide.
Configuring Network Clocks and Controllers
Because real-time video communications require a continuous and tightly meshed data stream to avoid loss of information, you must synchronize source and destination devices to a single master clock. In the following example, the clock source is derived from a device attached to T1 controller 0; then it is distributed to the devices attached to the local Cisco MC3810 serial ports and to T1 controller 1. Clock source decisions should be based on the network configuration, and a hierarchy of clock sources can be set up so that backup clock sources are available. For details, see the "Configuring Synchronized Clocking" appendix.
To configure network clocks and the controller to support real-time video, use the following commands beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# controller {T1 | E1} number
|
Enters controller configuration mode for controller T1/E1 0. The number argument indicates the network module number. The range is from 0 to 2. ATM traffic is supported on controller T1/E1 0 only.
|
Step 2
|
Router(config-controller)# clock source
{line | internal | loop-timed}
|
Configures controller T1/E1 0 to obtain its clocking from the internal network clock PLL. (Use the internal keyword.)
Keyword definitions are as follows:
•line—Specifies that the DS1 link uses the recovered clock. The line value is the default clock source used when the multiflex trunk module (MFT) is installed.
•internal—Specifies that the DS1 link uses the internal clock. The internal value is the default clock source used when the digital voice module (DVM) is installed.
|
| |
|
•loop-timed—Specifies that the T1/E1 controller will take the clock from the Rx (line) and use it for Tx. This setting decouples the controller clock from the system-wide clock set with the network-clock-select command. The loop-timed clock enables the DVM to connect to a PBX and to connect the MFT to a central office when both the PBX and the central office function as DCE clock sources. This situation assumes that the PBX also takes the clocking from the central office, thereby synchronizing the clocks on the DVM and the MFT.
|
Step 3
|
Router(config-controller)# no shutdown
|
Activates the controller.
|
Step 4
|
Router(config)# controller {T1 | E1} 1
|
Enters controller configuration mode for controller T1/E1 1. The number argument indicates the network module number. The range is from 0 to 2.
|
Step 5
|
Router(config-controller)# clock source {line |
internal | loop-timed}
|
Sets the T1/E1 line clock source.
For an explanation of the keywords, see Step 2 in this configuration task table.
|
Step 6
|
Router(config-controller)# no shutdown
|
Activates the controller.
|
Step 7
|
T1 Line
Router(config-controller)# framing {sf | esf}
E1 Line
Router(config-controller)# framing {crc4 | no-crc4}
[australia]
|
Sets the framing for the E1 or T1 data line.
The keywords are as follows:
•sf—Specifies Super Frame as the T1 frame type.
•esf—Specifies Extended Super Frame as the T1 frame type. This frame type is required for ATM on T1 lines. This setting is automatic for T1 when ATM mode is set.
•crc4—Specifies CRC4 frame as the E1 frame type. This frame type is required for ATM on E1 lines. This setting is automatic for E1 when the ATM mode is set.
•no-crc4—Specifies no CRC4 frame as the E1 frame type.
•australia—(Optional) Specifies the E1 frame type used in Australia.
|
Step 8
|
Router(config-controller)# linecode {ami | b8zs |
hdb3}
|
Selects the line-code type for T1 or E1 lines.
The keywords are as follows:
•ami—Specifies alternate mark inversion (AMI) as the line-code type. It is valid for T1 or E1 controllers. This is the default for T1 lines.
•b8zs—Specifies binary 8-zero substitution (B8ZS) as the line-code type. It is required for ATM on T1 lines. This setting is automatic for T1 when the ATM mode is set.
•hdb3—Specifies high-density bipolar 3 (HDB3) as the line-code type. It is required for ATM on E1 lines. This setting is automatic for E1 when the ATM mode is set.
Note When the E1 controller is specified, you must also configure scrambling on the ATM 0 interface. See Step 3 of the "Configuring ATM Interfaces to Support Video over PVCs and SVCs" configuration task table in this chapter.
|
Step 9
|
Router(config-controller)# mode {atm | cas}
|
Sets the mode of the T1/E1 controller and enters specific configuration commands for each mode type.
The keywords are as follows:
•atm—Sets the controller into ATM mode and creates an ATM interface (ATM 0) on the Cisco MC3810. When ATM mode is enabled, no channel groups, channel-associated signaling (CAS) groups, common channeling signaling (CCS) groups, or clear channels are allowed because ATM occupies all the DS0s on the T1/E1 trunk.
When you set the controller to ATM mode, the controller framing is automatically set to ESF for T1 or CRC4 for E1. The line code is automatically set to B8ZS for T1 or HDBC for E1. When you remove ATM mode by entering the no mode atm command, ATM interface 0 is deleted.
ATM mode is supported only on controller 0 (T1 or E1 0).
•cas—Sets the controller into CAS mode, which allows you to create channel groups, CAS groups, and clear channels (both data and CAS modes).
CAS mode is supported on both controllers 0
and 1.
|
Step 10
|
Router(config-controller)# exit
|
Exits controller configuration mode.
|
Step 11
|
Router(config)# network-clock base-rate {56k | 64k}
|
Sets the network clock base rate for the serial ports. For video stream rates of 384, 768, 1.152, or 1.28 kbps, set the rate to 64 kbps. The default is 56 kbps. (see Step 1 in the "Configuring Video over ATM AAL1" configuration task table in this chapter.)
Note At this point, you can also configure network protocol settings, such as IP hosts. For more information, see the
Cisco IOS IP Configuration Guide.
|
Verifying Network Clock and Controller Configuration
To verify the configuration of network clock sources and controller settings, complete the following steps:
Step 1 Enter the show network-clocks privileged EXEC command to see the status of clock source settings. In this example, the "inactive config" clock setting is the current configuration:
Router# show network-clocks
Priority 1 clock source(inactive config): T1 0
Priority 1 clock source(active config): T1 0
T1 0 is clocking system bus for 9319 seconds.
Run Priority Queue: controller0
Step 2 Enter the show controllers t1 or show controllers e1 privileged EXEC commands to see the status of T1 or E1 controllers, as in the following example:
Router# show controller t1 1
Applique type is Channelized T1
Cablelength is long gain36 0db
Slot 4 CSU Serial #07789650 Model TEB HWVersion 4.70 RX level = 0DB
Framing is ESF, Line Code is B8ZS, Clock Source is Internal.
Data in current interval (819 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 24 hours)
0 Line Code Violations, 0 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Router# show controllers E1 1
Applique type is Channelized E1 - balanced
Slot 4 Serial #06868949 Model TEB HWVersion 3.80
Framing is CRC4, Line Code is HDB3, Clock Source is Internal.
Data in current interval (292 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 66 15 minute intervals):
9 Line Code Violations, 0 Path Code Violations,
1 Slip Secs, 0 Fr Loss Secs, 4 Line Err Secs, 0 Degraded Mins,
5 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Configuring Serial Interfaces to Support the Video Codec
The configuration of serial interfaces to support the video codec is supported only on the Cisco MC3810 multiservice concentrator.
To configure the serial interfaces, use the following commands beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# interface serial {0 | 1}
|
Enters interface configuration mode for either for serial 0 or serial 1, depending on where the video codec is connected.
|
Step 2
|
Router(config-if)# clock rate network rate
|
Configures the network clock speed for DCE mode, in bits per second, corresponding to the video stream rate you are using. The rate must be a multiple of the value set with the network-clock base-rate command in Step 11 of the "Configuring Network Clocks and Controllers" configuration task table in this chapter. Make sure this setting is 384000, 768000, or 1152000. 768000 is a common setting.
|
Step 3
|
Router(config-if)# encapsulation atm-ces
|
Configures the interface for ATM encapsulation circuit emulation service (CES), which is required for video codec support.
|
Step 4
|
Router(config-if)# serial restart-delay count
|
Sets the amount of time that the router waits before trying to bring up a serial interface when the interface goes down. The router resets the hardware each time the restart timer expires. This command is often used with dial backup and with the pulse-time command, which sets the amount of time to wait before redialing when a data terminal ready (DTR) dialed device fails to connect.
The count argument is a value from 0 to 900 in seconds. This is the frequency at which the hardware is reset. A value of 0 means that the hardware is not reset when down. If the interface is used to answer a call, it does not cause the DTR circuit to drop. If the DTR circuit drops, the modem can disconnect.
|
Verifying Serial Interface Configuration for Video Codecs
To see the status of all serial interfaces or of a specific serial interface, enter the privileged EXEC command show interfaces serial as shown in the example below. You can use this command to check the encapsulation, scrambling, and serial restart delay settings:
Router# show interface serial0
Serial0 is down, line protocol is down
Hardware is PQUICC Serial Trans
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
reliability 255/255, txload 65/255, rxload 1/255
Encapsulation CES-ATM, loopback not set
Last input never, output never, output hang never
Last clearing of "showshow interface" counters 5d13h
Output queue 0/100, 101 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
13452224 packets input, 1526136219 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
215189699 packets output, 1654453088 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 output buffer failures, 0 output buffers swapped out
Cable attached: V.35 (DCE)
Hardware config: V.35; DCE; PLL nx64K;
DSR = UP DTR = DOWN RTS = DOWN CTS = DOWN DCD = DOWN
Configuring ATM Interfaces to Support Video over PVCs and SVCs
This section demonstrates how to set up the ATM interface and how to configure the ATM interface to support video over PVCs and SVCs. The video NSAP addressing commands specify session target information for SVC video communications.
This feature is supported only on the Cisco MC3810 multiservice concentrator.
To configure ATM interfaces to support video over PVCs and SVCs (including configuring a dial PVC for videoconferencing), use the following commands beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# interface atm
slot/port.subinterface-number {multipoint |
point-to-point}
|
Enters interface configuration mode.
The keywords and arguments are as follows:
•slot—Specifies the backplane slot number on your router. The value ranges from 0 to 4, depending on what router you are configuring. Refer to your router hardware documentation.
•/0—ATM port number. Because the ATM Interface Processor (AIP) and all ATM port adapters have a single ATM interface, the port number is always 0.
•.subinterface-number—Specifies a subinterface number in the range from 1 to 4294967293.
•multipoint—Specifies that your network is fully meshed and you want to communicate with multiple routers.
•point-to-point—Configures the subinterface for communication with one router, as in a hard-wired connection. There is no default for this parameter.
|
Step 2
|
Router(config-if)# ip address ip-address mask
[secondary]
|
For IP protocol communications, assigns the IP address and subnet mask to the interface.
The keywords and arguments are as follows:
•ip-address—IP address.
•mask—Mask for the associated IP subnet.
•secondary—(Optional) Specifies that the configured address is a secondary IP address. If this keyword is omitted, the configured address is the primary IP address.
|
Step 3
|
Router(config-if)# atm scramble-enable
|
(E1 configuration only) Helping to ensure reliability, scrambling randomizes the ATM cell payload frames to avoid continuous nonvariable bit patterns and to improve the efficiency of ATM cell delineation algorithms.
|
Step 4
|
Router(config-if)# atm video aesa
{default |esi-address}
|
Sets the unique ATM end-station address (AESA) for an ATM video interface that is using switched virtual circuit (SVC) mode.
The keywords and arguments are as follows:
•default—Automatically creates a network service access point (NSAP) address for the interface, based on a prefix from the ATM switch (26 hexadecimal characters), the MAC address (12 hexadecimal characters) as the end system identifier (ESI), and a selector byte (two hexadecimal characters).
•esi-address—Requires that you enter 12 hexadecimal characters as the ESI. The ATM switch provides the prefix, and the video selector byte provides the remaining characters.
You can view the assigned address by using the show atm video-voice address command.
|
Step 5
|
Router(config-if)# pvc [name] vpi/vci
[ilmi | qsaal | smds]
|
Creates or assigns a name to an ATM permanent virtual circuit (PVC), specifies the encapsulation type on an ATM PVC, and enters interface-ATM-VC configuration mode.
Note To set up communication with the Integrated Local Management Interface (ILMI), enter the ilmi keyword for ATM adaptation layer encapsulation; the associated vpi and vci values are ordinarily 0 and 16, respectively.
Note To enable the signaling for setup and teardown of SVCs, specify the Q.SAAL (signaling ATM adaptation layer) encapsulation as the name; the associated vpi and vci values are ordinarily 0 and 5, respectively. You cannot create this PVC on a subinterface.
|
| |
|
Complete keyword and argument definitions are as follows:
•name—(Optional) Specifies a unique label that can be up to 16 characters long. It identifies to the processor the virtual path identifier-virtual channel identifier (VPI-VCI) pair to use for a particular packet.
• |
