Subscribe Problem – Zombie Channel

Home » Asterisk Users » Subscribe Problem – Zombie Channel
Asterisk Users No Comments

On Tuesday, 7 February 2012, Örn Arnarson wrote:
> Hi Brian,
>
> Did you ever figure out what’s causing this, and how to deal with it?
>
> I’m seeing the same behavior with call-pickups (it’s rare, but it’s
> happened a few times) on Asterisk 1.6.1.11
>
> Did you figure out a way to get rid of the channel without restarting?
>
> Regards,
>

Hi Orn

I didn’t find a way except a restart once active calls drop to zero.

Regards,
Brian

>
> On Wed, Jul 28, 2010 at 9:45 PM, dotnetdub wrote:
>>
>>
>> On 28 July 2010 21:42, Stefan Schmidt wrote:
>>>
>>> dotnetdub schrieb:
>>> > Hi List,
>>>
>>> > core show channels
>>> > Channel Location State Application(Data)
>>> >
>>> > SIP/102–08e1 *8@from-inside Down (None)
>>> > SIP/102–08d6 *8@from-inside Ring (None)
>>> > SIP/102–08d7 *8@from-inside Ring (None)
>>> > 3 active channels
>>> > 0 active calls
>>> >
>>> > The only way to free them up is to force a restart.
>>> >
>>> > restart now
>>> >
>>> > Any clues on how I can debug this and try to sort it or even if anyone
>>> > has come across this.
>>> >
>>> > Many thanks in advance.
>>> >
>>> > Brian
>>> >
>>> >
>>> hello,
>>>
>>> you should recompile asterisk with DEBUG CHANNEL LOCKS flag and i think
>>> you will see some locks when this happens with core show locks.
>>> how do you make the pickup? do you use an extension *8 for this, or just
>>> the feature for pickup in features conf?
>>>
>>> best regards
>>>
>>> steve
>>>
>>>
>>
>> Hi Steve,
>>
>> Thanks for the reply. We have:
>>
>> pickupexten = *8 ; Configure the pickup extension.
Default
>> is *8
>>
>> in features.conf.
>>
>> I will recompile on one of the sites this happens on. It’s really odd,
can
>> go for weeks without this happening and then a customer will report to me
>> that their extension is showing in use and I will login and there can be
two
>> or three of these locks. On one site it actually makes asterisk
impossible
>> to stop and I need to kill -9
>>
>> We have stuck with version 1.4.22 as it has been so solid for us, no
dumps
>> or deadlocks etc. We have tried to move to 1.4.25 and 1.4.29 but would
>> experience random weirdness that we just don’t get with this version.
>>
>> When recompiled with this flag and if indeed it does show locks, what
would
>> be the next step?
>>
>> Thanks for your help.
>> Brian
>>
>>
>> —
>> _____________________________________________________________________
>> — Bandwidth and Colocation Provided by http://www.api-digital.com
>> New to Asterisk? Join us for a live introductory webinar every Thurs:
>> http://www.asterisk.org/hello
>>
>> asterisk-users mailing list
>> To UNSUBSCRIBE or update options visit:
>> http://lists.digium.com/mailman/listinfo/asterisk-users
>
> —
> _____________________________________________________________________
> — Bandwidth and Colocation Provided by http://www.api-digital.com
> New to Asterisk? Join us for a live introductory webinar every Thurs:
> http://www.asterisk.org/hello
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users