Skip to Content
Version 4.1 by colinw on 2014/09/15 15:56
Show last authors
1 == Problem ==
2
3 If iSymphony is using excessive amounts of CPU time, or is affecting call quality on the system it's installed on, here are a few things to check before opening a ticket with us.
4
5 == Troubleshooting ==
6
7 1. Ensure that the hardware installed in the system running iSymphony is reasonably close to our [[Hardware Requirements>>doc:ISYMDOCS.iSymphony Requirements]]. It doesn't need to exactly meet the recommendations, due to the inherent variability in requirements, but it should be close.
8 1. If you are using call detail records in MySQL, ensure that you have applied the [[index fix for the CDR database>>doc:mysqld spikes CPU when starting iSymphony V3]].
9
10 == Further Support ==
11
12 If you've checked the above items, and you're still having resource usage or call quality issues, feel free to open a ticket including the following information:
13
14 1. The symptoms you're experiencing (e.g. high cpu usage, high network traffic, call quality issues, etc).
15 1. (((
16 The output of the following commands:
17
18 {{code}}
19 $ cat /proc/cpuinfo
20 $ free -m
21 $ ps aux | grep -e "java.*isymphony3"
22 {{/code}}
23 )))
24 1. All files in /opt/isymphony3/server/log.
25 1. All files in /opt/isymphony3/server/conf.
26
27 == Related articles ==
28
29
30
31 {{contentbylabel spaces="" showLabels="false" reverse="true" sort="modified" max="5" labels="kb-troubleshooting-article" showSpace="false" type="page"/}}