Todays Problems

martin · 03-05-2009, 12:06 PM

Hi,

We have noticed quite a lot of problems reported today. We are still trawling through the logs to understand the root cause.

We have just sanity checked the servers and on our side things are looking OK at the moment. Are people still having problems right now?

If so, please provide details.

Thanks

g00fy · 03-05-2009, 12:26 PM

It seems it always OK from your side, but there are still problems very frequently and it takes too long time before they are solved! Not only these problems, but also individual ones. I wish to remember you I have still a case open for more than a month (started much earlier) and that is not solved also.
Search the forum for much more of these cases.

Why is this lack of customer support and communications. I think we deserve these as a premium member (for sure the communications should be much much better!).

kendid · 03-05-2009, 01:12 PM

Looks like everything is working again... YAY!

I noticed it first thing this AM (5:00 GMT) -- tried to make a call on the US servers. Nothing but dead air. Switched to EU server, nothing again. Tried calling voicemail and echo test but same dead air.

WHen doing test numbers on the dial plans, we found out the numbers that weren't working on our ATA devices, also did not work on the dial plan test applet (it just hung).

Hope that helps you identify the source of your problem!

Good luck...

JerryT · 03-05-2009, 01:41 PM

This one is weird.

All our outgoing calls go through Voxalot, almost all then via Pennytel. At about 2205 Sydney time, a friend called to say she'd had a call from us (we came up on the caller ID). I guess the call was silent. We hadn't called. I found a record of the call at 2159 Sydney time in the Voxalot and Pennytel logs, but not in the call log of our Billion 6404VGP, although an earlier call to a different number was in the log.

Only our Billion uses that Voxalot account.

My wife had called the same friend about nine hours earlier. The only explanation I can see is that Voxalot spontanaeously repeated that call.

carlosalbffgomes · 03-05-2009, 01:58 PM

Now I'm working with the EU Server. However, my voip user account still appears as being registered at the US Server. But apparently it works and calls tens to pass through to my IP phone (not always, but usually).
It seems to me that was some kind of problem with one of the US Server (IP 64.34.173.199) and this one was the server I was registered until some hours ago. Registration was taking some more delay and the phone was not allways registered.
Regards,

hayim · 03-05-2009, 03:13 PM

Had same problem today: voxalot wasnt placing calls through the dial plans but was registering and SIP calls worked.

All seems well now.

ladude626 · 03-05-2009, 06:41 PM

Quote:

Originally Posted by hayim

Had same problem today: voxalot wasnt placing calls through the dial plans but was registering and SIP calls worked.

All seems well now.

The problem seemed to be with the dialplan timing out (or related to). If I dialed a number that was set to go to through one of my VSP then the call wouldn'y work. If the number was to be dialed by Sip Broker (set in my dialplan) then the calls went through.

martin · 03-05-2009, 08:12 PM

After many hours of log file analysis we believe we have found the root cause of todays outage.

At 02:03:34 5th March GMT a huge amount of SIP traffic began hitting our core telephony engine. This traffic was clearly a DOS attack on our system, and lasted for approx 4 hours.

The source of the attack was from a number of different data centres around the world and until we complete our investigation, all IP traffic from those data centres have now been blocked until further notice.

We sincerely apologise for todays disruption and will provide additional updates as more information becomes available.

Thanks

travisnj · 04-12-2009, 02:22 PM

Tried, US. AU. EU all and get dead air, delays... Totally down.

Sent to udp:64.34.173.199:5060 at 12/04/2009 09:24:41 (914 bytes)

INVITE sip:18005551212@us.voxalot.com SIP/2.0
Via: SIP/2.0/UDP 65.26.136.110:42376;rport;branch=z9hG4bKhfnir4na8q o3gyfx6ra.g2yvq7voylx
Max-Forwards: 70
From: "XXXXXX" <sip:XXXXXX@us.voxalot.com>;tag=gh15elrl
To: <sip:18005551212@us.voxalot.com>
Call-ID: krx1914j@us.voxalot.com
CSeq: 26046 INVITE
Contact: <sip:XXXXXX@65.26.136.110:42376>
Allow: INVITE, CANCEL, BYE, ACK, REGISTER, OPTIONS, REFER, SUBSCRIBE, NOTIFY, MESSAGE, INFO, PRACK
Content-Disposition: session
Supported: replaces
User-Agent: snom-m3-SIP/01.22 (MAC=0004132A2278; HW=1)
Content-Type: application/sdp
Content-Length: 294

v=0
o=XXXXXX 490201879 490201879 IN IP4 65.26.136.110
s=-
c=IN IP4 65.26.136.110
t=0 0
a=sendrecv
m=audio 44484 RTP/AVP 18 0 8 97
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:97 iLBC/8000
a=fmtp:97 mode=20
a=sendrecv
a=rtcp:44485

I will dial a number; dead air and silence. I am on Road Runner.

I have family using voxalot on COX, they have SAME issue. No calls in or out. Via IP direct or VSP's.

satghost · 04-12-2009, 02:44 PM

i have tried all voxalot server ..... could not make any call or receive any call.
what is happening with voxalot ?

03-05-2009, 12:06 PM	#1
martin Join Date: Feb 2006 Posts: 2,930 Thanks: 528 Thanked 646 Times in 340 Posts	Todays Problems Hi, We have noticed quite a lot of problems reported today. We are still trawling through the logs to understand the root cause. We have just sanity checked the servers and on our side things are looking OK at the moment. Are people still having problems right now? If so, please provide details. Thanks __________________ Martin Please post support questions on the forum. Do not send PMs unless requested.

03-05-2009, 01:58 PM	#5
carlosalbffgomes Senior Member Join Date: May 2008 Location: Portugal and Brazil Posts: 107 Thanks: 7 Thanked 26 Times in 21 Posts	Voip User account still registered with US Server IP Now I'm working with the EU Server. However, my voip user account still appears as being registered at the US Server. But apparently it works and calls tens to pass through to my IP phone (not always, but usually). It seems to me that was some kind of problem with one of the US Server (IP 64.34.173.199) and this one was the server I was registered until some hours ago. Registration was taking some more delay and the phone was not allways registered. Regards,

03-05-2009, 08:12 PM	#8
martin Join Date: Feb 2006 Posts: 2,930 Thanks: 528 Thanked 646 Times in 340 Posts	Root Cause After many hours of log file analysis we believe we have found the root cause of todays outage. At 02:03:34 5th March GMT a huge amount of SIP traffic began hitting our core telephony engine. This traffic was clearly a DOS attack on our system, and lasted for approx 4 hours. The source of the attack was from a number of different data centres around the world and until we complete our investigation, all IP traffic from those data centres have now been blocked until further notice. We sincerely apologise for todays disruption and will provide additional updates as more information becomes available. Thanks __________________ Martin Please post support questions on the forum. Do not send PMs unless requested.

04-12-2009, 02:22 PM	#9
travisnj Junior Member Join Date: Feb 2008 Posts: 4 Thanks: 2 Thanked 0 Times in 0 Posts	Down Tried, US. AU. EU all and get dead air, delays... Totally down. Sent to udp:64.34.173.199:5060 at 12/04/2009 09:24:41 (914 bytes) INVITE sip:18005551212@us.voxalot.com SIP/2.0 Via: SIP/2.0/UDP 65.26.136.110:42376;rport;branch=z9hG4bKhfnir4na8q o3gyfx6ra.g2yvq7voylx Max-Forwards: 70 From: "XXXXXX" <sip:XXXXXX@us.voxalot.com>;tag=gh15elrl To: <sip:18005551212@us.voxalot.com> Call-ID: krx1914j@us.voxalot.com CSeq: 26046 INVITE Contact: <sip:XXXXXX@65.26.136.110:42376> Allow: INVITE, CANCEL, BYE, ACK, REGISTER, OPTIONS, REFER, SUBSCRIBE, NOTIFY, MESSAGE, INFO, PRACK Content-Disposition: session Supported: replaces User-Agent: snom-m3-SIP/01.22 (MAC=0004132A2278; HW=1) Content-Type: application/sdp Content-Length: 294 v=0 o=XXXXXX 490201879 490201879 IN IP4 65.26.136.110 s=- c=IN IP4 65.26.136.110 t=0 0 a=sendrecv m=audio 44484 RTP/AVP 18 0 8 97 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=yes a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:97 iLBC/8000 a=fmtp:97 mode=20 a=sendrecv a=rtcp:44485 I will dial a number; dead air and silence. I am on Road Runner. I have family using voxalot on COX, they have SAME issue. No calls in or out. Via IP direct or VSP's. Last edited by travisnj; 04-12-2009 at 02:29 PM.

04-12-2009, 02:44 PM	#10
satghost Junior Member Join Date: Mar 2009 Posts: 6 Thanks: 0 Thanked 0 Times in 0 Posts	All voxalot Server Down i have tried all voxalot server ..... could not make any call or receive any call. what is happening with voxalot ?

03-05-2009, 12:26 PM	#2
g00fy Member Join Date: Dec 2008 Posts: 91 Thanks: 7 Thanked 7 Times in 6 Posts	It seems it always OK from your side, but there are still problems very frequently and it takes too long time before they are solved! Not only these problems, but also individual ones. I wish to remember you I have still a case open for more than a month (started much earlier) and that is not solved also. Search the forum for much more of these cases. Why is this lack of customer support and communications. I think we deserve these as a premium member (for sure the communications should be much much better!).

03-05-2009, 01:12 PM	#3
kendid Member Join Date: Aug 2006 Location: UA Posts: 72 Thanks: 6 Thanked 3 Times in 3 Posts	Looks like everything is working again... YAY! I noticed it first thing this AM (5:00 GMT) -- tried to make a call on the US servers. Nothing but dead air. Switched to EU server, nothing again. Tried calling voicemail and echo test but same dead air. WHen doing test numbers on the dial plans, we found out the numbers that weren't working on our ATA devices, also did not work on the dial plan test applet (it just hung). Hope that helps you identify the source of your problem! Good luck...

03-05-2009, 01:41 PM	#4
JerryT Junior Member Join Date: Mar 2009 Location: Sydney Posts: 5 Thanks: 0 Thanked 0 Times in 0 Posts	This one is weird. All our outgoing calls go through Voxalot, almost all then via Pennytel. At about 2205 Sydney time, a friend called to say she'd had a call from us (we came up on the caller ID). I guess the call was silent. We hadn't called. I found a record of the call at 2159 Sydney time in the Voxalot and Pennytel logs, but not in the call log of our Billion 6404VGP, although an earlier call to a different number was in the log. Only our Billion uses that Voxalot account. My wife had called the same friend about nine hours earlier. The only explanation I can see is that Voxalot spontanaeously repeated that call.

03-05-2009, 03:13 PM	#6
hayim Junior Member Join Date: Dec 2008 Posts: 9 Thanks: 1 Thanked 0 Times in 0 Posts	Had same problem today: voxalot wasnt placing calls through the dial plans but was registering and SIP calls worked. All seems well now.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Dial plan and various problems	800793	Voxalot Support	6	11-19-2007 01:05 PM
Regitration problems	aleisorek	Voxalot Support	1	08-07-2007 01:29 PM
Dial plan problems with FaktorTel and VoXaLoT	Hally	Voxalot Support	1	01-06-2007 09:21 AM
Problems wit Voxalot this morning.	newbie_mt	Voxalot Support	2	12-01-2006 06:19 PM
Voxalot introducing Problems?	pmerrill	Voxalot Support	27	07-22-2006 05:32 PM