Vitelity inbound calling is failing
-
We have a few clients who use them and no one is having any issues.
-
Looks like inbound calls make it to the Pbx, but no audio is passing through.
-
@Minion-Queen I have 2 so far
-
What cities are they located in? Wondering if it is regional
-
Lancaster PA Area
-
We have Chicago, Birmingham, AL and LA. Nothing there (just checked in).
-
So sounds like regional. Their outage banner just says " reports of inbound calling issues ". No further info from their phone support people.
-
Looks like it is back up in this area. This brings up the topic of inbound calling failover. In this case, the call technically wasn't "failing" due to the provider not being able to connect to the PBX. The call was failing because of other issues, but not failing "enough" to be considered a failed call, where the call would failover to a backup number. So it begs the question... how is this avoidable or at the very minimum, mitigated to some degree?
-
Official response on the portal:
Monday November 21st 2016, 11:18am MST - Vitelity noticed several large loops that caused one of our inbound processing nodes to become overloaded. Vitelity worked with our vendor to block the loops and harden the routing policies to the Vitelity network. If you experience anything further open a support ticket.
-
@fuznutz04 said in Vitelity inbound calling is failing:
Looks like it is back up in this area. This brings up the topic of inbound calling failover. In this case, the call technically wasn't "failing" due to the provider not being able to connect to the PBX. The call was failing because of other issues, but not failing "enough" to be considered a failed call, where the call would failover to a backup number. So it begs the question... how is this avoidable or at the very minimum, mitigated to some degree?
This is an edge case and something you should have simply manually downed the trunk on your PBX forcing the failover to attempt to kick in.
But most likely it would have failed to resolve anything as the problem was on the inbound to Vitelity section of things. Not on Vitelity to you side.
-
@JaredBusch Good idea to manually down the trunk. However, I think you're right, Not sure if it would have done anything as the calls were coming into Vitelity but then not working 100% Such a random event.
I've had decent luck with Vitelity so far. Let's hope this is just a special case.
-
@fuznutz04 said in Vitelity inbound calling is failing:
@JaredBusch Good idea to manually down the trunk. However, I think you're right, Not sure if it would have done anything as the calls were coming into Vitelity but then not working 100% Such a random event.
I've had decent luck with Vitelity so far. Let's hope this is just a special case.
I quit using Vitelity because of these types of issues repeatedly happening a few times a year.
-
@JaredBusch said in Vitelity inbound calling is failing:
@fuznutz04 said in Vitelity inbound calling is failing:
@JaredBusch Good idea to manually down the trunk. However, I think you're right, Not sure if it would have done anything as the calls were coming into Vitelity but then not working 100% Such a random event.
I've had decent luck with Vitelity so far. Let's hope this is just a special case.
I quit using Vitelity because of these types of issues repeatedly happening a few times a year.
You typically use voip.ms right?
-
@fuznutz04 said in Vitelity inbound calling is failing:
@JaredBusch said in Vitelity inbound calling is failing:
@fuznutz04 said in Vitelity inbound calling is failing:
@JaredBusch Good idea to manually down the trunk. However, I think you're right, Not sure if it would have done anything as the calls were coming into Vitelity but then not working 100% Such a random event.
I've had decent luck with Vitelity so far. Let's hope this is just a special case.
I quit using Vitelity because of these types of issues repeatedly happening a few times a year.
You typically use voip.ms right?
Yes.
