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

[Lee Archer]

Yes I get the same message after reload chan_zap.so

Regards

Lee 

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Tzafrir
Cohen
Sent: 05 January 2007 08:53
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] chan_zap.c: Failed to read gains:
Invalidargument

On Fri, Jan 05, 2007 at 07:47:15AM -0000, Lee Archer wrote:
> 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

This is a debug message and not even a warning message. I'm not sure
that this is something to worry about.

The code there tries to first read the gains and set the gains based on
them. The return value from the ioctl that sets the gains does not seem
to be checked in several code pathes, though. So it may actually fail
silently.

Do you get the same debug messages on 'reload chan_zap.so' ?

-- 
               Tzafrir Cohen       
icq#16849755                    jabber:tzafrir at jabber.org
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com       
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir
_______________________________________________
--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
###########################################

This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.f-secure.com/