Click Here To Visit SIP Broker  

Go Back   Voxalot / SIP Broker Support Forums > Voxalot Forums > Voxalot General

Voxalot General Voxalot discussion, tips, tricks and suggestions. Talk about them here.

 
 
Reply
Thread Tools Display Modes
Unread 03-17-2008, 06:46 AM   #1
rovert
Junior Member
 
Join Date: Dec 2007
Location: Melbourne Australia
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
rovert is on a distinguished road
Default au.voxalot.com fails but IP OK

Hi,

I am not using Voxalot for multiple VSP registrations on an ATA, instead I am using it for trying out URL dialling and calling my IP phone direct from the SIP Broker PSTN gateway.

When I try to register my Voxalot account on a Snom190 or Snom 300 IP phone using au.voxalot.com as the Registrar it fails (tried on both phones). But if I use the IP address 202.60.88.238 it registers OK.

I don't have any problem with other VSP's on the phones using the DNS names.

I found reference to proxy01.au1.sipbroker.com in the phones DNS cache . When I use this as the Registrar it works OK. (in fact there were 2 "A" entries in the DNS cache - au.voxalot.com and proxy01.au1.voxalot.com)

Is this a phone problem or an ADSL router problem or a SIPBroker problem ?

I use the IP address of my ADSL router as the DNS entry in the phones as this give no problems with my Trixbox server and various other IP phones with other VSP's.

I even tried using my ISP's DNS server IP address directly in the Snom phones, but Voxalot still does not register with au.voxalot.com


Where do I start looking to solve this issue ?

Trevor
rovert is offline   Reply With Quote
Unread 03-17-2008, 08:20 PM   #2
emoci
 
Join Date: Jul 2007
Location: Toronto, Canada
Posts: 1,422
Thanks: 123
Thanked 369 Times in 282 Posts
emoci is a name known to allemoci is a name known to allemoci is a name known to allemoci is a name known to all
Default

Quote:
Originally Posted by rovert View Post
Hi,

I am not using Voxalot for multiple VSP registrations on an ATA, instead I am using it for trying out URL dialling and calling my IP phone direct from the SIP Broker PSTN gateway.

When I try to register my Voxalot account on a Snom190 or Snom 300 IP phone using au.voxalot.com as the Registrar it fails (tried on both phones). But if I use the IP address 202.60.88.238 it registers OK.

I don't have any problem with other VSP's on the phones using the DNS names.

I found reference to proxy01.au1.sipbroker.com in the phones DNS cache . When I use this as the Registrar it works OK. (in fact there were 2 "A" entries in the DNS cache - au.voxalot.com and proxy01.au1.voxalot.com)

Is this a phone problem or an ADSL router problem or a SIPBroker problem ?

I use the IP address of my ADSL router as the DNS entry in the phones as this give no problems with my Trixbox server and various other IP phones with other VSP's.

I even tried using my ISP's DNS server IP address directly in the Snom phones, but Voxalot still does not register with au.voxalot.com


Where do I start looking to solve this issue ?

Trevor
Try registering with the us or eu server, and see if you get the same behaviour.....

The other thing is to try a tracert (so RUN>>CMD>> tracert au.voxalot.com and see if you have any issues resolving au.voxalot.com)

On that note, I just ran a tracert from my end, and it seems there are a few timeouts on the path for au.voxalot.com which I'll try to have Martin or Craig take a look at (it could explain your problem), if you have a chance to run a tracert as well, please post....:

Code:
Tracing route to au.voxalot.com [202.60.88.238]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  WRT54G [192.168.0.1]
  2    11 ms     9 ms    10 ms  erx03.tor.pppoe.ca [206.248.154.101]
  3    10 ms    10 ms    10 ms  i2120.border1.pppoe.ca [206.248.155.233]
  4    10 ms     9 ms     9 ms  65.39.198.249
  5    70 ms    71 ms    70 ms  oc48-po3-0.van-hc21e-dis-1.peer1.net [216.187.11
4.137]
  6    75 ms    73 ms    76 ms  oc48-po0-0.sea-coloc-dis-1.peer1.net [216.187.88
.214]
  7    93 ms    92 ms    92 ms  oc48-po0-0.sj-mkp16-dis-1.peer1.net [216.187.88.
202]
  8    92 ms    92 ms    93 ms  oc48-po6-0.sj-mkp2-dis-1.peer1.net [216.187.88.1
34]
  9   101 ms   101 ms   100 ms  oc48-po9-0.la-600w-cor-2.peer1.net [216.187.88.1
30]
 10   102 ms   100 ms   103 ms  singtel.com.any2ix.crgwest.com [206.223.143.63]

 11   259 ms   259 ms   259 ms  203.208.148.18
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14   275 ms   275 ms   275 ms  business-networks.14vrc76f06.optus.net.au [61.88
.151.146]
 15   273 ms   273 ms   272 ms  vl3806.gi0.ar1.ade102.uecomm.net.au [203.94.191.
149]
 16     *        *        *     Request timed out.
 17   266 ms   265 ms   266 ms  202.60.88.238

Trace complete.

Trying to explain a few of the other things you are seeing:

If I am not wrong proxy01.au1.voxalot.com and proxy02.au1.voxalot.com are the SRV records for au.voxalot.com which however point to the same A record as au.voxalot.com....you however want to use either au.voxalot.com or the IP rather than the proxy01.au1.voxalot.com addreses to register

Now, I see no reason for a DNS issue, since au.voxalot.com has the server defined in the A record directly (no need to dig for the SRV records)

proxy01.au1.sipbroker.com is probably there since you've been placing calls from SipBroker to VoXalot

Last edited by emoci; 03-17-2008 at 08:28 PM.
emoci is offline   Reply With Quote
Unread 03-17-2008, 11:56 PM   #3
rovert
Junior Member
 
Join Date: Dec 2007
Location: Melbourne Australia
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
rovert is on a distinguished road
Thumbs up

emoci,

Thanks for the reply.

i did a tracert to au.voxalot.com and it looks OK - no timeouts

*************************
C:\Documents and Settings\Trevor>tracert au.voxalot.com

Tracing route to au.voxalot.com [202.60.88.238]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 741ge [192.168.1.254]
2 11 ms 11 ms 11 ms lo1.mel-lns2.vic.westnet.com.au [202.173.159.34]
3 12 ms 13 ms 13 ms gi2-9.mel-core.vic.westnet.com.au [202.173.159.97]
4 14 ms 14 ms 12 ms AS10223.melbourne.pipenetworks.com [218.100.13.20]
5 31 ms 33 ms 30 ms 218.185.30.50
6 49 ms 52 ms 52 ms 10265.at2-0.ade102-cs2.uecomm.net.au [218.185.30.118]
7 53 ms 51 ms 51 ms 10228.atm2-0.ade102-cs1.uecomm.net.au [203.94.191.89]
8 51 ms 50 ms 51 ms 203.94.189.114
9 63 ms 71 ms 73 ms 202.60.88.238

Trace complete.

********************

I tried eu.voxalot.com and us.voxalot.com but both these result in "Registration failed" on the Snom190

I think it must be the way the Snoms are interpreting the returned DNS information.

I will try Voxalot on a LinkSys SPA to see if it behaves the same.

Trevor
rovert is offline   Reply With Quote
Unread 03-18-2008, 01:38 AM   #4
craig
 
Join Date: Feb 2006
Posts: 243
Thanks: 8
Thanked 130 Times in 72 Posts
craig is a jewel in the roughcraig is a jewel in the roughcraig is a jewel in the rough
Default

Hmm... it is a bit hard to tell from here, however, my best guess would be that there is a problem with the snom's DNS handling.

Whether you connect via IP address or hostname shouldn't matter. The client (the snom, in this case) resolves the hostname into the IP address and from that point on, everything should be exactly the same. All I can presume is that for some reason, the snom is having trouble resolving the au.voxalot.com hostname into an IP address.

I am not a networking expert, but the timeouts that you see in the traceroutes should be immaterial... AFAIK, it is normal for some hops to drop ICMP packets. When you actually connect using TCP or UDP, it should blast on through.

I once had a situation where my PC was not resolving some hostnames, and eventually my ISP owned up to their DNS server having problems. Perhaps you are suffering from similar symptoms - although, you mentioned that you had tried several different DNS servers. Weird!

I will check with Mart to see if there is anything slightly different with the way the au.voxalot.com DNS settings are set up.

--
Craig
craig is offline   Reply With Quote
Unread 03-18-2008, 02:42 AM   #5
rovert
Junior Member
 
Join Date: Dec 2007
Location: Melbourne Australia
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
rovert is on a distinguished road
Default

Craig,

I tend to agree that it is something about the way the Snom's handle DNS - but just for Voxalot - they work for every other VSP I have tried - about 5 all up.

I just tried a Grandstream BT101 - a very basic phone (that I was just about to give away to a relative) and it is OK with au.voxalot.com


The Snom 190 has firmware 3.60x (last available - a couple of years old) and the Snom 300 has firmware 6.5.17 - the latest in the 6.x series, so that is span of a couple of years to sort out any DNS issues, so it must be a wierd combination of Snom DNS implementation and the voxalot DNS configuration.

I am happy to just continue using the IP address and leave the issue unresolved. The more I get into VoIp the more "strange" unexplained issues I come across !

Trevor
rovert is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Unable to register via au.voxalot.com BustaC Voxalot Support 4 11-13-2009 09:54 AM
Voxalot Registration Fails Craig33 Voxalot Support 9 02-18-2009 09:36 AM
Problem with au.voxalot.com vs voxalot.com.au MarkLL Voxalot Support 1 03-13-2007 10:26 PM
Can't connect to au.voxalot.com ozimarco Voxalot Support 5 02-12-2007 09:46 AM
e164: au.voxalot.com or voxalot.com rodsherwin Voxalot Support 1 01-25-2007 11:25 AM


All times are GMT. The time now is 08:52 AM.


Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.