search for: matchincontext

...s-bounces@lists.digium.com [mailto:asterisk-users- > bounces@lists.digium.com] On Behalf Of Alexander Lopez > Sent: Tuesday, September 13, 2005 9:08 PM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: RE: [Asterisk-Users] PRI zap channels not cleared when no > matchincontext for dialed number on inbound call > > > I se what you are talking about I an able to reproduce!!! > > However your PRI may be in a Round-Robin picking order, that would cycle > through all of the channels until it reaches an end and then it repeats. > I set our PRI to first...

...ers-bounces@lists.digium.com [mailto:asterisk-users- > bounces@lists.digium.com] On Behalf Of Alexander Lopez > Sent: Tuesday, September 13, 2005 9:27 PM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: RE: [Asterisk-Users] PRI zap channels not cleared > whennomatchincontext for dialed number on inbound call > > > Yeah the "variable stays there" because the channel is never up to be > cleared. If you do something like > > exten => _X.,1,Wait(1) > exten => _X.,2,Hangup > > You will see the same behavior. Can you confirm??...

...ounces@lists.digium.com > [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of > Damon Estep > Sent: Tuesday, September 13, 2005 11:11 PM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: RE: [Asterisk-Users] PRI zap channels not cleared > when nomatchincontext for dialed number on inbound call > > But it does indicated that a variable is staying assigned > that should not be, which could have other impact over time??? > > The behavior is very different for c call where there is a > dialplan match for the dialed number, when the call...