|
|
Table Of Contents
Prerequisites for Setting Video Parameters
Restrictions for Setting Video Parameters
Information About Setting Video Parameters
Matching Endpoint Capabilities
Retrieving Video Codec Information
Call Setup for Video Endpoints
How to Set Video Parameters for Cisco Unified SRST
Configuring Slow Connect Procedures
Setting Video Parameters for Cisco Unified SRST
Troubleshooting Video for Cisco Unified SRST
Setting Video Parameters
This chapter describes how to set video parameters for a Cisco Unified Survivable Remote Site Telephony (SRST) router.
Note
Prior to version 4.0, the name of this product was Cisco SRST.
Contents
•
Prerequisites for Setting Video Parameters
•
Restrictions for Setting Video Parameters
•
Information About Setting Video Parameters
•
How to Set Video Parameters for Cisco Unified SRST
•
Troubleshooting Video for Cisco Unified SRST
Prerequisites for Setting Video Parameters
•
Ensure that you are using Cisco Unified SRST 4.0 or later.
•
Ensure that you are using Cisco Unified CallManager 4.0 or later.
•
Ensure that the Cisco IP phones are registered with the Cisco Unified SRST router. Use the show ephone registered command to verify ephone registration.
•
Ensure that the connection between the Cisco Unified Video Advantage application and the Cisco Unified IP phone is up.
From a PC with Cisco Unified Video Advantage version 1.02 or later installed, ensure that the line between the Cisco Unified Video Advantage and the Cisco Unified IP phone is green. For more information, see the Cisco Unified Video Advantage User Guide.
•
Ensure that the correct video firmware is installed on the Cisco Unified IP phone. Use the show ephone phone-load command to view current ephone firmware. The following lists the minimum firmware version for video-enabled Cisco Unified IP phones:
–
Cisco Unified IP Phone 7940G release 6.0(4)
–
Cisco Unified IP Phone 7960G release 6.0(4)
–
Cisco Unified IP Phone 7970G release 6.0(2)
•
Perform basic Cisco Unified SRST configuration. For more information, see Cisco Unified SRST V4.0: Setting Up the Network.
•
Perform basic ephone configuration. For more information, see Cisco Unified SRST V4.0: Setting Up Cisco Unified IP Phones.
Restrictions for Setting Video Parameters
•
This feature supports only the following video codecs:
–
H.261
–
H.263
•
This feature supports only the following video formats:
–
Common Intermediate Format (CIF)—Resolution 352x288
–
One-Quarter Common Intermediate Format (QCIF)—Resolution 176x144
–
Sub QIF (SQCIF)—Resolution 128x96
–
4CIF—Resolution 704x576
–
16CIF—Resolution 1408x1152
•
The call start fast feature is not supported with an H.323 video connection. You must configure call start slow for H.323 video.
•
Video capabilities are configured per ephone, not per line.
•
All call feature controls (for example, mute and hold) apply to both audio and video calls, if applicable.
•
This feature does not support the following:
–
Dynamic addition of video capability—The video capability must be present before the call setup starts to allow the video connection.
–
T-120 data connection between two SCCP endpoints
–
Video security
–
Far-end camera control (FECC) for SCCP endpoints
–
Video codec renegotiation—The negotiated video codec must match or the call falls back to audio-only. The negotiated codec for the existing call can be used for a new call.
–
Video codec transcoding
•
When a video-capable endpoint connects to an audio-only endpoint, the call falls back to audio-only. During audio-only calls, video messages are skipped.
Information About Setting Video Parameters
This feature allows you to set video parameters for the Cisco Unified SRST to maintain close feature parity with Cisco Unified CallManager. When the Cisco Unified SRST is enabled, Cisco Unified IP phones do not have to be reconfigured for video capabilities because all ephones retain the same configuration used with Cisco Unified CallManager. However, you must enter call-manager-fallback configuration mode to set video parameters for Cisco Unified SRST. The feature set for video is the same as that for Cisco Unified SRST audio calls.
To set video parameters, you should understand the following concepts:
•
Matching Endpoint Capabilities
•
Retrieving Video Codec Information
•
Call Setup for Video Endpoints
•
Flow of the RTP Video Stream
Matching Endpoint Capabilities
Endpoint capabilities are stored in the Cisco Unified SRST during phone registration. These capabilities are used to match with other endpoints during call setup. Endpoints can update at any time; however, the router recognizes endpoint-capability changes only during call setup. If a video feature is added to a phone, the information about it is updated in the router's internal data structure, but that information does not take effect until the next call. If a video feature is removed, the router continues to see the video capability until the call is terminated but no video stream is exchanged between the two endpoints.
Note
The endpoint-capability match is executed every time a new call is set up or an existing call is resumed.
Retrieving Video Codec Information
Voice gateways use dial-peer configurations to retrieve codec information for audio codecs. Video codec selection is done by the endpoints and is not controlled by the H.323 service-provider interface (SPI) through dial-peer or other configuration. The video-codec information is retrieved from the SCCP endpoint using a capabilities request during call setup.
Call Fallback to Audio-Only
When a video-capable endpoint connects to an audio-only endpoint, the call falls back to an audio-only connection. Also, for certain features such as conferencing, where video support is not available, the call falls back to audio-only.
Cisco Unified SRST routers use a call-type flag to indicate whether the call is video-capable or audio-only. The call-type flag is set to video when the video capability is matched or set to audio-only when connecting to an audio-only TDM or an audio-only SIP endpoint.
Note
During an audio-only connection, all video-related media messages are skipped.
Call Setup for Video Endpoints
The process for handling SCCP video endpoints is the same as that for handling SCCP audio endpoints. The video call must be part of the audio call. If the audio call setup fails, the video call fails.
During call setup for video, media setup handling determines if a video-media path is required or not. If so, the corresponding video-media-path setup actions are taken.
•
For an SCCP endpoint, video-media-path setup includes sending messages to the endpoints to open a multimedia path and start the multimedia transmission.
•
For an H.323 endpoint, video-media-path setup includes an exchange between the endpoints to open a logical channel for the video stream.
A call-type flag is set during call setup on the basis of the endpoint-capability match. After call setup, the call-type flag is used to determine whether an additional video-media path is required. Call signaling is managed by the Cisco Unified CME router, and the media stream is directly connected between the two video-enabled SCCP endpoints on the same router. Video-related commands and flow-control messages are forwarded to the other endpoint. Routers do not interpret these messages.
Call Setup Between Two Local SCCP Endpoints
For interoperation between two local SCCP endpoints (that exist on the same router), video call setup uses all existing audio-call-setup handling, except during media setup. During media setup, a message is sent to establish the video-media path. If the endpoint responds, the video-media path is established and a start-multimedia-transmission function is called.
Call Setup Between SCCP and H.323 Endpoints
Call setup between SCCP and H.323 endpoints is the same as it is between SCCP endpoints except that, if video capability is selected, the event is posted to the H.323 call leg to send out a video open logical channel (OLC) and the gateway generates an OLC for the video channel. Because the router needs to both terminate and originate the media stream, video must be enabled on the router before call setup begins.
Call Setup Between Two SCCP Endpoints Across an H.323 Network
If call setup between SCCP endpoints occurs across an H.323 network, the setup is a combination of the processes listed in the previous two sections. The router controls the video media setup between the two endpoints, and the event is posted to the H.323 call leg so that the gateway can generate an OLC.
Flow of the RTP Video Stream
For video streams between two local SCCP endpoints, the Real-Time Transport Protocol (RTP) stream is in flow-around mode. For video streams between SCCP and H.323 endpoints or two SCCP endpoints on different Cisco Unified CME routers, the RTP stream is in flow-through mode.
•
Media flow-around mode enables RTP packets to stream directly between the endpoints of a VoIP call without the involvement of the gateway. By default, the gateway receives the incoming media, terminates the call, and then reoriginates it on the outbound call leg. In flow-around mode, only signaling data is passed to the gateway, improving scalability and performance.
•
Media flow-through mode involves the same video-media path as for an audio call. Media packets flow through the gateway, thus hiding the networks from each other.
To display information about RTP named-event packets, such as caller-ID number, IP address, and port for both the local and remote endpoints, use the show voip rtp connection command as show in the following sample output.
Router# show voip rtp connectionsVoIP RTP active connections :No. CallId dstCallId LocalRTP RmtRTP LocalIP RemoteIP1 102 103 18714 18158 10.1.1.1 192.168.1.12 105 104 17252 19088 10.1.1.1 192.168.1.1Found 2 active RTP connections============================How to Set Video Parameters for Cisco Unified SRST
When the Cisco Unified SRST is enabled, Cisco Unified IP phones do not have to be reconfigured for video capabilities because all ephones retain the same configuration used with Cisco Unified CallManager. However, you can set video parameters for Cisco Unified SRST.
Setting Video parameters for Cisco Unified SRST involves the following tasks:
•
Configuring Slow Connect Procedures
•
Verifying Cisco Unified SRST
•
Setting Video Parameters for Cisco Unified SRST
Configuring Slow Connect Procedures
Video streams require slow-connect procedures for Cisco Unified SRST. H.323 endpoints require a slow connect because the endpoint-capability match occurs after the connect message.
Note
For more information about slow-connect procedures, see Configuring Quality of Service for Voice.
Use the following procedure to configure slow-connect procedures.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
voice service voip
4.
h323
5.
call start slow
DETAILED STEPS
Verifying Cisco Unified SRST
Use the following procedure to verify that the Cisco Unified SRST feature is enabled, and to verify Cisco Unified IP phone configuration settings.
SUMMARY STEPS
1.
enable
2.
show running config
3.
show call-manager-fallback all
DETAILED STEPS
Note
Use the Settings display on the Cisco Unified IP phones in your network to verify that the default router IP address on the phones matches the IP address of the Cisco Unified SRST router.
Examples
The following example shows output from the show call-manager-fallback all command:
Router# show call-manager-fallback allCONFIG (Version=3.3)=====================Version 3.3For on-line documentation please see:www.cisco.com/univercd/cc/td/doc/product/access/ip_ph/ip_ks/index.htmip source-address 10.1.1.1 port 2000max-video-bit-rate 384(kbps)max-ephones 52max-dn 110max-conferences 16 gain -6dspfarm units 0dspfarm transcode sessions 0huntstopdialplan-pattern 1 4084442... extension-length 4voicemail 6001moh music-on-hold.autime-format 24date-format dd-mm-yytimezone 0 Greenwich Standard Timecall-forward busy 6001call-forward noan 6001 timeout 8call-forward pattern .Ttransfer-pattern .Tkeepalive 45timeout interdigit 10timeout busy 10timeout ringing 180caller-id name-only: enableLimit number of DNs per phone:7910: 347935: 347936: 347940: 347960: 347970: 34Log (table parameters):max-size: 150retain-timer: 15transfer-system full-consultlocal directory service: enabled.ephone-dn 1number 1001name 1001description 1001label 1001preference 0 secondary 9huntstopcall-forward busy 6001call-forward noan 6001 timeout 8call-waiting beepephone-dn 2number 1002name 1002description 1002preference 0 secondary 9huntstopcall-forward busy 6001call-forward noan 6001 timeout 8call-waiting beepephone-dn 3preference 0 secondary 9huntstopcall-waiting beepephone-dn 4preference 0 secondary 9huntstopcall-waiting beepephone-dn 5preference 0 secondary 9huntstopcall-waiting beepephone-dn 6preference 0 secondary 9huntstopcall-waiting beepephone-dn 7preference 0 secondary 9huntstopcall-waiting beepephone-dn 8preference 0 secondary 9huntstopcall-waiting beepephone-dn 9preference 0 secondary 9huntstopcall-waiting beepephone-dn 10preference 0 secondary 9huntstopcall-waiting beepephone-dn 11preference 0 secondary 9huntstopcall-waiting beepephone-dn 12preference 0 secondary 9huntstopcall-waiting beepephone-dn 13preference 0 secondary 9huntstopcall-waiting beepephone-dn 14preference 0 secondary 9huntstopcall-waiting beepephone-dn 15preference 0 secondary 9huntstopcall-waiting beepephone-dn 16preference 0 secondary 9huntstopcall-waiting beepephone-dn 17preference 0 secondary 9huntstopcall-waiting beepephone-dn 18preference 0 secondary 9huntstopcall-waiting beepephone-dn 19preference 0 secondary 9huntstopcall-waiting beepephone-dn 20preference 0 secondary 9huntstopcall-waiting beepNumber of Configured ephones 0 (Registered 2)voice-port 50/0/1station-id number 1001station-id name 1001timeout ringing 8!voice-port 50/0/2station-id number 1002station-id name 1002timeout ringing 8!voice-port 50/0/3!voice-port 50/0/4!voice-port 50/0/5!voice-port 50/0/6!voice-port 50/0/7!voice-port 50/0/8!voice-port 50/0/9!voice-port 50/0/10!voice-port 50/0/11!voice-port 50/0/12!voice-port 50/0/13!voice-port 50/0/14!voice-port 50/0/15!voice-port 50/0/16!voice-port 50/0/17!voice-port 50/0/18!voice-port 50/0/19!voice-port 50/0/20!dial-peer voice 20055 potsdestination-pattern 1001huntstopcall-forward busy 6001call-forward noan 6001progress_ind setup enable 3port 50/0/1dial-peer voice 20056 potsdestination-pattern 1002huntstopcall-forward busy 6001call-forward noan 6001progress_ind setup enable 3port 50/0/2dial-peer voice 20057 potshuntstopprogress_ind setup enable 3port 50/0/3dial-peer voice 20058 potshuntstopprogress_ind setup enable 3port 50/0/4dial-peer voice 20059 potshuntstopprogress_ind setup enable 3port 50/0/5dial-peer voice 20060 potshuntstopprogress_ind setup enable 3port 50/0/6dial-peer voice 20061 potshuntstopprogress_ind setup enable 3port 50/0/7dial-peer voice 20062 potshuntstopprogress_ind setup enable 3port 50/0/8dial-peer voice 20063 potshuntstopprogress_ind setup enable 3port 50/0/9dial-peer voice 20064 potshuntstopprogress_ind setup enable 3port 50/0/10dial-peer voice 20065 potshuntstopprogress_ind setup enable 3port 50/0/11dial-peer voice 20066 potshuntstopprogress_ind setup enable 3port 50/0/12dial-peer voice 20067 potshuntstopprogress_ind setup enable 3port 50/0/13dial-peer voice 20068 potshuntstopprogress_ind setup enable 3port 50/0/14dial-peer voice 20069 potshuntstopprogress_ind setup enable 3port 50/0/15dial-peer voice 20070 potshuntstopprogress_ind setup enable 3port 50/0/16dial-peer voice 20071 potshuntstopprogress_ind setup enable 3port 50/0/17dial-peer voice 20072 potshuntstopprogress_ind setup enable 3port 50/0/18dial-peer voice 20073 potshuntstopprogress_ind setup enable 3port 50/0/19dial-peer voice 20074 potshuntstopprogress_ind setup enable 3port 50/0/20tftp-server system:/its/SEPDEFAULT.cnftftp-server system:/its/SEPDEFAULT.cnf alias SEPDefault.cnftftp-server system:/its/XMLDefault.cnf.xml alias XMLDefault.cnf.xmltftp-server system:/its/ATADefault.cnf.xmltftp-server system:/its/united_states/7960-tones.xml alias United_States/7960-tones.xmltftp-server system:/its/united_states/7960-font.xml alias English_United_States/7960-font.xmltftp-server system:/its/united_states/7960-dictionary.xml alias English_United_States/7960-dictionary.xmltftp-server system:/its/united_states/7960-kate.xml alias English_United_States/7960-kate.xmltftp-server system:/its/united_states/SCCP-dictionary.xml alias English_United_States/SCCP-dictionary.xmltftp-server system:/its/XMLDefault7960.cnf.xml alias SEP003094C2772E.cnf.xmltftp-server system:/its/XMLDefault7960.cnf.xml alias SEP001201372DD1.cnf.xmltftp-server system:/its/XMLDefault7960.cnf.xml alias SEPFFDD00000001.cnf.xmltftp-server system:/its/XMLDefault7960.cnf.xml alias SEPFFDD00000002.cnf.xmltftp-server system:/its/XMLDefault7960.cnf.xml alias SEPFFDD00000003.cnf.xmltftp-server system:/its/XMLDefault7960.cnf.xml alias SEPFFDD00000004.cnf.xmltftp-server system:/its/XMLDefault7960.cnf.xml alias SEPFFDD00000005.cnf.xmltftp-server system:/its/XMLDefault7960.cnf.xml alias SEPFFDD00000006.cnf.xmltftp-server system:/its/XMLDefault7960.cnf.xml alias SEPFFDD00000007.cnf.xmltftp-server system:/its/XMLDefault7960.cnf.xml alias SEPFFDD00000008.cnf.xmltftp-server system:/its/XMLDefault7960.cnf.xml alias SEPFFDD00000009.cnf.xmltftp-server system:/its/XMLDefault7960.cnf.xml alias SEPFFDD0000000A.cnf.xmltftp-server system:/its/XMLDefault7960.cnf.xml alias SEPFFDD0000000B.cnf.xmltftp-server system:/its/XMLDefault7960.cnf.xml alias SEPFFDD0000000C.cnf.xmltftp-server system:/its/XMLDefault7960.cnf.xml alias SEPFFDD0000000D.cnf.xmltftp-server system:/its/XMLDefault7960.cnf.xml alias SEPFFDD0000000E.cnf.xmltftp-server system:/its/XMLDefault7960.cnf.xml alias SEPFFDD0000000F.cnf.xmltftp-server system:/its/XMLDefault7960.cnf.xml alias SEPFFDD00000010.cnf.xmltftp-server system:/its/XMLDefault7960.cnf.xml alias SEPFFDD00000011.cnf.xmltftp-server system:/its/XMLDefault7960.cnf.xml alias SEPFFDD00000012.cnf.xmlSetting Video Parameters for Cisco Unified SRST
Using the following procedure to set the maximum bit rate for all video-capable phones in a Cisco Unified SRST system.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
call-manager-fallback
4.
video
5.
maximum bit-rate value
DETAILED STEPS
Examples
The following example shows the configuration for video with Cisco Unified SRST:
call-manager-fallbackvideomaximum bit-rate 384max-conferences 2 gain -6transfer-system full-consultip source-address 10.0.1.1 port 2000max-ephones 52max-dn 110dialplan-pattern 1 4084442... extension-length 4transfer-pattern .Tkeepalive 45voicemail 6001call-forward pattern .Tcall-forward busy 6001call-forward noan 6001 timeout 3moh music-on-hold.autime-format 24date-format dd-mm-yy!Troubleshooting Video for Cisco Unified SRST
Use the following commands to troubleshoot Video for Cisco Unified SRST.
•
For SCCP endpoint troubleshooting, use the following debug commands:
–
debug cch323 video—Enables video debugging trace on the H.323 SPI.
–
debug ephone detail—Debugs all Cisco Unified IP phones that are registered to the router, and displays error and state levels.
–
debug h225 asn1—Displays Abstract Syntax Notation One (ASN.1) contents of H.225 messages that have been sent or received.
–
debug h245 asn1—Displays ASN.1 contents of H.245 messages that have been sent or received.
–
debug voip ccapi inout—Displays the execution path through the call-control-application programming interface (CCAPI).
•
For ephone troubleshooting, use the following debug commands:
–
debug ephone message—Enables message tracing between Cisco ephones.
–
debug ephone register—Sets registration debugging for ephones.
–
debug ephone video—Sets ephone video traces, which provide information about different video states for the call, including video capabilities selection, start, and stop.
•
For basic video-to-video call checking, use the following show commands:
–
show call active video—Displays call information for SCCP video calls in progress.
–
show ephone offhook—Displays information and packet counts for ephones that are currently off hook.
–
show ephone registered—Displays the status of registered ephones.
–
show voip rtp connections—Displays information about RTP named-event packets, such as caller ID number, IP address, and port, for both the local and remote endpoints.
Posted: Mon Jun 19 10:57:05 PDT 2006
All contents are Copyright © 1992--2006 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.