Eric "ManxPower" Wieling wrote:
Lee Jenkins wrote:
Stephen Bosch wrote:
Lee Jenkins wrote:
I forgot to mention that the one thing that seems to be consistent is
that I can get the zap line to reset and dialout again correctly by
calling into the system on that zap line, dialing and extension and
allowing the extension to hangup on the caller first.
Then it will dial out again. Odd.
Well, not really -- when the extension hangs up, Asterisk knows the
channel has been abandoned and clears it.
When the remote party hangs up first, the card doesn't tell Asterisk
that the channel is clear (because it doesn't know the caller has hung
up), so Asterisk has no idea and presumes it is unavailable.
Interesting. But if that was the case, wouldn't restarting asterisk
(#CLI restart now) clear the problem? Because on my system, it does
not clear the problem, only a complete restart of the server seems to
work. Well that and trying again some considerable time later which
may or may not work then.
Asterisk does not terminate active calls when doing a "reload". I
assume Asterisk thinks there is an active call on that port.
_______________________________________________
Hi Eric,
I did a restart, not a reload. Actually I've tried restarting the
server and where I originally thought it did reset, only randomly will
restarting the whole server actually work.
--
Warm Regards,
Lee
_______________________________________________
--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
