Question
We have meet the trouble that we can't join the meeting(with password protection) by URL API m.php?AT=JM".
The error detail infomation is following :
MYURL?AT=JM&ST=FAIL&RS=InvalidMeetingKeyOrPassword&MK=MEETING_KEY
We created the meeting with xml(the detail is following).
<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<header>
<securityContext>
###SECURITY_CONTEXT###
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.meeting.CreateMeeting">
<accessControl>
<isPublic>false</isPublic>
<listToPublic>false</listToPublic>
<meetingPassword>###MEETING_PASSWORD</meetingPassword>
</accessControl>
<metaData>
<confName><![CDATA[###CONF_NAME### - ###COMMUNITY_NAME###]]></confName>
<agenda><![CDATA[###AGENDA###]]></agenda>
</metaData>
<participants>
<maxUserNumber>25</maxUserNumber>
<attendees>
###ATTENDEES###
</attendees>
</participants>
<enableOptions>
<chat>true</chat>
<poll>true</poll>
<audioVideo>true</audioVideo>
<supportUCFRichMedia>true</supportUCFRichMedia>
<attendeeList>true</attendeeList>
<chatHost>true</chatHost>
<chatPresenter>true</chatPresenter>
<chatAllAttendees>true</chatAllAttendees>
</enableOptions>
<schedule>
<startDate>###START_DATE###</startDate>
<openTime>900</openTime>
<duration>###DURATION###</duration>
<timeZoneID>49</timeZoneID>
</schedule>
<attendeeOptions>
<excludePassword>false</excludePassword>
<emailInvitations>false</emailInvitations>
</attendeeOptions>
</bodyContent>
</body>
</serv:message>And following that we used the URL API and parameters.
https://myurl.webex.com/MYSITE/m.php?AT=JM&MK=###MEETING_KEY###&AN=###NAME###&AE=###EMAIL###&PW=###MEETING_PASSWORD###
Please teach us about success method of joinning the meeting(with password protection) by URL API "m.php?AT=JM".
Additional information:
- Before cisco applied WBS 39.11 version for our webex site, we could join the meeting with the same method. But the meeting was not set the password protection and PW parameter of URL API "m.php?AT=JM" was null.
- Above trying m.php access was success when signed by WebEx Meeting account in browser.
- In practice, the attendees don't have a WebEx Meeting account.
