[pjsip] IPv6/nameserver issues

[GoogleCodeExporter]

What steps will reproduce the problem?
1. use csip simple on verizon LTE 4g
2. select 'resolve dns srv' in csipsimple, settings, network
3. try to use it.

What is the expected output? 
I would expect it to work.

What do you see instead?
see bug 1302, this might explain that.

What version of the product are you using? 
market version, stable, and the nightly gingerbuild from last week.(1034)

On what operating system?
gingerbread 2.3.4, droid biotic.

additional information:
works on wifi, works on 3g.

looking at /etc/resolv.conf, I see two ipv4 nameservers there.
when I enable 4g/lte, I see an ipv6 nameserver.

nameserver 66.174.95.44
nameserver 2001:4888:0003:fffe:00c0:000d:0000:0003

Please provide any additional information below.
once I select dns srv records, and activate an account, I get this error 
message:

failed to init pjsua Invalid DNS nameserver
 address

now, it makes sense.   pjsua doesn't know what to do with ipv6 dns nameserver.

note: I rooted, and edited /etc/resolv.conf, restarted csip simple, didn't 
help.  I suspect its the ipv4 /vs ipv6 issue.

Original issue reported on code.google.com by michael....@gmail.com on 6 Oct 2011 at 2:00

[GoogleCodeExporter]

more info:
going to exert mode, setting ipv6 doesn't help.
error message is different, most likely since the sip server isn't ipv6 either.
other problem, even if that worked, is that if it switches to 3g or wifi, these 
arn't ipv6 either.

a workaround (which stopped error messages) was use custom dns (googles:  
8.8.8.8), but now, on let/4, it won't authenticate.

Original comment by michael....@gmail.com on 10 Oct 2011 at 9:14

[GoogleCodeExporter]

Revision 1498 will now allow detect of dns srv when it's ipv6 addresses and 
filter it out.

The root problem that is pjsip that doesn't support ipv6 dns resolution remains 
and can't be solved in CSipSimple project but in pjsip project. (tracking wiki 
page : http://trac.pjsip.org/repos/wiki/IPv6 / tracking issue : 
http://trac.pjsip.org/repos/ticket/419 )

Original comment by r3gis...@gmail.com on 13 May 2012 at 9:48

• Changed title: [pjsip] IPv6/nameserver issues
• Changed state: Accepted

[GoogleCodeExporter]

Well, I just changed in r1499 to take into account ipv6 address (but escaping 
[] that are added by android). Can you try with it and tell me how it goes? If 
you get a pjsua error or an authentication one. 
I've doubt on the fact pjsip doesn't already manage ipv6 for dns ip (and that 
the missing things is just DNS SRV in ipv6 mode).

Original comment by r3gis...@gmail.com on 13 May 2012 at 9:51

[GoogleCodeExporter]

I went a step further and dloaded r1638.
Seems to work in all cases now (wifi, 3g, and 4g)
wifi, (at my house) uses a router with alg that I can't turn off.
3g seems to be straight public ip
4g seems to give me an ipv4 private and an ipv6 address (with mixed dns 
servers) oh, and alg.. 
but it seems to work, I did select the 'DNS SRV' records but did NOT select use 
ipv6.

so, you fixed it and I promised $100.  How do I get it to you ?

(ps, bluetooth broken totally, doesn't show up as available, droidx, verizon, 
androis 2.3.4. 5.9.902.XT875.

Original comment by michael....@gmail.com on 22 Jun 2012 at 3:50

[GoogleCodeExporter]

For the BT problem it's under debugging. I changed something to support android 
4.0, but it has broken 2.3 support. Should not be too hard to find the root 
cause and fix it.

For the donation you can use : 
http://code.google.com/p/csipsimple/wiki/Donate?wl=en
But that's not mandatory :the fact you test and give me feedback is already 
very valuable for me :). Besides, it doesn't yet fully support ipv6 (this is 
something to be fixed in pjsip stack, and I've not skills to do that fast).

Also, something you might be interested in : I started to work on rewriting 
rules plugin to support itad and enum. The proof of concept of plugin part is 
already done (https://github.com/r3gis3r/Enum4CSipSimple) and I'm working on 
integrating the plugin inside csipsimple a clean way : as it has to be done 
asynchronously, it's not totally easy to integrate in csipsimple rewriting 
process that is for now synchronous.

I keep the issue opened to track the ipv6 implementation in pjsip and update 
csipsimple when done.

Original comment by r3gis...@gmail.com on 23 Jun 2012 at 11:42

[GoogleCodeExporter]

$50 in donation done!
the 'newer' nightly build, does fix the ipv6 issue, but the BT issue came
up.

is BT fixed on android 2.3.4 yet?
which nightly build fixed the ipv6 but didn't break bt yet?

Original comment by michael....@gmail.com on 7 Jul 2012 at 4:22

[GoogleCodeExporter]

report on builds:
1499 didn't fix the issue,
pj failed to init  unknown error 320044
FC's when I dial THROUGH a filter.

(ie: on main phone dialer, I type in '1234'.
filter: ^1\d{3}, suffix with @secnap.com

r1638 did work, but no BT.

note: new/different issue, on 1647,

I have a (really nice), caller id lookup program, uses 'opencnam' db.
when I dial OUT (using filter), it triggers the caller id lookup, thinking
this is an inbound call.

will try to identify later.

Original comment by michael....@gmail.com on 7 Jul 2012 at 4:37

[GoogleCodeExporter]

1569 works, dials in 4g, and BT works, and the (nifty) caller id program
still thinks this is an inbound call, but doesn't FC.

I will leave it, do you have a changelog for nightly builds?

On Sat, Jul 7, 2012 at 12:37 PM, Michael scheidell <
michael.scheidell@gmail.com> wrote:

Original comment by michael....@gmail.com on 7 Jul 2012 at 4:44

[GoogleCodeExporter]

Issue 2549 has been merged into this issue.

Original comment by r3gis...@gmail.com on 11 Nov 2013 at 5:59

[GoogleCodeExporter]

Issue 2549 has been merged into this issue.

Original comment by r3gis...@gmail.com on 15 Nov 2013 at 9:44

[GoogleCodeExporter]

Issue 2549 has been merged into this issue.

Original comment by r3gis...@gmail.com on 17 Nov 2013 at 10:37

[GoogleCodeExporter]

Issue 2549 has been merged into this issue.

Original comment by r3gis...@gmail.com on 30 Nov 2013 at 10:34