Web Call Back Down?
 

Is Web call Back Down This Evening?

I was using it earlier this afternoon OK, but as of now, 9.08pm Sydney time, the first "leg" never happens...

Anyone else confirm?

StephenH

I've been seeing the same thing for the past several hours. I'm also unable to call 500 (Voicemail) and 600 (Echo) -- they both get 'All circuits are busy'. All other features I've tried are still working normally.

I'm sure Martin will see this shortly and look into it for us.

Ron

Same here; unable to make any calls through VoXaLot. I just get busy tone.

Same here also. Registered alright but cannot dial out.

I think a fix could be in progress; I just received a web call-back that I tried a while ago.

Edit: Yep - just made an outgoing call ok :)

Thanks to whoever - Martin? ;)

Should be ok now. Our asterisk daemon needed a re-start

Thanks Martin!

Hooray Martin! Bad demons eh? :D

Martin,

As noted by others, Web Callback, Voicemail (500), and Echo (600) are now working again, but all incoming calls to my VoXaLot number are now going straight to voicemal. This started the instant the aforementioned items came back to life. Outgoing calls are fine.

Ron

Hi Ron,

Just called one of our inbounds ok. PM me your 6 digit number and I will test from here.

Actually, I've still got a problem Martin. Incoming calls to my Voxalot number terminate fine. However, if I use Web call back, with my Voxalot number as the terminating leg, it is going straight to voicemail.

Any ideas? Thanks.

I've just found what the problem was so thought I'd post in case anyone has any similar problems.

I've got a BudgeTone HT-488 ATA (registered to Voxalot), connected to my NTL PSTN line as well the router connection. My analogue phone is a DBtel DB3 DECT phone.

All outgoing calls were working fine; both PSTN and VoIP. Incoming PSTN calls worked fine. Incoming VoIP calls from PSTN via SipBroker PSTN access number worked fine. However, incoming VoIP calls initiated by Voxalot Web Callback, either directly from Voxalot or via SipBroker (*010....) weren't causing the DECT phone to ring. It was however, causing the ATA indicator to flash, indicating an incoming call. Nothing was being shown on the phone's display until a key was pressed; it was only then that I noticed the words "Call Bar" on the display.

After digging out the manual, I found that the phone supports the barring of up to five numbers. Currently the five entries on the phone are blank. I did another test call from PSTN via SipBroker except this time, witholding my CLI. This time, the phone didn't ring; it behaved exactly the same as the incoming Voxalot initiated call.

I changed the blank entries on the phone to some dummy numbers, retried the Voxalot initiated calls (as well as CLI witheld PSTN via SipBroker call) and everything now worked fine :)

I'm guessing that their must be a 'bug' with the DB3 that if a number is witheld/unavailable, it doesn't ring if any of the 5 entries for barred callers is left blank. I've never come across the problem before, because NTL don't have a Caller ID service in this area.

Anyway, that's a load of my chest! Normal service has been resumed. I'm really liking the Voxalot service, especially now I can phone South Africa for less than 1p/min and more to the point, using Web Callback, they can get the same rate back to me :)

Just now looking for the cherry on the cake; routing of one my SIP providers DID numbers to my Voxalot registered ATA, or even Voxalot providing a UK DID number :)

Keep up the great work guys.