No ipv6 dns name resolution?

Asterisk Asterisk Support
1

When trying to setup asterisk 13.1 with PJSIP to connect to my IPV6 capable SIP provider the registration fails.

[Dec 22 19:24:24] DEBUG[25247] pjsip: tsx0x110736c .Transaction created for Request msg REGISTER/cseq=36181 (tdta0x721d90) [Dec 22 19:24:24] DEBUG[25247] pjsip: tsx0x110736c Sending Request msg REGISTER/cseq=36181 (tdta0x721d90) in state Null [Dec 22 19:24:24] DEBUG[25247] pjsip: sip_resolve.c .Starting async DNS A query: target=sip1.easybell.de, transport=Unspecified, port=5060 [Dec 22 19:24:24] DEBUG[25247] pjsip: resolver.c .Transmitting 34 bytes to NS 0 (192.168.178.1:53): DNS A query for sip1.easybell.de: Success [Dec 22 19:24:24] DEBUG[25247] pjsip: tsx0x110736c .State changed from Null to Calling, event=TX_MSG [Dec 22 19:24:24] DEBUG[25252] pjsip: resolver.c Received 50 bytes DNS response from 192.168.178.1:53 [Dec 22 19:24:24] DEBUG[25252] pjsip: resolver.c Nameserver 192.168.178.1:53 state changed Active --> Active [Dec 22 19:24:24] WARNING[25252] pjsip: tsx0x110736c Failed to send Request msg REGISTER/cseq=36181 (tdta0x721d90)! err=171064 (Unsuitable transport selected (PJSIP_ETPNOTSUITABLE)) [Dec 22 19:24:24] DEBUG[25252] pjsip: tsx0x110736c State changed from Calling to Terminated, event=TRANSPORT_ERROR [Dec 22 19:24:24] DEBUG[25252] pjsip: tsx0x110736c Timeout timer event [Dec 22 19:24:24] WARNING[25247] res_pjsip_outbound_registration.c: No response received from 'sip:sip1.easybell.de:5060' on registration attempt to 'sip:004970718604945@sip1.easybell.de:5060', retrying in '60' [Dec 22 19:24:24] DEBUG[25252] pjsip: tsx0x110736c .State changed from Terminated to Destroyed, event=TIMER

For my naive eyes it looks as if there is no ipv6 name resolution (a DNS AAAA query) performed.

What is missing? Please help.

2

Did you compile pjproject w/ IPv6 support? pjproject does not enable IPv6 by default.

wiki.asterisk.org/wiki/display/ … +pjproject

3

Yes, I did, went through that already…

Here are the (relevant) entries in the configuration files:

pjsip.conf

[code][udp-ipv6]
type=transport
protocol=udp
bind=[2a02:8070:86c0:2ca0:ba27:ebff:feda:bbb6]:5060

…

endpoint-ipv6
type=endpoint
context=ExternalSets
transport=udp-ipv6
rtp_ipv6=yes
disallow=all
;allow=g722
allow=alaw
allow=gsm
allow=g726
allow=ulaw

registration-ipv6
type=registration
transport=udp-ipv6
;auth_rejection_permanent=no
retry_interval=60

easybell
outbound_auth=easybell
server_uri=sip:sip1.easybell.de:5060
client_uri=sip:@sip1.easybell.de:5060

easybell
;context=ExternalSets
outbound_auth=easybell
aors=easybell[/code]

The own IPV6 address is recognized:

[code][Dec 22 19:24:14] DEBUG[25222] pjsip: udpv60x998200 SIP UDP IPv6 transport started, published address is [2a02:8070:86c0:2ca0:ba27:ebff:feda:bbb6]:5060

…

[Dec 22 19:24:20] VERBOSE[25222] res_pjsip_multihomed.c: Local IPv4 address determined to be: 192.168.178.99
[Dec 22 19:24:20] VERBOSE[25222] res_pjsip_multihomed.c: Local IPv6 address determined to be: [2a02:8070:86c0:2ca0:ba27:ebff:feda:bbb6][/code]

The IP address of the partner is recognized:

[Dec 22 19:24:20] VERBOSE[25222] config.c: Parsing '/etc/asterisk/pjsip.conf': Found [Dec 22 19:24:20] DEBUG[25222] netsock2.c: Splitting 'sip1.easybell.de' into... [Dec 22 19:24:20] DEBUG[25222] netsock2.c: ...host 'sip1.easybell.de' and port ''. [Dec 22 19:24:20] DEBUG[25222] netsock2.c: Splitting '2001:4090:4008::124' into... [Dec 22 19:24:20] DEBUG[25222] netsock2.c: ...host '2001:4090:4008::124' and port ''. [Dec 22 19:24:20] DEBUG[25222] acl.c: [2001:4090:4008::124]:0/[ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff]:0 sense 0 appended to ACL

The problem is when Asterisk tries to register with the other host.

4

Howdy,

I don’t know the answer to this, but I’m sure someone on the asterisk-users mailing list does.

lists.digium.com/mailman/listinfo/asterisk-users

5

Thank you Malcolm,

I tried to post it there, but it shows not up in the archive. How long does it take for a mail to show up there?

I am falling back to the IPV4 NAT solution now, as this works. But IPV6 would be fine to use, direct traffic, no NAT-ing.

Regards and have a fine Christmas.

6

Hi @rbasche,
did you find a resolution for the issue?

I experience the same problem. I could make IPv6 work using the IP address of the SIP-server, but that is obviously only a workaround…

Asterisk 13.7 on RaspberryPi

7

Sorry, no, I have not followed it any further, I tried to post the question to the asterisk mailing list, but obviously I was to dumb to do that correctly and/or understandable, so I never received any reply there. Might be you have more luck…

Regards

8

Asterisk 13 uses the PJSIP DNS resolution. It is very limited and does not do AAAA lookups. We wrote our own support in master (which will become 14) that is more feature complete. It does AAAA and A lookups, depending on available transports, and supports NAPTR and SRV. We also have testsuite tests which verify it is behaving as expected.

9

@rosch, I replied to your query in your other thread…

@rbasche, since the recently released PJProject 2.5.5, your issue should be resolved even if you stay with Asterisk 13. Please, give it a try and report.