Difference between revisions of "Explanation about stucked calls"

From Kolmisoft Wiki
Jump to navigationJump to search
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
When call is stuck in [[Active Calls]] and soft hangup button does not hangup the call - that means that call stuck in Asterisk because of Asterisk lock problem.
When the call is stuck in [[Active Calls]] and soft hangup button does not hang up the call - that means that call stuck in Asterisk because of Asterisk lock problem.


Currently MOR uses Asterisk 1.4.18.1 which has many lock problems which leads to stuck channels.
This often happens in Asterisk 1.4.18.1 which has many lock problems which lead to stuck channels.


Only [[How to restart Asterisk server|Asterisk restart]] can delete these calls.
Only [[How to restart Asterisk server|Asterisk restart]] can delete these calls.


Currently Kolmisoft is working on MOR support for Asterisk 1.4.32+ to minimize as much as possible future lock problems.


Many lock problems are already solved in Asterisk 1.4.32 and we are planning to migrate MOR to this Asterisk version at 2010 July 1st.
We suggest upgrading to Asterisk 1.8 version which solves most of these problems.
 
Thank you for understanding.

Latest revision as of 13:21, 11 June 2019

When the call is stuck in Active Calls and soft hangup button does not hang up the call - that means that call stuck in Asterisk because of Asterisk lock problem.

This often happens in Asterisk 1.4.18.1 which has many lock problems which lead to stuck channels.

Only Asterisk restart can delete these calls.


We suggest upgrading to Asterisk 1.8 version which solves most of these problems.

Retrieved from "https://wiki.kolmisoft.com/index.php?title=Explanation_about_stucked_calls&oldid=24831"