View Single Post
Unread 04-14-2009, 04:08 PM   #6
markk
Junior Member
 
Join Date: Apr 2009
Posts: 6
Thanks: 0
Thanked 0 Times in 0 Posts
markk is on a distinguished road
Default

Quote:
Originally Posted by newxgate View Post
. . .
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. . .
[/size][/font]
The us.voxalot does not work since yesterday. It is obvious that the problem is larger than people at Voxalot can handle - it is just not acceptable that there are ANY outages especially for the mainstream users that pay for the service. If the company lost grip of the situation and can not fix the problem in a timely manner it should farm out the services to someone else while it is working on finding the problem and making sure it never happens again.

There are many other companies that have the resources and can handle the traffic that Voxalot has with no problem. In a meantime they don't even have to do that - they can reroute the traffic to the other servers that work. They could experiment with shutting-off the services several years ago when the service was in beta. Even now they can experiment on the free side of the service but interrupting service to users that pay for the service is just not acceptable in 2009 especially when there is a number of simple solutions that could reroute the affected traffic to other servers that work.

All the affected users should be automatically rerouted to another server immediately every time there is a problem with a server. It is 2009 and there is just no reason to ask the users themselves to reregister with another working server. I have trouble understanding why the company would do that to any of its users but at the very least the mainstream users that pay for the service should not be subjected to any service loss while the company decides to shut the server down for any reason during the business hours. This is just stupid - you can work on the affected server as long as it takes - in this case it is hours and now days but before you are doing that you should reroute the service to another server.

Besides, it seems that the existing Voxalot business model does not work well so maybe it is time to completely rearrange the service and maybe forget about routing the voice calls at all and do something similar to SipSwitch - actually this would solve the 99.999% of the problems that Voxalot has. They do not have to change it for everybody immediately but at least allow the users that pay for the service to stay OUT of the problem-prone Voxalot servers, at least till Voxalot lot can FIND the problem and make sure it NEVER happens again.

mk
markk is offline   Reply With Quote