|
|
This feature module describes the Multimedia Conference Manager with Voice Gateway Image with RSVP to ATM SVC Mapping feature. It includes information on the benefits of the new feature, supported platforms, related documents, and so forth.
This feature is designed to deliver Cisco's 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.
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's voice gateway and routing functionalities in the same image.
For more detailed information about the MCM, see Multimedia Conference Manager.
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 will be able to guarantee that video sessions will traverse that backbone with QoS features enabled. The Cisco IOS image will take H.323 RSVP reservations and map them to ATM VBR SVCs that will be 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.
One-Box Solution
By incorporating the gateway into the MCM image, customers will be able to reduce their overall cost of ownership. What was historically a two box solution is now reduced to one. 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 as well. Proxied calls will be 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.
Video over ATM Switched Virtual Circuits on the Cisco MC3810
Standards
New or modified standards supported by this feature:
MIBs
For descriptions of supported MIBs and how to use MIBs, see the Cisco MIB web site on CCO at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
No new or modified RFCs are supported by this feature.
For this feature to function properly, you must have 16 MB of Flash memory and 64 MB of DRAM memory. For the Cisco 3660 and Cisco 7200 series, 96 MB of DRAM is required.
See the following sections for configuration tasks for the Multimedia Conference Manager (MCM) with Voice Gateway Image with RSVP to ATM SVC Mapping feature.
To configure the MCM for voice and data traffic, refer to the document Multimedia Conference Manager.
To configure the MCM for this feature, follow the steps below.
| Command | Purpose/Comment | |
|---|---|---|
Step 1 | Router(config)#proxy h323 | Enables the proxy's activity. If the current running state has the negative specified, the proxy will be dormant. |
Step 2 | Router(config)#ip routing | Makes sure that Fast Switching is enabled, which is required for the T.120 feature. |
Step 3 | Router(config)#interface e0 | Enters interface configuration mode. |
Step 4 | Router(config-if)# ip route-cache same-interface | Tells the proxy that when sending the packets out, it should use the same interface that the packets came in on. The packets will be sent within the interrupt service context. Otherwise, the packets will be queued for processing by the Cisco IOS, which is slower and may lead to packet loss. |
Step 5 | Router(config-if)# | Enables proxy on this interface. With this feature, a port can be assigned. To use the default port, enter no h323 interface and then h323 interface. |
Step 6 | Router(config-if)# | Names proxy in registration with the gatekeeper. If the proxy has registered successfully on a CiscoMCM gatekeeper, you can see the name of the proxy if you enter show gatekeeper endpoints. |
Step 7 | Router(config-if)# | Specifies the gatekeeper interface for registration. You can specify a gatekeeper name (with id), IP address (with ipaddr), and port. You can also tell the proxy to use a well-known multicast address to discover a gatekeeper. |
Step 8 | Router(config-if)# | Enables T.120 proxy capabilities on the router. To disable the T.120 proxy, enter h323 t120 bypass. |
Step 9 | Router(config-if)# exit | Exits interface configuration mode. |
To configure the gatekeeper to support zones, use the zone local and zone remote commands, beginning in gatekeeper configuration mode, as described in "Configuring H.323 VoIP Gatekeeper for Cisco Access Platforms.
| Command | Purpose/Comment | |
|---|---|---|
Step 1 | Router(config)# gatekeeper | Enters gatekeeper configuration mode. |
Step 2 | Router(config-gk)# bandwidth session Zone3 500 | Specifies the maximum bandwidth allowed for a session in Zone3 to 500 kbps. |
Step 3 | Router(config-gk)# exit | Exits gatekeeper configuration mode. |
Refer to the document RSVP-ATM QoS Interworking for information on how to configure RSVP over an ATM network.
Router# show gatekeeper status Gatekeeper State:UP Zone Name: DVM1 Zone Name: DVM2 Zone Name: test1 Accounting: DISABLED Security: DISABLED Maximum Remote Bandwidth: Current Remote Bandwidth:0 kbps
Step 2 Enter the show gatekeeper zone status command. This displays the bandwidth information for all zones:
Router# sho gatekeeper zone status
GATEKEEPER ZONES
================
GK name Domain Name RAS Address PORT FLAGS
------- ----------- ----------- ----- -----
DVM1 dvm1.com 172.28.129.50 1719 LS
BANDWIDTH INFORMATION (kbps) :
Maximum interzone bandwidth :
Current interzone bandwidth : 0
Maximum total bandwidth :
Current total bandwidth : 0
Maximum session bandwidth :
SUBNET ATTRIBUTES :
All Other Subnets :(Enabled)
PROXY USAGE CONFIGURATION :
Inbound Calls from DVM2 :
to terminals in local zone DVM1 :use proxy
to gateways in local zone DVM1 :do not use proxy
Outbound Calls to DVM2 :
from terminals in local zone DVM1 :use proxy
from gateways in local zone DVM1 :use proxy
Inbound Calls from all other zones :
to terminals in local zone DVM1 :use proxy
to gateways in local zone DVM1 :do not use proxy
Outbound Calls to all other zones :
from terminals in local zone DVM1 :use proxy
from gateways in local zone DVM1 :do not use proxy
DVM2 dvm2.com 172.28.129.50 1719 LS
BANDWIDTH INFORMATION (kbps) :
Maximum interzone bandwidth :
Current interzone bandwidth : 0
Maximum total bandwidth :
Current total bandwidth : 0
Maximum session bandwidth :
SUBNET ATTRIBUTES :
All Other Subnets :(Enabled)
PROXY USAGE CONFIGURATION :
Inbound Calls from all other zones :
to terminals in local zone DVM2 :use proxy
to gateways in local zone DVM2 :do not use proxy
Outbound Calls to all other zones :
from terminals in local zone DVM2 :use proxy
from gateways in local zone DVM2 :do not use proxy
test1 cisco.com 172.28.129.50 1719 LS
BANDWIDTH 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 proxy
to gateways in local zone test1 :do not use proxy
Outbound Calls to all other zones :
from terminals in local zone test1 :use proxy
from gateways in local zone test1 :do not use proxy
TEST2 test2.com 172.28.129.54 1719 RS
Maximum interzone bandwidth :
Current interzone bandwidth : 0
Step 3 Enter the show proxy h323 status command. This displays information about the proxy such as the T.120 mode and what port is being used:
Router# sho proxy h323 status
H.323 Proxy Status
==================
H.323 Proxy Feature:Enabled
Proxy interface = Ethernet0:UP
Proxy IP address = 172.28.129.50
Proxy IP port = 11720
Application Specific Routing:Disabled
RAS Initialization:Complete
Proxy aliases configured:
H323_ID:PROXY
Proxy aliases assigned by Gatekeeper:
H323_ID:PROXY
Gatekeeper multicast discovery:Disabled
Gatekeeper:
Gatekeeper ID:DVM1
IP address:172.28.129.50
Gatekeeper registration succeeded
T.120 Mode:PROXY
RTP Statistics:OFF
Number of calls in progress:0
The following example is of an interzone calling configuration with two zones defined as Aspen and Vail.
The terminals are H.323 terminals.
The definitions for the above are:
Every device with Aspen in its name is registered to the Aspen gatekeeper, and every device with Vail in its nameis registered with the Vail gatekeeper.
The following is the configuration for Aspen MCM GK Proxy:
Hostname Aspen_MCM_GK_Proxy Proxy h323 interface Ethernet0/0 ip address 10.0.0.1 255.0.0.0 h323 interface h323 qos ip-precedence 6 h323 h323-id aspen-proxy h323 gatekeeper id aspen ipaddr 10.0.0.1 gatekeeper zone local aspen cisco.com 10.0.0.1 zone remote vail cisco.com 12.0.0.1 zone prefix aspen 11 zone prefix vail 12 gw-type-prefix 60 gw ipaddr 10.0.0.2 2720 gw-type-prefix 61 gw ipaddr 10.0.0.2 2720 gw-type-prefix 62 gw ipaddr 10.0.0.2 2720 use-proxy aspen default outbound-from gateway no shutdown
The following is the configuration for Vail MCM GK Proxy:
Hostname Vail_MCM_GK_Proxy Proxy h323 interface Ethernet0/0 ip address 10.0.0.1 255.0.0.0 h323 interface h323 qos ip-precedence 6 h323 h323-id vail-proxy h323 gatekeeper id vail ipaddr 12.0.0.1 gatekeeper zone local vail cisco.com 12.0.0.1 zone remote aspen cisco.com 10.0.0.1 zone prefix aspen 11 zone prefix vail 12 gw-type-prefix 60 hopoff aspen gw-type-prefix 61 hopoff aspen gw-type-prefix 62 hopoff aspen use-proxy aspen default outbound-from gateway no shutdown
In 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. 61 is the conference prefix, 555 is the conference password, ** is the invite, 33 is the E.164 address of Aspen Terminal C, 12 is the zone prefix to reach the Vail zone, and 21 is the E.164 address of Vail Terminal A.
Alternatively, each terminal could independently dial 61555 to join the conference.
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.
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
Syntax Description
interzone Specifies the total amount of bandwidth for H.323 traffic from the zone to any other zone. total Specifies the total amount of bandwidth for H.323 traffic allowed in the zone. session Specifies the maximum bandwidth allowed for a session in the zone. default Specifies the default value for all zones. zone zone-name A specific zone. bandwidth-size Maximum bandwidth. For interzone and total, range is 1 through 10,000,000 kbps. For session, range is 1 through 5,000 kbps.
Defaults
None
Command Modes
Gatekeeper configuration
Command History
12.1(3)XI This command was introduced.
Release
Modification
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)# gatekeeper Router(config-gk)# bandwidth total default 5000
Related Commands
bandwidth remote Specifies the total bandwidth for H.323 traffic between this gatekeeper and any other gatekeeper. h323 interface Defines which port the proxy will listen on. h323 t120 Enables the T.120 capabilities on your router and specifies bypass or proxy mode.
Command
Description
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
Syntax Description
bandwidth-size Maximum bandwidth. Range is 1 through 10,000,000 kbps.
Defaults
None
Command Modes
Gatekeeper configuration
Command History
12.1(3)XI This command was introduced.
Release
Modification
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)# gatekeeper Router(config-gk)# bandwidth remote 100000
Related Commands
bandwidth Specifies the maximum aggregate bandwidth for H.323 traffic from a zone to another zone, within a zone, or for a session in a zone. h323 interface Defines which port the proxy will listen on. h323 t120 Enables the T.120 capabilities on your router and specifies bypass or proxy mode.
Command
Description
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 ]
Syntax Description
port number (Optional) The port number the proxy will listen on for incoming call setup requests. Range is 1 through 65356. The default port number for the proxy is 11720 in -isx- or -jsx- Cisco IOS images. The default port number for the proxy is 1720 in -ix- Cisco IOS images, which do not contain the VoIP gateway.
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(3)XI The ability to specify the proxy port number was added.
Release
Modification
Usage Guidelines
At proxy startup, the code checks for the presence of the VoIP gateway subsystem, and if 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 configures Ethernet interface 0 (e0) for incoming call setup requests:
Router(config)# interface e0 Router(config-if)# h323 interface
Related Commands
bandwidth Specifies the maximum aggregate bandwidth for H.323 traffic from a zone to another zone, within a zone, or for a session in a zone. bandwidth remote Specifies the total bandwidth for H.323 traffic between this gatekeeper and any other gatekeeper. h323 t120 Enables the T.120 capabilities on your router and specifies bypass or proxy mode.
Command
Description
Syntax Description
bypass Bypass mode. In this mode, the H.245 Open Logical Channel messages for T.120 data channels were passed unmodified through the proxy, and TCP connections for T.120 are established directly between the two endpoints of the H.323 call. proxy Proxy mode. In this mode, T.120 features function properly.
Defaults
Bypass mode
Command Modes
Interface configuration
Command History
12.1(3)XI This command was introduced.
Release
Modification
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 enables the T.120 capabilities:
Router(config)# proxy h323 Router(config)# interface e0 Router(config-if)# h323 t120 proxy
Related Commands
bandwidth Specifies the maximum aggregate bandwidth for H.323 traffic from a zone to another zone, within a zone, or for a session in a zone. bandwidth remote Specifies the total bandwidth for H.323 traffic between this gatekeeper and any other gatekeeper. h323 interface Defines which port the proxy will listen on.
Command
Description
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.
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: RAS, use of Q.931, and use of 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.
IOS—Cisco's Internetworking Operating System.
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 RAS to communicate with the gatekeeper. For example, an endpoint such as a terminal, proxy, or gateway.
PAT—Port Address Translation.
proxy—Proxies are 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.
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.
Posted: Thu Sep 7 10:24:43 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.