[OpenSIPS-Users] Problem with add_rr_param() in v2.4.7

Bogdan-Andrei Iancu bogdan at opensips.org
Mon Apr 27 09:46:50 EST 2020


Hi John,

Using the latest 2.4 from GIT with the default cfg, I simply added your 
lines instead on the record_route();

     # record routing
     if (!is_method("REGISTER|MESSAGE")) {
         record_route_preset("127.0.0.1:5060;transport=udp", 
"127.0.0.1:5060");
         add_rr_param(";r2=on");
     }


As a result, in the outbound INVITE, I got the RR hdrs:

Record-Route: <sip:127.0.0.1:5060;transport=udp;ftag=719688679;lr;r2=on>
Record-Route: <sip:127.0.0.1:5060;ftag=719688679;lr;r2=on>

Again, could you come up (starting from the default opensips.cfg) with a 
minimal cfg to show your issue ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com

On 4/15/20 10:19 PM, John Quick wrote:
> Hi Bogdan,
>
> The only things that are unusual are:
>   1) transport protocol conversion between TLS and UDP so it requires double RR's.
>   2) it must use FQDN instead of IP address in the Record Route headers for the TLS interface
>
> The script adds two RR headers like this:
>
> record_route_preset("<addr-as-FQDN>:5061;transport=tls", "<addr-as-IP>:5060");
> add_rr_param(";r2=on");
>
> There is also one more call to add_rr_param() after those two lines, but none of the parameters is added.
>
> For calls going in the other direction:
> record_route_preset("<addr-as-IP>:5060", "<addr-as-FQDN>:5061;transport=tls");
> add_rr_param(";r2=on");
>
> When testing with v2.4.7, the listen statements were like this:
> auto_aliases=no
> alias=udp:<addr-as-FQDN>:5060
> alias=tls:<addr-as-FQDN>:5061
> listen=udp:<addr-as-IP>:5060
> listen=tls:<addr-as-IP>:5061
>
> One idea I had is that it might work to use record_route() instead of record_route_preset() provided I changed the second listen statement to this:
> listen=tls:<addr-as-IP>:5061 AS <addr-as-FQDN>:5061
>
> ...but I haven't tested to see if the fault only happens with record_route_preset() and not with record_route().
>
> John Quick
> Smartvox Limited
>
>
> -----Original Message-----
> From: Bogdan-Andrei Iancu <bogdan at opensips.org>
> Sent: 15 April 2020 18:37
> To: john.quick at smartvox.co.uk; OpenSIPS users mailling list <users at lists.opensips.org>
> Subject: Re: [OpenSIPS-Users] Problem with add_rr_param() in v2.4.7
>
> Hi John,
>
> So you say you experience a regression between 2.4.6 and 2.4.7.... Any particularities in terms of how you do the record_routing() and add_rr_param(), like sequence, other msg changes or signaling ?
>
> Any simple way to reproduce the issue?
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>     https://www.opensips-solutions.com
>
> On 4/14/20 6:24 PM, John Quick wrote:
>> I've tried running the same opensips.cfg script in v2.4.6 and then
>> 2.4.7 When it is changed to 2.4.7, the function add_rr_param() does nothing.
>> When run under 2.4.6 it updates the Record-Route header as you would expect.
>>
>> John Quick
>> Smartvox Limited
>> Web: www.smartvox.co.uk
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users




More information about the Users mailing list