joinTeleconfBeforeHost not working for CALLIN telephony type

Hello all,

My name is Maxi. I'm working with a bug related with the impossibility to create webex meetings using the API. Debugging the code, I figured out that the problem is related with the joinTeleconfBeforeHost attribute. The error I'm getting is this:

<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>FAILURE</serv:result>
<serv:reason>JoinTeleconfBeforeHost is not supported for specified telephony type</serv:reason>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
<serv:exceptionID>999999</serv:exceptionID>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent/>
</serv:body>
</serv:message>

This is my request XML:

<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:serv="http://www.webex.com/schemas/2002/06/service"
  xsi:schemaLocation="http://www.webex.com/schemas/2002/06/service">
  <header>
  <securityContext>
  <webExID>THEID</webExID>
  <password>THE PASSWORD</password>
  <siteName>THE SITE</siteName>
  </securityContext>
  </header>
  <body>
  <bodyContent xsi:type="java:com.webex.service.binding.meeting.CreateMeeting">
  <accessControl>
  <meetingPassword>1665</meetingPassword>
  <listToPublic>false</listToPublic>
  <isPublic>false</isPublic>
  </accessControl>
  <metaData>
  <confName>Otro Test</confName>
  <agenda>Otro Test</agenda>
  <greeting>Welcome to THE SITE</greeting>
  </metaData>
  <participants>
  <maxUserNumber>12</maxUserNumber>
  </participants>
  <enableOptions>
  <chat>true</chat>
  <meetingRecord>false</meetingRecord>
  <audioVideo>true</audioVideo>
  <attendeeList>true</attendeeList>
  <fileShare>true</fileShare>
  <presentation>true</presentation>
  <applicationShare>true</applicationShare>
  <desktopShare>true</desktopShare>
  <annotation>true</annotation>
  <importDocument>true</importDocument>
  <saveDocument>true</saveDocument>
  <printDocument>true</printDocument>
  <pointer>true</pointer>
  <switchPage>true</switchPage>
  <fullScreen>true</fullScreen>
  <thumbnail>true</thumbnail>
  <zoom>true</zoom>
  <chatHost>true</chatHost>
  <chatPresenter>true</chatPresenter>
  <chatAllAttendees>true</chatAllAttendees>
  </enableOptions>
  <schedule>
  <startDate>01/02/2015 12:00:00</startDate>
  <hostWebExID>THE HOST</hostWebExID>
  <openTime>900</openTime>
  <joinTeleconfBeforeHost>true</joinTeleconfBeforeHost>
  <duration>60</duration>
  <timeZoneID>17</timeZoneID>
  </schedule>
  <telephony>
  <telephonySupport>CALLIN</telephonySupport>
  <numPhoneLines>16</numPhoneLines>
  </telephony>
  <attendeeOptions>
  <request>false</request>
  <registration>false</registration>
  <auto>false</auto>
  <emailInvitations>false</emailInvitations>
  <joinRequiresAccount>false</joinRequiresAccount>
  </attendeeOptions>
  </bodyContent>
  </body>
</serv:message>

I don't know if something changed in the API or what is the problem. This is something that was working. Due to the telephonySupport is CALLIN, I tried adding callInNum, but this didn't work and I got the same error.

I hope you can help me.

Thanks in advance,

Maxi

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Hello,

This bug has been previously reported and a fix is scheduled for some time later this month.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Thanks Nathan for your answer.

Do you think the patch to this is to set joinTeleconfBeforeHost to false? Is there another workaround we can take?

Thanks!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Hello,

You can set it to false, or remove it from the request entirely as it defaults to false. I would test setting it to true in a couple weeks to see if the update was pushed yet.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Great! Many thanks for your help!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Articles in this section

Comments