# rtcp-mux multiplexing RTCP on the same port

**URL:** <https://community.wowza.com/t/rtcp-mux-multiplexing-rtcp-on-the-same-port/34203>\
**Category:** Wowza Streaming Engine\
**Created:** [November 5, 2010, 3:34pm UTC](https://community.wowza.com/t/rtcp-mux-multiplexing-rtcp-on-the-same-port/34203 "2010-11-05T15:34:44Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sander\_Kruger](https://avatars.discourse-cdn.com/v4/letter/s/5daacb/32.png) [@Sander\_Kruger](https://community.wowza.com/u/Sander_Kruger)\
**Post date:** [November 5, 2010, 3:34pm UTC](https://community.wowza.com/t/rtcp-mux-multiplexing-rtcp-on-the-same-port/34203/1 "2010-11-05T15:34:44Z")

</div>

I’m developing an application that publishes multiple RTP streams to Flash clients. Each RTP stream must have its own port. I use VLC for testing.

When using default settings for VLC, streaming RTP on, say, port 30001, will cause VLC to automatically occupy port 30002 with RTCP traffic.

VLC has a setting called rtcp-mux, which prevents this, but sends RTCP packets over the same port as RTP. You get an entry in the SDP file (a=rtcp-mux), and I put that on the Wowzaserver. However, I still hear clicks in the stream.

My custom depacketizer receives the RTCP packets in the method handleRTPPacket, not handleRTCPPacket.

Does Wowza support RTCP multiplexing?

Regards,

Sander.

---

<div class="post-metadata">

**Author:** ![Richard\_Lanham](https://avatars.discourse-cdn.com/v4/letter/r/c68b51/32.png) [@Richard\_Lanham](https://community.wowza.com/u/Richard_Lanham)\
**Post date:** [November 5, 2010, 10:20pm UTC](https://community.wowza.com/t/rtcp-mux-multiplexing-rtcp-on-the-same-port/34203/2 "2010-11-05T22:20:30Z")

</div>

Sander,

No, Wowza does not support RTCP multiplexing.

Richard

---

<div class="post-metadata">

**Author:** ![Charlie\_Good](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/charlie_good/32/383_2.png) [@Charlie\_Good](https://community.wowza.com/u/Charlie_Good)\
**Post date:** [November 6, 2010, 4:52am UTC](https://community.wowza.com/t/rtcp-mux-multiplexing-rtcp-on-the-same-port/34203/3 "2010-11-06T04:52:46Z")

</div>

No, it can’t at this time.

Charlie

---

<div class="post-metadata">

**Author:** ![Sander\_Kruger](https://avatars.discourse-cdn.com/v4/letter/s/5daacb/32.png) [@Sander\_Kruger](https://community.wowza.com/u/Sander_Kruger)\
**Post date:** [November 6, 2010, 9:40am UTC](https://community.wowza.com/t/rtcp-mux-multiplexing-rtcp-on-the-same-port/34203/4 "2010-11-06T09:40:16Z")

</div>

Hello,

When multiplexing RTCP, it doesn’t seem that Wowza ‘misses’ the RTCP information, so it seems to me that Wowza doesn’t really need this.

For an RTP stream on port X, Wowza also binds to port X+1 to listen for RTCP. As a result, port X+1 cannot be used for another RTP stream. Can this mechanism be deactivated?

Regards,

Sander.