DNS SRV support

[GoogleCodeExporter]

I think that SIP client must lookup DNS SRV record before trying to connect. 
For example i have asterisk on server pbx.lex.gs, while i use @lex.gs domain 
for auth.

Original issue reported on code.google.com by zdevel on 19 Jun 2010 at 12:56

[GoogleCodeExporter]

I'll check for that but I though that it was already managed by the sip stack I 
use (pjsip).

Are you sure your DNS SRV entry is 
_sip._udp.lex.gs => pbx.lex.gs on the SOA of lex.gs?

Btw, there is also a workaround if you want to test quickly bypassing the 
automatic DNS resolution.

Add your account with the Expert Wizard.
Then fill your account id
<sip:username@lex.gs>
And your registration uri as:
sip:pbx.lex.gs 
or if you prefer
sip:192.168.1.1 where 192.168.1.1 is your server IP address.
This kind of configuration can be usefull if you are into a LAN without any dns 
configured.
Finally, you should also fill the password field.

Anyway i'll test it a little bit more on my side, but will take me time to 
set-up a sip server with this conf.

Original comment by r3gis...@gmail.com on 20 Jun 2010 at 3:02

[GoogleCodeExporter]

you can use mine - i can add user for you without any problem, just contact me 
directly by email.

Original comment by zdevel on 20 Jun 2010 at 3:07

[GoogleCodeExporter]

(and expert wizard crashes for me after filling all params, that's why i filled 
#53)

Original comment by zdevel on 20 Jun 2010 at 3:08

[GoogleCodeExporter]

Ok
Many thanks for your very fast response.

I'll not need an account on your server, but if you allow me I will use it with 
a fake username/password.
It allow me to reproduce your issue in fact, and unfortunately, also with the 
advanced registration uri set.

I will debug it but i'm not sure it's linked to the DNS SRV.
I'll keep you informed.

Original comment by r3gis...@gmail.com on 20 Jun 2010 at 3:22

• Changed state: Accepted

[GoogleCodeExporter]

without any problem, since this is personal PBX.
Also, maybe merge that with issue #53? Since problem is in dns...

Original comment by zdevel on 20 Jun 2010 at 3:27

[GoogleCodeExporter]

please sorry if you can't check connect ATM. My server went down, and i don't 
know when they bring it online.

Original comment by zdevel on 22 Jun 2010 at 7:55

[GoogleCodeExporter]

I can confirm, I have valid SRV for the dc3.com domain (server sip.dc3.com). I 
can place a call to (e.g.) 100@sip.dc3.com but not 100@dc3.com. I can call the 
latter/SRV from other SIP phones (Bria, XLite, 3CX, 3CX/Android) so I know the 
SRV records are correct in our DNS.

Original comment by dc3de...@gmail.com on 31 Jul 2010 at 1:22

[GoogleCodeExporter]

Ok, there is something on my branch that should fix this issue.
In fact, I though that pjsip does the job to get back the dns server, but it 
has to be done by the sip application.
So, I get DNS server from android with a method not really documented... but 
well should work.
So fix soon :)

Original comment by r3gis...@gmail.com on 5 Oct 2010 at 7:25

• Changed state: Started

[GoogleCodeExporter]

http://code.google.com/p/csipsimple/downloads/detail?name=CSipSimple_0.00-13-05.
apk
Should improve things
Only primary DNS for now.

Original comment by r3gis...@gmail.com on 7 Oct 2010 at 7:25

[GoogleCodeExporter]

Should be fully completed in 0.00-13-06-b
Now :
* The two DNS are get back from the android system and configured in pjsip so 
that the sip stack can try to resolve things by its own
* There is an option to disable DNS SRV resolution (and settings from android 
to pjsip - that could break A dns resolution)
* There is an option to put your own DNS server if you don't want to use the 
one configured in android.

Original comment by r3gis...@gmail.com on 9 Oct 2010 at 11:01

• Changed state: NextRelease