emiago
Allow specify RTCP port manually
Hi.
I see that now RTCP port is hardcoded as RTP + 1 which may lead to a problem when such port is already bound on a host.
Can we have an opportunity to specify custom RTCP port?
It even should be possible to set it to 0 to let host automatically choose it but in this case it must be specified in SDP as well.
Hi Noksa, does RTPPortStart help?
Otherwise I think you need to understand this goes to supporting on multiple levels per RFC, which I so far did not see as needed. My feeling you are building client and want specific port, so above should fix your issue.
Hey @emiago , thanks for the answer!
We are doing load-testing, built a client on top of diago (thanks for that!).
In one of scenarios it is around ~10k online calls in a system at the same time (from one host).
The problem is that diago uses random ports for RTP by default and these ports are not always even.
In such cases RTCP ports become even and we encounter a problem when such port can be already bound on a host (by another app or a call).
Due to this we get bind: address already in use.
I did some changes in my fork to make this works with a:rtcp in SDP (for our case we just use random ports for RTCP without default behaviour), but would like to have such opportunity in the upstream some time :)
RTPPortStart will make more continuos usage of ports, which minimizes chance of hitting reused. Default behavior is indeed not best, but yeah making both system level requires signaling to be done.
I leave this ticket open as feature request. If you want to prioritize roadmap, pls contact via email.