[asterisk-bugs] [Asterisk 0018141]: AMI command 'MeetMeList' responds with error when no conferences exist
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Oct 14 15:08:27 CDT 2010
The following issue requires your FEEDBACK.
======================================================================
https://issues.asterisk.org/view.php?id=18141
======================================================================
Reported By: coreyfarrell
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18141
Category: Applications/app_meetme
Reproducibility: always
Severity: minor
Priority: normal
Status: feedback
Asterisk Version: 1.6.2.11
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-10-14 08:21 CDT
Last Modified: 2010-10-14 15:08 CDT
======================================================================
Summary: AMI command 'MeetMeList' responds with error when no
conferences exist
Description:
When running MeetMeList without specifying a conference (to get information
on all conferences), an error is returned if no conferences exist. I feel
that this is not an error unless a 'Conference: <id>' is specified and does
not exist.
On an authenticated AMI connection send:
Action: MeetMeList
ActionID: 1234
If no conferences exist, you receive:
Response: Error
ActionID: 1234
Message: No active conferences.
I would expect to instead receive:
Response: Success
ActionID: 1234
Message: No active conferences.
Or even:
Response: Success
EventList: start
Message: Meetme user list will follow
Event: MeetmeListComplete
EventList: Complete
ListItems: 0
======================================================================
----------------------------------------------------------------------
(0128057) lmadsen (administrator) - 2010-10-14 15:08
https://issues.asterisk.org/view.php?id=18141#c128057
----------------------------------------------------------------------
This sounds like a feature request for me. While this may not be what you
expect to happen, it is just working as expected.
Issue History
Date Modified Username Field Change
======================================================================
2010-10-14 15:08 lmadsen Note Added: 0128057
2010-10-14 15:08 lmadsen Status new => feedback
======================================================================
More information about the asterisk-bugs
mailing list