Agreed. From: VoiceOps [mailto:[email protected]] On Behalf Of Alex Balashov Sent: Thursday, July 01, 2021 10:43 AM To: VoiceOps Subject: Re: [VoiceOps] TMobile Sending Calls to LRN not Called Number
I periodically have to explain to vendors of various things, including quite reputable vendors, that you can’t route based on the To header in any way, and the value in it matters for nothing, and it doesn’t need to align with the RURI, and in many cases won’t and shouldn’t. For some reason, the idea that the To URI has some non-cosmetic value just won’t die. I don’t know what it is. Maybe the mind just can’t get past the name and the way it intimates a destination. But, in 3261, it’s a purely cosmetic commentary on the intended logical destination. It’s a cue for humans. It means absolutely nothing else and should never, ever, ever, ever be used for routing, nor compared to the RURI in a way that has bearing on routing, nor anything else functional. — Sent from mobile, with due apologies for brevity and errors. On Jul 1, 2021, at 11:26 AM, Joseph Jackson <[email protected]> wrote: We’ve seen this on Ribbon SBCs running their 8.2.x code. If a forwarded call comes in (where the number on the RURI is not the same as the To) when the PSX does an LNP dip it will rewrite the RURI to the LRN. Which of course causes the call to fail. I have no idea if this is the same issue but we’ve been working through that issue on one of our SBCs and they said it would be resolved in the latest V08.02.06R000 release. According to Ribbon TAC this issue is also present in their V9.X train as well and will have a fix released on july 23rd. Joseph From: VoiceOps [mailto:[email protected]] On Behalf Of Matthew Sutton Sent: Thursday, July 01, 2021 10:08 AM To: [email protected] Subject: [VoiceOps] TMobile Sending Calls to LRN not Called Number Anyone else seeing calls from TMobile coming in with the LRN as the called number? The ISUP doesn't show the actual called number so we can't route the calls. -Matthew _______________________________________________ VoiceOps mailing list [email protected] https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list [email protected] https://puck.nether.net/mailman/listinfo/voiceops
