'
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?
-Original Message-
From: sr-users [mailto:sr-user
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 t
o: 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
-users-boun...@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 interpretat
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 t
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
Un
Any idea?
From: Mickael Marrache [mailto:mickaelmarra...@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 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
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_rel
