RTP Header Compression: How does it effect flow through network?

Discussion in 'VOIP' started by CCGolfer, Jun 8, 2004.

  1. CCGolfer

    CCGolfer Guest

    It seems that RTP header compression would be a good idea, but as the
    packets flow through the network they need to be uncompressed at each
    hop don't they? What's the trade-off in todays routing equipment for
    handling RTP header compressed packets vs. the bandwidth that they


    Greg in MA
    CCGolfer, Jun 8, 2004
    1. Advertisements

  2. CCGolfer

    shope Guest

    it depends. (stock answer - sorry)

    1st - a lot of soho type routers dont seem to do this anyway. You need to
    support compression at both ends of the link, (or VPN tunnel).
    2nd - devices that do support (eg cisco), tend to run compression in
    software for this - hit on the router CPU depends on router, line speed, and
    the amount of voice traffic.
    3rd - the "choke point" is often a router at a aggregation point - eg a
    frame relay site where lots of PVCs terminate - you need to check processor
    load at each RTP compression point.
    4th - you need to be careful about interactions between compression, QoS and
    call admission control. Basically, the router may not look at compressed
    data to calculate QoS thresholds, so you may end up deliberately
    misconfiguring things to compensate (e.g. with RSVP) - which is great until
    someone alters the config and "corrects" the mistake.

    since you can get compression in hardware as an option in many routers (and
    you may have to use that in an aggregation router to get enough compression
    without CPU overload), it may make more sense to compress everything - that
    way you gain on data traffic as well.
    shope, Jun 10, 2004
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.