|Summary:||ASTERISK-08526: Asterisk crashes in call centre environment several times a week|
|Date Opened:||2007-01-09 04:28:53.000-0600||Date Closed:||2007-02-16 17:05:00.000-0600|
|Environment:||Attachments:||( 0) Dec18th-2.txt|
( 1) Dec20th.txt
( 2) Dec21st.txt
( 3) Dec27th.txt
( 4) Dec29th.txt
( 5) Nov22nd.txt
( 6) Nov27th.txt
( 7) Nov6th.txt
( 8) Nov7th-2.txt
|Description:||Asterisk is being used in a call center.|
Call center has 40 agents and 18 queues.
Queues are using members (not agents).
They have 3 x ISDN PRI lines on the system
They just receive inbound calls from their customers. All incoming calls go to queues.
Their average simultaneous calls is about 60 inbound and 5 outbound calls.
They have 2 to 3 crashes every week where asterisk creates a core dump.
Of these there are 8 instances where the same backtrace is produced.
I have attached these 8 backtraces. Can you tell me what these indicate?
****** ADDITIONAL INFORMATION ******
Dell PowerEdge 1850 server
Linux 22.214.171.124 Intel(R) Xeon(TM) CPU 3.20GHz
|Comments:||By: Tilghman Lesher (tilghman) 2007-01-09 08:06:58.000-0600|
There are is fatal problem with your bug report. You reported that this issue is with 1.2.13, but the backtraces indicate that you are running 1.4.
In any case, this issue in 1.4 has already been patched. Please upgrade to the most recent 1.4 SVN.
By: sk2133 (sk2133) 2007-01-09 10:19:28.000-0600
We are running asterisk 1.2.13 but with some patches for agent login.
We put in the following for manager:
And this was also merged into 126.96.36.199
Can you tell me what makes you think that this is running asterisk 1.4?
By: Tilghman Lesher (tilghman) 2007-01-09 10:34:16.000-0600
You're running a patched version of Asterisk, which you did not mention in the original bug report. Please revert all patches and test again. Those patches are unsupported.
By: sk2133 (sk2133) 2007-01-09 11:14:56.000-0600
Sorry about not mentioning the patch.
We will revert back and re-test.
By: Joshua C. Colp (jcolp) 2007-02-16 17:04:59.000-0600
The crashes are clearly being caused by the patch that is not part of Asterisk. If you can reproduce the issue in 1.4 where the patch was officially applied then feel free to reopen this.