Re: [Linphone-developers] ortp: using port used by other process

[Simon Morlat]

Hello,

Are you setting explicitely the port using rtp_session_set_local_addr() ?
In lastest version of oRTP, if rtp_session_set_local_addr() is used, 
SO_REUSEADDR is used to allow the socket to be reused later (after close()).
If rtp_session_set_local_addr() is NOT used, then a random port is choosen by 
oRTP, and in this case SO_REUSEADDR is not used to avoid binding on a busy 
port.
Does it solve your problem ?

Simon

Le Thursday 19 March 2009 13:36:38 Petr Kuba, vous avez écrit :
> Hello,
>
> We met the following problem with ortp in our application: if the local
> port we want to use is already used by some other process no error is
> reported. Therefore we do not hear any audio without being informed
> about the problem.
>
> We believe that this is caused by the following line in the
> create_and_bind() function:
>
> err = setsockopt (sock, SOL_SOCKET, SO_REUSEADDR,
>               (SOCKET_OPTION_VALUE)&optval, sizeof (optval));
>
> The create_and_bind() function is called from the
> rtp_session_set_local_addr() function.
>
> We met this problem in ortp 0.13.1 (under Windows XP) but after quick
> check it looks like the same would happen with 0.15.0.
>
> Could you explain us why SO_REUSEADDR option is used and suggest some
> way to detect problems? Our idea is to make use of SO_REUSEADDR
> configurable.
>
> Thanks,
> Petr