asterisk users - Jun 2023 - Get channel variables via ARI/AMI

I’m in training, so I have to demonstrate something SIP related.  I figure it
would be cool to hack a call, hanging it up while in progress from outside
Asterisk.  Doing so will demonstrate use/knowledge of ARI, AMI, SIP, route-sets,
UDP, etc.

 

Practical value: zero

 

:)

 

Who knows, maybe this will have an actual application for someone someday.  In
practical terms I think building a proxy would be the right way to manipulate
the SIP for a call in progress, but that sounds like a huge project.  I’ve got
to demonstrate something by end of week.

 

From: asterisk-users [mailto:asterisk-users-bounces at lists.digium.com] On
Behalf Of Jeff LaCoursiere
Sent: Monday, June 26, 2023 6:20 PM
To: asterisk-users at lists.digium.com
Subject: Re: [asterisk-users] Get channel variables via ARI/AMI

 

On 6/26/23 9:00 AM, Joshua C. Colp wrote:

On Mon, Jun 26, 2023 at 10:57 AM TTT <lists at telium.io <mailto:lists at
telium.io> > wrote:

I am connecting to the ARI with subscribe all, so I can see channels being
created.  I now want to extract a variety of header variables (at the moment the
from and to tag).  I tried to read them from the ARI but Asterisk refuses since
the channel is not in a  stasis app.

 

Is there a way to read these from either the ARI or AMI ?  I’m trying not to
modify the dialplan.

 

ARI, No.

AMI, Yes[1]. 

 

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+20+ManagerAction_Getvar


 

I'm curious what the actual application is here - you want to connect to AMI
to pull information that you will use to pretend to be a leg, just to send
"BYE", when you could just hangup the leg with AMI (or do just about
anything else you might think of).  Sometimes it is better to fully explain what
you are trying to accomplish, and some folks here can try to steer you towards a
workable solution.  It almost sounds... nefarious.

Cheers,

-- 
Jeff LaCoursiere
StratusTalk, Inc.
703 496 4990 x108
815 546 6599 cell
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20230627/438eecf1/attachment.html>

I need to get hooked up with this class, I could have students doing 
projects for homework :) Interested in RTCP?

j

On 6/26/23 7:45 PM, TTT wrote:
>
> I’m in training, so I have to demonstrate something SIP related.  I 
> figure it would be cool to hack a call, hanging it up while in 
> progress from outside Asterisk.  Doing so will demonstrate 
> use/knowledge of ARI, AMI, SIP, route-sets, UDP, etc.
>
> Practical value: *zero*
>
> J
>
> Who knows, maybe this will have an actual application for someone 
> someday.  In practical terms I think building a proxy would be the 
> right way to manipulate the SIP for a call in progress, but that 
> sounds like a huge project.  I’ve got to demonstrate something by end 
> of week.
>
> *From:*asterisk-users [mailto:asterisk-users-bounces at lists.digium.com] 
> *On Behalf Of *Jeff LaCoursiere
> *Sent:* Monday, June 26, 2023 6:20 PM
> *To:* asterisk-users at lists.digium.com
> *Subject:* Re: [asterisk-users] Get channel variables via ARI/AMI
>
> On 6/26/23 9:00 AM, Joshua C. Colp wrote:
>
>     On Mon, Jun 26, 2023 at 10:57 AM TTT <lists at telium.io> wrote:
>
>         I am connecting to the ARI with subscribe all, so I can see
>         channels being created.  I now want to extract a variety of
>         header variables (at the moment the from and to tag).  I tried
>         to read them from the ARI but Asterisk refuses since the
>         channel is not in a  stasis app.
>
>         Is there a way to read these from either the ARI or AMI ?  I’m
>         trying not to modify the dialplan.
>
>     ARI, No.
>
>     AMI, Yes[1].
>
>     [1]
>    
https://wiki.asterisk.org/wiki/display/AST/Asterisk+20+ManagerAction_Getvar
>
> I'm curious what the actual application is here - you want to connect 
> to AMI to pull information that you will use to pretend to be a leg, 
> just to send "BYE", when you could just hangup the leg with AMI
(or do
> just about anything else you might think of).  Sometimes it is better 
> to fully explain what you are trying to accomplish, and some folks 
> here can try to steer you towards a workable solution.  It almost 
> sounds... nefarious.
>
> Cheers,
>
> -- 
> Jeff LaCoursiere
> StratusTalk, Inc.
> 703 496 4990 x108
> 815 546 6599 cell
>
-- 
Jeff LaCoursiere
StratusTalk, Inc.
703 496 4990 x108
815 546 6599 cell
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20230626/eda65dcc/attachment.html>