similar to: AMI versions

Displaying 20 results from an estimated 20000 matches similar to: "AMI versions"

2023 Jul 11
1
AMI versions
https://docs.asterisk.org/latest/Configuration/Interfaces/Asterisk-Manager-Interface-AMI/Asterisk-Manager-Interface-AMI-Changes/ On Tue, Jul 11, 2023 at 11:54 AM, TTT <[lists at telium.io](mailto:On Tue, Jul 11, 2023 at 11:54 AM, TTT <<a href=)> wrote: > Is there a web page that lists the AMI versions mapped to Asterisk versions? > > I noticed that the AMI version increased
2023 Jul 11
1
AMI versions
That answers part two…but is there any mapping of AMI version to Asterisk versions? From: asterisk-users [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Sean Bright Sent: Tuesday, July 11, 2023 11:58 AM To: asterisk-users at lists.digium.com Subject: Re: [asterisk-users] AMI versions
2023 Jul 11
1
AMI versions
On Tue, Jul 11, 2023 at 3:40 PM Joshua C. Colp <jcolp at sangoma.com> wrote: > On Tue, Jul 11, 2023 at 3:38 PM TTT <lists at telium.io> wrote: > >> That answers part two…but is there any mapping of AMI version to Asterisk >> versions? >> > > No, there is not. > I can say that Asterisk 13 is 2.x.x though because I just looked, so you can use the
2023 Jul 11
1
AMI versions
On Tue, Jul 11, 2023 at 3:38 PM TTT <lists at telium.io> wrote: > That answers part two…but is there any mapping of AMI version to Asterisk > versions? > No, there is not. -- Joshua C. Colp Asterisk Project Lead Sangoma Technologies Check us out at www.sangoma.com and www.asterisk.org -------------- next part -------------- An HTML attachment was scrubbed... URL:
2023 Jun 26
2
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
2023 Jun 26
1
Get channel variables via ARI/AMI
On 6/26/23 5:19 PM, Jeff LaCoursiere wrote: > 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
2023 Jun 26
2
Get channel variables via ARI/AMI
It looks like if I call Getvar and pass PJSIP_HEADERS() I can get the entire SIP header for a channel. I also read (on stackoverflow) that the PJSIP_HEADER function will only return the headers from the INVITE of the inbound channel. If that’s correct, how would I get the headers from the outbound channel (second leg of the bridged call) INVITE ? Or will PJSIP_HEADERS() in fact return the
2023 Jun 26
2
Get channel variables via ARI/AMI
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
2023 Jun 27
1
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
2023 Aug 08
1
Subscribing to events on AMI login
On Tue, Aug 8, 2023 at 12:44 PM TTT <lists at telium.io> wrote: > I'm looking at an old app I wrote that upon AMI login would subscribe to > events as follows: > > > > Action: Login > > ActionID: myid > > Username: myun > > Secret: mypw > > Events: call, system, security > > > > I noticed this old code isn't working, and I
2023 Jul 02
1
Get channel variables via ARI/AMI
>> There are SOME protocol level things accessible using CHANNEL[1] but that's it. >> [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+20+Function_CHANNEL I am trying to use the CHANNEL function listed above from the AMI. Since it is not an AMI “action”, but rather a dialplan “function”, I’m trying to figure out how to call this from the AMI. Using a telnet session
2023 Jun 26
2
Get channel variables via ARI/AMI
I think that’s getting me close. I’m trying to get (or recreate) the FROM and TO lines of the header, from a system running PJSIP. I think if I use CHANNEL to get local_uri and local_tag I can recreate a FROM line like: FROM=<URI>;tag=TAG And if I use CHANNEL to get remote_uri and remote_tag I can recreate a FROM line like: TO=<URI>;tag=TAG Would it be correct to assume
2023 Jun 26
1
Get channel variables via ARI/AMI
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. Thanks Brian
2023 Aug 08
1
Subscribing to events on AMI login
I'm looking at an old app I wrote that upon AMI login would subscribe to events as follows: Action: Login ActionID: myid Username: myun Secret: mypw Events: call, system, security I noticed this old code isn't working, and I *think* that the events parameter of login has been deprecated; I don't see it referenced in:
2023 Aug 08
1
Subscribing to events on AMI login
Ok – so if I forgot to add “security” to the read= line in manager.conf for this user, will that cause the user to be unable to subscribe to the “security” events upon login? (in other words, although subscribed at login, no security events will be shown to this user) Thanks From: asterisk-users [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Joshua C. Colp Sent: Tuesday,
2023 Jun 26
1
Get channel variables via ARI/AMI
On Mon, Jun 26, 2023 at 4:04 PM TTT <lists at telium.io> wrote: > It looks like if I call Getvar and pass PJSIP_HEADERS() I can get the > entire SIP header for a channel. I also read (on stackoverflow) that the > PJSIP_HEADER function will only return the headers from the INVITE of the > *inbound* channel. > > > > If that’s correct, how would I get the headers from
2023 Jul 02
1
Get channel variables via ARI/AMI
>> You use the AMI action Getvar[1] which allows channel variables and dialplan functions. >> [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+20+ManagerAction_Getvar I actually tried that, and although I get “success” I never get useful data. For example: action: Getvar actionid: act1 channel: PJSIP/Twilio-NA-W-2-In-00000025 Variable: channel(pjsip,call-id)
2023 Jun 26
1
Get channel variables via ARI/AMI
On Mon, Jun 26, 2023 at 4:35 PM TTT <lists at telium.io> wrote: > I think that’s getting me close. I’m trying to get (or recreate) the FROM > and TO lines of the header, from a system running PJSIP. I think if I use > CHANNEL to get local_uri and local_tag I can recreate a FROM line like: > > *FROM=<URI>;tag=TAG* > > > > And if I use CHANNEL to get
2020 Jun 12
2
Send message to AMI from dialplan
Is it possible to simply send a message to appear as an AMI message/event, from the dialplan? For example exten =>123,1,ami(myEvent, param1, param2) and in the AMI a message appears like: Event: myEvent Privilege: call,all Channel: PJSIP/misspiggy-00000001 Uniqueid: 1368479157.3 ChannelState: 3 ChannelStateDesc: Up CallerIDNum: 657-5309 CallerIDName: Miss Piggy
2023 Jul 03
1
Get channel variables via ARI/AMI
The uppercase command made a difference. I now get a call-id as show below. However, does the call-id look valid? The @0.0.0.0 seems strange. action: Getvar actionid: act1 channel: PJSIP/Twilio-NA-W-3-In-00000028 Variable: CHANNEL(pjsip,call-id) Response: Success ActionID: act1 Variable: CHANNEL(pjsip,call-id) Value: 4decf884e3ae74595906283a74f7154e at 0.0.0.0 As well,