On 9/8/10 11:26 AM, Alex Balashov wrote:
Daniel,
On 09/08/2010 04:20 AM, Daniel-Constantin Mierla wrote:
have you added some xlogs to see where it ends the execution for that
case?
If you can run the config with devel version, then load debugger
module and enable execution trace.
I have f
Daniel,
On 09/08/2010 04:20 AM, Daniel-Constantin Mierla wrote:
have you added some xlogs to see where it ends the execution for that
case?
If you can run the config with devel version, then load debugger
module and enable execution trace.
I have found the problem. It was a bug on my side t
Hello,
have you added some xlogs to see where it ends the execution for that case?
If you can run the config with devel version, then load debugger module
and enable execution trace.
Cheers,
Daniel
On 9/7/10 9:42 PM, Alex Balashov wrote:
Daniel,
Thank you. In that case, perhaps I should
Daniel,
Thank you. In that case, perhaps I should ask the question differently:
Why would the relay not be happening in this situation?
Cheers,
-- Alex
On 09/07/2010 03:02 PM, Daniel-Constantin Mierla wrote:
Hi Alex,
this warning is given when the transaction is created but no stateful
re
Hi Alex,
this warning is given when the transaction is created but no stateful
reply or relay was done.
Cheers,
Daniel
On 9/7/10 6:41 PM, Alex Balashov wrote:
Hi,
I have a somewhat unusual log entry after some calls:
Sep 3 09:12:23 kamgw01 /usr/local/sbin/kamailio[542]: WARNING: tm
[t_
Hi,
I have a somewhat unusual log entry after some calls:
Sep 3 09:12:23 kamgw01 /usr/local/sbin/kamailio[542]: WARNING: tm
[t_lookup.c:1551]: WARNING: script writer didn't release transaction
These calls fail in that they are processed instantly, but no time is
ever given to receive a resp
