[OpenSIPS-Users] unusual RURI format

[Brett Nemeroff]

so I tried to use the dialplan module to rewrite this ruri like this:
 dp_translate("$avp(s:ntrunkid)","$ruri.user/$ruri.user");

With a rule like this

+----+------+----+----------+-----------------+-----------+-----------------+----------+-------+
| id | dpid | pr | match_op | match_exp       | match_len | subst_exp
| repl_exp | attrs |
+----+------+----+----------+-----------------+-----------+-----------------+----------+-------+
|  7 |   21 | 50 |        1 | ^(1[0-9]{10}).+ |         0 | ^(1[0-9]{10}).+
| \1       |       |
+----+------+----+----------+-----------------+-----------+-----------------+----------+-------+


Calls now fail with a 500 Overlapping request. SIP Trace shows me receving a
200 OK and it not being relayed I don' think..

Any ideas?
-Brett
On Fri, Jun 26, 2009 at 2:06 PM, Brett Nemeroff <brett at nemeroff.com> wrote:

> 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?
>
> Thanks,
> Brett
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20090626/6a96e2eb/attachment.htm