voxalot.com STUN server is unreachable
It seems that voxalot's STUN server is unreachable. That's fine for most SIP UAs which have an option to configure STUN manually. But if you want to rely on DNS - no way :(
Code:
$ nslookup |
Did you try stun.voxalot.com.au ?
This one is definitely working on my ATA. I do not believe that there is one at stun.voxalot.com though the website could probably be a bit clearer about this. Hope this helps .... |
Quote:
This is not about the user who can't use specific STUN. This is about the invalid server reported by DNS. Quote:
|
stun.voxalot.com and stub.voxalot.com.au both point to 202.60.88.239 and is definitely reachable.
. |
Code:
Code:
C:\TEMP>stun-client-0-96 202.60.88.239 |
Not sure the same traceroute reports fine from the U.S and AU:
Code:
14 61.88.171.198 (61.88.171.198) 237.021 ms 236.947 ms 236.620 ms . |
A traceroute from DNS tools, reports and Hosting tests, advanced network and domain name tools. also reached its destination:
Code:
1 12 * * 0.6 ms |
Code:
1 * |
Fine here too on my Aussie People Telecom connection which sometimes tends to have the odd routing issue. I can't get to some ipkall pages for instance, but my Exetel connection gets there fine.
|
It seems that one of our networks (/14) is filtered there:
Code:
$ ping 202.60.88.239 If anybody from Admins is willing to help please let me know. Thanks. |
All times are GMT. The time now is 03:49 PM. |
Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.