why UDP6 when I use SIMPLE protocol to login SIP proxy?

[Hawkins, William - AES]

In reference to listening only on UDPv6 port 5060, I believe this is what the developers intended. The SIMPLE code calls purple_network_listen_range to open these ports. This function iterates through each port in that range with each available protocol. The function uses (on linux) getaddrinfo to create a list of protocols to try with each port. As soon as a port is open, the function returns.  It would appear that Linux favors UDPv6 over UDPv4 which leads to the behavior that you are seeing. 

It is possible to "hint" to the getaddrinfo function that you want v4 addresses to have preference. However, that is something that the libpurple people (eaters) would have to address. 

Please correct me if I am wrong in my interpretation of this code. 

Thanks,
Will


-----Original Message-----
From: devel-bounces at pidgin.im on behalf of CHEN XUEQIN
Sent: Sat 9/22/2007 1:29 PM
To: devel at pidgin.im
Subject: why UDP6 when  I use SIMPLE protocol to login SIP proxy?
 
Hello all:

I want to test SIP based IM and Presence. I setup openser (1.2.1) as SIP
proxy. Then I configure a SIMPLE account in pidgin, including screen
name/server/password/local alias/check publish status/check use UDP. My
problem is:

    * Pidgin can register to openser, but the AOR of pigdin SIMPLE
      account is incorrect. The AOR IP address is IP address of openser
      server which was wrong. It should be IP address of pidgin client.
    * In CLI, run "netstat -aup | grep pidgin"

udp6 0 0 *:sip *:* 19821/pidgin
udp6 0 0 *:sip *:* 19821/pidgin
Why pidgin only listen on udp6 5060 port. I think it should listen on
ipv4 port 5060 .

    * When I quit pidgin, it seemed that no unregister SIP message was
      sent to SIP proxy. The AOR in SIP proxy still remain. Why?


Any suggestion? Thanks in advance

Regards,
Chen Xueqin

*****************************************************************
This e-mail and any files transmitted with it may be proprietary 
and are intended solely for the use of the individual or entity to 
whom they are addressed. If you have received this e-mail in 
error please notify the sender. Please note that any views or
opinions presented in this e-mail are solely those of the author 
and do not necessarily represent those of ITT Corporation. The 
recipient should check this e-mail and any attachments for the 
presence of viruses. ITT accepts no liability for any damage 
caused by any virus transmitted by this e-mail.
*******************************************************************