Recommendations for RTP header compression

Last Updated : May 03, 2013 |

Enterprises that deploy routers capable of this feature can benefit from the feature. However, Cisco suggests caution in using RTP header compression on its routers because it can significantly tax the processor if the compression is done in software. Depending on the processor load before compression, enabling RTP header compression can significantly slow down the router or cause the router to stop completely. For best results, use a hardware/IOS/interface module combination that permits the compression to be done in hardware.

RTP header compression has to function with precision or audio will be disrupted. If, for any reason, the compression at one end of the WAN link and decompression at the other end do not function properly, the result can be intermittent loss of audio or one-way audio. RTP header compression has been very difficult to quantify, but there is evidence that cRTP sometimes leads to voice-quality issues. One production site in particular experienced intermittent one-way audio, the cause of which was garbled RTP audio samples inserted by the cRTP device. When, for experimentation purposes, RTP header compression was disabled, the audio problems disappeared.