[VoIP] Progress, I suppose.

[ikjtel]

--- John Novack <jnovack at stromberg-carlson.org> wrote:

> ... though it seems that the pulse dial
> problem has reappeared.

Hey John

That's interesting....   What symptom exactly are you
seeing?

Which hardware driver(s) are you using?  All from the
"offical" asterisk/zaptel package, or are you using
"third-party" drivers?  (tsk tsk)

In any case the T1 path does not lead thru wctdm.c at
all, so the older "rotary dialing" patch (to halve the
debounce time) wouldn't even apply to this situation. 
It's tempting to imagine that there might be an
analogous bug in the T1 stuff, but wctdm appears to be
the only one that even bothers to debounce/filter the
signals before sending them to the zaptel core... 
(Assuming you're using the standard wct1xxp/wct4xxp
ones).

This suggests that your problem may be unrelated to
the earlier one.  Regardless, it should be a simple
matter to add "printk" statements to diagnose it (as
Kirt did last time)....

Any case where rotary dials aren't working perfectly
is an offense against the General Order, and must be
eliminated.

Max

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com