Printable View
I'm unable to get a call through to my home phone this morning. I get a recorded message "We're sorry, but all circuits are busy now. It's just a temporary condition and we hope you'll try your call again later."
I've got a second account and that number goes through ok.
Just tested mine from an outside line.. inbound call works just fine here
This has been an issue now for over an hour (at least since I first noticed it). I'm able to make inbound/outbound calls on one of my two separate residential accounts, but on the other one I can only make outbound calls. Inbound calls receive the recording "all circuits are busy."
I rebooted my Voipo device (for what that may be worth) and verified my internet connection. The device locked on in about 30 seconds. Inbound calls from my cellphone result in a fast busy signal. Still get the "all circuits busy" recording when I call from another landline.
I noticed some people having issues with the simul-ring beta option and I have it enabled on the troubled line, so I disabled it. No difference.
According to my call log, the last time a call was received on this line was 10:44pm yesterday evening. It's been 2 1/2 hours since I first encountered the problem and nothing has changed. Still can't get a call through.
A few questions:
First, I know it's a holiday weekend, but did you put in a ticket? If not, go ahead and do so.
Second, when you log into vPanel and look at the Features --> Devices command, do you see an entry for the line that's failing?
Third, have you tried (for what it's worth--possibly nothing) changing your 'preferred' server in vPanel? Features --> Preferences --> Network Preferences
That page shows which server you're connected to, which may not correlate with your 'preferred' server.
Fourth, have you tried using the SIP credentials with a softphone for the account that's not ringing in?
Fifth, have you tried intentionally taking your 'misbehaving' line down and seeing if/how the failover function works (e.g. to your cell phone)? Do you still get an 'all circuits busy' message, does it forward the call, or is there another issue? (Alternative to taking your line down, have you tried turning on call forwarding in vPanel and seeing how that behaves?)
I hate to hit you with a ton of questions, but I'm trying to think of different things to try that might point out the source of your issue...
FWIW, I'm registered to central, and I just made a successful inbound call.
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.Quote:
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.
https://secure.voipo.com/preferences/networkQuote:
Originally Posted by bwyatt
Features => Preferences => Network Preferences
VOIPo would benefit from breadcrumb links
Knowing/reviewing
Features => Preferences => Advanced
may be useful too.
You don't see it in Features/Preferences/Network Preferences? That setting does not appear for a Virtual Number assigned to a 2nd line, but it should appear for your primary line on a Residential Account.Quote:
Originally Posted by bwyatt
Im betting this is at the carrier level.
Go to https://secure.voipo.com/preferences/advanced look at audio. Select "Use VOIPo Network for Audio".