[EMAIL PROTECTED] wrote:
> 
> > ...At first I thought it would happen after a few days of operation
> > but more recently I noted that it always stops working after a
> > failed call.
> 
> You guys do know that diald goes into blocked mode after some number
> of failed calls, right?
> 
> I don't know if the default settings have changed (I haven't had it do
> this my newer installs), but it used to be three failed calls and
> you're out.  It's all configurable (of course!); and there's no need
> to restart diald, just echo unblock >diald.ctl.
> 
> <Joe
> 
> -

Yes, I am aware of that situation also, but I don't think this is
what was happening to me when I moved up to 0.99.2. After all, it
did start when I went to 0.99.2 and stop when I went back to 0.99.1.

I'm not sure what state diald got itself into but, if I remember
correctly, dctrl, when iconized, showed the bottom two lights both
yellow. I think it reported the state as "down". I also vaguely 
remember that the last message in the dctrl information window was
"trigger: udp" and there was no "calling site" message following
that.

-- 
____________________________________________________________________
Robert Paulsen                         http://paulsen.home.texas.net

-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]

Reply via email to