[asterisk-users] Failed to read gains: Invalid argument
Hi, all , hope u all are good and fine . me getting new error which i am pasting below.. This will came when i am reloading the asterisk. i also tried [reload chan_zap.so ] on asterisk cli, then out is same as i mention below, i there is any misconfiguration in zapata.conf?? i am posting below mine zapta.conf. hope that we help u to solve it . Thanks a lot... aman DhallY [Jul 9 14:52:41] WARNING[32279] chan_zap.c: Ignoring signalling [Jul 9 14:52:41] WARNING[32279] chan_zap.c: Ignoring rxwink [Jul 9 14:52:41] WARNING[32279] chan_zap.c: Ignoring switchtype [Jul 9 14:52:41] WARNING[32279] chan_zap.c: Ignoring signalling [Jul 9 14:52:41] WARNING[32279] chan_zap.c: Ignoring pridialplan [Jul 9 14:52:41] WARNING[32279] chan_zap.c: Ignoring resetinterval [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 1, ISDN PRI signalling [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 2, ISDN PRI signalling [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 3, ISDN PRI signalling [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 4, ISDN PRI signalling [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 5, ISDN PRI signalling [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 6, ISDN PRI signalling [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 7, ISDN PRI signalling [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 8, ISDN PRI signalling [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 9, ISDN PRI signalling [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 10, ISDN PRI signalling [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 11, ISDN PRI signalling [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 12, ISDN PRI signalling [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 13, ISDN PRI signalling [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 14, ISDN PRI signalling [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 15, ISDN PRI signalling [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 17, ISDN PRI signalling [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 18, ISDN PRI signalling [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 19, ISDN PRI signalling [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 20, ISDN PRI signalling [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 21, ISDN PRI signalling [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 22, ISDN PRI signalling [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 23, ISDN PRI signalling [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 24, ISDN PRI signalling [Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument [Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 25, ISDN PRI signalling [Jul 9 14:52:41]
RE: [Asterisk-Users] Failed to read gains: Invalid argument
On 3/22/06, Mimmus [EMAIL PROTECTED] wrote: What are these error messages? Mar 22 17:41:10 DEBUG[3592] chan_zap.c: Failed to read gains: Invalid argument Mar 22 17:41:10 DEBUG[3592] chan_zap.c: Failed to read gains: Invalid argument Mar 22 17:41:10 DEBUG[3592] chan_zap.c: Updated conferencing on 1, with 0 conference users Mar 22 17:41:10 VERBOSE[3592] logger.c: -- Registered channel 1, PRI Signalling signalling ... (for all channels) that means chan_zap is not communicating well with zaptel driver. I have never had that problem with zapata, wich version of asteris are you using? Post more relevant configuration of zapata.conf, like the channels configured, does ztcfg gives any errors? This is my setup: PSTN PRI E1 --- Asterisk --- Crossed E1 cable --- Alcatel PBX Asterisk v.1.2.1 with a Sangoma A102 card (wanpipe driver v. beta1-2.3.4) 'ztcfg -vv' gives no error. # wanpipe1.conf [devices] wanpipe1 = WAN_AFT, Comment [interfaces] w1g1 = wanpipe1, , TDM_VOICE, Comment [wanpipe1] CARD_TYPE = AFT S514CPU = A CommPort= PRI AUTO_PCISLOT= NO PCISLOT = 1 PCIBUS = 6 FE_MEDIA= E1 FE_LCODE= HDB3 FE_FRAME= CRC4 FE_LINE = 1 TE_CLOCK= NORMAL TE_REF_CLOCK= 0 TE_HIGHIMPEDANCE= NO FE_TXTRISTATE = NO MTU = 1500 UDPPORT = 9000 TTL = 255 IGNORE_FRONT_END = NO TDMV_SPAN = 1 TDMV_DCHAN = 0 TDMV_HWEC = NO [w1g1] ACTIVE_CH = ALL TDMV_ECHO_OFF = NO # zaptel.conf: span=1,1,2,ccs,hdb3,crc4,yellow span=2,0,2,ccs,hdb3 bchan = 1-15, 17-31 dchan = 16 bchan = 32-46,48-62 dchan = 47 loadzone= it defaultzone = it # zapata.conf: [trunkgroups] [channels] language=it switchtype=euroisdn pridialplan=dynamic prilocaldialplan=local overlapdial=yes internationalprefix=00 nationalprefix=0 localprefix=omissis privateprefix=omissis unknownprefix= priindication=inband facilityenable=yes rxgain=0.0 txgain=0.0 jitterbuffers=2 usecallerid=yes hidecallerid=no callwaiting=yes callwaitingcallerid=yes usecallingpres=yes useincomingcalleridonzaptransfer=yes threewaycalling=yes transfer=yes cancallforward=yes callreturn=yes echocancel=yes echocancelwhenbridged=yes echotraining=800 immediate=no callerid=asreceived musiconhold=native-random ; Incoming only group=0 signalling=pri_cpe context=from-pstn faxdetect=incoming channel = 1-10 ; Outgoing only group=1 faxdetect=no channel = 11-15,17-21 ; Not used group=3 faxdetect=no channel = 22-31 ; To/From Alcatel group=2 signalling=pri_net faxdetect=no context=from-alcatel channel = 32-46,48-62 Thanks Mimmus ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Failed to read gains: Invalid argument
On 03/23/06 16:45 Mimmus said the following: This is my setup: PSTN PRI E1 --- Asterisk --- Crossed E1 cable --- Alcatel PBX Asterisk v.1.2.1 with a Sangoma A102 card (wanpipe driver v. beta1-2.3.4) 'ztcfg -vv' gives no error. that's probably an issue with the sangoma wanpipe drivers than it is with asterisk. the wanpipe drivers have probably not marked the channel with ZT_FLAG_AUDIO or it hasnt registered the channels with the zaptel driver. i've seen this happen on a sangoma AFT101 with the latest drivers, version 2.8.4. -- Regards, /\_/\ All dogs go to heaven. [EMAIL PROTECTED](0 0)http://www.alphaque.com/ +==oOO--(_)--OOo==+ | for a in past present future; do| | for b in clients employers associates relatives neighbours pets; do | | echo The opinions here in no way reflect the opinions of my $a $b. | | done; done | +=+ ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[Asterisk-Users] Failed to read gains: Invalid argument
What are these error messages? Mar 22 17:41:10 DEBUG[3592] chan_zap.c: Failed to read gains: Invalid argument Mar 22 17:41:10 DEBUG[3592] chan_zap.c: Failed to read gains: Invalid argument Mar 22 17:41:10 DEBUG[3592] chan_zap.c: Updated conferencing on 1, with 0 conference users Mar 22 17:41:10 VERBOSE[3592] logger.c: -- Registered channel 1, PRI Signalling signalling Mar 22 17:41:10 DEBUG[3592] chan_zap.c: Failed to read gains: Invalid argument Mar 22 17:41:10 DEBUG[3592] chan_zap.c: Failed to read gains: Invalid argument Mar 22 17:41:10 DEBUG[3592] chan_zap.c: Updated conferencing on 2, with 0 conference users Mar 22 17:41:10 VERBOSE[3592] logger.c: -- Registered channel 2, PRI Signalling signalling ... (for all channels) I have a PRI E1 line configured with: txgain=0.0 rxgain=0.0 in zapata.conf. -- Mimmus ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Failed to read gains: Invalid argument
that means chan_zap is not communicating well with zaptel driver. I have never had that problem with zapata, wich version of asteris are you using? Post more relevant configuration of zapata.conf, like the channels configured, does ztcfg gives any errors? Regards On 3/22/06, Mimmus [EMAIL PROTECTED] wrote: What are these error messages? Mar 22 17:41:10 DEBUG[3592] chan_zap.c: Failed to read gains: Invalid argument Mar 22 17:41:10 DEBUG[3592] chan_zap.c: Failed to read gains: Invalid argument Mar 22 17:41:10 DEBUG[3592] chan_zap.c: Updated conferencing on 1, with 0 conference users Mar 22 17:41:10 VERBOSE[3592] logger.c: -- Registered channel 1, PRI Signalling signalling Mar 22 17:41:10 DEBUG[3592] chan_zap.c: Failed to read gains: Invalid argument Mar 22 17:41:10 DEBUG[3592] chan_zap.c: Failed to read gains: Invalid argument Mar 22 17:41:10 DEBUG[3592] chan_zap.c: Updated conferencing on 2, with 0 conference users Mar 22 17:41:10 VERBOSE[3592] logger.c: -- Registered channel 2, PRI Signalling signalling ... (for all channels) I have a PRI E1 line configured with: txgain=0.0 rxgain=0.0 in zapata.conf. -- Mimmus ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- Su nombre es GNU/Linux, no solamente Linux, mas info en http://www.gnu.org; ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[Asterisk-Users] Failed to read gains: Invalid argument
Hello,When I start Asterisk, I get the following in my log (/var/log/asterisk/full):Mar 15 17:16:55 VERBOSE[4242] logger.c: == Parsing '/etc/asterisk/zapata.conf': Mar 15 17:16:55 VERBOSE[4242] logger.c: == Parsing '/etc/asterisk/zapata.conf': FoundMar 15 17:16:55 DEBUG[4242] chan_zap.c: Failed to read gains: Invalid argumentMar 15 17:16:55 DEBUG[4242] chan_zap.c: Failed to read gains: Invalid argumentMar 15 17:16:55 DEBUG[4242] chan_zap.c: Updated conferencing on 1, with 0 conference usersMar 15 17:16:55 VERBOSE[4242] logger.c: -- Registered channel 1, PRI Signalling signallingMar 15 17:16:55 DEBUG[4242] chan_zap.c: Failed to read gains: Invalid argumentMar 15 17:16:55 DEBUG[4242] chan_zap.c: Failed to read gains: Invalid argumentMar 15 17:16:55 DEBUG[4242] chan_zap.c: Updated conferencing on 2, with 0 conference usersMar 15 17: 16:55 VERBOSE[4242] logger.c: -- Registered channel 2, PRI Signalling signallingMar 15 17:16:55 DEBUG[4242] chan_zap.c: Failed to read gains: Invalid argumentMar 15 17:16:55 DEBUG[4242] chan_zap.c: Failed to read gains: Invalid argumentMar 15 17:16:55 DEBUG[4242] chan_zap.c: Updated conferencing on 3, with 0 conference usersMar 15 17:16:55 VERBOSE[4242] logger.c: -- Registered channel 3, PRI Signalling signallingMar 15 17:16:55 DEBUG[4242] chan_zap.c: Failed to read gains: Invalid argumentMar 15 17:16:55 DEBUG[4242] chan_zap.c: Failed to read gains: Invalid argumentMar 15 17:16:55 DEBUG[4242] chan_zap.c: Updated conferencing on 4, with 0 conference usersMar 15 17:16:55 VERBOSE[4242] logger.c: -- Registered channel 4, PRI Signalling signallingMar 15 17:16:55 DEBUG[4242] chan_zap.c: Failed to read gains: Invalid argumentMar 15 17:16:55 DEBUG[4242] chan_zap.c: Failed to rea d gains: Invalid argumentMar 15 17:16:55 DEBUG[4242] chan_zap.c: Updated conferencing on 5, with 0 conference usersMar 15 17:16:55 VERBOSE[4242] logger.c: -- Registered channel 5, PRI Signalling signallingMar 15 17:16:55 DEBUG[4242] chan_zap.c: Failed to read gains: Invalid argumentMar 15 17:16:55 DEBUG[4242] chan_zap.c: Failed to read gains: Invalid argumentMar 15 17:16:55 DEBUG[4242] chan_zap.c: Updated conferencing on 6, with 0 conference usersMar 15 17:16:55 VERBOSE[4242] logger.c: -- Registered channel 6, PRI Signalling signallingMar 15 17:16:55 DEBUG[4242] chan_zap.c: Failed to read gains: Invalid argumentMar 15 17:16:55 DEBUG[4242] chan_zap.c: Failed to read gains: Invalid argumentMar 15 17:16:55 DEBUG[4242] chan_zap.c: Updated conferencing on 7, with 0 conference usersMar 15 17:16:55 VERBOSE[4242] logger.c: -- Registered channel 7, PRI Signalling signallingMar 1 5 17:16:55 DEBUG[4242] chan_zap.c: Failed to read gains: Invalid argumentMar 15 17:16:55 DEBUG[4242] chan_zap.c: Failed to read gains: Invalid argumentMar 15 17:16:55 DEBUG[4242] chan_zap.c: Updated conferencing on 8, with 0 conference usersMar 15 17:16:55 VERBOSE[4242] logger.c: -- Registered channel 8, PRI Signalling signallingMar 15 17:16:55 DEBUG[4242] chan_zap.c: Failed to read gains: Invalid argumentMar 15 17:16:55 DEBUG[4242] chan_zap.c: Failed to read gains: Invalid argumentMar 15 17:16:55 DEBUG[4242] chan_zap.c: Updated conferencing on 9, with 0 conference usersMar 15 17:16:55 VERBOSE[4242] logger.c: -- Registered channel 9, PRI Signalling signallingMar 15 17:16:55 DEBUG[4242] chan_zap.c: Failed to read gains: Invalid argumentMar 15 17:16:55 DEBUG[4242] chan_zap.c: Failed to read gains: Invalid argumentMar 15 17:16:55 DEBUG[4242] chan_zap.c: Updated conferencing on 10, with 0 confe rence usersMar 15 17:16:55 VERBOSE[4242] logger.c: -- Registered channel 10, PRI Signalling signalling What does this log mean?My zapata.conf is [channels]language = encontext = incominggroup = 1signalling = pri_netswitchtype = dms100callerid = asreceived underrxwink = 300usecallerid = yeshidecallerid = nocallwaiting = yesusecallingpres = yesthreewaycalling = yestransfer = yescancallforward = yescallreturn = yesechocancel = yesechocancelwhenbridged = yesechotraining = 400rxgain = 0.0txgain = 0.0callgroup = 1pickupgroup = 1immediate = nochannel = 1-23 Thanks in advance.richard ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Failed to read gains: Invalid argument
Richard OSS wrote: rxgain= 0.0 txgain= 0.0 callgroup = 1 pickupgroup = 1 immediate = no channel = 1-23 Where did you find any example that suggested using '=' for every setting was appropriate? It's not. Use '=' for normal settings, and '=' for assigning channel numbers. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Failed to read gains: Invalid argument
Ooops...I thought I'd clean up my config files and check for typos. Turns out I was making my problems worse. grinAm surprised As terisk does not complain. Another thing happened to me also. I typed [channel] instead of [channels]. ztcfg looked ok. Asterisk did not complain when started. It just did not create the channels.Learning a lot. It's painful but fun.Thanks.richard"Kevin P. Fleming" [EMAIL PROTECTED] wrote: Richard OSS wrote: rxgain = 0.0 txgain = 0.0 callgroup = 1 pickupgroup = 1 immediate = no channel = 1-23Where did you find any example that suggested using '=' for everysetting was appropriate? It 's not. Use '=' for normal settings, and '='for assigning channel numbers.___--Bandwidth and Colocation provided by Easynews.com --Asterisk-Users mailing listTo UNSUBSCRIBE or update options visit:http://lists.digium.com/mailman/listinfo/asterisk-users___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
