Service Down ?

[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 ... :-)

[Russell]

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]

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]

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]

And that's why I contacted support!!

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

[Russell]

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".

[bakntime]

I've already submitted a ticket, but I just thought I'd post this here in case someone else has a similar issue or can help.

When I call my friend's cell phone, I hear a couple rings, then a "this number is no longer in service or is disconnected" recording. She does not hear any rings on her end. If I call her cell from a landline/POTS, the call goes through fine. I can call several other phone numbers with VOIPo and there are no issues, so it's just this particular number that's an issue (though I suspect there are other numbers out there that would have the same issue).