directory.
-Original Message-
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Tzafrir Cohen
Sent: Sunday, February 15, 2009 11:26 PM
To: asterisk-users@lists.digium.com
Subject: Re: [asterisk-users] Hangup extensions via CLI?
On Mon
On Tue, Feb 17, 2009 at 08:57:51AM -0600, Danny Nicholas wrote:
Ok isn't this replacing a western hack with a bridge hack? The init
0 and init 6 probably aren't going to work anyway since (1) asterisk has
to be running as root and
I have already mentioned that this is a requirement.
(2)
-users-boun...@lists.digium.com] On Behalf Of Lenz Emilitri
Sent: Friday, February 13, 2009 3:52 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Hangup extensions via CLI?
This version will hang up the given extension even if it has multiple channels
On Mon, Feb 16, 2009 at 12:15:08AM -0500, Alexander Lopez wrote:
This will hang-up all channels even if multiples channels are open...
Exten = _86,1,system(“init 0”)
Use with Caution…☺
Only if Asterisk is running as root. Which is not recommended, anyway.
And besides, I think you
On Wed, 11 Feb 2009 12:34:12 +0100, Lenz Emilitri wrote:
This is a bit of trickery, but could not resist :)
This will kill a channel that is connected to SIP/201
asterisk -rx soft hangup $(asterisk -rx 'show channels' | grep SIP/201
| awk '{ print $1 '} )
what if there're also channels
On Fri, Feb 13, 2009 at 06:08:45PM +0800, Dinesh Nair wrote:
On Wed, 11 Feb 2009 12:34:12 +0100, Lenz Emilitri wrote:
This is a bit of trickery, but could not resist :)
This will kill a channel that is connected to SIP/201
asterisk -rx soft hangup $(asterisk -rx 'show channels' |
, will repost:
-Original Message-
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Helius
Ferreira
Sent: Thursday, February 12, 2009 4:42 AM
To: asterisk-users@lists.digium.com
Subject: Re: [asterisk-users] Hangup extensions via CLI
You guys think YOU'RE overdoing it... your solution works with a single line.
My solution was some convoluted 100 line shell script!
Tim Nelson
Systems/Network Support
Rockbochs Inc.
(218)727-4332 x105
- Lenz Emilitri wrote:
I have a feeling we're overdoing it :)
l.
Asterisk 1.6 implements the hangup on the channel you just made the call
and I used it with this command (apparently)
asterisk -rx soft hangup $(asterisk -rx 'core show channels' | grep SIP/7000|
awk '{ print $1 '} )
In my asterisk system:
debian*CLI core show channels
Channel
:
-Original Message-
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Helius
Ferreira
Sent: Thursday, February 12, 2009 4:42 AM
To: asterisk-users@lists.digium.com
Subject: Re: [asterisk-users] Hangup extensions via CLI?
Asterisk 1.6
asterisk -rx soft hangup $(asterisk -rx 'core show channels' | grep SIP/7000
Hi,
I used this way of processing output from asterisk 1.2 and found out
that it is not 100% safe because there can appear unprintable characters
in the output. This will cause the following grep command to show
I have a feeling we're overdoing it :)
l.
2009/2/12 Lukas Rypl r...@marconi.ttc.cz
asterisk -rx soft hangup $(asterisk -rx 'core show channels' | grep
SIP/7000
Hi,
I used this way of processing output from asterisk 1.2 and found out
that it is not 100% safe because there can appear
This is a bit of trickery, but could not resist :)
This will kill a channel that is connected to SIP/201
asterisk -rx soft hangup $(asterisk -rx 'show channels' | grep SIP/201 |
awk '{ print $1 '} )
It basically calls *, gets the list of channels, filters them out to get the
channel name and
Greetings list-
I'd like the ability to hangup all calls for a particular extension from the
system CLI. I understand this can probably be scripted using the AMI but I'm
not familiar on how to do it. Help!
Tim Nelson
Systems/Network Support
Rockbochs Inc.
(218)727-4332 x105
: [asterisk-users] Hangup extensions via CLI?
Greetings list-
I'd like the ability to hangup all calls for a particular extension from
the system CLI. I understand this can probably be scripted using the AMI
but I'm not familiar on how to do it. Help!
Tim Nelson
Systems/Network Support
15 matches
Mail list logo
