dns lookup error out when registering with HT502

[terryyl]

Hi,

I hope somebody can help me figure this out:
About 3 weeks ago, my ATA was disconnecting very frequently
Started the troubleshooting with the regular cycling down and up of all devices (Modem then ATA which is doubling as my router(Grandstream HT-502)
Since it did not fix the issue, I upgrade to the latest firmware 1.0.15.5 which did not fix the issue neither.
Enabled the syslog to figure our that I was having issue with the DNS not resolving the 4 fpl addresses (voip, voip2, voip3 and voip4.freephoneline.ca:6060) from the ATA. Nslookup from my pc on the same network resolves without any problem.
I have now hardcoded the IP address and it works !
I know this is not the right solution but my wife was getting very frustrated with the service.
I was wondering if the error is related to the fact that was getting a registration ban. Eventhough, I have set the reg-retry to 120secs, I saw that the ATA was trying to connect over the 5 times within 5mins.

My setup:
ISP: Electronic Box over cable
ATA/Router: Grandstream HT-502

Thanks
Terry


Dec 23 11:10:59 192.222.180.172 logger: HT-502 [00:0B:82:32:58:B0]: [1.0.15.5] SIPStack(0)::snd_message:(621)REGISTER sip:voip.freephoneline.ca SIP/2.0 Via: SIP/2.0/UDP 192.222.180.###:34095;branch=z9hG4bK303582310;rport From: <sip:1514683####@voip.freephoneline.ca>;tag=1351505386 To: <sip:1514683####@voip.freephoneline.ca> Call-ID: 123264201-34095-2@BJC.CCC.BIA.BHC CSeq: 2002 REGISTER Contact: <sip:1514683####@192.222.180.###:34095>;reg-id=1;+sip.instance="<urn:uuid:00000000-0000-1000-8000-000B823258B0>" Max-Forwards: 70 User-Agent: Grandstream HT-502 V1.2A 1.0.15.5 chip V2.2 Supported: path Expires: 3600 Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE Content-Length: 0
Dec 23 11:10:59 HT-502 [00:0B:82:32:58:B0]: [1.0.15.5] DNS::check_dns_answer_cname, 657 i = 73 rdata = 5128
Dec 23 11:10:59 HT-502 [00:0B:82:32:58:B0]: [1.0.15.5] DNS::parse_pkt_cname, 762 retval = -1
Dec 23 11:10:59 HT-502 [00:0B:82:32:58:B0]: [1.0.15.5] DNS::_lookup, 342 parse_pkt_cname error
Dec 23 11:10:59 HT-502 [00:0B:82:32:58:B0]: [1.0.15.5] SIPStack(0)::cb_transport_error: Transport error (-1) for transaction 4
Dec 23 11:10:59 HT-502 [00:0B:82:32:58:B0]: [1.0.15.5] SIPStack(0)::cb_nict_kill_transaction: Kill NICT transaction 4
Dec 23 11:10:59 HT-502 [00:0B:82:32:58:B0]: [1.0.15.5] SIPStack(0)::run: Active transactions: 1
Dec 23 11:10:59 HT-502 [00:0B:82:32:58:B0]: [1.0.15.5] SIPTransaction::waitForResponse: Request 4 is cancelled or killed
Dec 23 11:10:59 HT-502 [00:0B:82:32:58:B0]: [1.0.15.5] SigCtrl::performRegistration, transaction got code 2:-1
Dec 23 11:10:59 HT-502 [00:0B:82:32:58:B0]: [1.0.15.5] SigCtrl::performRegistration, regRetries:3, retryAfter:0, regRetryWait:120
Dec 23 11:13:00 HT-502 [00:0B:82:32:58:B0]: [1.0.15.5] DNS::check_dns_answer_cname, 657 i = 73 rdata = 5128
Dec 23 11:13:00 HT-502 [00:0B:82:32:58:B0]: [1.0.15.5] DNS::parse_pkt_cname, 762 retval = -1
Dec 23 11:13:00 HT-502 [00:0B:82:32:58:B0]: [1.0.15.5] DNS::_lookup, 342 parse_pkt_cname error
Dec 23 11:13:01 HT-502 [00:0B:82:32:58:B0]: [1.0.15.5] SigCtrl::performReg on acct 0, registered: 0, proxy: voip.freephoneline.ca, preferPrimary: 0

[Liptonbrisk]

DNS errors are not related to temporary registration IP bans from FPL SIP servers.
In order to be temporarily IP banned, your ATA needs to connect to the FPL server first.
In order to connect to the FPL SIP server, DNS lookup needs to work properly in your ATA (unless you're specifying IP addresses instead of voip.freephoneline.ca, etc.)
In other words, you can't be temporarily IP banned unless DNS lookups are working properly for you in the first place.

I don't have a 502 nor have used one.
But if you believe you're having DNS issues, I would specify your ISP's DNS servers or try OpenDNS (208.67.222.222 and 208.67.220.220) in your ATA.
You should then be able to revert to specifying voip.freephoneline,ca, voip2.freephoneline.ca, or voip4.freephoneline.ca:6060 instead of IP addresses.


http://support.freephoneline.ca/hc/en-u ... redentials

These three timers need to be set properly:

1. Registration Interval: 3600 seconds (1 hour)

I believe that's "Reregister before expiration" = 0 for you
(since that's based on #2)

2. Registration Expiry: 3600 seconds (1 hour)

I believe that's "Register Expiration" = 60 minutes for you

3. Failed Registration Re-Try Interval: 120 seconds

I believe that's "Sip Registration Failure Retry Wait time" is 120 seconds for you

[terryyl]

Hi Liptonbrisk,

Thank you for your prompt response.
I have all the timers set as you mentioned.

So everything has been working since this morning without any disconnection with the ip address.
I tried 1st to set it back to voip2.freephoneline.ca since I saw there were issues with the network this moning. No luck.
Tried the open dns addresses. No luck
btw. I shutdown the ATA/router for more than 2 mins between each try.

Now I tried a new address since I saw with the nslookup that voip2 was resolving to fplproxy3.fongo.com
And this resolves correctly. I am starting to think that there should be a timeout setting somewhere that I could increase to give enough time for the ATA to resolve the voip.freephoneline.ca address.

See the difference between the 2 traces. much faster for the fplproxy3 address

C:\>tracert voip2.freephoneline.ca
Tracing route to fplproxy3.fongo.com [162.213.111.22]
over a maximum of 30 hops:
1 3 ms 1 ms 1 ms 192.168.0.240
2 385 ms 33 ms 632 ms 10.170.167.222
3 9 ms 10 ms 10 ms 10.170.192.58
4 15 ms 12 ms 10 ms mtl7-mx960-xe11-0-0.ebox.ca [74.116.184.65]
5 11 ms 10 ms 14 ms 96.127.249.138
6 17 ms 12 ms 12 ms he.peer.qix.ca [198.179.18.5]
7 19 ms 21 ms 23 ms 100ge6-1.core1.tor1.he.net [184.105.64.57]
8 20 ms 18 ms 20 ms fibernetics-corporation.10gigabitethernet3-1.core1.tor1.he.net [209.51.163.214]
9 * * * Request timed out.
10 * * * Request timed out.
11 17 ms 17 ms 17 ms host-162-213-111-22.static.295.ca [162.213.111.22]

C:\>tracert fplproxy3.fongo.com
Tracing route to fplproxy3.fongo.com [162.213.111.22]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.240
2 31 ms 31 ms 31 ms 10.170.167.222
3 9 ms 17 ms 23 ms 10.170.192.58
4 13 ms 9 ms 10 ms mtl7-mx960-xe11-0-0.ebox.ca [74.116.184.65]
5 12 ms 9 ms 9 ms 96.127.249.138
6 21 ms 9 ms 13 ms he.peer.qix.ca [198.179.18.5]
7 17 ms 17 ms 22 ms 100ge6-1.core1.tor1.he.net [184.105.64.57]
8 113 ms 17 ms 20 ms fibernetics-corporation.10gigabitethernet3-1.core1.tor1.he.net [209.51.163.214]
9 * * * Request timed out.
10 * * * Request timed out.
11 17 ms 18 ms 18 ms host-162-213-111-22.static.295.ca [162.213.111.22]

[Liptonbrisk]

I tried 1st to set it back to voip2.freephoneline.ca since I saw there were issues with the network this moning. No luck.

An error message might be useful here (registration status/3 digit SIP error code), but I doubt I'm going to be useful troubleshooting this problem further, since I've never used an HT502 and am not familiar with its routing features. I can't tell you where to find specific settings because I'm not familiar with the ATA's menus.

Tried the open dns addresses. No luck
btw.

I'm not sure if you're using DSL or Cable, but if you are using the HT502 as a router, make sure that whatever your ISP gave you (modem/router combination) is in bridge mode.
If it's DSL, your HT502 needs to be doing PPoE login. You need to ensure the HT502 is being used as a DHCP to assign LAN IP leases.

Since I've never used a HT502, I don't know where these settings are, but somewhere you should be able to assign DNS IP address to the ATA itself, as opposed to devices on your LAN.
So, what I'm stating about specifying DNS servers has nothing to do with the LAN side.You want to specify WAN DNS since your ATA is acting as a router.

I am starting to think that there should be a timeout setting somewhere that I could increase to give enough time for the ATA to resolve the voip.freephoneline.ca address.

I'm not aware of any need to do this, and I'm certainly not aware of any ATA or device that has a setting that waits for DNS resolving.

See the difference between the 2 traces. much faster for the fplproxy3 address

C:\>tracert voip2.freephoneline.ca
Tracing route to fplproxy3.fongo.com [162.213.111.22]
over a maximum of 30 hops:
1 3 ms 1 ms 1 ms 192.168.0.240
2 385 ms 33 ms 632 ms 10.170.167.222
3 9 ms 10 ms 10 ms 10.170.192.58
4 15 ms 12 ms 10 ms mtl7-mx960-xe11-0-0.ebox.ca [74.116.184.65]
5 11 ms 10 ms 14 ms 96.127.249.138
6 17 ms 12 ms 12 ms he.peer.qix.ca [198.179.18.5]
7 19 ms 21 ms 23 ms 100ge6-1.core1.tor1.he.net [184.105.64.57]
8 20 ms 18 ms 20 ms fibernetics-corporation.10gigabitethernet3-1.core1.tor1.he.net [209.51.163.214]
9 * * * Request timed out.
10 * * * Request timed out.
11 17 ms 17 ms 17 ms host-162-213-111-22.static.295.ca [162.213.111.22]

C:\>tracert fplproxy3.fongo.com
Tracing route to fplproxy3.fongo.com [162.213.111.22]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.240
2 31 ms 31 ms 31 ms 10.170.167.222
3 9 ms 17 ms 23 ms 10.170.192.58
4 13 ms 9 ms 10 ms mtl7-mx960-xe11-0-0.ebox.ca [74.116.184.65]
5 12 ms 9 ms 9 ms 96.127.249.138
6 21 ms 9 ms 13 ms he.peer.qix.ca [198.179.18.5]
7 17 ms 17 ms 22 ms 100ge6-1.core1.tor1.he.net [184.105.64.57]
8 113 ms 17 ms 20 ms fibernetics-corporation.10gigabitethernet3-1.core1.tor1.he.net [209.51.163.214]
9 * * * Request timed out.
10 * * * Request timed out.
11 17 ms 18 ms 18 ms host-162-213-111-22.static.295.ca [162.213.111.22]

It's really the last hop that's important. You're getting 17 ms. That's fine.

Second hop is a private IP address. Might be a CMTS. Or internal routers on their end. The private IPs are normal. Sometimes these routers or CMTS (do not respond or) delay the results of ICMP ping requests, especially when under heavy load.

The high ping is slightly odd, but I would be more troubled if each ping going along the path were increasing or high, but they're not. So, I don't feel the second hop is the cause of your problem, unless you're getting tons of packet loss at the last hop, and I doubt you are with a 17 ms ping.

If help from others isn't forthcoming, you might want to ask at the Grandstream forums, which are located at http://forums.grandstream.com/forums/.
You can also submit a ticket at https://helpdesk.grandstream.com/.