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

List overview All Threads
Download

newer

older

Timeout session Kamailio w/...

Maximum feasible size of htable?

Mickael Marrache

13 Apr 2015 13 Apr '15

5:46 p.m.

Any idea?

From: Mickael Marrache [mailto:mickaelmarrache@gmail.com] Sent: Thursday, April 09, 2015 2:08 PM To: sr-users@lists.sip-router.org Subject: RE: Avoiding "script writer didn't release transaction" warnings

I think understand in which case it happens.

When I receive a REGISTER, I create a transaction since I need to use the t_continue feature to wake up a suspended transaction. However, the save() command of the REGISTRAR module doesn't seem to call t_reply for replying the 200 (it looks like the SL module is used instead). Therefore, I get the warning every time it happens since the transaction is not released explicitly.

Should I call t_release just before exiting the block handling the REGISTER?

From: Mickael Marrache [mailto:mickaelmarrache@gmail.com] Sent: Thursday, April 09, 2015 1:43 PM To: sr-users@lists.sip-router.org Subject: Avoiding "script writer didn't release transaction" warnings

Hi,

In my logs, I get a lot of the following warnings:

WARNING: tm [t_lookup.c:1476]: t_unref(): WARNING: script writer didn't release transaction

I force transaction creation from my script to absorb retransmissions as soon as possible. I understand that I need to explicitly call t_release in order to avoid this warning.

What is the most appropriate place in the script to call t_release?

Thanks,

Mickael

Attachments:

attachment.html (text/html — 5.7 KB)

Show replies by date

Alex Balashov

13 Apr 13 Apr

5:54 p.m.

New subject: Avoiding "script writer didn't release transaction" warnings

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

A safe approach is:

if(t_lookup_request()) t_release();

-- 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/

Alex Balashov

5:55 p.m.

New subject: 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.

Mickael Marrache

6:02 p.m.

New subject: 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@lists.sip-router.org] On Behalf Of Alex Balashov Sent: Monday, April 13, 2015 8:55 PM To: sr-users@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@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Alex Balashov

6:06 p.m.

New subject: 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.

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/

Mickael Marrache

7:04 p.m.

New subject: Avoiding "script writer didn't release transaction" warnings

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@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.

-- 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/

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.

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/

Alex Balashov

7:09 p.m.

New subject: Avoiding "script writer didn't release transaction" warnings

No, but I can think of many cases where a transaction won't exist 99% of the time. For the minority exotic cases, this is why manual transaction create/destroy functions are provided by TM.

-- 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 15:05 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

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

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.

-- 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/

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.

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/

3664

Age (days ago)

3664

Last active (days ago)

sr-users@lists.kamailio.org

6 comments

2 participants

tags (0)

participants (2)

Alex Balashov
Mickael Marrache