All installation and configuration problems and questions
Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N
by farish » Fri May 18, 2007 9:21 pm
i am getting this warning some times in the asterisk consoles .....some times it never stop , until hangup the channel, what is the couse of that warning? i am using asterisk 1.2.17 and astguiclient 2.0.3...
- Code: Select all
May 19 06:44:54 WARNING[32177]: app_meetme.c:1560 conf_run: Unable to write frame to channel Local/8600053@default-262a,2
May 19 06:44:54 WARNING[32177]: app_meetme.c:1560 conf_run: Unable to write frame to channel Local/8600053@default-262a,2
May 19 06:44:54 WARNING[32177]: app_meetme.c:1560 conf_run: Unable to write frame to channel Local/8600053@default-262a,2
May 19 06:44:54 WARNING[32177]: app_meetme.c:1560 conf_run: Unable to write frame to channel Local/8600053@default-262a,2
May 19 06:44:54 WARNING[32177]: app_meetme.c:1560 conf_run: Unable to write frame to channel Local/8600053@default-262a,2
May 19 06:44:54 WARNING[32177]: app_meetme.c:1560 conf_run: Unable to write frame to channel Local/8600053@default-262a,2
May 19 06:44:54 WARNING[32177]: app_meetme.c:1560 conf_run: Unable to write frame to channel Local/8600053@default-262a,2
May 19 06:44:54 WARNING[32177]: app_meetme.c:1560 conf_run: Unable to write frame to channel Local/8600053@default-262a,2
May 19 06:55:50 WARNING[3776]: app_meetme.c:1560 conf_run: Unable to write frame to channel Local/78600055@default-4c4f,2
thanks
farish
-
farish
-
- Posts: 17
- Joined: Tue Apr 24, 2007 4:39 pm
by prabhakar_asterisk » Fri May 18, 2007 11:24 pm
what type of timer you are using..it normally happens with ztdummy..
i didnt get this after going for beta version of astguiclient.
-
prabhakar_asterisk
-
- Posts: 79
- Joined: Sun Aug 06, 2006 11:09 pm
-
by ramindia » Fri May 18, 2007 11:32 pm
Hi
its pure on ztdummy driver problem
i seen many of my clients place
when the timer is not set to 1000Hz
this this kind of problems persists
what is the OS
what is zaptel and asterisk version
what is the kernel version
so kindly get timer cards to solve this problem
ram
-
ramindia
-
- Posts: 688
- Joined: Wed Oct 11, 2006 4:06 am
- Location: India
by prabhakar_asterisk » Fri May 18, 2007 11:36 pm
hi ram,
i had this problem before but i didnt get this after going for beta version of astguiclient...
-
prabhakar_asterisk
-
- Posts: 79
- Joined: Sun Aug 06, 2006 11:09 pm
-
by ramindia » Sat May 19, 2007 1:17 am
Hi
what version of AGC ?
what is your OS and kernel version
its very important
so we can make point of this
ram
-
ramindia
-
- Posts: 688
- Joined: Wed Oct 11, 2006 4:06 am
- Location: India
by farish » Sat May 19, 2007 11:40 am
I am using digium TDM400P as timing device...
and AGC 2.0.3 and asterisk 1.2.17
OS : Debian etch with 2.6.18-4-686 kernel
i have the same problem coming some times if i use ztdummy in the other server which does not have any digium card installed
thanks
-
farish
-
- Posts: 17
- Joined: Tue Apr 24, 2007 4:39 pm
by ramindia » Sat May 19, 2007 12:36 pm
Hi
Ztdummy driver should work with 1000hz
thats what i tested , i dont see any errors as of now.
FC5 x86_64
SVN asterisk 1.2
SVN Zaptel 1.2
SVN AGC
iam also trying with debian
i will get back to you , if i get any errors like this
ram
-
ramindia
-
- Posts: 688
- Joined: Wed Oct 11, 2006 4:06 am
- Location: India
by saqibali » Wed Nov 28, 2007 11:13 am
i am also getting this error but i found that when there are more than 150 calls per second ... thats happen often
astguiclient version 2.0.2
OS centos 5
asterisk 1.2.18
zaptel 1.2.18
using TE420B cards
System Dell 2950
when i got this warrnig
Nov 27 18:19:01 WARNING[14911]: app_meetme.c:1570 conf_run: Unable to write frame to channel Local/8600123@default-1930,2
i also try to kick that paticular conference number but no avail .. and when this warning showing up in the CLI the calls are overlapping between agents.Any suggestion regarding this issue.
-
saqibali
-
- Posts: 48
- Joined: Wed Nov 22, 2006 7:48 pm
by gardo » Wed Nov 28, 2007 1:13 pm
try upgrading to asterisk 1.2.24 and see if that problem still persists.
-
gardo
-
- Posts: 1926
- Joined: Fri Sep 15, 2006 10:24 am
- Location: Manila, 1004
-
Return to Support
Who is online
Users browsing this forum: No registered users and 130 guests