Rpgace rtp

ContentsConfiguring Class-Based RTP and TCP Header CompressionFinding Feature InformationPrerequisites for Class-Based RTP and TCP Header CompressionRestrictions for Class-Based RTP and TCP Header CompressionInformation About Class-Based RTP and TCP Header CompressionClass-Based Header Compression and the MQCBenefits of Class-Based Header CompressionHeader Compression on Local and Remote RoutersAbout Header-Compression ConnectionsHow to Configure Class-Based RTP and TCP Header CompressionEnabling RTP or TCP Header Compression for a Class in a Policy MapAttaching the Policy Map to an InterfaceVerifying the Class-Based RTP and TCP Header Compression ConfigurationConfiguration Examples for Class-Based RTP and TCP Header CompressionExample Enabling RTP or TCP Header Compression for a Class in a Policy MapExample Attaching the Policy Map to an InterfaceExample Verifying the Class-Based RTP and TCP Header Compression ConfigurationAdditional ReferencesGlossaryFeature Information for Class-Based RTP and TCP Header CompressionLast Updated: December 5, 2011 Header compression is a mechanism that compresses the IP header in a packet before the packet is transmitted. Header compression reduces network overhead and speeds up the transmission of either Real-Time Transport Protocol (RTP) packets or Transmission Control Protocol (TCP) packets. Cisco provides two types of header compression: RTP header compression and TCP header compression. RTP and TCP header compression are typically configured on a per-interface (or subinterface) basis. Class-based RTP and TCP header compression allows you to configure either type of header compression on a per-class basis. This module describes the concepts and tasks related to configuring class-based RTP and TCP header compression. Note If you want to configure RTP or TCP header compression on a per-interface (or subinterface) basis, see the "Configuring RTP Header Compression" module or the "Configuring TCP Header Compression" module, respectively. Finding Feature InformationPrerequisites for Class-Based RTP and TCP Header CompressionRestrictions for Class-Based RTP and TCP Header CompressionInformation About Class-Based RTP and TCP Header CompressionHow to Configure Class-Based RTP and TCP Header CompressionConfiguration Examples

Audio quality. Caller/Called max instant jitter - Same as RFC3550 jitter but not smoothed by low-pass filter. Equals to immediate deviation of packet time. Caller/Called packet time - RTP packet time in milliseconds Caller/Called non-silent duration - duration of non-silent RTP packets in audio stream Caller/Called RTP delay - delay between intitial INVITE and first RTP packet, in milliseconds. Silent RTP packets are considered, not like in "Audio signal delay" Caller/Called SDP-RTP delay - delay between SDP negotiation (183 or 200 response) and first RTP packet, in milliseconds. Silent RTP packets are considered, not like in "Audio signal delay" Caller/Called DSCP - DSCP field value RTCP RTT - IP network's round-trip delay measured by RTCP packets. The RTT is measured few times during a call, max. value is selected for this report RTCP caller lost packets (%) - loss rate of RTP packets, which are generated by caller party. Is measured at called side. This indicator is transmitted inside RTCP packets RTCP called lost packets (%) - loss rate of RTP packets, which are generated by called party. Is measured at caller side. This indicator is transmitted inside RTCP packets RTCP caller max jitter (ms) - jitter of RTP packets, which are generated by caller party. Is measured at called side. The jitter is measured few times per call, max. value is selected. RTCP called max jitter (ms) - jitter of RTP packets, which are generated by called party. Is measured at caller side. The jitter is measured few times per call, max. value is selected. RTCP caller mean jitter (ms) - jitter of RTP packets, which are generated by caller party. Is measured at called side. The jitter is measured few times per call, mean (average) value is selected. RTCP called mean jitter (ms) - jitter of RTP packets,

Introduzione Questo documento descrive un processo dettagliato su come configurare l'interworking SRTP-RTP su CUBE. Prerequisiti Requisiti Cisco raccomanda la conoscenza dei seguenti argomenti: Cisco Unified Border Element (CUBE) SIP (Session Initiation Protocol) TLS (Transport Layer Security) Protocollo RTP (Real-time Transport Protocol) Secure Media - Protocollo SRTP (Secure Real-time Transport Protocol) Componenti usati Le informazioni fornite in questo documento si basano sulle seguenti versioni software e hardware: Cisco Unified Border Element (CUBE) Cisco IOS XE - versione 17.6 e successive Cisco C8200-1N-4T Le informazioni discusse in questo documento fanno riferimento a dispositivi usati in uno specifico ambiente di emulazione. Su tutti i dispositivi menzionati nel documento la configurazione è stata ripristinata ai valori predefiniti. Se la rete è operativa, valutare attentamente eventuali conseguenze derivanti dall'uso dei comandi. Premesse Il supporto Cisco Unified Border Element (CUBE) per la funzione di interoperabilità SRTP-RTP connette i domini SRTP aziendali ai trunk SIP del provider SIP RTP. L'interworking SRTP-RTP collega le reti RTP aziendali con SRTP su una rete esterna tra aziende. Questo garantisce comunicazioni business-to-business flessibili e sicure senza la necessità di tunnel IPsec statici o di implementare l'SRTP all'interno dell'azienda. I punti chiave sull'interoperabilità SRTP-RTP su CUBE includono: Crittografia e decrittografia: CUBE è in grado di crittografare e decrittografare i flussi di dati da e verso le reti SRTP e RTP. Supporto TLS: è possibile abilitare o disabilitare Transport Layer Security (TLS) tra il server SCCP e il client SCCP. Per impostazione predefinita, TLS è abilitato per proteggere le chiavi SRTP. Servizi supplementari: in Cisco IOS versione 15.2(1), la funzione è stata estesa per supportare servizi supplementari su CUBE. Transcoding: l'internetworking SRTP-RTP è disponibile con transcoder normali e universali, richiamati tramite messaggistica SCCP. Gestione fallback: se uno degli endpoint di chiamata non supporta SRTP, la chiamata può eseguire il fallback a RTP-RTP o avere esito negativo, a seconda della configurazione. Questo fallback si verifica solo se il comando srtp fallback è configurato sul rispettivo dial peer. Implementazione: l'interoperabilità SRTP-RTP può essere implementata su interfacce UNI (User to Network Interfaces) e NNI (Network to Network Interfaces). Nota: Le risorse DSP sono richieste per le

End (Optional) Exits privileged EXEC mode. Configuration Examples for Class-Based RTP and TCP Header CompressionExample Enabling RTP or TCP Header Compression for a Class in a Policy MapExample Attaching the Policy Map to an InterfaceExample Verifying the Class-Based RTP and TCP Header Compression ConfigurationExample Enabling RTP or TCP Header Compression for a Class in a Policy Map In the following example, a class map called class1 and a policy map called policy1 have been configured. Policy1 contains the class called class1, within which RTP header compression has been enabled by using the compression header ip rtp command. Router> enable Router# configure terminal Router(config)# class-map class1 Router(config-cmap)# match protocol ip Router(config-cmap)# exit Router(config)# policy-map policy1 Router(config-pmap)# class class1 Router(config-pmap-c)# compression header ip rtp Router(config-pmap-c)# end Example Attaching the Policy Map to an Interface In the following example, the policy map called policy1 has been attached to serial interface 0. Router> enable Router# configure terminal Router(config)# interface serial0 Router(config-if)# service-policy output policy1 Router(config-if)# end Example Verifying the Class-Based RTP and TCP Header Compression Configuration This section provides sample output from a typical showpolicy-mapinterfacecommand. NoteDepending upon the interface in use and the QoS feature enabled (such as Class-Based Weighted Fair Queuing [CBWFQ]), the output you see may vary from that shown below. The following sample displays the statistics for serial interface 0. In this sample configuration, three classes, called gold, silver, and voice, have been configured. Traffic is classified and grouped into classes on the basis of the IP precedence value and RTP port protocol number. class-map match-all gold match ip precedence 2 class-map match-all silver match ip precedence 1 class-map match-all voice match ip precedence 5 match ip rtp 16384 1000 This sample configuration also contains a policy map called mypolicy, configured as shown below. QoS features such as RTP header compression