cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1164
Views
0
Helpful
2
Replies

Promting MeetingID while accessing the Join Meeting link

 

We are facing an issue, when we are clicking the Join meeting from the mail.

For the first time it doesn’t ask us for Meeting ID, but when we close the browser and again while trying the same it is prompting us to enter the Meeting ID.

Assuming the API’s have been upgraded with some security patches recently. Help us if we need to include any new parameters to the API calls.

Your help is very much appreciated.

 

1 Accepted Solution

Accepted Solutions

kasutton
Cisco Employee
Cisco Employee

Hi Anandha,

I believe Nathan answered this via email, but adding it here for visibility:

"

            If this is a generic join link, this should not occur. This can occur if you are using an API generated host link, however, as it will include a one time session ticket that will expire after first use, dropping you at the normal WebEx site landing page after failing to log on. I may be able to provide a more specific answer with additional details such as the failing link, steps to duplicate, and expected behavior."

Kasey

View solution in original post

2 Replies 2

kasutton
Cisco Employee
Cisco Employee

Hi Anandha,

I believe Nathan answered this via email, but adding it here for visibility:

"

            If this is a generic join link, this should not occur. This can occur if you are using an API generated host link, however, as it will include a one time session ticket that will expire after first use, dropping you at the normal WebEx site landing page after failing to log on. I may be able to provide a more specific answer with additional details such as the failing link, steps to duplicate, and expected behavior."

Kasey

Thanks a lot Nathan & Kasey

Yes, I'm using the API generated host link.

But previously when we were using WebEx with the same API calls, It was not prompting us to enter MeetingID at any cost(tried with more than once with the same link).

It always allowed us to directly enter to the meeting without prompting the User to enter the Meeting ID.

Not sure why there is a change in the behavior now. Again assuming due to some recent security patch upgrade in WebEx.

Help me to work in the old way. As our Users are not instructed to enter the Meeting ID, we need a solution to override it.

API calls involved in creating the meeting:

1. createMeeting --> returned with createMeetingResponse

2. gethosturlMeeting --> returned with gethosturlMeetingResponse

Please refer the below SOAP Messages:

Step 1:
Request:

<?xml version="1.0"?>
<serv:message xmlns:meet="http://www.webex.com/schemas/2002/06/service/meeting" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:att="http://www.webex.com/schemas/2002/06/service/attendee" xmlns:serv="http://www.webex.com/schemas/2002/06/service">
  <serv:header>
    <serv:securityContext>
      <webExID xmlns="http://www.webex.com/schemas/2002/06/common">temp</webExID>
      <password xmlns="http://www.webex.com/schemas/2002/06/common">****/password>
      <siteName xmlns="http://www.webex.com/schemas/2002/06/common">company</siteName>
    </serv:securityContext>
  </serv:header>
  <serv:body>
    <serv:bodyContent xsi:type="meet:createMeeting">
      <meet:metaData>
        <meet:confName>WebEx Testing</meet:confName>
        <meet:agenda>WebEx Testing</meet:agenda>
        <meet:sessionTemplate>
          <default xmlns="http://www.webex.com/schemas/2002/06/common">true</default>
        </meet:sessionTemplate>
      </meet:metaData>
      <meet:participants>
        <meet:attendees>
          <meet:attendee>
            <att:person>
              <email xmlns="http://www.webex.com/schemas/2002/06/common">anandhax.dhandapani@company.com</email>
            </att:person>
            <att:role>HOST</att:role>
          </meet:attendee>
          <meet:attendee>
            <att:person>
              <email xmlns="http://www.webex.com/schemas/2002/06/common">dipakx.upadhayaya@company.com</email>
            </att:person>
            <att:role>HOST</att:role>
          </meet:attendee>
        </meet:attendees>
      </meet:participants>
      <meet:schedule>
        <meet:startDate>03/10/2017 04:08:54</meet:startDate>
        <meet:timeZoneID>7</meet:timeZoneID>
        <meet:timeZone>GMT-06:00, Central (Chicago)</meet:timeZone>
        <meet:duration>5</meet:duration>
        <meet:openTime>300</meet:openTime>
        <meet:jocompanyeconfBeforeHost>true</meet:jocompanyeconfBeforeHost>
      </meet:schedule>
      <meet:attendeeOptions />
    </serv:bodyContent>
  </serv:body>
</serv:message>

Response:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:meet="http://www.webex.com/schemas/2002/06/service/meeting" xmlns:att="http://www.webex.com/schemas/2002/06/service/attendee">
  <serv:header>
    <serv:response>
      <serv:result>SUCCESS</serv:result>
      <serv:gsbStatus>PRIMARY</serv:gsbStatus>
    </serv:response>
  </serv:header>
  <serv:body>
    <serv:bodyContent xsi:type="meet:createMeetingResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <meet:meetingkey>929104235</meet:meetingkey>
      <meet:iCalendarURL>
        <serv:host>https://company.webex.com/company/j.php?MTID=mdf5ba3a750fe388d2b74b0e27cb5e6cf</serv:host>
        <serv:attendee>https://company.webex.com/company/j.php?MTID=m7a1fa94f46431d4b9bc6cb5ab7e1273c</serv:attendee>
      </meet:iCalendarURL>
      <meet:guestToken>3cfa40174a1880f140b64f5b8018f809</meet:guestToken>
    </serv:bodyContent>
  </serv:body>
</serv:message>

Step 2:
Request:
<?xml version="1.0"?>
<serv:message xmlns:meet="http://www.webex.com/schemas/2002/06/service/meeting" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:att="http://www.webex.com/schemas/2002/06/service/attendee" xmlns:serv="http://www.webex.com/schemas/2002/06/service">
  <serv:header>
    <serv:securityContext>
      <webExID xmlns="http://www.webex.com/schemas/2002/06/common">temp</webExID>
      <password xmlns="http://www.webex.com/schemas/2002/06/common">****</password>
      <siteName xmlns="http://www.webex.com/schemas/2002/06/common">company</siteName>
    </serv:securityContext>
  </serv:header>
  <serv:body>
    <serv:bodyContent xsi:type="meet:gethosturlMeeting">
      <meet:sessionKey>929104235</meet:sessionKey>
    </serv:bodyContent>
  </serv:body>
</serv:message>

Response:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:meet="http://www.webex.com/schemas/2002/06/service/meeting" xmlns:att="http://www.webex.com/schemas/2002/06/service/attendee">
  <serv:header>
    <serv:response>
      <serv:result>SUCCESS</serv:result>
      <serv:gsbStatus>PRIMARY</serv:gsbStatus>
    </serv:response>
  </serv:header>
  <serv:body>
    <serv:bodyContent xsi:type="meet:gethosturlMeetingResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <meet:hostMeetingURL>https://company.webex.com/company/p.php?AT=LI&WID=temp&TK=df31f74914f776017540e089498d1bb504d67e75394871370788b102ad10535a&MU=https%3A%2F%2Fcompany.webex.com%2Fcompany%2Fm.php%3FAT%3DHM%26MK%3D929104235%26Rnd%3D0.5130927062153927</meet:hostMeetingURL>
    </serv:bodyContent>
  </serv:body>
</serv:message>

Let me know if we need to include any extra parameters to the existing call to avoid the WebEx to prompt for Meeting ID.

Thanks in advance.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: