August 2026 - VoiceOps - lists.voiceops.org

Spectrum\Charter
by Mike Hammett Aug. 19, 2026

Aug. 19, 2026

We're trying to make sure that our TPP information is current with each carrier we work with. My people aren't hearing back from anyone at Spectrum\Charter. Do any of you have a contact there? They tried every contact in NPAC and haven't gotten anywhere. --Mike ----- Mike Hammett Fiber Data Internet Exchange DNA Communications

1 0

Has anyone tested VoxyWatch?
by Moisés Amiga Aug. 18, 2026

Aug. 18, 2026

Hi everyone, We are currently testing VoxyWatch in a lab environment and would like to know if anyone here has previous experience using or evaluating it. I am particularly interested in feedback regarding HEP/SIPREC capture, audio reconstruction, resource usage under load, and how it compares in practice to tools like HOMER or VoIPmonitor. If you have worked with it, did you encounter any limitations, installation issues, or operational concerns? Full disclosure: I have been involved with the project, so I am specifically looking for independent, critical technical feedback rather than endorsements. Thanks, Moy -- *AVISO DE CONFIDENCIALIDAD*: Este mensaje y los archivos adjuntos contienen Información Privilegiada y Confidencial. Cualquier divulgación, diseminación, distribución o copia está estrictamente prohibida. Si usted no es el destinatario, bórrelo y destrúyalo en su totalidad y notifique de ello al remitente. *CONFIDENTIALITY NOTICE*: This message and the files attached herewith contain Privileged and Confidential Information. Any unauthorized disclosure; dissemination; distribution or copying is strictly prohibited. If you are not the intended recipient, delete and destroy it in its entirety and immediately notify the sender.

1 0

Skyetel experiences as a SIP provider?
by Carlos Alvarez Aug. 18, 2026

Aug. 18, 2026

We are considering moving from a combination of Bandwidth and Commio to them. $1400/mo, 100k minutes, 2k DID, simple stuff. The friction with BW goes up every single day, and is only getting worse. Our contact there is Paul Laregina, who we did business with long ago with another company. At that time, he was straight shooting, delivered 100% as promised. Comments on list or direct are appreciated.

1 0

US Porting Out of LUMEN to an MVNO: Problematic
by Peter Beckman Aug. 18, 2026

Aug. 18, 2026

I've just spent the last several days, maybe even a week now, on an issue where multiple end users want to Port a number from LUMEN to an MVNO wireless carrier. I'd love to hear thoughts on this. Short Version: T-Mobile is fake Rejecting Port Out Requests made to LUMEN because LUMEN won't accept an LSR with a DDD they find "too soon," and creates a complete lack of accoutability and logging. Long Version: BACKGROUND * LUMEN made a new Port Out Tool and made everyone move to it in mid-to-late July 2026 * This Tool refuses to accept your LSR / Port Out Request unless you select a valid DDD (Desired Due Date, or Requested FOC). * MVNOs cannot (or might not) see this information prior to submitting the Port Request PROBLEM * MVNO Tello Mobile uses T-Mobile * Tello Mobile sends ALL Port Requests to T-Mobile, with a DDD * T-Mobile attempts to submit an LSR to LUMEN * LUMEN does not offer the DDD selected, but T-Mobile cannot actually submit the LSR to LUMEN, so LUMEN has no record of the attempt * T-Mobile is forced to fake a "Rejection" for the Port Out Request to Tello Mobile. LUMEN didn't reject it, T-Mobile did * Tello Mobile tells the customer that their request was Rejected and to contact the losing carrier * They contact us, we talk to LUMEN, LUMEN has no record of any rejection POTENTIAL FIXES The RIGHT FIX IMHO * LUMEN accepts LSRs even with a DDD they might know they won't allow, but the Rejection then comes *FROM LUMEN* and they have a record of their rejection. Plus it is standardized A Hack to avoid frustration * Tello Mobile sees the rejection for DDD, resubmits immediately with an updated DDD, which T-Mobile seems to helpfully provide DISCUSSION I don't think that a valid LSR should be prevented from being created, as it creates an audit trail, and since I have the relationship with the CLEC holding the DID, I can resolve any issues with them, AND get a clear answer for why an LSR was rejected. By refusing to accept an LSR with a "too soon" DDD, my CLEC has no logging and thus no idea that a Port Request was even submitted, and now a Rejection occurs, but that Rejection was sent by an Entity that I do not have a relationship with, and so I have to rely on the Winning Carrier, and their willingness to communicate with me, to try to get a clear answer. Beckman --------------------------------------------------------------------------- Peter Beckman Internet Guy beckman(a)angryox.com https://www.angryox.com/ ---------------------------------------------------------------------------

1 1