Meeting Services

Hi Yuriy,
 
What you are doing in your XML is scheduling a meeting for y.glushanin and setting up test@test.com as an alternate host for the meeting.  Both users must have a an active host account in order to host a meeting,  or to be an alternate host for a meeting. There is no way around this. Attendees without host accounts can only receive the host option after the meeting has been started by the host.
 
Thank you,
-Kingsley Lewis

Hi Yuriy,

The XML API is best for back and forth data.  If you need to perform an action such as loging into a site,  or starting/joining a meeting,  then you will want to use our URL API.  The two go together and should both be used in most integrations.  Also a lot of the time you will find that if one API does not meet your requirements the other one will.

Launching the actual meeting client is always done through a browser.  In its most basic form the URL will look like this for a host to start a meeting.

https://sitename.webex.com/sitename/p.php?AT=LI &WID=enter_login&PW=enter_password&MU=/sitename/m.php?AT=HM%26MK=enter_meeting_number%26BU=http://yourerrorpage.com/back_test.htm?fURL=sitename&BU=http://yourerrorpage.com/back_test.htm?fURL=sitename

This is the API login command. Since you must login before you can host a meeting, we are providing a chained command to allow you to do login and host a meeting all in one URL.:

p.php?AT=LI

This is the WebEx ID login parameter:

&WID=enter_login

This is the password parameter for the WebEx login:

&PW=enter_password

This is the MU parameter which is the URL that will load if the login is successful. In this example the MU value is a chained Host Meeting command. If you enter the correct meeting number info it will immediately start the meeting associated with the number you supplied. NOTE: You can only use the MU parameter to chain a second API command with the Login command.

&MU=/sitename/m.php?AT=HM %26MK=enter_meeting_number %26BU=http://ats.corp.webex.com/tools/ts/back_test.htm?fURL=sitename

This is the BU or BackURL for the login command, which means this URL will load if the login is not successful. The page specified below will parse the returned info and notify you of success or provide an error message.

&BU=http://ats.corp.webex.com/tools/ts/back_test.htm?fURL=sitename

Details about the Host Meeting command:
This is the Host Meeting command:

m.php?AT=HM

This is the meeting number parameter. The %26 is NOT a typo, multiple parameters in the MU have to be URL-Encoded and the %26 represents an &.:

%26MK=enter_meeting_number

This is the BU for the Host Meeting command. This URL will be loaded after the meeting if the command is successful or immediately if the command is not successful. The page specified below will parse the returned info and notify you of success or provide an error message.:

%26BU=http://ats.corp.webex.com/tools/ts/back_test.htm?fURL=sitename

For your second question you would not pass the admin role.  The admin role is an account that has the ability to , add/modify/delete host accounts.  The admin also has the ability to modify site settings from the site admin page. 

In the context of meetings (the client that pops up when you click on start meeting) the admin who starts a meeting is just a host account.  This means that in-meeting functionality an admin is equal to a host.  There are no special features or functions an admin would have over a normal host. 

With that said,  you could start a meeting with any host account,  once in the meeting you can then pass host rights over to any attendee that is in the meeting.  Test would never be able to start the meeting and instantly gain the host role, because he does not have host rights on the site.