[SR-Users] Avoiding "script writer didn't release transaction" warnings

Mickael Marrache mickaelmarrache at gmail.com
Mon Apr 13 21:04:27 CEST 2015


Can you think of a case where one wants to reply stateless even if a
transaction exists?

-----Original Message-----
From: sr-users [mailto:sr-users-bounces at lists.sip-router.org] On Behalf Of
Alex Balashov
Sent: Monday, April 13, 2015 9:06 PM
To: Mickael Marrache
Subject: Re: [SR-Users] Avoiding "script writer didn't release transaction"
warnings

Kamailio has a send_reply() function that accomplishes this for manually
issued replies, but that won't help with internally generated replies by the
registrar, since these are automatic.

As to a registrar patch, it's up to Daniel, but my personal opinion is that
it's not practical to go through the code to patch everything sent SL just
to make it more user-friendly in a transactional context where
t_suspend/continue are used. Maybe the users should just deal.

--
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center North, Suite 300
Atlanta, GA 30346
United States

Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

Sent from my BlackBerry.
  Original Message
From: Mickael Marrache
Sent: Monday, April 13, 2015 14:03
To: 'Kamailio (SER) - Users Mailing List'
Reply To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] Avoiding "script writer didn't release transaction"
warnings

Does Kamailio have a way to determine if to use the TM or SL module to send
the reply?

If yes, maybe the right solution is to modify the REGISTRAR sources to use
it.

I know OpenSIPS has a module called SIGNALING that allows exactly that.

-----Original Message-----
From: sr-users [mailto:sr-users-bounces at lists.sip-router.org] On Behalf Of
Alex Balashov
Sent: Monday, April 13, 2015 8:55 PM
To: sr-users at lists.sip-router.org
Subject: Re: [SR-Users] Avoiding "script writer didn't release transaction"
warnings

On 04/13/2015 01:54 PM, Alex Balashov wrote:

> Your interpretation is correct; an SL final reply within a context 
> where a transaction exists will trigger the error.

Well, more pedantically, exiting script following an SL final reply in a
context where a transaction exists is what will trigger the error.

--
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center North, Suite 300
Atlanta, GA 30346
United States

Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users at lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users at lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users at lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users




More information about the sr-users mailing list