[newxgate]

I just upgraded from a Basic account to Voxlite. I tried using the Web callback feature after I upgraded. It was working fine up until around 2.00 pm EST, then it suddenly stopped working, by which I mean neither number would be connected, eventually the web page returns with a message saying 'We're sorry. We are unable to complete your calls' . According to the call records log in Voxalot there is ' no answer' from the destination phone number.

I am using two VSP's with the web callback - Sipphone (Gizmo) and Inphonex. I have tried the callback using both my Dialplan and manually selecting the VSP's. Outgoing calls work fine for both VSP's when I use them via ATA (still using Voxalot as the gateway).

Not sure if it is related but I have also been unable to register either of these two VSP's with Voxalot despite the upgrade to Voxlite.

Update at 9.37 PM EST. Seems to be related to the server location - Web Callback and VSP registration works fine when I changed my preferred server from us.voxalot to au.voxalot.

FWIW here is the traceroute to us.voxalot.com at 9.45 EST :

Tracing route to us.voxalot.com [64.34.173.199]
over a maximum of 30 hops:

1 3 ms 2 ms 3 ms 192.168.2.1
2 13 ms 12 ms 12 ms 10.1.82.1
3 14 ms 12 ms 13 ms so-2-1-3-0.CORE-RTR1.RES.verizon-gni.net [130.81
.7.93]
4 14 ms 12 ms 12 ms so-6-0-0-0.RES-BB-RTR1-RE1.20.81.130.in-addr.arp
a [130.81.20.16]
5 15 ms 14 ms 15 ms 0.ge-4-2-0.BR2.IAD8.ALTER.NET [152.63.32.141]
6 18 ms 16 ms 22 ms 204.255.168.30
7 967 ms 19 ms 19 ms cr1.wswdc.ip.att.net [12.122.135.14]
8 17 ms 17 ms 17 ms gar1.ascva.ip.att.net [12.122.135.129]
9 18 ms 16 ms 20 ms 12.118.44.50
10 * * * Request timed out.
11 * * * Request timed out.
12 19 ms 17 ms 18 ms premium.voxalot.com [64.34.173.199]

Trace complete.