<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body 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>
Juan<br>
<br>
Iñaki Baz Castillo wrote:
<blockquote
cite="mid:cc1f582e0906281118n4dfc5ceaj7a3befbac65829d9@mail.gmail.com"
type="cite">
<pre wrap="">2009/6/26 Brett Nemeroff <a class="moz-txt-link-rfc2396E" href="mailto:brett@nemeroff.com"><brett@nemeroff.com></a>:
</pre>
<blockquote type="cite">
<pre wrap="">All,
I've got a customer that is sending me calls with an RURI like this:
<a class="moz-txt-link-freetext" href="sip:13155551207;npdi=yes;rn=13155550000@1.2.3.4">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 class="moz-txt-link-freetext" href="sip:131555551207;npdi=yes;rn=13155550000">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 wrap=""><!---->
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>
</body>
</html>