Service Down ?

**Russell** · 03-29-2010 07:54 PM

Another issue tonight about our phone being "not in service". Phone rings a couple of times; we pick it up and hear nothing. Shortly thereafter phone rings again from same caller and all is well. The caller (our child) says she heard that our number was "not in service" the first time (I guess, while we were hearing the rings). 420208917_113882314@192.168.37.76 is the id of the questionable call.

**sr98user** · 03-30-2010 07:54 AM

Russell,

Yesterday I had couple of calls that went to voicemail after two rings. I created a ticket and they have notified the upstream carrier about this issue. Its working fine now. Voipo thinks its an issue with the upstream carrier.

Last week, a caller told me that they got the "phone not in service" message and got through the second time. I did not create a ticket for this and chalked it up to a network issue since it didn't happen again when I tested with my cell phone.

**ptrowski** · 03-30-2010 03:57 PM

Things are a bit flaky here. People have called and they said that they get a fast busy but the call routes to my cell phone. I just tried calling my brother in law who is a voipo customer and there was a substantial pause before it started ringing and went to his failover number. Calling into a conference call today there was also a very long pause before the call picked up.

**VOIPoTim** · 03-30-2010 04:08 PM

If you have issues, please submit a ticket so support can look into it.

With that said, I do think this week we may be hitting some load issues. We're doing another round of upgrades to our database cluster tonight to double capacity.

I don't know 100% that these are related, but for a few of the disconnected messages, the logs show a delay in the database query so the other carrier assumed it failed by the time it completed. So it could be related.

We didn't anticipate needing to go beyond that last upgrades, but we've grown about 10x in the last 2 months and have decided to just go ahead and double the hardware at this time.

http://forums.voipo.com/showthread.p...7825#post17825

**slk2k** · 03-30-2010 08:08 PM

I'm having similar issues as well (caller gets number is disconnected),
a few times on outbound, I get fast busy when dialing out.

I opened a TT (HBG-874105) and support is having me set up port
forwarding inside my pfsense box.

Somehow, I screwed that up (when I set the ATA to a static, it
no longer registers I can't get back into the ata - but that's a seperate
issue I hope support can help me with ... :-)

**Russell** · 03-30-2010 08:19 PM

Originally Posted by slk2k

I'm having similar issues as well (caller gets number is disconnected),
a few times on outbound, I get fast busy when dialing out.

I opened a TT (HBG-874105) and support is having me set up port
forwarding inside my pfsense box.

Somehow, I screwed that up (when I set the ATA to a static, it
no longer registers I can't get back into the ata - but that's a seperate
issue I hope support can help me with ... :-)

Do note a caller getting number is disconnected is due to issues on the VOIPo side - as Tim mentioned the database didn't respond quickly enough. Hopefully, measures being taken will improve things. I really like VOIPo and am hoping the various sever side issues get resolved and we don't have the experience of my former company after the SunRocket closure. Tim's honesty about the cause of the issue in this case is appreciated - I appreciate less "network glitch" reasons :-).

Tim, hopefully, we shouldn't have to report these number not in service issues. I'd like to imagine that reports can be run on your side to filter and determine the cause of such failed calls without us opening tickets.

**slk2k** · 03-30-2010 08:52 PM

Originally Posted by Russell

Do note a caller getting number is disconnected is due to issues on the VOIPo side - as Tim mentioned the database didn't respond quickly enough. Hopefully, measures being taken will improve things. I really like VOIPo and am hoping the various sever side issues get resolved and we don't have the experience of my former company after the SunRocket closure. Tim's honesty about the cause of the issue in this case is appreciated - I appreciate less "network glitch" reasons :-).

Tim, hopefully, we shouldn't have to report these number not in service issues. I'd like to imagine that reports can be run on your side to filter and determine the cause of such failed calls without us opening tickets.

I do realize that the "number is disconnected" issue may very well be a voipo-sided problem, but I was trying to follow the golden rule of "let support know about it". It it wasn't for my own idiocy (must of set the GW or DNS IP wrong), I would most likely still be on line....

**VOIPoTim** · 03-30-2010 08:59 PM

It's still important to contact support because it may not be related.

The vast majority of the cases we see with it are when port forwarding is not set.

It could be a variety of things.

**slk2k** · 03-30-2010 09:02 PM

And that's why I contacted support!!

I do want to say "Thank You" for being so personally involved in your business!

**Russell** · 03-31-2010 05:21 AM

Originally Posted by VOIPoTim

It's still important to contact support because it may not be related.

The vast majority of the cases we see with it are when port forwarding is not set.

It could be a variety of things.

Tim are you saying that the in the vast majority of the cases of the "number disconected or not in service", the issues are port forwarding? If yes, I'm very curious as to why the system doesn't either use the fallback number or voicemail instead of generating "number disconected or not in service".