[asterisk-users] Asterisk 11.2.1 / dahdi destroy channel / asteriskcrashes

[Richard Mudgett]

----- Original Message -----
> CLI>channel request hangup DAHDI/1-1
> Would work.
> 
> But 'dahdi destroy channel 1' shouldn't segfault asterisk.

The "dahdi destroy channel" command is *only* for use when you know
what your doing.  Even then I would not recommend ever using that
command.  The CLI help for that command shows:
Usage: dahdi destroy channel <chan num>
	DON'T USE THIS UNLESS YOU KNOW WHAT YOU ARE DOING.  Immediately removes a given channel, whether it is in use or not.

So if that channel were in use then I would expect to get a segfault
because that channel is unconditionally removed from the system and
cannot be used again until Asterisk is restarted.

> 
> Alec
> 
> > -----Original Message-----
> > From: asterisk-users-bounces at lists.digium.com
> > [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of
> > Thorsten Göllner
> > Sent: Thursday, 11 April 2013 8:57 p.m.
> > To: asterisk-users at lists.digium.com
> > Subject: [asterisk-users] Asterisk 11.2.1 / dahdi destroy
> > channel / asteriskcrashes
> > 
> > Hi,
> > 
> > I have the following setup:
> > 
> > Ubuntu 12.04.02 LTS (64 bit)
> > Asterisk 11.2.1
> > Sangoma 4-Port-Card (A104d) with firmware 43 (german e1-ports
> > connected) WANPIPE Release: 3.5.28 DAHDI Version: 2.6.1 Echo
> > Canceller: HWEC libpri version: 1.4.12
> > 
> > I call via sip into the dialplan. Then I do a
> > "Dial(DAHDI/g1/voicenumber,r)". The call is bridged and
> > everything is fine. "dahdi show channels" shows me, that
> > channel 1 is used for the outcall. Then I try to hangup the
> > outcall via "dahdi destroy channel 1".
> > Asterisk crahes immediatly. No message is logged (verbose is
> > 10 and debug is 10).
> > 
> > I get disconnected from the atserisk cli at this moment:
> > 
> > vlr-3*CLI> dahdi destroy channel 1
> > vlr-3*CLI>
> > Disconnected from Asterisk server
> > Asterisk cleanly ending (0).
> > Executing last minute cleanups
> > voxi at vlr-3:/tmp$
> > 
> > Is this a bug or is this my fault?

It is the wrong command.

Richard