[asterisk-dev] Code hint to change ZAP behaviour

[John Lange]

I've seen this happen and we do not have any wireless phones.

It is relatively rare (14 times since April) and in only one case did
not channel not eventually clear on its own but perhaps this is a larger
problem?

The problem manifests itself to the users as a busy signal.

John

On Mon, 2006-06-19 at 11:59 +0100, Steve Davies wrote:
> Hi,
> 
> We have an asterisk user who has wireless phones - I believe that
> these phones are causing occasional locked-up SIP channels. While this
> is a problem in itself, it is not easily diagnosable, so I am looking
> for a solution from a different angle.
> 
> The problem occurs when a ZAP channel hangs up, but cannot clear down
> the bridged channels, presumably because of their locked-up state.
> This leaves the PRI/telco thinking it has a clear channel, but
> asterisk thinking it is still busy. If a new call is presented by the
> telco on this channel, it is hung-up with the message:
> 
> chan_zap.c:8062 pri_dchannel: Ring requested on channel 0/2 already in
> use on span 1.  Hanging up owner.
> 
> What I was hoping for was a hint as to how I could modify this code so
> that it also tries to clear the "stuck" call. I cannot think of a case
> where the telco sends a call in on a channel, and that channel is
> in-use already that is valid, so I would like to be more harsh in the
> clearing up the mess in this case.
> 
> Thanks for any pointers.
> Steve
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
> 
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>