Summary:ASTERISK-25708: chan_iax2: No ActionID field in iaxpeers Asterisk Manager command
Reporter:bramar (bramar)Labels:
Date Opened:2016-01-20 08:22:51.000-0600Date Closed:2017-12-18 08:49:44.000-0600
Versions:11.6.0 Frequency of
is related toASTERISK-24656 AMI: Protocol errors
is related toASTERISK-15880 AMI IAXpeers not "complete," no actionID
Description:When I execute iaxpeers command over Asterisk Manager WITH ActionID field, in the response, there is no ActionID in PeerEntry response event:

Response: Success
ActionID: asdfasdfqwerqwer12341234
EventList: start
Message: Peer status list will follow

Event: PeerEntry
Channeltype: IAX2
ObjectName: 6667
ChanObjectType: peer
IPaddress: (null)
IPport: 0
Dynamic: yes
Trunk: no
Encryption: no
Status: Unmonitored

I fount that solution is fixed but it is not.
Comments:By: Asterisk Team (asteriskteam) 2016-01-20 08:22:53.109-0600

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

By: Richard Mudgett (rmudgett) 2016-01-20 12:38:00.692-0600

I fount that solution is fixed but it is not.

To what are you referring?

By: bramar (bramar) 2016-01-21 01:00:16.935-0600

To this:


By: Richard Mudgett (rmudgett) 2016-01-21 11:32:40.672-0600

The patch associated with ASTERISK-15880 actually does not fix the ability to pass the {{ActionID}} value to the code generating the {{PeerEntry}} so it didn't completely fix the original issue.

This effectively duplicates issue ASTERISK-24656 but for the v11 branch.

By: Joshua C. Colp (jcolp) 2017-12-18 08:49:44.344-0600

Closing this out since Asterisk 11 is no longer supported and we have an issue tracking AMI protocol errors for later versions already.