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
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
