[OpenSIPS-Users] Change 200 OK of BYE message

[Bogdan-Andrei Iancu]

BYE is a different SIP transaction, so you need to arm the routes 
separately.

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 02/07/2017 03:08 PM, Daniel Zanutti wrote:
> Hi
>
> No, i didn't set it. After set the onreply, it worked fine. I didn't 
> know that the BYE is a new request internally.
>
> Thanks Bogdan
>
> On Tue, Feb 7, 2017 at 10:37 AM, Bogdan-Andrei Iancu 
> <bogdan at opensips.org <mailto:bogdan at opensips.org>> wrote:
>
>     Hi,
>
>     As the 200OK belongs to the BYE request, are you sure you arm the
>     onreply route when handling the _BYE_ request ?
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>     OpenSIPS Founder and Developer
>     http://www.opensips-solutions.com <http://www.opensips-solutions.com>
>
>     On 02/07/2017 01:48 PM, Daniel Zanutti wrote:
>>     The sip client is working fine, I can confirm that both BYE and
>>     200 OK are flowing through the proxy, the problem is I cannot
>>     modify the 200 OK message.
>>     I need to modify a header on the 200 OK of the BYE but I cannot
>>     since the message doesn't pass to internal on_reply_route or main
>>     Route inside Opensips. It's being routed internally by Opensips
>>     directly to the destination.
>>     Do you have any idea?
>>     On Tue, Feb 7, 2017 at 5:40 AM, Johan De Clercq <johan at democon.be
>>     <mailto:johan at democon.be>> wrote:
>>
>>         Any chance to have a small capture ?
>>         I tend to agree with Robert, if you use rr consistently there
>>         should be no problem. It can of course also be that the
>>         client does something strange ...
>>         2017-02-06 21:43 GMT+01:00 Daniel Zanutti
>>         <daniel.zanutti at gmail.com <mailto:daniel.zanutti at gmail.com>>:
>>
>>             Hi Robert
>>             Yes, all messages are passing through the proxy, but when
>>             I receive the 200 OK of the BYE message, it doesn't go to
>>             Main Route or Reply Route. It just go to the destination
>>             and I cannot change anything on it.
>>             Any idea?
>>             On Mon, Feb 6, 2017 at 6:14 PM, Mundkowsky, Robert
>>             <rmundkowsky at ets.org <mailto:rmundkowsky at ets.org>> wrote:
>>
>>                 Did you use “record_route”?
>>
>>                 For reference:
>>
>>                 http://www.iptel.org/sip/intro/scenarios/rr
>>                 <http://www.iptel.org/sip/intro/scenarios/rr>
>>
>>                 Robert Mundkowsky
>>
>>                 *From:*Users [mailto:users-bounces at lists.op
>>                 <mailto:users-bounces at lists.op>ensips.org
>>                 <http://ensips.org>] *On Behalf Of *Daniel Zanutti
>>                 *Sent:* Monday, February 6, 2017 3:01 PM *To:*
>>                 OpenSIPS users mailling list
>>                 <users at lists.opensips.org
>>                 <mailto:users at lists.opensips.org>> *Subject:*
>>                 [OpenSIPS-Users] Change 200 OK of BYE message
>>
>>                 Hi
>>
>>                 I need to change something on the 200 OK of BYE
>>                 message. Tried everything on Opensips but looks like
>>                 this message doesn't follow standard message path.
>>                 Neither Main Route or Reply route pass this message.
>>
>>                 Is there any way to do it?
>>
>>                 Thanks
>>
>>                 ------------------------------------------------------------------------
>>
>>                 This e-mail and any files transmitted with it may
>>                 contain privileged or confidential information. It is
>>                 solely for use by the individual for whom it is
>>                 intended, even if addressed incorrectly. If you
>>                 received this e-mail in error, please notify the
>>                 sender; do not disclose, copy, distribute, or take
>>                 any action in reliance on the contents of this
>>                 information; and delete it from your system. Any
>>                 other use of this e-mail is prohibited.
>>
>>                 Thank you for your compliance.
>>
>>                 ------------------------------------------------------------------------
>>                 _______________________________________________ Users
>>                 mailing list Users at lists.opensips.org
>>                 <mailto:Users at lists.opensips.org>
>>                 http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>                 <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
>>
>>
>>             _______________________________________________ Users
>>             mailing list Users at lists.opensips.org
>>             <mailto:Users at lists.opensips.org>
>>             http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>             <http://lists.opensips.org/cgi-bin/mailman/listinfo/users> 
>>
>>         _______________________________________________ Users mailing
>>         list Users at lists.opensips.org
>>         <mailto:Users at lists.opensips.org>
>>         http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>         <http://lists.opensips.org/cgi-bin/mailman/listinfo/users> 
>>
>>     _______________________________________________
>>     Users mailing list
>>     Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>     <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20170207/86f0ec00/attachment-0001.html>