Voxox as a carrier... ISSUES, can anyone relate?

[udfxrookie]

Ok, I've used this company for over two years and honestly have the same problem ALL THE TIME.
This issue is yet to be resolved and I am told that we double dial numbers immediately or call the same number twice at the same time, etc...
I've heard everything from them...

Code: Select all

You should never send duplicate INVITE.

RFC permits you to resend an INVITE that does not receive a timely reply (100 Trying), but this is not the same as immediately sending two INVITE 0.1 second apart.
This behavior might be the consequence of an improperly configured "SIP Retry Timer" or similar feature, or some network element might be literally sending a duplicate packet.
If two legitimately unique calls are being placed to the same destination, they should have unique "Call-ID" values; your duplicate INVITE are identical.
This is a vitally important change to your configuration - Voxox is currently investigating an issue with our server at 69.26.183.204. For the time being, please retest using two or more of the other servers below (as described in the next point), and either remove 69.26.183.204 from routing or give it the lowest priority. We have observed measurable improvement in customer traffic once moved away from this server.

LAX

69.26.183.204 - remove or demote
69.26.183.207
69.26.183.217

NYC

207.238.191.233
207.238.191.252

You should treat a rejection from one of our servers as final, and not immediately resend that call to any other Voxox IP nor immediately resend from another one of your IP.

Here is the full explanation:
Under normal conditions, we expect you to load-balance your calls between two or more of our IP addresses. In an unlikely case that one of these IPs is down, all calls will be processed by the IPs that remains in-service. You may detect such an event by pinging each IP with “SIP OPTIONS Polling”, rather than waiting for one or more INVITE to time out. This will save you PDD and unnecessary signaling during a Voxox incident.
In case you cannot use OPTIONS Polling to determine the state of our IPs, please avoid trying calls twice based on cause-code. For example, do not immediately retry on an alternate IP if you receive from us "503 Service Unavailable", "486 Busy Here" or "404 Not Found".
Please avoid unnecessary signaling and treat all rejection codes as being final: do not retry such calls to another Voxox IP address, or from another one of yours, if the first Voxox IP rejected the call. Please only retry calls on another IP if the first IP you attempted is down (as determined by OPTIONS Polling or INVITE timeout).
Redials to the same number should be spaced at least one minute apart.
Excessive redialing may result in automatic blocks for a variety of reasons, including downstream carriers that specifically react to dialer traffic patterns. This downstream blocking will happen without our knowledge. Care should be taken regarding your caller identification and how destinations are selected.
In the case that multiple sites are sharing identical lists, please ensure these lists are not executed simultaneously in identical order. In this case it may help to have those servers aware of each other or otherwise manage your call lists to ensure they are not overlapping called numbers.

and then one day they told me what I believe to be the absolute truth:

Code: Select all

It looks like their ASR is at about 36% with a FSR of 3% within the last hour on 1646 calls which is very high for our standard dialer routes. What I am going to do is move them to the premium routes for now and at the end of the week we will reach out to you to see how you would like to proceed from there. That should increase the ASR. If your server is going to use low call volume for higher quality calls and times such as sales calls or support calls, you may need a Conversational trunk instead of dialer for reliable functionality. I do not know the differences in costs or what your plans for the route is in the future but those are much higher quality calls. This would be easy to add to your account but obviously sales or your account manager here would have more info.

Has anyone had success with this carrier? Rates are low: $0.0089 and they offer billing, Net10/Net15 which is why we stick by them honestly... the post billing vs pre billing.
If anyone has experience, negative or positive please share.
If anyone has a carrier that allows post billing and a great rate with no connectivity issues, and works with call centers, PLEASE SHARE =)
Even if they need to build trust and have pre-pay happen for a bit prior to post billing, thats fine.

[udfxrookie]

Here's the kind of issues I face. TONS of congestion:

Code: Select all

[Sep 23 10:35:26] -- Executing [58600055@default:1] MeetMe("Local/58600055@default-0000088f;2", "8600055,Fmq") in new stack
[Sep 23 10:35:26] > Channel Local/58600055@default-0000088f;1 was answered.
[Sep 23 10:35:26] -- Executing [8309@default:1] Answer("Local/58600055@default-0000088f;1", "") in new stack
[Sep 23 10:35:26] -- AMD: Channel [SIP/voxox_nyc2-000007a7]. Changed state to STATE_IN_SILENCE
[Sep 23 10:35:26] -- Executing [8309@default:2] Monitor("Local/58600055@default-0000088f;1", "wav,20140923-103525_5855910060_1000") in new stack
[Sep 23 10:35:26] -- Executing [8309@default:3] Wait("Local/58600055@default-0000088f;1", "3600") in new stack
[Sep 23 10:35:26] -- <SIP/voxox_nyc2-000007af>AGI Script agi-VDAD_ALL_outbound.agi completed, returning 0
[Sep 23 10:35:26] -- Executing [010*010*010*183*8600054@default:1] Goto("SIP/voxox_nyc2-000007af", "default,8600054,1") in new stack
[Sep 23 10:35:26] -- Goto (default,8600054,1)
[Sep 23 10:35:26] -- Executing [8600054@default:1] MeetMe("SIP/voxox_nyc2-000007af", "8600054,F") in new stack
[Sep 23 10:35:26] -- SIP/voxox_nyc2-000007b9 is making progress passing it to Local/815185551212@default-0000088d;2
[Sep 23 10:35:27] -- Got SIP response 503 "Service Unavailable" back from 207.238.191.252:5060
[Sep 23 10:35:27] -- SIP/voxox_nyc2-000007b8 is circuit-busy
[Sep 23 10:35:27] == Everyone is busy/congested at this time (1:0/1/0)

[geoff3dmg]

I'm confused why you would bother tolerating such a rubbish service from a VoIP provider when there are so many others to choose from? At a minimum I have a second carrier just as a backup. It very easy to blame the carrier when you have a second trunk with another provider that works perfectly.

[udfxrookie]

Bahhahahahaha, my solution to the problem as well.
But the company I provided Voxox to likes their support (even though all they do is blow smoke up our butts).
So I wanted to see if others have had this experience with this specific carrier, or has had a good experience...
And if they are new to VoxOx hopefully they are now LOOKING at their traffic =)


Any specific carriers that have good pricing and routes you would point me to? =)
Think I'm going to do just what you said, get a second prove quality.

[perci100]

I am running into the same issue now with Voip innovations. I love the interface and the control they provide and the price. However this past month they hit me for charges because calls are failing to 800 numbers. The funny thing is , its because they are not routing them. My congestion/channelunavail is almost 10% at times. I am having trouble getting through to commercial banks and businesses for verification purposes and its killing us. I have a couple of backups that work. I am finding out Its definitely a chore to find a reliable carrier. I haven't been able to get failover working as of yet. I need a better understanding of dialplan functions.

give flowroute a try , they seem to be ok when i need a backup. Sometimes its just a matter of it being a different company with different routes.

[udfxrookie]

Flowroute connected almost all of our calls, however they will not work with call center traffic without MAD fines and penalties.
They tell you up front they do work with call centers, and will ensure no penalties as they will get you to the correct ASR%,etc
We do two types of campaigns.... Energy Deregulation and Alarms... in both we were so far away from the ASR it would be impossible not to have to pay the penalties... although they continue to try and reach out lol

Have tried Alcazar in the days, not sure why I switched so I will be reaching out to them.
Also trying to speak with Star Telecom.

If anyone has experience with those two, insight would be awesome, else I will post my findings

[udfxrookie]

So posted the problem to Voxox and 2-3 hours later finally get a response, here's their quality response:

I would like to work with you in narrowing down this issue. I'll give you a call at XXX-XXX-XXXX to discuss the issues you are having, gather information needed and, if needed, consult with my tier 2 department for assistance.

Thanks,

Warren

They must've missed the 50 other tickets with the same unresolved problem, that ALWAYS gets escalated to a Tier 2 technician... ohh they must've also missed the packet captures of the same exact problem they never fixed that I have done for them three times.

[perci100]

Learned about the fees the hard way shortly after this post actually. Voipinnovations went down at 8am of course and i had to switch over to flowroute. I thought it would be ok for a day. Expensive mistake. but they do get everything through. Let me know if you find anyone that's reliable with a <3 for dialer traffic. I was thinking of trying voxox but i think maybe not now haha.