[VoiceOps] Trouble completing calls to Alliance Connect

[Pete E]

We were experiencing similar issues with long PDD but not limited to
Alliance Connect. We just found out that Level3 has "lost all their routes"
to Verizon (whatever that means) and that has been the source of the
problem. We hadn't been able to nail it down to any one carrier because we
were seeing it from other outbound routes as well, but that was generally
the smaller guys who also use Level3 in their routes, so chances are it is
all related. If we terminate the same call directly to Verizon it goes
through, no issues.

Anyone seeing similar?

On Wed, Sep 24, 2014 at 1:05 AM, Frank Bulk <frnkblk at iname.com> wrote:

> I do – I will reach out to them.
>
>
>
> Frank
>
>
>
> *From:* VoiceOps [mailto:voiceops-bounces at voiceops.org] *On Behalf Of *Jared
> Geiger
> *Sent:* Tuesday, September 23, 2014 1:26 PM
> *To:* VoiceOps
> *Subject:* [VoiceOps] Trouble completing calls to Alliance Connect
>
>
>
> Out of the 14 routes I have to connect to LRN 13196717000 Alliance
> Connect, only one route works. I've opened trouble tickets and haven't
> gotten anywhere with vendors. I get very long PDD and then the call fails
> on all routes. Carriers tested included Intelepeer, Bandwidth.com, O1,
> Verizon, Onvoy legacy, Onvoy 360 Networks, Global Crossing legacy,
> Peerless, Hypercube, and more.
>
>
>
> If anyone has a contact for this company that can look into this issue,
> please contact me off list.
>
>
>
> Regards,
>
> Jared Geiger
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20140925/c9f7b068/attachment.html>