[asterisk-users] chan_zap.c: Failed to read gains: Invalid argument

Lee Archer lee.archer at pentagon-systems.com
Fri Jan 5 00:47:15 MST 2007


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

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)
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
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid
argument
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid
argument
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Updated conferencing on 1, with
0 conference users
Jan  5 01:27:11 VERBOSE[22490] logger.c:     -- Registered channel 1,
PRI Signalling signalling
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid
argument
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid
argument
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Updated conferencing on 2, with
0 conference users
Jan  5 01:27:11 VERBOSE[22490] logger.c:     -- Registered channel 2,
PRI Signalling signalling
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid
argument
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid
argument
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Updated conferencing on 3, with
0 conference users
Jan  5 01:27:11 VERBOSE[22490] logger.c:     -- Registered channel 3,
PRI Signalling signalling
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid
argument
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid
argument
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Updated conferencing on 4, with
0 conference users
Jan  5 01:27:11 VERBOSE[22490] logger.c:     -- Registered channel 4,
PRI Signalling signalling
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid
argument
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid
argument
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Updated conferencing on 5, with
0 conference users
Jan  5 01:27:11 VERBOSE[22490] logger.c:     -- Registered channel 5,
PRI Signalling signalling
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid
argument
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid
argument
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Updated conferencing on 6, with
0 conference users
Jan  5 01:27:11 VERBOSE[22490] logger.c:     -- Registered channel 6,
PRI Signalling signalling
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid
argument
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid
argument
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Updated conferencing on 7, with
0 conference users
Jan  5 01:27:11 VERBOSE[22490] logger.c:     -- Registered channel 7,
PRI Signalling signalling
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid
argument
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Failed to read gains: Invalid
argument
Jan  5 01:27:11 DEBUG[22490] chan_zap.c: Updated conferencing on 8, with
0 conference users
Jan  5 01:27:11 VERBOSE[22490] logger.c:     -- Registered channel 8,
PRI Signalling signalling
Jan  5 01:27:11 VERBOSE[22490] logger.c:     -- Automatically generated
pseudo channel
Jan  5 01:27:11 VERBOSE[22490] logger.c:   == Starting D-Channel on span
1

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

; You may also set the default receive and transmit gains (in dB)
;
rxgain=4.0
txgain=0.0

Have I done something wrong or has something changed?

Thanks

Lee
###########################################

This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.f-secure.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070105/e829a0f7/attachment.htm


More information about the asterisk-users mailing list