I have configured cRTP on a PPP (in fact, Multilink PPP) link. I noticed that, when the command
"ip rtp header-compression"
is issued, the command
"ip tcp header-compression"
is automatically added by the router.
What makes me worry is that, as this link transports both voice and data (and much data, in fact), the TCP compression will take much of my CPU. And, as I need header compression only for voice packets, which are NOT TCP, I'd like to disable the TCP header compression. But, for my surprise, when I disable it, using the command
"no ip tcp header-compression"
the RTP compression is removed too!
Is there a way to have cRTP on a PPP link WITHOUT TCP compression?
Before going to PPP, I was using Frame Relay with RTP compression, and it was NOT necessary to have TCP compression too.
This is a link between a 2620 and a 7206, both with 12.2(1). The rate is 512k.
cRTP "compresses" both RTP UDP packets and all TCP packets. You can't tell cRTP to stop compressing TCP packets. It does it all. You might accurately call it cRTP-TCP, or even more accurately call it truncated-RTP-TCP since it doesn't actually compress the packets but merely removes most of the header info, reassembling the chopped up packets on the recieving router.
Thank you for the explanation. But why can't RTP header compression be configured independently of TCP?? As most of the link will be used by data packets, there'll be much more demand for the CPU, which is not desired (mainly because TCP compression will not be so efficient as RTP compression, since data packets are much bigger than voice packets). What do you think?
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.