First the good news:
Incoming calls were connecting once again as of 2:39pm this afternoon.
As a troubleshooting note:
I had not changed any settings in VPanel immediately prior to the problem occurring, nor were there any changes made in VPanel just prior to service being restored.
A google search on this issue made it obvious to me this is not too unusual for VOIP customers. One technician made this point:
I have no idea whether this is accurate or not, but it could mean that Voipo is experiencing growing pains? Then again it was suggested that this happens sometimes when there is a fiber cut somewhere or something... or sometimes there is just an unusual demand in a certain area. It was suggested the latter problem usually remedies itself in minutes, not hours as this case was.When you get this type of message it usually means that the server/network segment is overloaded because there are too many people utilizing that server/network segment. This type of problem means that the XXXX/YMAX need to load balance the workload by adding more servers or re-sizing their server/network.
So in the future if you get this type of message --- you will have to try your call later. Since XXXXXX is growing by leaps and bounds it will take time for them to properly configure their network/servers for the number of users that are utilizing the system.
fisamo - Thanks for your suggestions! In response:
1) Yes, I submitted a ticket.
2) There was no entry for failure in devices command.
3) I don't have a "network preferences" tab in my VOIP panel. Is this something available to some Voipo customers and not others?
4) Service was restored before I got to try out the softphone option, but that was going to be my next step.
5) Didn't get a chance to try this one either, but I don't think it would have worked because the call was not registering with Voipo. There was no record of any of the inbound calls during the recorded message period in the call log of my Vpanel.
What made this problem more perplexing for me was having two residential accounts; one line worked fine with inbound and outbound calls, while the other line had the recording.
Bookmarks