[OpenSIPS-Users] Route header in CANCEL requests

mayamatakeshi mayamatakeshi at gmail.com
Sat Oct 10 06:21:23 CEST 2015


For completeness, it will be also necessary to call t_reply to send '100
Trying' as we are using t_newtran():

                append_hf("Route: <sip:xyz at test.com>\r\n");
                t_newtran();
                t_reply("100", "Trying");
                t_add_hdrs("Route: <sip:zyz at test.com>\r\n");


On Sat, Oct 10, 2015 at 10:27 AM, mayamatakeshi <mayamatakeshi at gmail.com>
wrote:

> Hello,
> i have found the solution in the docs:
>
>                 append_hf("Route: <sip:xyz at test.com>\r\n");
>                 t_newtran();
>                 t_add_hdrs("Route: <sip:zyz at test.com>\r\n");
>
> Regards,
> Takeshi
>
> On Sat, Oct 10, 2015 at 9:03 AM, mayamatakeshi <mayamatakeshi at gmail.com>
> wrote:
>
>> Hi, i have opensips behind another SIP proxy.
>> When I need to t_relay an INVITE from an uac to the proxy, my
>> opensips.cfg uses append_hf to add a Route header with a username required
>> by the proxy (some sort of validation).
>> This works fine. However, if the uac cancels the INVITE, the
>> transaction-controlled CANCEL generated by opensips goes out without this
>> Route header.
>> I was expecting opensips to add this Route header because opensips is
>> also used as a registrar and the proxy in front of it adds Path header to
>> the REGISTER requests and then when I relay an INVITE to the registered
>> entity (after doing lookup() ), the INVITE goes out with the contents of
>> the Path header in a Route header and the same Route header is added by
>> opensips to the CANCEL it generates.
>>
>> So, is there a way to force opensips to add this header to CANCEL? (I
>> cannot change the proxy in front of opensips. I need to conform with it).
>> I am using opensips 1.11 commit 719f298d5ad3300b790f64cfed40e797eeb23225.
>> Regards,
>> Takeshi
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20151010/103f91f1/attachment.htm>


More information about the Users mailing list