[OpenSIPS-Users] unusual RURI format

[Brett Nemeroff]

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.-Brett


On Sat, Jul 4, 2009 at 11:55 PM, "Juan E. Rodríguez" <jerdguez at gmail.com>wrote:

>  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).
>
> Ragards,
> Juan
>
>
> Iñaki Baz Castillo wrote:
>
> 2009/6/26 Brett Nemeroff <brett at nemeroff.com> <brett at nemeroff.com>:
>
>
>  All,
> I've got a customer that is sending me calls with an RURI like this:
>  sip:13155551207;npdi=yes;rn=13155550000 at 1.2.3.4
>
> when I use anything that parses the RURI like $rU, it shows
> $rU=sip:131555551207;npdi=yes;rn=13155550000
> 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?
>
>
>  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.
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20090705/eff5fd54/attachment.htm