>I do not have inside knowledge as to whether Onvoy appropriately notified
>Vonage of the port-out, ...
Ah, Vonage.
Back when they were young, they didn't plan adequately for growth so
their service was chaotic and their customer service was worse. So I
ported my number to another VoIP
The fact that Vonage hasn't disconnected the ATAs makes me feel like
their disconnect workflow hasn't quite worked, and if they have a direct
peering arrangement with AT this could be involved in that. They may
try to contact Vonage as well and ask them about it, they certainly have
Just to update everybody, I have been advised by a Vonage engineer that there
is in fact a common peering partner between them and AT that does not route
on LRN (whether using ENUM/DNS or not he didn't say). He was kind enough to
open a ticket with them on our behalf to have the TNs in
Sounds like a possible ENUM routing issue if it's bypassing the PSTN. Was
Vonage notified of the port away by Onvoy?
Regards,
Andrew Paolucci
Sent with [ProtonMail](https://protonmail.com) Secure Email.
Original Message
Subject: Re: [VoiceOps] AT / Onvoy / Vonage call
So here's a weird one: we took over a small business account from Vonage.
Vonage was using Onvoy for origination, and we elected to keep the TNs with
Onvoy (through a wholesaler). So the "port" only consisted of Onvoy repointing
traffic for those TNs internally away from Vonage and to our
