Failed Calls
 

Ok, tonight I have gotten a bunch of calls on my phone where no voice seems to go through. I called from my cellphone and I could get one way sound. The problem is though that none of these semi-failed calls doesn't even show in the call log. It's actually not the first time it has happened - it has happened regularly through the years. Normally, I have just rebooted my device to force it to re-register, and that mostly works. But since I don't even see the calls in the log I suspect this to be a voxalot issue.

We are currently investigating a problem with proxy01.us1.voxalot.com. In the mean time, you should point your device to proxy02.us1.voxalot.com

I will keep you updated.

I currently have 5 SIP registered providers on us.voxalot.com server ( I assume it is proxy01.us1.voxalot.com). None of them can SIP register at this time, all I get is a busy tone but they are showing as Registered on the Voice Service Providers page.

I suspect the problem is that you are unable to register to Voxalot. That would be consistent with my experience today.

us.voxalot.com seems to be pointing at proxy02.us1.voxalot.com, which responds to pings whereas proxy01 does not. Regardless, I am unable to register.

I am in Sydney, but have been registering to the us servers in recent months, because of the unreliability of the au server. However, I've moved one of my accounts back to the au server, where it now registers.

As a stop gap, you might want to use either the au or the eu server, otherwise, going by recent experience, you might have to wait a day or more for things to be fixed. You would need to substitute au (or eu) for us in your ATA setup, and make a similar change in your Voxalot account settings (this also requires de-registering all your VSPs first, and re-registering them afterwards).

Seems the issues are gone, but I still wonder why call records never seem recorded when these things fail? Shouldn't it be logged as a failed call at least?

I still can't SIP connect or register my VSPs and there isn't an option for proxy02.us1.voxalot.com on the main page.

Same problem here.

No incoming calls to providers registered with us.voxalot.com though they appear as "registered".

Webcall does not work either.

Voxalot, please wake up !

I've been having issues since last night of not receiving calls from Messagenet - Fax VoIP SMS even though it says it was registered. After being frustrated I figured I'd try switching servers from us...to "eu.voxalot.com" and all is back to normal.

I read the forums on what to check before thinking there may be a server issue and am posting my results for the us.voxalot.com server.

http://forum.voxalot.com/voxalot-sup...eing-down.html

>tracert us.voxalot.com

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

1 1 ms 1 ms 1 ms Tomato.comcast.net [192.168.1.1]
2 11 ms 7 ms 15 ms 96.129.8.1
3 68 ms 10 ms 10 ms ge-5-39-ur01.lowell.ma.boston.comcast.net [68.85
.161.105]
4 11 ms 20 ms 11 ms be-21-ar01.needham.ma.boston.comcast.net [68.87.
144.157]
5 23 ms 16 ms 17 ms pos-2-2-0-0-cr01.newyork.ny.ibone.comcast.net [6
8.86.93.185]
6 18 ms 16 ms 17 ms xe-10-3-0.edge1.NewYork2.Level3.net [4.71.184.1]

7 17 ms 16 ms 18 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
8 21 ms 26 ms 23 ms ae-3-3.ebr2.Washington1.Level3.net [4.69.132.89]

9 30 ms 41 ms 32 ms ae-72-72.csw2.Washington1.Level3.net [4.69.134.1
50]
10 24 ms 23 ms 32 ms ae-2-79.edge2.Washington3.Level3.net [4.68.17.76
]
11 26 ms 23 ms 25 ms PEER-1-NETW.edge2.Washington3.Level3.net [4.71.2
34.6]
12 * * * Request timed out.
13 * * * Request timed out.
14 * 34 ms 25 ms proxy02.us1.voxalot.com [64.34.173.199]
Trace complete.

same here.

phone from caller is dailing; but at the other side (incomming call) the phone does not ring.

voxalot support????

It's the weekend, maybe on Monday the problem will be resolved.