Configuring RTCP Report Generation
|
|||||||||||||||||||
Contents Configuring RTCP Report GenerationLast Updated: March 22, 2012
The assisted Real-time Transport Control Protocol (RTCP) feature adds the ability for Cisco Unified Border Element (Cisco UBE) to generate standard RTCP keepalive reports on behalf of endpoints. RTCP reports determine the liveliness of a media session during prolonged periods of silence, such as call hold or mute. Therefore, it is important for the Cisco UBE to generate RTCP reports irrespective of whether the endpoints send or receive media. Cisco UBE generates RTCP report only when inbound and outbound call legs are SIP, or SIP to H.323, or H.323 to SIP. Finding Feature InformationYour software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. PrerequisitesRestrictions
Configuring RTCP Report Generation on Cisco UBERTCP keepalive packets indicate session liveliness. When configured on Cisco UBE, RTCP keepalive packets are sent on both inbound and outbound SIP or H.323 call legs. Perform this task to configure RTCP report generation on Cisco UBE. DETAILED STEPS Troubleshooting TipsUse the following debug commands for debugging related to RTCP keepalive packets:
Router# debug voip rtcp packet
01:06:27.450: //6/xxxxxxxxxxxx/RTP//Event/voip_rtp_send_rtcp_keepalive: Generate RTCP Keepalive
*Mar 17 01:06:27.450: rtcp_send_report: Attributes
(src ip=192.168.30.3, src port=17101, dst ip=192.168.30.4, dst port=18619
bye=0, initial=1, ssrc=0x07111E02, keepalive=1)
*Mar 17 01:06:27.450: rtcp_construct_keepalive_report: Constructed Report
(rtcp=0x2E5AF214, ssrc=0x07111E02, source->ssrc=0x00001E03, total_len=36)
2E5AF210: 80C90001 07111E02 81CA0006 .I.......J..
2E5AF220: 07111E02 010F302E 302E3040 392E3435 ......0.0.0@9.45
2E5AF230: 2E33302E 33000000 00 .30.3....
Router# debug voip rtp packet
VOIP RTP All Packets debugging is on
Router# debug voip rtp session
VOIP RTP All Events debugging is on
Router# debug voip rtp error
VOIP RTP Errors debugging is on
Router# debug ip rtp protocol
RTP protocol debugging is on
Router# debug voip rtcp session
VOIP RTCP Events debugging is on
Router# debug voip rtcp error
VOIP RTCP Errors debugging is on
Feature Information for Configuring RTCP Report GenerationThe following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Feature History Table entry for the Cisco Unified Border Element. .
Feature History Table entry for the Cisco Unified Border Element (Enterprise) .
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. © 2012 Cisco Systems, Inc. All rights reserved.
|
|||||||||||||||||||