I'm not an expert in how STIR/SHAKEN is implemented in the TDM world, but I've never heard of this happening until recently. I've heard anything sent over the SS7 network has issues with the token being dropped. Maybe the problem is bigger than just the token being dropped.....maybe what they are doing is causing the called number to be dropped as well! That's the only reason I can come up with as to why one would get the LRN but not the called number. Just a thought, MARY LOU CAREY BackUP Telecom Consulting Office: 615-791-9969 Cell: 615-796-1111 On 2021-07-01 10:15 AM, Mark Timm wrote:

It?s not just T-Mobile, it?s Verizon, US Cell and Lumen originations. I believe it is traffic that Inteliquent back hauls.

[1]

Mark Timm?

Switch Engineer

Aureon

7760 Office Plaza Drive South

West Des Moines

,

IA

50266

Mark.Timm at aureon.com

515?830?0478

[2]

www.Aureon.com [2]

[3]

[4]

[5]

[6]

This message contains confidential information and is intended only for the intended recipients. If you are not an intended recipient you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.

From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Matthew Sutton Sent: Thursday, July 1, 2021 10:08 AM To: voiceops at voiceops.org 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

Links: ------ [1] https://www.aureon.com/ [2] http://www.aureon.com/ [3] https://www.facebook.com/aureon [4] https://www.youtube.com/channel/UCv6xwRKJCouZM6FPQEJ6CMA [5] https://www.twitter.com/aureon [6] https://www.linkedin.com/company/aureon _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

STIR/SHAKEN isn't implemented at all in TDM world. I've had problems on and off for years where a carrier will take SS7 traffic, send it over some janky arrangement that strips the GenericAddress parameter (where your actual destination number is hidden in the IAM - when you dip in SS7 you send the LRN as your CallingPartyNumber, set the flag indicating the call is dipped, and put the original TN in the GenericAddressParameter field) and then I get a pile of calls from specific carriers rocking into my LRN until I can get one of them to call their carrier and report the issue, which fixes it. Our usual trick is the LRNs are routed to the NOC, so they have a procedure where if they start getting calls from all over the place looking for our customers, that they ask the caller to reach out to their phone company and have them write down a little spiel to put in their trouble ticket with their carrier ("Clear Rate says they are getting the calls without the generic address parameter, which is related to failure of local number portability in your switch or tandem provider" or something to that effect), which is typically pretty effective. How often? Happens probably once a year since I set up the network in 2007 we'll have a spate of them for a day. -Paul On 7/1/21 11:42 AM, Mary Lou Carey wrote:

I'm not an expert in how STIR/SHAKEN is implemented in the TDM world, but I've never heard of this happening until recently. I've heard anything sent over the SS7 network has issues with the token being dropped. Maybe the problem is bigger than just the token being dropped.....maybe what they are doing is causing the called number to be dropped as well! That's the only reason I can come up with as to why one would get the LRN but not the called number.

Just a thought,

MARY LOU CAREY BackUP Telecom Consulting Office: 615-791-9969 Cell: 615-796-1111

On 2021-07-01 10:15 AM, Mark Timm wrote:

...

It?s not just T-Mobile, it?s Verizon, US Cell and Lumen originations.? I believe it is traffic that Inteliquent back hauls.

???????? [1]

??????? Mark Timm?

??????? Switch Engineer

??????? Aureon

7760 Office Plaza Drive South

West Des Moines

??????? ,

IA

50266

??????? Mark.Timm at aureon.com

515?830?0478

???????? [2]

??????? www.Aureon.com [2]

???????? [3]

???????? [4]

???????? [5]

???????? [6]

This message contains confidential information and is intended only for the intended recipients. If you are not an intended recipient you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.

From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Matthew Sutton Sent: Thursday, July 1, 2021 10:08 AM To: voiceops at voiceops.org 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

Links: ------ [1] https://www.aureon.com/ [2] http://www.aureon.com/ [3] https://www.facebook.com/aureon [4] https://www.youtube.com/channel/UCv6xwRKJCouZM6FPQEJ6CMA [5] https://www.twitter.com/aureon [6] https://www.linkedin.com/company/aureon _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

---

VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

-- Paul Timmins Clear Rate Communications Direct: (248) 556-4532 Customer Support: (877) 877-4799 24 Hour Repair: (866) 366-4665 Network Operations: (877) 877-1250 www.clearrate.com This message contains confidential information intended only for the use of the intended recipient(s) and may contain information that is privileged. If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, you are hereby notified that reading, disseminating or copying this message is strictly prohibited. If you have received this message by mistake, please immediately send notification by replying to the message, indicate the message was received by mistake, and then delete the original message immediately thereafter. Thank you. Clear Rate Communications, Inc. 2600 W Big Beaver, Suite 450, Troy, MI 48034.

Agreed. From: VoiceOps [mailto:voiceops-bounces at voiceops.org] 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 <jjackson at aninetworks.net> 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:voiceops-bounces at voiceops.org] On Behalf Of Matthew Sutton Sent: Thursday, July 01, 2021 10:08 AM To: voiceops at voiceops.org 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 VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops