Difference between revisions of "Call is going but not visible in Active Calls"

From Kolmisoft Wiki
Jump to navigationJump to search
(Created page with '<br><br> = See also = * I have a Problem with Calls * Asterisk problems * I HAVE A PROBLEM')
 
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
=  Too much active calls =
In Settings increase the number of Active Calls to be shown in the GUI.
By default limit is 100 for performance issues.
<br><br>
= Other issues =
On ALL system servers (where appropriate - explanation -> no need to upgrade Asterisk on GUI server if Asterisk is not present here):
# Stop Asterisk normally
# killall -9 safe_asterisk
# killall -9 asterisk
# Upgrade GUI/DB/Core
# Run Asterisk/httpd
# to DB: delete from sessions;
# Make sure /home/mor/config/environment.rb does not have or has correct setting with ENV[TZ]
# Make sure time is the same on all servers in the system
<br><br>
If it does not help:
# Enable SQL debug in Core
# Make a call
# Get SQL from CLI which starts with: INSERT INTO activecalls....
# Paste it into DB
# Watch Active Calls window
<br><br>
<br><br>
= See also =  
= See also =  
* [[I have a Problem with Calls]]
* [[I have a problem with Calls]]
* [[Main_Page#Asterisk_2 | Asterisk problems]]
* [[Main_Page#Asterisk_2 | Asterisk problems]]
* [[I HAVE A PROBLEM]]
* [[I HAVE A PROBLEM]]

Latest revision as of 14:24, 1 September 2013

Too much active calls

In Settings increase the number of Active Calls to be shown in the GUI. By default limit is 100 for performance issues.



Other issues

On ALL system servers (where appropriate - explanation -> no need to upgrade Asterisk on GUI server if Asterisk is not present here):

  1. Stop Asterisk normally
  2. killall -9 safe_asterisk
  3. killall -9 asterisk
  4. Upgrade GUI/DB/Core
  5. Run Asterisk/httpd
  6. to DB: delete from sessions;
  7. Make sure /home/mor/config/environment.rb does not have or has correct setting with ENV[TZ]
  8. Make sure time is the same on all servers in the system



If it does not help:

  1. Enable SQL debug in Core
  2. Make a call
  3. Get SQL from CLI which starts with: INSERT INTO activecalls....
  4. Paste it into DB
  5. Watch Active Calls window




See also