[jitsi-dev] Fwd: Bug#735146: ignores SRV records, tries UDP


#1

Package: jitsi
Version: 2.3.4952-1

I created a SIP account "pocock@debian.org"

In DNS for debian.org, we have

_sips._tcp.debian.org (SRV record)

and no SRV record for _sip._udp

There is currently no NAPTR record

I believe that in this situation, Jitsi should try TLS, but it just
appears to be trying UDP. Exceptions appear in the console mentioning
port 5060

···

---------- Forwarded message ----------
From: Daniel Pocock <daniel@pocock.com.au>
Date: Mon, Jan 13, 2014 at 10:41 AM
Subject: Bug#735146: ignores SRV records, tries UDP
Reply-To: Daniel Pocock <daniel@pocock.com.au>, 735146@bugs.debian.org

To: Debian Bug Tracking System <submit@bugs.debian.org>


#2

Package: jitsi
Version: 2.3.4952-1

I created a SIP account "pocock@debian.org"

In DNS for debian.org, we have

_sips._tcp.debian.org (SRV record)

and no SRV record for _sip._udp

There is currently no NAPTR record

I believe that in this situation, Jitsi should try TLS, but it just
appears to be trying UDP. Exceptions appear in the console mentioning
port 5060

openssl s_client -connect vogler.debian.org:5061
Loading 'screen' into random state - done
connect: No such file or directory
connect:errno=0

Jitsi tries does try to connect to port 5061 with TLS and receives no
answer. The port 5060 you see in the console is the header for the
registrar, not the proxy. I see no attempt to connect via UDP.

Ingo


#3

The console logs (with full exception stacks) are actually quite verbose
for checking connectivity problems, I should have looked through them
more closely but it may be helpful if you can find a way to log this
activity without full stack traces.

Now we have a NAPTR record for debian.org and fixed our authentication
mechanism on the server, the connection and registration seems to work
automatically (apart from the username issues, I open other bugs for
them) so I have closed this bug. Thanks for the feedback.

···

On 13/01/14 10:42, Ingo Bauersachs wrote:

Package: jitsi
Version: 2.3.4952-1

I created a SIP account "pocock@debian.org"

In DNS for debian.org, we have

_sips._tcp.debian.org (SRV record)

and no SRV record for _sip._udp

There is currently no NAPTR record

I believe that in this situation, Jitsi should try TLS, but it just
appears to be trying UDP. Exceptions appear in the console mentioning
port 5060

openssl s_client -connect vogler.debian.org:5061
Loading 'screen' into random state - done
connect: No such file or directory
connect:errno=0

Jitsi tries does try to connect to port 5061 with TLS and receives no
answer. The port 5060 you see in the console is the header for the
registrar, not the proxy. I see no attempt to connect via UDP.