Problem solved! max. 350 Socket Problem

[Jeffrey C. Ollie]

On Thu, 2006-06-08 at 12:56 +0200, Wiese, Hendrik wrote:
>  
> Now the problem is, if the probed RTP port is available and the RTCP
> port is _NOT_ (bind for RTP is successful, but not for RTCP), the ports
> are also increased by 2 and the while loop starts over, trying to bind
> the already successfully bound RTP port to the increased portnumber
> (e.g. 5002) _AGAIN_. And this bind fails with errno == EINVAL. 

If the RTP socket is bound successfully, but the RTCP socket is not, you
should close and recreate the RTP socket before trying again with higher
port numbers.  That's the short term solution.  Longer term, I would
rewrite your RTP/RTCP stack to deal with RTCP ports numbers that are not
one more than the RTP port number.

Jeff

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.fedoraproject.org/pipermail/devel/attachments/20060608/53a7d3de/attachment-0002.bin