Yes, I'm familiar with all of that. The issue was how to handle all of that with something that uses $rU like drouting.. I've got a solution with the dialplan module already. Thanks for your reply.<div>-Brett</div>
<div><br><br><div class="gmail_quote">On Sat, Jul 4, 2009 at 11:55 PM, "Juan E. Rodríguez" <span dir="ltr"><<a href="mailto:jerdguez@gmail.com">jerdguez@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#ffffff" text="#000000">
This URI is from a server or gateway which manage Number Portability
data. The rn is the routing number used to route the call (LRN) and the
npdi is the Number Portability DIP indication (means that the NP DIP
was done).<br>
<br>
Ragards,<br><font color="#888888">
Juan</font><div><div></div><div class="h5"><br>
<br>
Iñaki Baz Castillo wrote:
<blockquote type="cite">
<pre>2009/6/26 Brett Nemeroff <a href="mailto:brett@nemeroff.com" target="_blank"><brett@nemeroff.com></a>:
</pre>
<blockquote type="cite">
<pre>All,
I've got a customer that is sending me calls with an RURI like this:
<a>sip:13155551207;npdi=yes;rn=13155550000@1.2.3.4</a>
when I use anything that parses the RURI like $rU, it shows
$rU=<a>sip:131555551207;npdi=yes;rn=13155550000</a>
Which is exactly everything from sip: to the first @ sign. The customer
isn't able to change this RURI (it's coming from their downstream)
What can I do to properly have $rU parse this up?
</pre>
</blockquote>
<pre>That SIP URI seems to come from a TEL conversion. However the URI
username is "13155551207;npdi=yes;rn=13155550000". An user shouldn't
send such an username to a server expecting that the server will drop
after the ";" in the username.
If you want to parse it, I would use a substitution by deleting all
the content after the first ";" in the RURI username using AVPOPS.
</pre>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div>