[asterisk-bugs] [JIRA] Created: (ASTERISK-20245) Asterisk manager output for command "Action:queues" is inconsistent from other commands.
Ron Gage (JIRA)
noreply at issues.asterisk.org
Thu Aug 16 12:43:07 CDT 2012
Asterisk manager output for command "Action:queues" is inconsistent from other commands.
----------------------------------------------------------------------------------------
Key: ASTERISK-20245
URL: https://issues.asterisk.org/jira/browse/ASTERISK-20245
Project: Asterisk
Issue Type: Bug
Security Level: None
Components: Core/ManagerInterface
Affects Versions: 1.8.14.0
Environment: FreePBX 2.10.1.1 based on CentOS 5.8 final
Reporter: Ron Gage
Severity: Minor
This is reference the management interface over TCP/5038
With the apparent sole exception of the "Action:queues" command, every command that returns data does so in a key:value format. For example - an excerpt from the Action:SipPeers command:
Event: PeerEntry
Channeltype: SIP
ObjectName: 213
ChanObjectType: peer
IPaddress: 10.15.3.74
IPport: 5060
Dynamic: yes
Forcerport: no
VideoSupport: no
TextSupport: no
ACL: yes
Status: OK (3 ms)
RealtimeDevice: no
With the Action:Queues command, you get an entirely different (and much harder to parse) format:
0157 has 0 calls (max unlimited) in 'ringall' strategy (0s holdtime, 0s talktime), W:0, C:0, A:1, SL:0.0% within 300s
Members:
Ron (Local/200 at from-queue/n) (dynamic) (Not in use) has taken no calls yet
No Callers
default has 0 calls (max unlimited) in 'ringall' strategy (0s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0% within 0s
No Members
No Callers
Please either fix the Queues command to provide an output consistent with other commands in the AMI or provide a method to toggle the output format of this command.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list