27 Nov
2019
27 Nov
'19
3:03 a.m.
Is the idea behind doing this to provide extra safety in case the TM
callbacks that feed into dialog life-cycle tracking do not work? Are
there remaining known cases of this, given how long the dialog module
has been around?
On Tue, Nov 26, 2019 at 03:33:19PM +0100, Daniel-Constantin Mierla wrote:
Hello,
the recommended way is to call dlg_manage() for all requests belonging
to the dialog. There can be a record-routing callback executed for
requests within dialog for the same purpise, but it has some constraints
related to the presence of an unaltered parameter, as well as it was
designed with the use of setting a flag for tracking the dialogs. Even
the r-r callback is executed, doing the dlg_manage() for all requests is
still safe.
Cheers,
Daniel
On 26.11.19 15:25, George Diamantopoulos wrote:
Thank you both for your input. I guess I'll
continue calling
dlg_manage() for in-dialog requests for now until I gather more
feedback, since we do cater for a large set of endpoints and several
have at times exhibited various offending behaviours.
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/