I solved this problem. It turns out I had channel 21 listed twice in
my zaptel.conf.
I guess the 06/06/2003 CVS was more lenient.
On Thursday, August 7, 2003, at 04:31 PM, John Congdon wrote:
> Any suggestions would be great.
>
> No config files changed. I have been trying the latest cvs every
> few days for a few weeks now. I currently am using 06/06/2003.
>
>
> [root@pbx asterisk]# asterisk -c
> Asterisk CVS-08/07/03-15:43:33, Copyright (C) 1999-2001 Linux Support
> Services, Inc.
> Written by Mark Spencer <markster@linux-support.net>
> =======================================================================
> => [ Booting.......... -- Registered indication country 'us'
> -- Registered indication country 'au'
> -- Registered indication country 'fr'
> -- Registered indication country 'de'
> -- Registered indication country 'nl'
> -- Registered indication country 'uk'
> -- Setting default indication country to 'us'
> ........WARNING[16384]: File chan_iax2.c, Line 5064 (set_config):
> Ignoring port for now
> ...WARNING[16384]: File chan_zap.c, Line 577 (zt_open): Unable to
> specify channel 21: Device or resource busy
> ERROR[16384]: File chan_zap.c, Line 4781 (mkintf): Unable to open
> channel 21: Device or resource busy
> here = 0, tmp->channel = 0, channel = 21
> ERROR[16384]: File chan_zap.c, Line 6498 (load_module): Unable to
> register channel '18-19'
> WARNING[16384]: File loader.c, Line 299 (ast_load_resource):
> chan_zap.so: load_module failed, returning -1
> WARNING[16384]: File loader.c, Line 394 (load_modules): Loading module
> chan_zap.so failed!
> [root@pbx asterisk]# Ouch ... error while writing audio data: : Broken
> pipe
> Ouch ... error while writing audio data: : Broken pipe
> Ouch ... error while writing audio data: : Broken pipe
> Ouch ... error while writing audio data: : Broken pipe
>
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users