Configuring Iphc-Type Header Compression - Avaya G250 Administration

Note:
Non-IETF encapsulation is compatible with other vendors.
Note:

Configuring IPHC-type header compression

IHPC-type header compression applies to RTP, TCP, and UDP headers.
Note:
You cannot specify IPHC-type header compression for a Frame Relay non-IETF
Note:
interface.
1. Optionally, configure header compression parameters. If you do not configure these
parameters, their default values are used.
Use the ip rtp compression-connections command to control the number of
●
RTP header compression connections supported on the interface. Use the no form of
this command to restore the default value of 16. This command also sets the number
of connections in the non-TCP space, not just RTP.
Use the ip tcp compression-connections command to control the number of
●
TCP header compression connections supported on the interface. Use the no form of
this command to restore the default value of 16.
Use the ip rtp max-period command to set the maximum number of compressed
●
RTP headers that can be sent between full headers.
Use the ip rtp max-time command to set the maximum number of seconds
●
between full RTP headers.
Use the ip rtp non-tcp-mode command to set the header compression mode.
●
When set to ietf, the command performs IP header compression according to IPHC
RFCs. When set to non-ietf, the command performs IP header compression
compatible with other vendors, which do not strictly follow the RFCs. The default
header compression mode is non-ietf.
Note:
IETF mode is not compatible with non-IETF mode.
Note:
Configuring header compression
Issue 3 February 2007 203