Use the latest callweaver SVN and simply put "polarityevents=no" in zapata.conf for the relevant channel. See the latest zapata.conf.sample for details.
Mind you, non-detection of caller ID shouldn't leave garbage in the vars. I'll have a look... N.B. X100Ps don't support the complex impedance used for UK lines (HW limitation) so balancing RX gain, TX gain and echo can be "interesting". TDM400s and clones work fine - and have polarity detection (which needs a zaptel driver patch to stop it screwing up) Mike On Sun, May 20, 2007 at 05:49:00PM +0100, Steve Hill wrote: > > I have an X100P card running with the Zaptel 1.4.2.1 driver (patched with > the use_hist patch from http://www.lusyn.com/resources/asterisk/index.htm) > and CallWeaver 1.2.svn.2762. > > When a call comes in from the X100P card, I have an OGI script which does > 'GET VARIABLE "CALLERID(num)"' and 'GET VARIABLE "CALLERID(name)'. Both > caller ID variables are returned with garbage contents - looks like > uninitialised memory. > > It does not appear to matter whether I set "usecallerid" to yes or no in > my zapata.conf file. I've tried it with both a plain CallWeaver and a > CallWeaver with the use_hist patch and I get the same in both cases. I've > not yet tried running the plain unpatched zaptel kernel module, but I > suspect I will get the same results since the "usecallerid" flag doesn't > affect it. > > The caller ID stuff works fine for SIP and IAX2 - it looks like it's only > affecting the ZapTel device. -- Mike Jagdis Web: http://www.eris-associates.co.uk Eris Associates Limited Tel: +44 7780 608 368 Reading, England Fax: +44 118 926 6974 _______________________________________________ Callweaver-users mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-users
