[asterisk-bugs] [JIRA] (ASTERISK-25708) No ActionID field in iaxpeers Asterisk Manager command

Asterisk Team (JIRA) noreply at issues.asterisk.org
Wed Jan 20 08:24:33 CST 2016


    [ https://issues.asterisk.org/jira/browse/ASTERISK-25708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229076#comment-229076 ] 

Asterisk Team commented on ASTERISK-25708:
------------------------------------------

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].

> No ActionID field in iaxpeers Asterisk Manager command
> ------------------------------------------------------
>
>                 Key: ASTERISK-25708
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25708
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_iax2
>    Affects Versions: 11.6.0
>            Reporter: bramar
>            Severity: Minor
>
> 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
> Description: 
> I fount that solution is fixed but it is not.



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list