Example create call not idempotent:

[GoogleCodeExporter]

What steps will reproduce the problem?

1. This create call is not idempotent and can only be issued once.

http://test-install.blindsidenetworks.com/bigbluebutton/api/create?meetingID=Mee
ting-24&checksum=4fbb2c49f9d0f008bb92ca10b61a9abf187afb50

What is the expected output? 

The create works fine, but second call errors.
Expected SUCCESS duplicate warning on second attempt.

What do you see instead?

Call the second time gives.
<response>
<returncode>FAILED</returncode>
<messageKey>idNotUnique</messageKey>
<message>
A meeting already exists with that meeting ID. Please use a different meeting 
ID.
</message>
</response>

Not a major issue, but should be documented, that no params = not idempotent

Its a feature :)

Original issue reported on code.google.com by 207T...@gmail.com on 17 Jun 2015 at 11:15

[GoogleCodeExporter]

Appears this issue is more "major". If "no moderator or attendee PW" is sent, 
bbb-web assigns them.  In a number of cases this call is not idempotent and 
returns idNotUnique instead of duplicateWarning so integration logic fails.

Im troubleshooting now, since it seems to be intermittment in a customer 
implementation, and i think has to do with other params, like logoutURL and 
meeting name.

The api states params need to be the same?  Im just hitting the refresh in 
browser on create call. so no params are changing and i get the error.

Will get some test cases asap.

Original comment by 207T...@gmail.com on 19 Jul 2015 at 4:18