Configuring Class Based Header Compression

This topic describes the Cisco IOS commands that are required to configure class-based header compression.

Configure class-based TCP and RTP header compression within a policy map using the compression header ip command.

If you do not specify either RTP or TCP header compression, both RTP and TCP header compressions will be configured.

Note Header compression is only auto-negotiated on PPP links. On Frame Relay or high-level data link control (HDLC) links, both ends of the links have to match.

In the figure, the compression header ip command is configured to use TCP header compression for a traffic class called "interactive." The "interactive" traffic class is part of a policy map called "cust1." This "cust1" policy map is applied to the s0/0 interface in the outbound direction.

This policy provides a minimum bandwidth guarantee of 64 kbps for the "interactive" traffic class and will perform TCP header compression on the "interactive" traffic class (all Telnet packets in this example) leaving the s0/0 interface.

In the figure, the compression header ip command has been configured to use RTP header compression for a traffic class called "voip." The "voip" traffic class is part of a policy map called "cust1" This "cust1" policy map is applied to the s0/0 interface in the outbound direction.

This policy provides a maximum bandwidth guarantee of 384 kbps for the "voip" traffic class and will perform RTP header compression on the "voip" traffic class (all RTP packets in this example) leaving the s0/0 interface.

Was this article helpful?

0 0

Post a comment