Service Down ?

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

[Russell]

I believe there are two separate issues here - incoming calls getting the "disconnected or not longer in service" message and ditto for outgoing calls. I was referring to the incoming calls in my posts - and that too sporadically.

[ptrowski]

I submitted the ticket this AM. While growth is very good, I hope that in the future the upgrades can be anticipated so the service will go back to the quality it was at before.

[ctaranto]

Maybe I'm finally lucky (and don't want to curse myself), but I haven't experienced any issues lately.

My intent isn't to say "ha ha", it's to express that not everyone is having issues and this may be isolated to certain regions.

I hope the upgrades this morning help those that were seeing issues.

-Craig

[slk2k]

Looks like even Tech Support is having troubles .....

While trying to call VOIPo support (as directed by support through
ny ticket), I get the famous "you have reached a call source number
that is no longer in service".

Not good. Not good at all.

[usa2k]

See your other post - looks like a fat finger error!
(Just an expression!)

[slk2k]

See your other post - looks like a fat finger error!
(Just an expression!)

I did and I didn't!!

I used the number as sent to me by tech support and didn't map it
myself!

Thanks for the help!

[oldcqr]

These sound like the issues I was having starting on 3/19. Unfortunately, support at the time continued to insist that I needed to forward nearly every port on my router to the Voipo ATA (from 5000 to 65000) for both TCP and UDP. Not that I would want to do anything else with my internet service.....

Finally I just gave up on the ticket, and things started to work again by themselves.

[VOIPoTim]

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

Failover works when you're not connected to our servers or we can't make any kind of connection. If we make the first connection but then the router blocks another part of the transaction, it fails but failover does not come on since it initially connected to you. There is no real way to modify that.

These sound like the issues I was having starting on 3/19. Unfortunately, support at the time continued to insist that I needed to forward nearly every port on my router to the Voipo ATA (from 5000 to 65000) for both TCP and UDP. Not that I would want to do anything else with my internet service.....

Finally I just gave up on the ticket, and things started to work again by themselves.

The majority of disconnect issues we see are related to routers blocking the ports which is resolved by port forwarding.

What happens a lot is that the initial connection is made to the router and then when we send the 2nd part from another IP somewhere (such as the audio), the router considers that traffic to be "unknown" and blocks it. This generates an error. So an error gets sent back to the phone carrier you are calling FROM and they play the generic error message which is disconnected.

In some cases, it's also just been latency in connections. As an example if we send a request to a customer and it takes too long to hear back and for us to relay back to the carrier you're calling from, it will trigger a failed error which causes them to play disconnected. This is why support commonly checks the ping time and connection between a customer and our network.

So far we've only seen a handful of calls that have failed due to a slow database query recently, but wanted to do these updates as a precautionary measure so that it wouldn't happen at all. So if you've seen it multiple times, that wouldn't be related. We definitely were not at a point where there was a ton of strain on the system and had to immediately upgrade...it was just a situation where we apparently had hit it a few times at peak capacity and wanted to stop it before it became an issue since hardware upgrades as easy to do.

The other thing to keep in mind is that all of these things apply upstream as well. The internet is used for the connection between US and our carriers and between the customer and us. So if there is an issue in either layer that causes something to be too slow or fail, that's another possibility.

That's why it's always important to contact support so they can look at all the scenarios and see why you had issues. We typically do use port forwarding because it is the most efficient way to address the issue and make sure the traffic gets through the router.

[ctaranto]

These sound like the issues I was having starting on 3/19. Unfortunately, support at the time continued to insist that I needed to forward nearly every port on my router to the Voipo ATA (from 5000 to 65000) for both TCP and UDP. Not that I would want to do anything else with my internet service.....

Finally I just gave up on the ticket, and things started to work again by themselves.

Both TCP and UDP? I thought VOIPo suggested that range for UDP only. At least that's what I've seen many times in these forums, and how I have my router configured.

I can't imagine forwarding all those for TCP...

-Craig