Page 1 of 1

Call disconnection - checked Log - Help

PostPosted: Fri May 23, 2008 3:43 am
by kurianthayil
Hi All,

We are using Vicidial with Asterisk to make outbound calls. We are using 2 T1 lines for this and interfaced with Digium TE410P card. We are facing frequent call disconnections, and it also happens when an agent is in the middle of a call. Is there any way that we can remove or atleast reduce the amount of call disconnections. When I checked Asterisk log, I see some output and I have posted it below. Please have a look at it and do suggest if it has anything to do with the Call disconnection problem we have. I tried some google to analyze the issue using this log info. But it was of no use. Do suggest some tips. Any help is highly appreciated. Do suggest some tips. Thank you in advance.

May 22 13:36:43 NOTICE[12603] chan_local.c: No such extension/context XXYYXXYYXXYYXX48600053@default creating local channel
May 22 13:36:43 NOTICE[12603] channel.c: Unable to request channel Local/XXYYXXYYXXYYXX48600053@default
May 22 13:36:44 NOTICE[12608] chan_local.c: No such extension/context XXYYXXYYXXYYXX48600053@default creating local channel
May 22 13:36:44 NOTICE[12608] channel.c: Unable to request channel Local/XXYYXXYYXXYYXX48600053@default
May 22 13:37:30 WARNING[12879] file.c: Unexpected control subclass '-1'
May 22 13:38:34 WARNING[13302] file.c: Unexpected control subclass '-1'
May 22 13:39:13 WARNING[13506] file.c: Unexpected control subclass '-1'
May 22 13:42:28 WARNING[14538] file.c: Unexpected control subclass '-1'
May 22 13:47:49 WARNING[16124] file.c: Unexpected control subclass '-1'
May 22 13:47:57 WARNING[16145] file.c: Unexpected control subclass '-1'
May 22 13:47:57 WARNING[16151] file.c: Unexpected control subclass '-1'
May 22 13:48:07 WARNING[16252] file.c: Unexpected control subclass '-1'
May 22 13:48:16 WARNING[16296] file.c: Unexpected control subclass '-1'
May 22 13:48:27 WARNING[16338] file.c: Unexpected control subclass '-1'
May 22 13:49:18 WARNING[16661] file.c: Unexpected control subclass '-1'
May 22 13:49:27 WARNING[16703] file.c: Unexpected control subclass '-1'
May 22 13:51:42 WARNING[17433] file.c: Unexpected control subclass '-1'
May 22 13:51:45 WARNING[17443] file.c: Unexpected control subclass '-1'
May 22 13:52:07 WARNING[17605] file.c: Unexpected control subclass '-1'
May 22 13:53:27 WARNING[17960] file.c: Unexpected control subclass '-1'
May 22 13:53:38 WARNING[18027] file.c: Unexpected control subclass '-1'
May 22 13:55:10 WARNING[18627] file.c: Unexpected control subclass '-1'
May 22 13:55:17 WARNING[18656] file.c: Unexpected control subclass '-1'
May 22 13:55:23 WARNING[18694] file.c: Unexpected control subclass '-1'
May 22 13:56:01 WARNING[18919] file.c: Unexpected control subclass '-1'
May 22 13:58:28 WARNING[19627] file.c: Unexpected control subclass '-1'
May 22 13:58:52 WARNING[19633] app_meetme.c: Unable to write frame to channel Local/78600053@default-8b00,2
May 22 14:00:07 WARNING[20028] file.c: Unexpected control subclass '-1'


Regards,

Kurian Mathew Thayil.[/code]

PostPosted: Fri May 23, 2008 3:45 am
by kurianthayil
Hi,
I forgot to mention our system setup. Its a linux box loaded with CentOS 4.4 server with asterisk and astguiclient loaded. Our DB (MySQL) is in a different box and that too loaded with CentOS 4.4 server.

Regards,

Kurian Mathew Thayil.

PostPosted: Fri May 23, 2008 5:04 am
by mflorell
astGUIclient version?

Asterisk version?

loadavg when drops occur?

Do you have kernel process preemption set to SERVER in your compiled Linux kernel?

PostPosted: Fri May 23, 2008 5:20 am
by kurianthayil
Hi,

Thank you for the reply. The following are the informations to the best of my knowledge.

Asterisk version: 1.2.18
astGUIclient version: 2.0.3

Its an SMP kernel upgraded using YUM.

Kernel version: 2.6.9-42.0.10.ELsmp

The load goes upto 1.80 when doing 'uptime'. In an average it stands in between 0.90 to 1.10.

Please do suggest some tips. Thank you in advance.

Regards,

Kurian Mathew Thayil.

PostPosted: Fri May 23, 2008 7:40 am
by mflorell
What kind of CPU do you have?

As for the Kernel settings, you might have a process prioritization set to Desktop which can cause problems and is one reason we don't recommend using a stock CentOS install. There is more info on that at the bottom of the first page and on the second page of this posting:

http://www.eflo.net/VICIDIALforum/viewt ... ritization

PostPosted: Sat May 24, 2008 4:18 am
by kurianthayil
Hi,
Thanks for the info. But to reset the kernel Preemption value, we need to re-compile the kernel. But we currently are able to make calls and the call disconnections comes to around 10%. Is this 10% call disconnection natural or can it reach a state where the call disconnection is 0% (nil)? Just curious. And in the asterisk log Im getting message like the ones below:

Unexpected control subclass '-1'


chan_local.c: No such extension/context XXYYXXYYXXYYXX48600053@default creating local channel


app_meetme.c: Unable to write frame to channel Local/78600053@default-8b00,2


Any idea what these means. Trying to resolve the issue somehow. I really appreciate your help and support. Thank you in advance.

Regards,

Kurian Mathew Thayil.

PostPosted: Sat May 24, 2008 12:36 pm
by mflorell
The first one is fairly normal, the second one is one of your agents trying to change their volume, but something is configured wrong and the third one can be caused by all sorts of reasons from bandwidth issues to high system load.

PostPosted: Sat May 24, 2008 3:50 pm
by pylinuxian
But to reset the kernel Preemption value, we need to re-compile the kernel


if I folow the scratch install recompiling the kernel is step 1 & one of the rare steps where the words (VERY IMPORTANT) are mentioned together ...

let me guess what happens when you don't do step 1 & start with step 2 instead .... you get errors even the developper himself never had , you loose money because you system isn't acting as it is supposed to.

Centos have their own way to recompile - just follow it (only a bunch of yum something & you're finished) and you lose nothing as you can always boot your old kernel.