[SR-Users] t_reply in failure route with dialog module

[Daniel-Constantin Mierla]

Hello,

I will investigate more -- meanwhile had some traveling. It would speed 
up if you can send the backtrace of one process that blocks when you 
applied the patch.

You need to connect with gdb to it:

gdb /path/to/kamailio _PID_

replace _PID_ with the pid of blocked kamailio process.

Cheers,
Daniel

On 11/15/13 5:50 PM, Efelin Novak wrote:
> Hi Daniel,
>
> thanks for a reply. I applied the patch and now the Kamailio just prints
>
> WARNING: tm [t_lookup.c:1564]: t_unref(): WARNING: script writer 
> didn't release transaction
>
> and than freezes without any log. It does not resend the incoming 
> "winning" failure reply neither response to any other messages, not 
> even to a new calls. It just freezes. All kamailio processes are 
> running and eating the whole 4-core processor.
>
> Restart of Kamailio solves this problem.
>
> Any ideas how to continue with debug?
>
> Thanks
>
> Efelin
>
>
> 2013/11/15 Daniel-Constantin Mierla <miconda at gmail.com 
> <mailto:miconda at gmail.com>>
>
>     Hello,
>
>     can you try attached patch?
>
>     Let me know if all goes fine and I will commit it to the repository.
>
>     Cheers,
>     Daniel
>
>
>     On 11/15/13 10:25 AM, Efelin Novak wrote:
>>     Hi,
>>
>>     when I use t_reply("505", "Error"); in my failure route, the
>>     response is not forwarded and following is written into a log:
>>
>>     kamailio[26216]: WARNING: tm [t_lookup.c:1559]: t_unref():
>>     WARNING: script writer didn't release transaction
>>
>>     plus next line is written exactly 416000 times into a log afterwards:
>>
>>     kamailio[32685]: CRITICAL: dialog [dlg_hash.c:794]:
>>     log_next_state_dlg(): bogus event 4 in state 5 for dlg 0xb4af6588
>>     [2575:7017] with clid '121d44f0-6555f4c8' and tags
>>     'd12546d053aadc68o2' ''
>>
>>     My point is to change the incoming code from users and append a
>>     Q.850 reason code.
>>     Is there any other way how to do this or a way how to fix this?
>>     I'm using Kamilio 4.0.4 on Debian 7.1
>>
>>
>>     The code is as follows:
>>     failure_route[MANAGE_FAILURE]
>>     {
>>             if (t_is_canceled()) {
>>                     exit;
>>             }
>>             if($T_reply_code == 408 && isflagset(10))
>>             {
>>                     xlog("Ringing timeout");
>>                     append_to_reply("Reason: Q.850;cause=28\r\n");
>>                     t_reply("505", "Error");
>>             }
>>     }
>>
>>
>>     _______________________________________________
>>     SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>     sr-users at lists.sip-router.org  <mailto:sr-users at lists.sip-router.org>
>>     http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>     -- 
>     Daniel-Constantin Mierla -http://www.asipto.com
>     http://twitter.com/#!/miconda  <http://twitter.com/#%21/miconda>  -http://www.linkedin.com/in/miconda
>     Kamailio Advanced Trainings - Berlin, Nov 25-28
>        - more details about Kamailio trainings athttp://www.asipto.com  -
>
>
>     _______________________________________________
>     SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
>     list
>     sr-users at lists.sip-router.org <mailto:sr-users at lists.sip-router.org>
>     http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Trainings - Berlin, Nov 25-28
   - more details about Kamailio trainings at http://www.asipto.com -

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