Hi Mike, Mike Jagdis wrote: > On Mon, May 21, 2007 at 11:42:23AM +0100, Steve Hill wrote: > >> On Mon, 21 May 2007, Mike Jagdis wrote: >> >> >>> 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. >>> >> Does that do the same job as "cidstart=usehist"? The usehist patch for >> Asterisk 1.2 seemed to apply cleanly once I'd renamed various variables in >> it (and it works) >> > > Sort of. Same effect, slightly different way of doing it. > > Apparently there's absolutely no chance of the history patches ever > becoming standard in zaptel (or in asterisk for that matter). > > Callweaver's (standard) polarityevents=no simply tells chan_zap to > monitor that line continuously (i.e. pre-ring and don't expect a > polarity event wake up because they either don't happen or they're > not detectable). > > polarityevents=no also works for non-X100Ps plugged in to whacky > telcos that send pre-ring callerid with no warning. (Apparently > they really do exist!) > > Mike > >
That might fix his problem, but why did he got garbage in the strings. Surely they should be set to something clean. I haven't heard back whether my changes to spandsp to handle the additional forms of DTMF CLI have solved the Kuwait guy's problem. I think he needed entry to terminate on the "C" for things to work. If things work for him now, we can clean up your patch to use spandsp to break up the strings in a DTMF caller ID. Regards, Steve _______________________________________________ Callweaver-users mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-users
