Skip Menu |

This queue is for tickets about the Asterisk-AMI CPAN distribution.

Report information
The Basics
Id: 132966
Status: open
Priority: 0/
Queue: Asterisk-AMI
People
Owner: Nobody in particular
Requestors: ad_user [...] runbox.com
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Wed Jul 08 22:55:17 2020 ad_user [...] runbox.com - Ticket created
Subject: amiver() not working with asterisk > 1.8
Date: Thu, 9 Jul 2020 11:47:57 +1000
To: bug-Asterisk-AMI [...] rt.cpan.org
From: Alex 'AdUser' Z <ad_user [...] runbox.com>
I discovered, that amiver() method working only for oldest known asterisk versions. Tested on latest stable module version (0.2.8). Here is collection of AMI greeetings from our site: * Asterisk Call Manager/1.1 (Asterisk 1.8) <- works * Asterisk Call Manager/2.8.0 (Asterisk 13) <- don't * Asterisk Call Manager/5.0.1 (Asterisk 16) <- don't Official docs also says, that AMI now using tree-component versions: Show quoted text
> AMI version numbers are formatted as MAJOR.BREAKING.NON-BREAKING:
Show quoted text
> MAJOR – changes when a new major version of Asterisk is released > BREAKING – changes when an incompatible API modification is made > NON-BREAKING – changes when backwards compatible updates are made
From: https://wiki.asterisk.org/wiki/display/AST/Asterisk+Manager+Interface+%28AMI%29+Changes But module expects only two-component versions (MAJOR.MINOR): if ($line =~ /^Asterisk\ Call\ Manager\/([0-9]\.[0-9])$/ox) { $self->{AMIVER} = $1; -- -- Alex
  Thu Jul 09 02:53:48 2020 mspiegelmock [...] gmail.com - Correspondence added
Subject: Re: [rt.cpan.org #132966] amiver() not working with asterisk > 1.8
Date: Thu, 9 Jul 2020 09:53:36 +0300
To: bug-Asterisk-AMI [...] rt.cpan.org
From: Mischa S <mspiegelmock [...] gmail.com>
Consider not using Perl in 2020 Show quoted text
> On Jul 9, 2020, at 5:55 AM, ad_user@runbox.com via RT <bug-Asterisk-AMI@rt.cpan.org> wrote: > > Wed Jul 08 22:55:17 2020: Request 132966 was acted upon. > Transaction: Ticket created by ad_user@runbox.com > Queue: Asterisk-AMI > Subject: amiver() not working with asterisk > 1.8 > Broken in: (no value) > Severity: (no value) > Owner: Nobody > Requestors: ad_user@runbox.com > Status: new > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=132966 > > > > I discovered, that amiver() method working only for oldest known > asterisk versions. Tested on latest stable module version (0.2.8). > > Here is collection of AMI greeetings from our site: > > * Asterisk Call Manager/1.1 (Asterisk 1.8) <- works > * Asterisk Call Manager/2.8.0 (Asterisk 13) <- don't > * Asterisk Call Manager/5.0.1 (Asterisk 16) <- don't > > Official docs also says, that AMI now using tree-component versions: >
>> AMI version numbers are formatted as MAJOR.BREAKING.NON-BREAKING:
>
>> MAJOR – changes when a new major version of Asterisk is released >> BREAKING – changes when an incompatible API modification is made >> NON-BREAKING – changes when backwards compatible updates are made
> > From: > https://wiki.asterisk.org/wiki/display/AST/Asterisk+Manager+Interface+%28AMI%29+Changes > > But module expects only two-component versions (MAJOR.MINOR): > > if ($line =~ /^Asterisk\ Call\ Manager\/([0-9]\.[0-9])$/ox) { > $self->{AMIVER} = $1; > > -- > -- Alex >
  Thu Jul 09 02:53:49 2020 The RT System itself - Status changed from 'new' to 'open'
  Thu Jul 09 05:01:40 2020 ad_user [...] runbox.com - Correspondence added
Subject: Re: [rt.cpan.org #132966] amiver() not working with asterisk > 1.8
Date: Thu, 9 Jul 2020 19:01:16 +1000
To: bug-Asterisk-AMI [...] rt.cpan.org
From: Alex 'AdUser' Z <ad_user [...] runbox.com>
Show quoted text
> Mischa Spiegelmock
Consider taking your unsolicited advices in that hole, from where you're taking it.