Re: [Linphone-users] sip.linphone.org and UDP no longer working?

[Greg Troxel]

Greg Troxel <address@hidden> writes:

> The plot thickens.  This may be confusion on my part, but I thought the
> URIs were "address@hidden".  That has a srv record, but points to a
> server/port that is not functioning.  But "address@hidden" points
> to both a nonworking server (with priority 10) and a working server.
> Plus, the ports on the working server are unusual (not 5060 and 5061).

I did not receive any response to my posting about this trouble, other
than some helpful debugging advice from Russell Treleaven.

(First, I realize now that URIs are address@hidden  That
confusion turned out not to be important.)

I wrote earlier about SRV records.

Now, one can register with the standard UDP port at the address returned
in an A record from sip.linphone.org.  That didn't use to work.

The SRV records still point to unusual ports for tcp and tls; I don't
know if that's about firewall issues.  

Both hosts pointed to by SRV are up, and in addition answer TCP
connections on 5060 and 5061.

sip.linphone.org.       10800   IN      A       91.121.209.194

_sip._udp.sip.linphone.org. 3600 IN     SRV     0 100 5060 sip6.linphone.org.
_sip._udp.sip.linphone.org. 3600 IN     SRV     10 100 5060 sip1.linphone.org.

_sip._tcp.sip.linphone.org. 3600 IN     SRV     10 100 5228 sip1.linphone.org.
_sip._tcp.sip.linphone.org. 3600 IN     SRV     0 100 5228 sip6.linphone.org.

_sips._tcp.sip.linphone.org. 3600 IN    SRV     20 100 443 sip6.linphone.org.
_sips._tcp.sip.linphone.org. 3600 IN    SRV     10 100 5223 sip1.linphone.org.
_sips._tcp.sip.linphone.org. 3600 IN    SRV     0 100 5223 sip6.linphone.org.

sip1.linphone.org.      10800   IN      A       91.121.209.194
sip6.linphone.org.      10800   IN      A       54.37.202.229
sip6.linphone.org.      10789   IN      AAAA    2001:41d0:700:789::2020


So now the person I am helping is having their VOIP phone register with 
linphone.org.


I conclude that it appears that somebody at linphone.org addressed the
issue of one server not responding, ports, SRV records.   But apparently
they are not reading this list :-)