[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-developers] Cannot dissolve connect() association for rtp

From: Petr Kuba
Subject: Re: [Linphone-developers] Cannot dissolve connect() association for rtp socket
Date: Mon, 08 Feb 2010 17:50:29 +0100
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv: Gecko/20100111 Thunderbird/3.0.1

Hi Simon,

thanks a lot for your explenation. I was never sure whether we need this rtp_session_set_connected_mode() method and what it is good for. I've disabled connected socket and now everything is ok.

Thanks once again,

On 3.2.2010 10:29, Simon Morlat wrote:

Apparently windows server 2003 does not support connect()
disassociations, that is cancelling a previous connect() done on a
The question is do you really need UDP connected socket ?
You can use
void rtp_session_set_connected_mode(RtpSession *session, bool_t yesno);
to disable connect().
Personnaly in linphone I don't use the connected mode.
The "features" brought by doing connect on a udp socket are:
1. the kernel automatically discards UDP messages that don't come from
the connected peer address
2. you are notified with "connection refused" errnos when the remote
socket is not opened or closed.

2 is nice but 1 is a problem when you don't know where the packets will
come from (common with firewalls), that's why I don't use it.


Le jeudi 28 janvier 2010 à 17:57 +0100, Petr Kuba a écrit :

We've met the following problem. Ortp reports plenty of the following

Cannot dissolve connect() association for rtp socket: Error code : 10047
Cannot dissolve connect() association for rtcp socket: Error code : 10047

Does anyone know what it means?

This occures on Windows Server 2003 with standard IP4 network. I'm not
sure whether we ever met this on Windows XP.

I've explored that 10047 stands for WSAEAFNOSUPPORT which has the
following description:

Address family not supported by protocol family.
An address incompatible with the requested protocol was used. All
sockets are created with an associated address family (that is, AF_INET
for Internet Protocols) and a generic protocol type (that is,
SOCK_STREAM). This error is returned if an incorrect protocol is
explicitly requested in the socket call, or if an address of the wrong
family is used for a socket, for example, in sendto.

I'm not sure whether this could influence the problem but may be I
should mention that we do'nt define SO_REUSE_ADDR in ortp.

Thanks for help,
Petr Kuba

Linphone-developers mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]