<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>chan_zap.c: Failed to read gains: Invalid argument</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><FONT SIZE=2 FACE="Arial">I am running Asterisk 1.2.14 and Zaptel 1.2.12 and using a Digium TE110P card in E1 mode. I've recently noticed in my logs the following</FONT></P>
<P><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 VERBOSE[22490] logger.c: [chan_zap.so]Jan 5 01:27:11 VERBOSE[22490] logger.c: [chan_zap.so] => (Zapata Telephony w/PRI)</FONT></P>
<P><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 VERBOSE[22490] logger.c: == Parsing '/etc/asterisk/zapata.conf': Jan 5 01:27:11 VERBOSE[22490] logger.c: == Parsing '/etc/asterisk/zapata.conf': Found</FONT></P>
<P><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid argument</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid argument</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Updated conferencing on 1, with 0 conference users</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 VERBOSE[22490] logger.c: -- Registered channel 1, PRI Signalling signalling</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid argument</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid argument</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Updated conferencing on 2, with 0 conference users</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 VERBOSE[22490] logger.c: -- Registered channel 2, PRI Signalling signalling</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid argument</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid argument</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Updated conferencing on 3, with 0 conference users</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 VERBOSE[22490] logger.c: -- Registered channel 3, PRI Signalling signalling</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid argument</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid argument</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Updated conferencing on 4, with 0 conference users</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 VERBOSE[22490] logger.c: -- Registered channel 4, PRI Signalling signalling</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid argument</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid argument</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Updated conferencing on 5, with 0 conference users</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 VERBOSE[22490] logger.c: -- Registered channel 5, PRI Signalling signalling</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid argument</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid argument</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Updated conferencing on 6, with 0 conference users</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 VERBOSE[22490] logger.c: -- Registered channel 6, PRI Signalling signalling</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid argument</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid argument</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Updated conferencing on 7, with 0 conference users</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 VERBOSE[22490] logger.c: -- Registered channel 7, PRI Signalling signalling</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid argument</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid argument</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 DEBUG[22490] chan_zap.c: Updated conferencing on 8, with 0 conference users</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 VERBOSE[22490] logger.c: -- Registered channel 8, PRI Signalling signalling</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 VERBOSE[22490] logger.c: -- Automatically generated pseudo channel</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jan 5 01:27:11 VERBOSE[22490] logger.c: == Starting D-Channel on span 1</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">Which seems to suggest that I've done something wrong with the rx and txgain option in /etc/asterisk/zapata.conf. But these haven't been changed in 18 months and still say</FONT></P>
<P><FONT SIZE=2 FACE="Arial">; You may also set the default receive and transmit gains (in dB)</FONT>
<BR><FONT SIZE=2 FACE="Arial">;</FONT>
<BR><FONT SIZE=2 FACE="Arial">rxgain=4.0</FONT>
<BR><FONT SIZE=2 FACE="Arial">txgain=0.0</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">Have I done something wrong or has something changed?</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">Thanks</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">Lee</FONT>
</P>
###########################################<br><br>This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.<br>For more information, connect to http://www.f-secure.com/</BODY>
</HTML>