Hi, Rodrigo!
The only HACK that I can think of is when you get the BYE message, set
the dialog timeout to 0, match it against the dialog, and then drop the
message. OpenSIPS will behave as if the dialog expired in that moment.
However, you seem to have a flow logic - most likely the Contact header
in the BYE is not correct. Could you send us a trace to help you figure
out what the problem is? Also, did you try to validate the message
against the dialog[1] and fix it accordingly[2]?
[1] http://www.opensips.org/html/docs/modules/2.2.x/dialog#id295894
[2] http://www.opensips.org/html/docs/modules/2.2.x/dialog#id295982
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
On 11/08/2016 10:07 PM, Rodrigo Pimenta Carvalho wrote:
Hi.
Dialogs in my OpenSIPS is programmed to finish after 60 seconds.
(timeout = 1 minute).
So, when 2 peers are in a dialog, OpenSIPS sends SIP BYE to both
peers, automatically after 60 seconds.
Is it possible to make OpenSIPS send this exact kind of SIP BYE to
both peers, before the dialog timeout? I mean, in a configured way
(opensips.cfg)?
When OpenSISP sends SIP BYE automatically, both peers receive the SIP
BYE correctly.
However, when a peer sends SIP BYE, it reaches the OpenSIPS, but
OpenSIPS is unable to forward this SIP BYE. Due to some unknown
reason, in this moment there is no open socket to communicate with
such peer. That is why I would like to make OpenSIPS send 'its own'
SIP BYE, and see if such idea will simulate a normal situation, until
I discover why there is a socket problem.
Any hint will be very helpful!
Best regards.
RODRIGO PIMENTA CARVALHO
Inatel Competence Center
Software
Ph: +55 35 3471 9200 RAMAL 979
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
