VOIP router requires re-registration

Forums › Slingshot and CallPlus › VOIP router requires re-registration

nzschooltech

14 posts

Geek
Inactive user

Topic # 31884 3-Apr-2009 08:30

I got the DVG-1402S up and running with my Uniden cordless phone. It worked fine for a couple of days, then I went to pick up, broken dial tone (which is actually produced by the router) and incoming calls would go straight to voicemail.

Couldn't figure this out but after poking around the config interface there is a section called "Query Registeration State" (sic)

Click the Query button and it says "registration_failed"
Click the Register button and it comes back with a URL:
sip:@203.184.16.2;expires=142

Every time I click query since then it comes back with the same, which keeps resetting itself at zero i.e. it appears to re-register so that the expiry goes back up to the high value. And the phone is working again.

The address 203.184.16.2 looks up to italksrv2.tranzpeer.net
The server that I put into my configuration settings is chc.italk.co.nz which also looks up to 203.184.16.2

So what caused the registration to fail? Did Slingshot change something on their end like the IP address?
Is there something I missed in the configuration settings of the router that it dropped the registration after a certain period?

nzschooltech

14 posts

Geek
Inactive user

Reply # 205064 3-Apr-2009 08:40

Found this thread and comments:

mjb: And finally, the ATA device itself registers with the SIP trunk fine, but will periodically drop off and give a registration status of 'Failed'. Seemingly randomly. With no other SIP clients connecting.

Aha... for anyone else that may be interested - turns out that this is a DNS thing. When it initially boots, the DNS servers given by DHCP are fine, but the Provisioning configuration from Slingshot set the DNS servers on the device to 202.180.64.10 and 202.180.64.11. Even if you specifically set the DNS servers in the config. Sadly, neither of these servers will answer the ATA's query for the SIP domain.

A bit of judicious use of DNAT and SNAT on my router transparently points it at my DNS server which does work.

Now it also says further in the thread:
http://www.dslreports.com/forum/r19525805-viatalk-with-SPA2102-adapter-It-restarts-every-60min

This is for a different product so it wouldn't seem to apply... also, I am not using Provisioning because the router was not supplied by Slingshot.

Now, further down in the config settings we have

DNS-SRV Query Domain
Service Domain
URL Format	SIP-URLTEL-URL
User Parameter Phone	DisabledEnabled
Caller ID Delivery	YESNO
Display CID	DisabledEnabled
Timer T2	481632 sec

Initial Unregister	DisabledEnabled
Register Expiration	sec
Session Expires	sec
Min-SE	sec
Session Expires Refresher	uacuas
Keep Ping Hole	DisabledEnabled
Ping Hole interval

Both of these seem to relate to my situation but I don't know much about how to set them up.
The setting for "Service Domain" is probably incorrect, I actually haven't got a clue what should go in there.

mjb

922 posts

Ultimate Geek
+1 received by user: 21

Trusted

Reply # 205069 3-Apr-2009 09:15

If it's being provisioned, then the chances are high they're provisioning the DNS server entries on your device. They'll deny it, but I never entered those DNS servers :)

This is only a problem if your broadband is not with slingshot. The DNS servers they provision will not respond to an external query for xyz.italk.co.nz.

contentsofsignaturemaysettleduringshipping

nzschooltech

14 posts

Geek
Inactive user

Reply # 205076 3-Apr-2009 09:42

mjb: If it's being provisioned, then the chances are high they're provisioning the DNS server entries on your device. They'll deny it, but I never entered those DNS servers :)

This is only a problem if your broadband is not with slingshot. The DNS servers they provision will not respond to an external query for xyz.italk.co.nz.

It's not being provisioned - on the provisioning page it is disabled - and as Slingshot didn't supply this device there's no way it knows where to be provisioned from, anyway.

And I'm not going to provision it (LOL)

Seems strange their DNS servers can't respond to a query when Telstra's can. I wonder if they changed the DNS entry recently? The results I posted as above came from Telstra's DNS server(s).