[sr-dev] double record-routing also at outbound edge

[Peter Dunkley]

I am saying that record-route()/loose_route() doesn't do anything with 
GRUU when outbound is used right now.

I am not sure what the right changes would be.  But there might be 
something easy you can do to avoid the problem for now.

Changing the code to add a custom parameter isn't a good idea as it will 
be outside of any RFC specification.  I think whatever is in the code 
should be based on the RFCs.  So if you want to do something to work 
around it with custom parameters as you have suggested I think this 
should be done entirely on the config file side of things.

Regards,

Peter

On 25/04/13 10:24, Juha Heinanen wrote:
> Peter Dunkley writes:
>
>> If you don't want Record-Route:/Route: based routing why not just not
>> add the Record-Route:s?
> i didn't understand.  i have to add record-router header pointing to
> proxy/registrar 1 when invite is forwarded to proxy/registrar 2.
> without gruu this has worked fine just by calling record_route().
>
> are you now suggesting that gruu cannot be handled automatically by
> record_route() call and that i need to use record_route_preset(string
> [,string2]) instead?
>
> -- juha
>
> _______________________________________________
> sr-dev mailing list
> sr-dev at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev