> Thanks for the help. I was able to use setClientPortNum() inside
> setupNextSubsession() to specify which port for it to use so it didn’t
> auto-search. Oddly enough, any even port between 65408 – 65518 seems to
> work. That was just the range I tested, it probably works outside of that as
Ross,
Thanks for the help. I was able to use setClientPortNum() inside
setupNextSubsession() to specify which port for it to use so it didn't
auto-search. Oddly enough, any even port between 65408 - 65518 seems to
work. That was just the range I tested, it probably works outside of that
as w
> I noticed that the code that calls setupDatagramSocket is trying to find
> sequential port numbers (even for RTP, following odd for RTSP). The trouble
> seems to be with the RTSP ports.
You mean "RTCP" here, not "RTSP".
But yes, it's important (for now, at least) that these port numbers be
I am using the testRTSPClient and I am having some trouble with the bind()
call in GroupsockHelper.cpp::setupDatagramSocket() on both Linux and QNX
OSes using a Sabrelite board (uses iMx6 quad-core ARM processor). It is
frequently trying all the ports and not being able to bind to any of the odd
p
