|
|
This chapter describes how to configure Compressed Real-Time Protocol (CRTP) header.
For complete conceptual information, see the section "Compressed Real-Time Protocol Header" in the chapter "Link Efficiency Mechanisms Overview" in this book.
For a complete description of the CRTP commands in this chapter, refer to the Cisco IOS IP and IP Routing Command Reference. To locate documentation of other commands that appear in this chapter, use the command reference master index, or search online.
![]() |
Note You must enable compression on both ends of a serial connection. |
See the end of this chapter for "CRTP Configuration Examples."
CRTP is supported on serial lines using Frame Relay, High-Level Data Link Control (HDLC), or PPP encapsulation. It is also supported over ISDN interfaces.
You should configure CRTP if the following conditions exist in your network:
![]() |
Note CRTP should not be used on links greater than 2 Mbps. |
Enabling compression on both ends of a low-bandwidth serial link can greatly reduce the network overhead if it carries a substantial amount of RTP traffic. Although the multicast backbone (MBONE)-style RTP traffic has higher payload sizes, compact encodings such as Compressed Encoding for Linear Prediction (CELP) can also help considerably.
Before you can enable RTP header compression, you must have configured a serial line that uses either Frame Relay, HDLC, or PPP encapsulation, or an ISDN interface. To configure RTP header compression, perform the tasks in the following sections.
To enable CRTP header for serial encapsulations HDLC or PPP, use the following command in interface configuration mode (you must enable compression on both ends of a serial connection):
Command | Purpose |
|---|---|
ip rtp header-compression [passive] |
|
If you include the passive keyword, the Cisco IOS software compresses outgoing RTP packets only if incoming RTP packets on the same interface are compressed. If you use the command without the passive keyword, the software compresses all RTP traffic.
Command | Purpose |
|---|---|
frame-relay ip rtp header-compression [passive] |
|
frame-relay map ip ip-address dlci [broadcast] rtp header-compression [active | passive] |
|
frame-relay map ip ip-address dlci [broadcast] compress |
|
By default, the software supports a total of 16 RTP header compression connections on an interface. To change that number, use the following command in interface configuration mode:
Command | Purpose |
|---|---|
ip rtp compression-connections number |
|
You can display specific statistics such as the contents of IP routing tables, caches, and databases. Information provided can be used to determine resource utilization and solve network problems. You can also display information about node reachability and discover the routing path your device's packets are taking through the network.
To display various routing statistics, use the following commands in EXEC mode:
Command | Purpose |
|---|---|
show frame-relay ip rtp header-compression [interface type number] |
|
show ip rtp header-compression [type number] [detail] |
|
The following example enables RTP header compression for a serial, ISDN, or asynchronous interface. For ISDN, you also need a broadcast dialer map.
interface serial 0 :or interface bri 0 ip rtp header-compression encapsulation ppp ip rtp compression-connections 25
The following example for Frame Relay encapsulation enables RTP header compression on the specified map:
interface serial 0 ip address 1.0.0.2 255.0.0.0 encapsulation frame-relay no keepalive clockrate 64000
frame-relay map ip 1.0.0.1 17 broadcast rtp header-compression
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Mon Aug 21 21:26:07 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.