<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">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. <div><br></div><div>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.<br><br><div dir="ltr">—<div>Sent from mobile, with due apologies for brevity and errors.</div></div><div dir="ltr"><br><blockquote type="cite">On Jul 1, 2021, at 11:26 AM, Joseph Jackson <jjackson@aninetworks.net> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#44546A;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#44546A">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#44546A">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 23<sup>rd</sup>.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#44546A">Joseph<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> VoiceOps [mailto:voiceops-bounces@voiceops.org]
<b>On Behalf Of </b>Matthew Sutton<br>
<b>Sent:</b> Thursday, July 01, 2021 10:08 AM<br>
<b>To:</b> voiceops@voiceops.org<br>
<b>Subject:</b> [VoiceOps] TMobile Sending Calls to LRN not Called Number<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica","sans-serif";color:black">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. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica","sans-serif";color:black">-Matthew<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<span>_______________________________________________</span><br><span>VoiceOps mailing list</span><br><span>VoiceOps@voiceops.org</span><br><span>https://puck.nether.net/mailman/listinfo/voiceops</span><br></div></blockquote></div></body></html>