DNS-SRV Registered Phones to Not Respond to Options Messages

[joshe]

I am experiencing a bug with all Yealink phones, where if I use a DNS-SRV address as the registrar, they do not respond to SIP OPTIONS messages to keep the NAT pinhole open. If I switch back to UDP, they respond normally.

When I do a PCAP on the yealink phone itself, I can see that the phone gets the packet, bt it does not respond.

Is there anything we can do to get that working?

[admin1]

hi, Could you upload your PCAP file, so may be we could get some message from it

[ldardini]

Hello,
I have the same problem. Is there any solution available? Have Joshe provided the pcap? I can provide it if needed.

Leandro

[Flora_Yealink]

(12-03-2012 05:23 AM)ldardini Wrote:  Hello,
I have the same problem. Is there any solution available? Have Joshe provided the pcap? I can provide it if needed.

Leandro

Hi Leandro,
We have fixed this issue in V70 version , and the firmware will be ready within this week, you can download the version from our web site http://www.yealink.com/ next Monday and test.

Flora Wu

[ldardini]

Hello Flora,
unfortunately the issue is not solved. I have upgraded the phone and then reset it. The phone is still not answering to OPTIONS messages. Is there a way I can help you solving the issue?

For a brief tcpdump I run, it seems the phone performs a DNS request for NAPTR once booted, then correctly the SRV request, but then make an A request to the DNS_SRV record provided that is not needed to be resolved. However, even by providing an A record for such entry, doesn't solve the issue.

21:38:38.368828 IP 192.168.2.104.1024 > 192.168.2.254.53: 2+ NAPTR? voip.domain.com. (39)
21:38:38.369346 IP 192.168.2.254.53 > 192.168.2.104.1024: 2 1/2/4 NAPTR (286)
21:38:38.374623 IP 192.168.2.104.1024 > 192.168.2.254.53: 2+ SRV? _sip._udp.voip.domain.com. (49)
21:38:38.375041 IP 192.168.2.254.53 > 192.168.2.104.1024: 2 2/2/2 SRV pbx2.domain.com.:5060 20 100, SRV pbx1.domain.com.:5060 10 100 (224)
21:38:38.379817 IP 192.168.2.104.1024 > 192.168.2.254.53: 2+ A? pbx1.domain.com. (40)
21:38:38.380185 IP 192.168.2.254.53 > 192.168.2.104.1024: 2 1/2/0 A xx.xx.xx.245 (115)
21:38:38.391439 IP 192.168.2.104.1024 > 192.168.2.254.53: 2+ A? pbx2.domain.com. (40)
21:38:38.391830 IP 192.168.2.254.53 > 192.168.2.104.1024: 2 1/2/0 A xx.xx.xx.182 (115)
21:38:39.080625 IP 192.168.2.104.1024 > 192.168.2.254.53: 2+ A? voip.domain.com. (39)
21:38:39.080982 IP 192.168.2.254.53 > 192.168.2.104.1024: 2 0/1/0 (108)
21:38:39.082650 IP 192.168.2.104.1024 > 192.168.2.254.53: 3+ A? voip.domain.com."dardini.it". (52)
21:38:39.083057 IP 192.168.2.254.53 > 192.168.2.104.1024: 3 NXDomain 0/1/0 (127)
21:38:39.085476 IP 192.168.2.104.1024 > 192.168.2.254.53: 4+ A? voip.domain.com. (39)
21:38:39.085737 IP 192.168.2.254.53 > 192.168.2.104.1024: 4 0/1/0 (108)
21:38:39.087533 IP 192.168.2.104.1024 > 192.168.2.254.53: 5+ A? voip.domain.com."dardini.it". (52)

Leandro

[Flora_Yealink]

(12-11-2012 04:56 AM)ldardini Wrote:  Hello Flora,
unfortunately the issue is not solved. I have upgraded the phone and then reset it. The phone is still not answering to OPTIONS messages. Is there a way I can help you solving the issue?

For a brief tcpdump I run, it seems the phone performs a DNS request for NAPTR once booted, then correctly the SRV request, but then make an A request to the DNS_SRV record provided that is not needed to be resolved. However, even by providing an A record for such entry, doesn't solve the issue.

21:38:38.368828 IP 192.168.2.104.1024 > 192.168.2.254.53: 2+ NAPTR? voip.domain.com. (39)
21:38:38.369346 IP 192.168.2.254.53 > 192.168.2.104.1024: 2 1/2/4 NAPTR (286)
21:38:38.374623 IP 192.168.2.104.1024 > 192.168.2.254.53: 2+ SRV? _sip._udp.voip.domain.com. (49)
21:38:38.375041 IP 192.168.2.254.53 > 192.168.2.104.1024: 2 2/2/2 SRV pbx2.domain.com.:5060 20 100, SRV pbx1.domain.com.:5060 10 100 (224)
21:38:38.379817 IP 192.168.2.104.1024 > 192.168.2.254.53: 2+ A? pbx1.domain.com. (40)
21:38:38.380185 IP 192.168.2.254.53 > 192.168.2.104.1024: 2 1/2/0 A xx.xx.xx.245 (115)
21:38:38.391439 IP 192.168.2.104.1024 > 192.168.2.254.53: 2+ A? pbx2.domain.com. (40)
21:38:38.391830 IP 192.168.2.254.53 > 192.168.2.104.1024: 2 1/2/0 A xx.xx.xx.182 (115)
21:38:39.080625 IP 192.168.2.104.1024 > 192.168.2.254.53: 2+ A? voip.domain.com. (39)
21:38:39.080982 IP 192.168.2.254.53 > 192.168.2.104.1024: 2 0/1/0 (108)
21:38:39.082650 IP 192.168.2.104.1024 > 192.168.2.254.53: 3+ A? voip.domain.com."dardini.it". (52)
21:38:39.083057 IP 192.168.2.254.53 > 192.168.2.104.1024: 3 NXDomain 0/1/0 (127)
21:38:39.085476 IP 192.168.2.104.1024 > 192.168.2.254.53: 4+ A? voip.domain.com. (39)
21:38:39.085737 IP 192.168.2.254.53 > 192.168.2.104.1024: 4 0/1/0 (108)
21:38:39.087533 IP 192.168.2.104.1024 > 192.168.2.254.53: 5+ A? voip.domain.com."dardini.it". (52)

Leandro

hi Leandro,
Could you upload your PCAP file, so then we can investigate this issue ?

Best Regards!

[ldardini]

Hi Flora, thank you for the interest, can you let me know the email where to send the pcap? I don't like to post them publicly

Leandro

[ldardini]

After a double check of the firmware version, I was still running the old version. Upgrading to the latest version fixes the problem. Thank you Yealink and thank you Flora for the patience.

Leandro

[Flora_Yealink]

(12-20-2012 12:18 AM)ldardini Wrote:  After a double check of the firmware version, I was still running the old version. Upgrading to the latest version fixes the problem. Thank you Yealink and thank you Flora for the patience.

Leandro

Hi Leandro,
You are welcome and I'm happy to hear that the issue is fixed.
Best Regards!