I've just finished updating my Asterisk to the CVS version. Unfortunately, chan_zap won't load anymore. The hardware has not changed and the config files have not changed. I can re-install the two packages back and forth. The old one will still work. The new one won't. I tried updating to a brand-new zaptel and wcfxo modules, with no difference. This has got to be the most frustrating thing about dealing with Asterisk. This is also the same error I get trying to get the FXS cards to work (I have never succeeded). There must be something else in the Makefile or configuration files. Is there anything different regarding zap interfaces in the config files since maybe 3 months ago? The other differences I noticed were the modules chan_alsa.so, chan_oss.so (which didn't appear to be there before, or maybe in a different order), and a new requirement for libpri.so Same error message: [chan_zap.so] => (Zapata Telephony w/PRI) == Parsing '/etc/asterisk/zapata.conf': Found DEBUG[16384]: File chan_zap.c, Line 1043 (update_conf): Updated conferencing on 1, with 0 conference users ERROR[16384]: File chan_zap.c, Line 5287 (mkintf): Unable to get span status: Inappropriate ioctl for device ERROR[16384]: File chan_zap.c, Line 6838 (load_module): Unable to register channel '1' WARNING[16384]: File loader.c, Line 305 (ast_load_resource): chan_zap.so: load_module failed, returning -1 WARNING[16384]: File loader.c, Line 400 (load_modules): Loading module chan_zap.so failed! zapata.conf: [channels] echocancelwhenbridged=yes echocancel=yes stripmsd=1 callerid=asreceived language=en context=incoming3121 signalling=fxs_ks rxgain=3.0 txgain=0.0 usecallerid=yes group=1 channel=1 echocancelwhenbridged=yes echocancel=yes stripmsd=1 usecallerid=no callwaiting=no callerid="intercom" <9876543210> context=incoming3130 language=en signalling=fxs_ks group=1 channel=2 zaptel.conf can be blank or: loadzone=us defaultzone=us fxoks=1-2
Matt,> I've just finished updating my Asterisk to the CVS version. > Unfortunately, chan_zap won't load anymore. > > The hardware has not changed and the config files have not changed. I > can re-install the two packages back and forth. The old one will still > work. The new one won't. I tried updating to a brand-new zaptel and > wcfxo modules, with no difference. This has got to be the most > frustrating thing about dealing with Asterisk. This is also the same > error I get trying to get the FXS cards to work (I have never succeeded). > > There must be something else in the Makefile or configuration files. Is > there anything different regarding zap interfaces in the config files > since maybe 3 months ago?I had the same problem the other day. Resolved it by essentially blowing away the existing src directories (rename them if you want) and doing a new cvs checkout. I know I seen someone post something a month or two ago relative to using a cvs flag to effectively over-write everything on the local system. Guess we're all supposed to be linux cvs experts. In my case, I was simply trying to do an update to asterisk (without zaptel, zapata, etc), and that didn't work since some constants were apparently defined in some non-asterisk header file (zaptel, I think, but I didn't bother to search it out) that were needed in one of the channels modules. Sounds like you've bumped against the same issue.
make sure the modules for your boards are loaded. ztcfg -vv shouldn't return with any errors. regards Martin On Fri, 14 Nov 2003, Matt Lawson wrote:> I've just finished updating my Asterisk to the CVS version. > Unfortunately, chan_zap won't load anymore. > > The hardware has not changed and the config files have not changed. I > can re-install the two packages back and forth. The old one will still > work. The new one won't. I tried updating to a brand-new zaptel and > wcfxo modules, with no difference. This has got to be the most > frustrating thing about dealing with Asterisk. This is also the same > error I get trying to get the FXS cards to work (I have never succeeded). > > There must be something else in the Makefile or configuration files. Is > there anything different regarding zap interfaces in the config files > since maybe 3 months ago? > > The other differences I noticed were the modules chan_alsa.so, > chan_oss.so (which didn't appear to be there before, or maybe in a > different order), and a new requirement for libpri.so > > Same error message: > > [chan_zap.so] => (Zapata Telephony w/PRI) > == Parsing '/etc/asterisk/zapata.conf': Found > DEBUG[16384]: File chan_zap.c, Line 1043 (update_conf): Updated > conferencing on 1, with 0 conference users > ERROR[16384]: File chan_zap.c, Line 5287 (mkintf): Unable to get span > status: Inappropriate ioctl for device > ERROR[16384]: File chan_zap.c, Line 6838 (load_module): Unable to > register channel '1' > WARNING[16384]: File loader.c, Line 305 (ast_load_resource): > chan_zap.so: load_module failed, returning -1 > WARNING[16384]: File loader.c, Line 400 (load_modules): Loading module > chan_zap.so failed! > > zapata.conf: > [channels] > echocancelwhenbridged=yes > echocancel=yes > stripmsd=1 > callerid=asreceived > language=en > context=incoming3121 > signalling=fxs_ks > rxgain=3.0 > txgain=0.0 > usecallerid=yes > group=1 > channel=1 > > > echocancelwhenbridged=yes > echocancel=yes > stripmsd=1 > usecallerid=no > callwaiting=no > callerid="intercom" <9876543210> > context=incoming3130 > language=en > signalling=fxs_ks > group=1 > channel=2 > > > zaptel.conf can be blank or: > > loadzone=us > defaultzone=us > fxoks=1-2 > > > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users >
Matt Lawson
2003-Nov-18 11:35 UTC
[Asterisk-Users] Re: chan_zap won't load after CVS update
Ah ha. That's *almost* got it. It will now load and * will run. The
only big gotcha is it won't pick up or dial out on a POTS line. ztcfg
shows both channels configured OK, as does 'zap show channels.' If I
try to dial out I get:
-- Executing Goto("SIP/3063-74d0", "outside|9555|1") in
new
stack
-- Goto
(outside,9555,1)
-- Executing Dial("SIP/3063-74d0", "Zap/g1/ww954.......")
in new
stack
== Everyone is busy at this time
>I had the same problem the other day. Resolved it by essentially
>blowing away the existing src directories (rename them if you want) and
>doing a new cvs checkout. I know I seen someone post something a month
>or two ago relative to using a cvs flag to effectively over-write
>everything on the local system. Guess we're all supposed to be linux
>cvs experts.
>
>In my case, I was simply trying to do an update to asterisk (without
>zaptel, zapata, etc), and that didn't work since some constants were
>apparently defined in some non-asterisk header file (zaptel, I think,
>but I didn't bother to search it out) that were needed in one of the
>channels modules. Sounds like you've bumped against the same issue.
>
>
>
>
>Regards Mick West
>
>
>
>--__--__--
>
>_______________________________________________
>Asterisk-Users mailing list
>Asterisk-Users@lists.digium.com
>http://lists.digium.com/mailman/listinfo/asterisk-users
>
>
>End of Asterisk-Users Digest
>
>