Creating a Meeting Not Working

[carlowahlstedt]

Tried using the sample code to create a meeting, but it doesn't work.

console.log('hello from Node.js')

const WebExClient = require('webex-api-client');
const securityContext = {
    webExID: 'ID',
    password: 'password',
    siteName: 'site'
};

const requestBuilder = new WebExClient.Builder(securityContext, 'https://site.webex.com/WBXService/XMLService');

const createMeeting =
    requestBuilder
        .metaData({
            confName: 'Sample Meeting',
            meetingType: 1,
        }).accessControl({
            listStatus: 'PUBLIC',
            registration: false,
            sessionPassword: '1234567890'
        }).schedule({
            startDate: new Date(), // today
            openTime: 900,
            duration: 30,
            timeZoneID: 5
        })
        .setService('CreateMeeting')
        .build();

// Initiate meeting whenever you are ready
createMeeting
    .exec()
    .then((resp) => console.log(resp));

I started adding the fields that it was throwing errors about, but got stuck on a ListStatus error. With or without adding list status (it's shown above), it still throws the following error:

<?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"><serv:header><serv:response><serv:result>FAILURE</serv:result><serv:reason>validation: unable to find FieldDescriptor for 'listStatus' in ClassDescriptor of accessControlType</serv:reason><serv:gsbStatus>PRIMARY</serv:gsbStatus><serv:exceptionID>999999</serv:exceptionID></serv:response></serv:header><serv:body><serv:bodyContent/></serv:body></serv:message>

[brh55]

@carlowahlstedt can you retry this code but without the listStatus in the accessControl.

[carlowahlstedt]

@brh55 It does the same without.

With or without adding list status (it's shown above), it still throws the following error:

[brh55]

@carlowahlstedt
The error is coming back from the WebEx service, letting us know that listStatus isn't a valid property of accessControlType. We do some validation client side before making request, but it's impossible to catch everything due to the tremendous amount of variations with each service type. This is the schema that should be used per latest schema docs on devnet for XML API 10.0 SP 12 when using the meeting service.

	<xsd:complexType name="accessControlType">
		<xsd:sequence>
			<xsd:element name="listToPublic" type="xsd:boolean" minOccurs="0"/>
			<xsd:element name="isPublic" type="xsd:boolean" minOccurs="0"/>
			<xsd:element name="meetingPassword" minOccurs="0">
				<xsd:simpleType>
					<xsd:restriction base="xsd:string">
						<xsd:maxLength value="16"/>
					</xsd:restriction>
				</xsd:simpleType>
			</xsd:element>
			<xsd:element name="enforcePassword" type="xsd:boolean" default="true" minOccurs="0"/>
		</xsd:sequence>
	</xsd:complexType>

So only the following properties should be used with the accessControl:

• listToPublic: Bool
• isPublic: Bool
• meetingPassword: String
• enforcePassword: Bool

I just want to piggy back on this issue:

We are getting this error:
{ "data": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<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>Meeting password must not be null</serv:reason><serv:gsbStatus>PRIMARY</serv:gsbStatus><serv:exceptionID>060026</serv:exceptionID></serv:response></serv:header><serv:body><serv:bodyContent/></serv:body></serv:message>" }

There is no documentation on how to put in a Meeting password (which is NOT the webexID password).

[brh55]

@digitalpomegranate You should be able to do it under securityContext

Thank you for the quick response. I do have the password in the securityContext:

const securityContext = {
webExID: req.param("userid",""),
password: req.param("password",""),
siteName: req.param("sitename","")
};

I don't think that is it, thou. For my client, I think they require a meeting password. Which is from the schema looks like this element "meetingPassword". Is there a way to set the "meetingPassword"?:

<xsd:complexType name="accessControlType">
xsd:sequence
<xsd:element name="listToPublic" type="xsd:boolean" minOccurs="0"/>
<xsd:element name="isPublic" type="xsd:boolean" minOccurs="0"/>
<xsd:element name="meetingPassword" minOccurs="0">
xsd:simpleType
<xsd:restriction base="xsd:string">
<xsd:maxLength value="16"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="enforcePassword" type="xsd:boolean" default="true" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>

[brh55]

@digitalpomegranate Sorry the schema links are now broken, but based on some PDFs, the accessControl schema has meetingPassword:

<accessControl>
     <meetingPassword>pass123</meetingPassword>
</accessControl>

So you should be able to pass it with the accessControl method once it's in the builder state like such:

.accessControl({
   password: 'pass123'
})

[yoloVoe]

Well, to anyone who has this problem....
Don't use the accessControl method.
It seems to stick in a list* field regardless of whether you want it or not when you use the accessControl method.

I got around it by doing this:
First, build your createMeeting object (code borrowed from OP):

const createMeeting =
    requestBuilder
        .metaData({
            confName: 'Sample Meeting',
            meetingType: 1,
        }).schedule({
            startDate: new Date(), // today
            openTime: 900,
            duration: 30,
            timeZoneID: 5
        })
        .setService('CreateMeeting')
        .build();

Do NOT use the accessControl method.

Then, access the xml payload by doing createMeeting.payload.
Pipe the output out.
Check the docs to see what the xml payload is supposed to look like if you want meetingPassword. Change the payload.

This is a hacky solution.

[carlowahlstedt]

Unfortunately, while I applaud the attempt to simplify the legacy SOAP WebEx APIs, the lack of support to actually do this and the issues that the API seem to have make even this solution not stable enough for me to consider putting into place.

[PriyakantVelocis]

Well, to anyone who has this problem....
Don't use the accessControl method.
It seems to stick in a list* field regardless of whether you want it or not when you use the accessControl method.

I got around it by doing this:
First, build your createMeeting object (code borrowed from OP):

const createMeeting =
    requestBuilder
        .metaData({
            confName: 'Sample Meeting',
            meetingType: 1,
        }).schedule({
            startDate: new Date(), // today
            openTime: 900,
            duration: 30,
            timeZoneID: 5
        })
        .setService('CreateMeeting')
        .build();

Do NOT use the accessControl method.

Then, access the xml payload by doing createMeeting.payload.
Pipe the output out.
Check the docs to see what the xml payload is supposed to look like if you want meetingPassword. Change the payload.

This is a hacky solution.

@yoloVoe Could you please elaborate the way how can we add meeting password on payload..