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

[Mickael Marrache]

Any idea?

 

From: Mickael Marrache [mailto:mickaelmarrache at gmail.com] 
Sent: Thursday, April 09, 2015 2:08 PM
To: sr-users at 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 at gmail.com] 
Sent: Thursday, April 09, 2015 1:43 PM
To: sr-users at 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20150413/cbfeae53/attachment.html>