[OpenSIPS-Users] Dialog hanging at State 5

Răzvan Crainea razvan at opensips.org
Wed Apr 1 17:43:34 CEST 2015


Hi, John!

Can you put on pastebin the output of the "opensipsctl fifo 
dlg_list_ctx" command while multiple dialogs are stuck in state 5?

Best regards,

Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com

On 03/31/2015 01:29 PM, John Mathew wrote:
> Opensips 1.11.3
>
> On Tuesday, 31 March 2015, Răzvan Crainea <razvan at opensips.org 
> <mailto:razvan at opensips.org>> wrote:
>
>     Hi, John!
>
>     What OpenSIPS version are you running?
>
>     Regards,
>
>     Răzvan Crainea
>     OpenSIPS Solutions
>     www.opensips-solutions.com  <http://www.opensips-solutions.com>
>
>     On 03/30/2015 08:08 PM, John Mathew wrote:
>>     Razvan,
>>
>>     I tried to reproduce the issue, by making UAS not to respond for
>>     opensips request. but opensips is handling it correctly. That
>>     means the issue is not during Request Timeout.
>>
>>     Then what what could be reason, when intermittently Dialog not
>>     deleted from state 5 and once in 2-3 days state 5 calls will be
>>     5000 numbers and opensips ran out of shmem and crashes.
>>
>>     On Mon, Mar 30, 2015 at 1:54 PM, Răzvan Crainea
>>     <razvan at opensips.org
>>     <javascript:_e(%7B%7D,'cvml','razvan at opensips.org');>> wrote:
>>
>>         Do the dialogs get stuckin state 5 and they are never deleted?
>>         By default, when a negative reply is received and there is no
>>         failure route armed to handle it, the transaction/dialog is
>>         destroyed and the reply is sent back to the client.
>>
>>         Can you please be a bit more specific about what is happening
>>         with your call, and what would you like to happend?
>>
>>         Best regards,
>>
>>         Răzvan Crainea
>>         OpenSIPS Solutions
>>         www.opensips-solutions.com  <http://www.opensips-solutions.com>
>>
>>         On 03/29/2015 09:19 AM, John Mathew wrote:
>>>         Guys,
>>>
>>>         Waiting for your response. Any help will be appreciated.
>>>
>>>         On Fri, Mar 27, 2015 at 8:36 PM, John Mathew
>>>         <john.mathew at divoxmedia.com
>>>         <javascript:_e(%7B%7D,'cvml','john.mathew at divoxmedia.com');>> wrote:
>>>
>>>             Hi,
>>>
>>>             Normally how do we handle the situation, when we do not
>>>             receive any response from destination for any request?
>>>
>>>             On Fri, Mar 27, 2015 at 2:10 PM, John Mathew
>>>             <john.mathew at divoxmedia.com
>>>             <javascript:_e(%7B%7D,'cvml','john.mathew at divoxmedia.com');>>
>>>             wrote:
>>>
>>>                 Hi Razvan,
>>>
>>>                 I mean dialog not deleted from memory and they are
>>>                 at state 5. This happens only for calls
>>>                 where, destination not responding for Register and
>>>                 Invite requests. And they are not deleted from memory.
>>>
>>>                 I guess i am missing some timer related configuration.
>>>
>>>
>>>                 On Friday, 27 March 2015, Răzvan Crainea
>>>                 <razvan at opensips.org
>>>                 <javascript:_e(%7B%7D,'cvml','razvan at opensips.org');>>
>>>                 wrote:
>>>
>>>                     Hi, John!
>>>
>>>                     What do you mean the dialog is hanging in state
>>>                     5? The dialog is never deleted from DB/memory?
>>>
>>>                     The dialog starts when the call is completed
>>>                     (the 200 OK is sent), so you can't "move a
>>>                     dialog" in failure route.
>>>                     What you can do is to handle the Request failure
>>>                     in failure_route and route it somewhere else, or
>>>                     drop it and the dialog is closed. To handle a
>>>                     request in failure_route, you have to engage it
>>>                     before sending the first request out, using:
>>>
>>>                     t_on_failure("handle_fails");
>>>                     ...
>>>
>>>
>>>                     failure_route[handle_fails] {
>>>                         ...
>>>                         # handle the failed call
>>>                         ...
>>>                     }
>>>
>>>                     Best regards,
>>>
>>>                     Răzvan Crainea
>>>                     OpenSIPS Solutions
>>>                     www.opensips-solutions.com  <http://www.opensips-solutions.com>
>>>
>>>                     On 03/26/2015 03:55 PM, John Mathew wrote:
>>>>                     Hi,
>>>>
>>>>                     Dialog state is hanging at "state 5" when there
>>>>                     is no response from the destination.
>>>>
>>>>                     What config we need to add to get the dialog
>>>>                     moved to failure_route if, opensips is not
>>>>                     receiving any response from destination for any
>>>>                     request sent out.?
>>>>
>>>>                     Or
>>>>
>>>>
>>>>                     How can we drop the dialog instead of moving to
>>>>                     failure_route?
>>>>
>>>>                     -- 
>>>>
>>>>                     Regards,
>>>>                     John Mathew
>>>>                     CEO/Director
>>>>                     Divox International Inc.
>>>>                     Contact: +91-9037100001
>>>>                     Email/MSN: John.Mathew at divoxmedia.com
>>>>                     WEB: www.divoxmedia.com
>>>>                     <http://www.divoxmedia.com/>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>                     _______________________________________________
>>>>                     Users mailing list
>>>>                     Users at lists.opensips.org
>>>>                     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>>
>>>                 -- 
>>>                 Sent from iPhone 6
>>>
>>>
>>>
>>>
>>>             -- 
>>>
>>>             Regards,
>>>             John Mathew
>>>             CEO/Director
>>>             Divox International Inc.
>>>             Contact: +91-9037100001
>>>             Email/MSN: John.Mathew at divoxmedia.com
>>>             <javascript:_e(%7B%7D,'cvml','John.Mathew at divoxmedia.com');>
>>>             WEB: www.divoxmedia.com <http://www.divoxmedia.com/>
>>>
>>>
>>>
>>>
>>>
>>>
>>>         -- 
>>>
>>>         Regards,
>>>         John Mathew
>>>         CEO/Director
>>>         Divox International Inc.
>>>         Contact: +91-9037100001
>>>         Email/MSN: John.Mathew at divoxmedia.com
>>>         <javascript:_e(%7B%7D,'cvml','John.Mathew at divoxmedia.com');>
>>>         WEB: www.divoxmedia.com <http://www.divoxmedia.com/>
>>>
>>>
>>>
>>>
>>>
>>>         _______________________________________________
>>>         Users mailing list
>>>         Users at lists.opensips.org  <javascript:_e(%7B%7D,'cvml','Users at lists.opensips.org');>
>>>         http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>         _______________________________________________
>>         Users mailing list
>>         Users at lists.opensips.org
>>         <javascript:_e(%7B%7D,'cvml','Users at lists.opensips.org');>
>>         http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>>
>>     -- 
>>
>>     Regards,
>>     John Mathew
>>     CEO/Director
>>     Divox International Inc.
>>     Contact: +91-9037100001
>>     Email/MSN: John.Mathew at divoxmedia.com
>>     <javascript:_e(%7B%7D,'cvml','John.Mathew at divoxmedia.com');>
>>     WEB: www.divoxmedia.com <http://www.divoxmedia.com/>
>>
>>
>>
>>
>>
>>     _______________________________________________
>>     Users mailing list
>>     Users at lists.opensips.org  <javascript:_e(%7B%7D,'cvml','Users at lists.opensips.org');>
>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> -- 
> Sent from iPhone 6
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20150401/15475d92/attachment-0001.htm>


More information about the Users mailing list