Anyone having issues Porting Out of LUMEN since mid-July? I believe the problem is that LUMEN is refusing to accept LSRs with a DDD/Requested FOC that is "too soon." "Too soon" seems to be anything short of 4 business days cannot submit the LSR at all. LUMEN used to accept shorter periods. Does it break Porting for a carrier to refuse to accept an LSR based on information it contains, rather than accepting and immediately rejecting the LSR? Beckman On Thu, 13 Aug 2026, Peter Beckman via VoiceOps wrote:
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@angryox.com https://www.angryox.com/ --------------------------------------------------------------------------- _______________________________________________ VoiceOps mailing list -- VoiceOps@voiceops.org https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/ To unsubscribe send an email to voiceops-leave@voiceops.org
--------------------------------------------------------------------------- Peter Beckman Internet Guy beckman@angryox.com https://www.angryox.com/ ---------------------------------------------------------------------------