Solved: Re: GetjoinurlMeeting xml API Response error

sud · ‎06-09-2020

<?xml version="1.0" encoding="ISO-8859-1"?>
<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <header>
        <securityContext>
            <webExID>sud</webExID>
            <password>xxx</password>
            <siteID>123</siteID>
            <partnerID>3343</partnerID>
        </securityContext>
    </header>
    <body>
        <bodyContent xsi:type="java:com.webex.service.binding.meeting.GetjoinurlMeeting">
            <sessionKey>123131231</sessionKey>
            <attendeeName>Sud J</attendeeName>
        </bodyContent>
    </body>
</serv:message>

Above XML service API call received below response from server.

<?xml version="1.0" encoding="ISO-8859-1"?>
<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>Null Point Error</serv:reason>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
            <serv:exceptionID>000000</serv:exceptionID>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

Can you help or correct me, if I am missing any syntax?

Thanks in advance.

nmorrow · ‎06-11-2020

Hello,

There is an uncaught exception that is throwing a null point error when a required value is missing in this request, attendeeEmail. There is an open bug report on this, and it will be addressed in a future release. You just need to add the required attendeeEmail element and value to get a working join link for that specific attendee.

View solution in original post

dstaudt · ‎06-11-2020

I can reproduce what you're seeing, at least on the apidemoeu.webex.com site. It works fine if you include only <sessionKey> in the body.

As I don't think you can have unique URLs per meeting per user (or per password, region, etc.) I'm not sure that anything other than <sessionKey> makes sense for the request...? What is the scenario where you need to specify the extra <attendeeName> field?

Given if true, the docs probably need to be updated to remove those extraneous elements, and the API should maybe give a more useful error if invalid fields are present.

Might suggest opening a ticket via email/portal here: https://developer.webex.com/support where they can open a defect and track/notify you on update.

nmorrow · ‎06-11-2020

Hello,

There is an uncaught exception that is throwing a null point error when a required value is missing in this request, attendeeEmail. There is an open bug report on this, and it will be addressed in a future release. You just need to add the required attendeeEmail element and value to get a working join link for that specific attendee.

sud · ‎06-11-2020

Thank you @nmorrow.

It's working fine now.