Table Of Contents
Multimedia Conference Manager with Voice Gateway Image with RSVP to ATM SVC Mapping
MCM, Gatekeeper, Proxy, and Gateway
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Configuring the Proxy and T.120
Cisco IP/VC 3510 MCU with Cisco IOS MCM/Proxy
Multimedia Conference Manager with Voice Gateway Image with RSVP to ATM SVC Mapping
November 2, 2000
Cisco IOS Software Release 12.1(3)XIThis feature module describes the Multimedia Conference Manager with Voice Gateway Image with RSVP to ATM SVC Mapping feature. It includes information on the following topics:
•
Supported Standards, MIBs, and RFCs
Feature Overview
This feature is designed to deliver the Cisco H.323 gatekeeper, proxy, and voice gateway solutions with routing as a single Cisco IOS image. In addition, the ability to map H.323 Resource Reservation Protocol (RSVP) reservations to ATM non-real-time variable bit rate (VBR) switched virtual circuits (SVCs) has also been incorporated for guaranteeing quality of service (QoS) over ATM backbones for video applications.
MCM, Gatekeeper, Proxy, and Gateway
The H.323 Multimedia Conference Manager (MCM) provides the network administrator with the ability to identify H.323 traffic and apply appropriate policies. H.323 MCM is implemented on Cisco IOS software. MCM provides a network manager with the ability to limit the H.323 traffic on the LAN and WAN; provides user accounting for records based on the service utilization; injects QoS for the H.323 traffic generated by applications such as VoIP, data conferencing and video conferencing; and provides the mechanism to implement security for H.323 communications. In addition to this functionality, this new and separate image also incorporates Cisco voice gateway and routing functionalities in the same image.
For more detailed information about the MCM, see Multimedia Conference Manager.
ATM VBR SVC Support for Video
ATM non-real-time variable bit rate (VBR) switched virtual circuit (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 permanent virtual circuit (PVC) or an SVC with an ATM signaling mechanism.
With this feature, customers that use ATM backbones can guarantee that video sessions traverse that backbone with QoS features enabled. The Cisco IOS image takes H.323 RSVP reservations and maps them to ATM VBR 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.
Benefits
One-Box Solution
By incorporating the gateway into the MCM image, customers can reduce their overall cost of ownership. What was historically a two-box solution is now reduced to one box. Not only is this a cost savings to the customer, but also one less box to manage.
Bandwidth and Resource Management
Users can stipulate bandwidth limits for each video conferencing connection as well as an aggregate bandwidth limit for all video conferencing sessions. This is not an attempt to provide line conditioning, rather the ability to provide notification to endpoints of bandwidth limitations.
NetMeeting Capabilities
The Proxy can now forward T.120 connections, thus enhancing real-time data conferencing capabilities.
Load-Balancing
The gatekeeper has been enhanced to perform load-balancing functionality for external H.323 v2 gateways.
Call Accounting
The MCM supports Call Accounting functionality for proxied calls. Proxied calls are recorded into call history to provide additional call detail information.
Call Manager Environments
Use of an H.323 gatekeeper is recommended for use with multiple Call Manager or Call Manager cluster domains. This provides critical Connection Admission Control (CAC) between domains to guarantee that the number of calls between locations does not exceed available bandwidth. Thus, integration of necessary gatekeeper functionality within a Cisco IOS gateway device saves costs and increases reliability of IP telephony systems.
Restrictions
•
•
•
•
Related Features and Technologies
Multimedia Conference Manager
Deploying H.323 applications and services requires careful design and planning both on the network infrastructure and the H.323 devices. The Multimedia Conference Manager provides both gatekeeper and proxy capabilities, which are required for service provisioning and management of H.323 networks. The Multimedia Conference Manager feature provides H.323 application options previously unavailable. Using Multimedia Conference Manager, you can implement H.323-compliant applications on existing networks in an incremental fashion without upgrades.
Related Documents
•
•
•
•
•
Supported Platforms
•
•
•
•
Supported Standards, MIBs, and RFCs
Standards
New or modified standards supported by this feature:
•
MIBs
New or modified MIBs supported by this feature:
•
•
To obtain lists of MIBs supported by platform and Cisco IOS release and to download MIB modules, go to the Cisco MIB web site on Cisco Connection Online (CCO) at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
No new or modified RFCs are supported by this feature.
Prerequisites
For this feature to function properly, you must have 16 megabytes of Flash memory and 64 megabytes of DRAM memory. For the Cisco 3660 and Cisco 7200 series, 96 megabytes of DRAM is required.
Configuration Tasks
See the following sections for configuration tasks for the Multimedia Conference Manager (MCM) with Voice Gateway Image with RSVP to ATM SVC Mapping feature. Each task in the list indicates if the task is optional or required.
•
Configuring the Proxy and T.120
To configure the MCM for voice, video, and data traffic, refer to the document Multimedia Conference Manager.
To configure the MCM for this feature, follow these steps:
Configuring the Gatekeeper
To configure the gatekeeper to support zones, use the zone local and zone remote commands, beginning in gatekeeper configuration mode, as described in the document Configuring H.323 VoIP Gatekeeper for Cisco Access Platforms.
Configuring the ATM SVC
Refer to the document RSVP-ATM QoS Interworking for information on how to configure RSVP over an ATM network.
Verifying Configuration
Step 1
Router# show gatekeeper statusGatekeeper State:UPZone Name: DVM1Zone Name: DVM2Zone Name: test1Accounting: DISABLEDSecurity: DISABLEDMaximum Remote Bandwidth:Current Remote Bandwidth:0 kbps
Step 2
Router# show gatekeeper zone statusGATEKEEPER ZONES================GK name Domain Name RAS Address PORT FLAGS------- ----------- ----------- ----- -----DVM1 dvm1.com 172.28.129.50 1719 LSBANDWIDTH INFORMATION (kbps) :Maximum interzone bandwidth :Current interzone bandwidth : 0Maximum total bandwidth :Current total bandwidth : 0Maximum session bandwidth :SUBNET ATTRIBUTES :All Other Subnets :(Enabled)PROXY USAGE CONFIGURATION :Inbound Calls from DVM2 :to terminals in local zone DVM1 :use proxyto gateways in local zone DVM1 :do not use proxyOutbound Calls to DVM2 :from terminals in local zone DVM1 :use proxyfrom gateways in local zone DVM1 :use proxyInbound Calls from all other zones :to terminals in local zone DVM1 :use proxyto gateways in local zone DVM1 :do not use proxyOutbound Calls to all other zones :from terminals in local zone DVM1 :use proxyfrom gateways in local zone DVM1 :do not use proxyDVM2 dvm2.com 172.28.129.50 1719 LSBANDWIDTH INFORMATION (kbps) :Maximum interzone bandwidth :Current interzone bandwidth : 0Maximum total bandwidth :Current total bandwidth : 0Maximum session bandwidth :SUBNET ATTRIBUTES :All Other Subnets :(Enabled)PROXY USAGE CONFIGURATION :Inbound Calls from all other zones :to terminals in local zone DVM2 :use proxyto gateways in local zone DVM2 :do not use proxyOutbound Calls to all other zones :from terminals in local zone DVM2 :use proxyfrom gateways in local zone DVM2 :do not use proxytest1 cisco.com 172.28.129.50 1719 LSBANDWIDTH INFORMATION (kbps) : Maximum session bandwidth :SUBNET ATTRIBUTES :All Other Subnets :(Enabled)PROXY USAGE CONFIGURATION :Inbound Calls from all other zones :to terminals in local zone test1 :use proxyto gateways in local zone test1 :do not use proxyOutbound Calls to all other zones :from terminals in local zone test1 :use proxyfrom gateways in local zone test1 :do not use proxyTEST2 test2.com 172.28.129.54 1719 RSMaximum interzone bandwidth :Current interzone bandwidth : 0Step 3
Router# show proxy h323 statusH.323 Proxy Status==================H.323 Proxy Feature:EnabledProxy interface = Ethernet0:UPProxy IP address = 172.28.129.50Proxy IP port = 11720Application Specific Routing:DisabledRAS Initialization:CompleteProxy aliases configured:H323_ID:PROXYProxy aliases assigned by Gatekeeper:H323_ID:PROXYGatekeeper multicast discovery:DisabledGatekeeper:Gatekeeper ID:DVM1IP address:172.28.129.50Gatekeeper registration succeededT.120 Mode:PROXYRTP Statistics:OFFNumber of calls in progress:0
Configuration Examples
Cisco IP/VC 3510 MCU with Cisco IOS MCM/Proxy
The following example is of an interzone calling configuration with two zones defined as Aspen and Vail.
Figure 1 Interzone Calling Configuration with Two Zones
The terminals are H.323 terminals.
The definitions for the above are as follows:
•
•
•
•
•
•
•
•
•
•
•
•
Every device with Aspen in its name is registered with the Aspen gatekeeper, and every device with Vail in its name is registered with the Vail gatekeeper.
The following is the configuration for Aspen MCM GK Proxy:
Hostname Aspen_MCM_GK_ProxyProxy h323interface Ethernet0/0ip address 10.0.0.1 255.0.0.0h323 interfaceh323 qos ip-precedence 6h323 h323-id aspen-proxyh323 gatekeeper id aspen ipaddr 10.0.0.1gatekeeperzone local aspen cisco.com 10.0.0.1zone remote vail cisco.com 12.0.0.1zone prefix aspen 11zone prefix vail 12use-proxy aspen default outbound-from gatewayno shutdownThe following is the configuration for Vail MCM GK Proxy:
Hostname Vail_MCM_GK_ProxyProxy h323interface Ethernet0/0ip address 10.0.0.1 255.0.0.0h323 interfaceh323 qos ip-precedence 6h323 h323-id vail-proxyh323 gatekeeper id vail ipaddr 12.0.0.1gatekeeperzone local vail cisco.com 12.0.0.1zone remote aspen cisco.com 10.0.0.1zone prefix aspen 11zone prefix vail 12gw-type-prefix 60 hopoff aspengw-type-prefix 61 hopoff aspengw-type-prefix 62 hopoff aspenuse-proxy aspen default outbound-from gatewayno shutdownIn this example, any terminal registered with the Aspen or Vail gatekeeper may participate in a multiparty call with any participant in either zone. For example, Aspen Terminal A could have a conference with Aspen Terminal C and Vail Terminal A by dialing 61555**33**1221. The conference prefix is 61, the conference password is 555, the invite is **, the E.164 address of Aspen Terminal C is 33, the zone prefix to reach the Vail zone is 12, and the E.164 address of Vail Terminal A is 21.
Alternatively, each terminal could independently dial 61555 to join the conference.
Command Reference
This section documents new or modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.1 command reference publications.
bandwidth
To specify the maximum aggregate bandwidth for H.323 traffic, use the bandwidth gatekeeper configuration command. To disable, use the no form of this command.
bandwidth { interzone | total | session } { default | zone zone-name } bandwidth-size
no bandwidth { interzone | total | session } { default | zone zone-name } bandwidth-size
Syntax Description
Defaults
None
Command Modes
Gatekeeper configuration
Command History
Usage Guidelines
The functionality of this command in previous Cisco IOS software releases was obtained by using the zone gatekeeper command.
Examples
The following example configures the default maximum bandwidth for all zones to 5,000 kbps:
Router(config)# gatekeeperRouter(config-gk)# bandwidth total default 5000Related Commands
bandwidth remote
To specify the total bandwidth for H.323 traffic between this gatekeeper and any other gatekeeper, use the bandwidth remote gatekeeper configuration command. To disable, use the no form of this command.
bandwidth remote bandwidth-size
no bandwidth remote bandwidth-size
Syntax Description
Defaults
None
Command Modes
Gatekeeper configuration
Command History
Usage Guidelines
The functionality of this command in previous Cisco IOS software releases was obtained by using the zone gatekeeper command.
Examples
The following example configures the remote maximum bandwidth to 100,000 kbps:
Router(config)# gatekeeperRouter(config-gk)# bandwidth remote 100000Related Commands
h323 interface
To select an interface whose IP address will be used by the proxy to register with the gatekeeper, use the h323 interface interface configuration command. To use the default port, use no h323 interface and then h323 interface.
h323 interface [ port number ]
no h323 interface [ port number ]
Syntax Description
Defaults
Default port number is image dependent; see the Syntax Description table above.
Command Modes
Interface configuration
Command History
12.0(5)
This command was introduced.
12.1(5)T
The ability to specify the proxy port number was added.
Usage Guidelines
At proxy startup, the code checks for the presence of the VoIP gateway subsystem. If the subsystem is found to be present, the proxy code opens and listens for call setup requests on the new port. The proxy then registers this port with the gatekeeper.
Examples
The following example show how to configure Ethernet interface 0 (e0) for incoming call setup requests:
Router(config)# interface e0Router(config-if)# h323 interfaceRelated Commands
h323 t120
To enable the T.120 capabilities on your router and to specify bypass or proxy mode, use the h323 t120 interface configuration command.
h323 t120 { bypass | proxy }
Syntax Description
Defaults
Bypass mode
Command Modes
Interface configuration
Command History
Usage Guidelines
The no form of this command has no function—the only possible commands are h323 t120 bypass and h323 t120 proxy.
Examples
The following example shows how to enable the T.120 capabilities:
Router(config)# proxy h323Router(config)# interface e0Router(config-if)# h323 t120 proxyRelated Commands
Glossary
AAA—Authorization, authentication, and accounting.
ABR—Available bit rate.
ASR—Application Specification Routing.
ATM—Asynchronous Transfer Mode. The ATM module command-line interface (CLI) uses a subset of the Cisco IOS software commands. Generally, the Cisco IOS software works the same on the ATM module as it does on routers.
BGP—Border Gateway Protocol.
Cisco IOS—The Cisco Internetwork Operating System.
CLI—Command-line interface.
gatekeeper—A gatekeeper maintains a registry of devices in the multimedia network. The devices register with the gatekeeper when they start up, and request admission to a call from the gatekeeper.
gateway—Gateways allow H.323 terminals to communicate with non-H.323 terminals by converting protocols.
H.225.0—An ITU standard that governs H.323 session establishment and packetization. H.225.0 actually describes several different protocols: Registration, Admission, and Status protocol (RAS); use of Q.931,;and use of Real-Time Transport Protocol (RTP).
H.245—An ITU standard that governs H.323 endpoint control.
H.323—An International Telecommunication Union (ITU) standard that describes packet-based video, audio, and data conferencing. H.323 is an umbrella standard that describes the architecture of the conferencing system, and refers to a set of other standards (H.245, H.225.0, and Q.931) to describe its actual protocol.
H.323 terminal—Endpoints in the multimedia network that provide real-time, two-way communications with another H.323 terminal. H.323 terminals are typically computer-based video conferencing systems.
MCM—Multimedia Conference Manager. Provides both gatekeeper and proxy capabilities, which are required for service provisioning and management of H.323 networks.
MCU— Multipoint control unit. An endpoint on the LAN that provides the capability for three or more terminals and gateways to participate in a multipoint conference.
NAT—Network Address Translation.
NMS—Network management system.
node—An H.323 entity that uses Registration, Admission, and Status protocol (RAS) to communicate with the gatekeeper; for example, an endpoint such as a terminal, proxy, or gateway.
PAT—Port Address Translation.
proxy—Special gateways that relay one H.323 session to another.
PVC—Permanent virtual circuit.
Q.931—An ITU standard that describes ISDN signaling. The H.225.0 standard uses a variant of Q.931 to establish and disconnect H.323 sessions.
QoS—Quality of service. Prioritizes network traffic with IEEE 802.1P class of service (CoS) values that allow network devices to recognize and deliver high-priority traffic in a predictable manner. When congestion occurs, QoS drops low-priority traffic to allow delivery of high-priority traffic.
RAI—Resource Availability Indication.
RAS—Registration, Admission, and Status protocol. This is the protocol used between endpoints and the gatekeeper.
RTP—Real-Time Transport Protocol. An IETF standard protocol. The H.225.0 standard describes how to use RTP to handle the packetization of video and audio in H.323.
SNMP—Simple Network Management Protocol.
SVC—Switched virtual circuits.
T.120—An ITU standard that describes data conferencing. H.323 provides for the ability to establish T.120 data sessions inside an existing H.323 session.
VBR—Variable bit rate.
VoFR—Voice over Frame Relay.
VoIP—Voice over IP. Voice over IP enables a router to carry voice traffic (for example, telephone calls and faxes) over an IP network.
Guest
