Hello, I schedule a new meeting, and then I call GethosturlMeeting to obtain host url. But when someone opens this host url in the browser, it not only opens Cisco WebEx Meeting Center teleconferencing module, but also logs him/her in the browser as the host (giving him/her access to My WebEx, scheduling new meetings and so on). You can see that on the screenshot below - the browser is in the background. My question is: is it somehow possible not to log in the browser? Just open the teleconferencing module/plugin but do not let the user do whatever (s)he wants in the browser/My WebEx as the host? Thanks! ... View more

Hello, I've noticed that some screens in WebEx offer the possibility to log in using thin client ("Join by browser"). It is an interesting option for me as it does not require participants to install browser plugins/extensions nor to launch a temporary executable file, which might be forbidden by local security policy. In my case, I am calling WebEx XML API GetjoinurlMeeting, retrieve <meet:joinMeetingURL> and send it to meeting participants. But when they click the link, the option of Joining by browser is no longer there... They either see the following: ...or the following: So, my question is: Is it possible to generate a joinMeetingURL that would additionally display the possibility to join the meeting by browser / using the thin client? Thanks! ... View more

Hello, I am using WebEx XML API V10.0.0 SP23. I am on Central European time (Paris/Brussels/Amsterdam...). When calling LstmeetingusageHistory and LstmeetingattendeeHistory API methods, the returned time fields ( history:meetingStartTime, meeting/EndTime, joinTime, leaveTime ) are 1 hour too early. For instance, I had a meeting which started on 12:12 and ended on 12:30. But LstmeetingusageHistory returns the following: <history:meetingUsageHistory>     ...     <history:meetingStartTime>03/01/2018 11:12:34</history:meetingStartTime>     <history:meetingEndTime>03/01/2018 11:30:41</history:meetingEndTime>     ...     <history:timezone>GMT+01:00, Europe (Paris)</history:timezone>     <history:timeZoneID>23</history:timeZoneID>     <history:timeZoneWithDST>Paris (Europe Time, GMT+01:00)</history:timeZoneWithDST> What is surprising is that GetMeeting API method returns the scheduled meeting start time correctly! <meet:schedule>     <meet:startDate>03/01/2018 12:10:00</meet:startDate>     <meet:timeZoneID>23</meet:timeZoneID>     <meet:timeZone>GMT+01:00, Europe (Paris)</meet:timeZone>     ... So, why are these inconsistent? Does it mean that time fields returned by LstmeetingusageHistory and LstmeetingattendeeHistory are in GMT+0 and I have to manually apply the "+01:00" for my local timezone? And what about the daylight saving time? Does it mean that after 25 March 2018, I will have to correct time fields returned by these two methods by +2 hours? Thanks. ... View more

Hello, I have a script that is querying our WebEx instance every minute to retrieve information updates. Looking into logs, I discovered that last Friday, around 20:30, it started responding with the following data in the header:     <serv:response>       <serv:result>FAILURE</serv:result>       <serv:reason>Sorry, no record found</serv:reason>       <serv:gsbStatus> BACKUP </serv:gsbStatus>       <serv:exceptionID>000015</serv:exceptionID>     </serv:response> Today it's back to <serv:gsbStatus> PRIMARY </serv:gsbStatus> . What does this "BACKUP" value mean? Did the server go into some kind of maintenance mode and started redirecting me to a secondary, fallback node, under the same DNS name? Do I have to always verify if gsbStatus I receive is PRIMARY or not? Thanks! ... View more

Hello, Is there any way to allow Attendees to join the teleconference before the Host in VoIP-only meetings? When calling the CreateMeeting API method, if I set JoinTeleconfBeforeHost to true and telephonySupport to OTHER or NONE, I get error message: "JoinTeleconfBeforeHost is not supported for specified telephony type". When I set telephonySupport to CALLIN, the meeting is successfully created, but when I read it back with GetMeeting API method, it turns out that CALLIN has been changed to CALLBACK... Thanks! ... View more

Hello, WebEx XML API. I've noticed that if I call gethosturlMeeting a few times in a row with the same meetingKey parameter, I get slightly different URLs. They are always identical apart from the value of Rnd, e.g.: https://rose22.webex.com/rose22/p.php?AT=LI&WID=hostid&PW=pass&MU=https%3A%2F%2Frose22.webex.com%2Frose22%2Fm.php%3FAT%3DHM%26MK%3D48591508%26Rnd%3D 0.9044222067369163 https://rose22.webex.com/rose22/p.php?AT=LI&WID=hostid&PW=pass&MU=https%3A%2F%2Frose22.webex.com%2Frose22%2Fm.php%3FAT%3DHM%26MK%3D48591508%26Rnd%3D 0.1015060849139265 https://rose22.webex.com/rose22/p.php?AT=LI&WID=hostid&PW=pass&MU=https%3A%2F%2Frose22.webex.com%2Frose22%2Fm.php%3FAT%3DHM%26MK%3D48591508%26Rnd%3D 0.5142255340681853 Does the Rnd parameter have any importance? Can I generate 3 host URLs with different Rnd values, and then use any of them to log in, or only the last one generated? Thanks! ... View more

Hello, I am using the following WebEx XML API invocation (headers omitted): <bodyContent xsi:type="java:com.webex.service.binding.history.LstmeetingusageHistory">     <meetingKey>123 456 789</meetingKey>     <inclAudioOnly>true</inclAudioOnly> </bodyContent> My problem is that I don't understand from which point in time can I call this method. For instance, If I join meeting 123 456 789 as a host, then I end the meeting, I still get the following response (headers omitted): <serv:response>     <serv:result>FAILURE</serv:result>     <serv:reason>Sorry, no record found</serv:reason>     <serv:gsbStatus>PRIMARY</serv:gsbStatus>     <serv:exceptionID>000015</serv:exceptionID> </serv:response> So, when will I start getting meaningful responses after calling LstmeetingusageHistory() on a finished meeting? The next day? An hour after all the attendees leave? Thanks for any help. PS. There's no typo in my request, as I'm getting history for older meetings... ... View more

Hello, WebEx XML API. Let's say I have a meeting in progress and I want to know how many active participants are there at the moment, and, ideally, what are their names. GetMeeting() returns participantsJoined, but it is only a true/false field. The names of active participants are not a part of the response, either. LstmeetingattendeeHistory() would work, because for every attendee it returns fields like name, email, joinTime, leaveTime... But it doesn't work on meetings in progress, only on historical ones! Thanks for any help... ... View more

Hello, I am already successfully using WebEx XML API, but I also wanted to try the URL API. One interesting feature of the URL API is the ability to end an ongoing meeting (which is not possible via the XML API). So, I reserved a shared sandbox through the Try WebEx Conferencing API's webpage. I created user with ID = 1410997 and password 'mypassword'. Then, I manually started a meeting with meeting key '622 900 191'. Now, I want to end this meeting through the URL API. So, I am first sending the following HTTP GET request (programatically, not typing it manually in the browser): https://apidemoeu.webex.com/apidemoeu/p.php?AT=LO&WID=1410997&PW=mypassword ...which returns an HTML page containing some JavaScript and a form with a hidden field 'destUrl': <input type="hidden" id="destUrl" value=" https://apidemoeu.webex.com/mw3200/mywebex/default.do?siteurl=apidemoeu&AT=LO&ST=SUCCESS "> So far, so good. Then, I am sending second HTTP GET request to kill the meeting: https://apidemoeu.webex.com/apidemoeu/w.php?AT=KM&MK=622900191&WID=1410997&PW=mypassword And this one unfortunately fails, returning the following text: AT=KM&ST=FAIL&RS=AccessDenied 1. So, what am I doing wrong? Why is the AT=KM command failing? Is it because of improper cookie management on my side? Do I need to execute JS scripts from the HTML returned by the AT=LO command? Do I need to visit the destUrl to finished the logging-in process? 2. Also, do you have any working sourcecode examples (in Java or PHP) of using WebEx URL API? Thanks! ... View more