<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: GetjoinurlMeeting xml API Response error in Cloud Collaboration</title>
    <link>https://community.cisco.com/t5/cloud-collaboration/getjoinurlmeeting-xml-api-response-error/m-p/4101830#M2155</link>
    <description>&lt;P&gt;I can reproduce what you're seeing, at least on the apidemoeu.webex.com site.&amp;nbsp; It works fine if you include only &amp;lt;sessionKey&amp;gt; in the body.&lt;/P&gt;
&lt;P&gt;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 &amp;lt;sessionKey&amp;gt; makes sense for the request...?&amp;nbsp; What is the scenario where you need to specify the extra &amp;lt;attendeeName&amp;gt; field?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;Might suggest opening a ticket via email/portal here: &lt;A href="https://developer.webex.com/support" target="_blank"&gt;https://developer.webex.com/support&lt;/A&gt; where they can open a defect and track/notify you on update.&lt;/P&gt;</description>
    <pubDate>Thu, 11 Jun 2020 20:17:45 GMT</pubDate>
    <dc:creator>dstaudt</dc:creator>
    <dc:date>2020-06-11T20:17:45Z</dc:date>
    <item>
      <title>GetjoinurlMeeting xml API Response error</title>
      <link>https://community.cisco.com/t5/cloud-collaboration/getjoinurlmeeting-xml-api-response-error/m-p/4100011#M2154</link>
      <description>&lt;PRE&gt;&amp;lt;?xml version="1.0" encoding="ISO-8859-1"?&amp;gt;
&amp;lt;serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"&amp;gt;
    &amp;lt;header&amp;gt;
        &amp;lt;securityContext&amp;gt;
            &amp;lt;webExID&amp;gt;sud&amp;lt;/webExID&amp;gt;
            &amp;lt;password&amp;gt;xxx&amp;lt;/password&amp;gt;
            &amp;lt;siteID&amp;gt;123&amp;lt;/siteID&amp;gt;
            &amp;lt;partnerID&amp;gt;3343&amp;lt;/partnerID&amp;gt;
        &amp;lt;/securityContext&amp;gt;
    &amp;lt;/header&amp;gt;
    &amp;lt;body&amp;gt;
        &amp;lt;bodyContent xsi:type="java:com.webex.service.binding.meeting.GetjoinurlMeeting"&amp;gt;
            &amp;lt;sessionKey&amp;gt;123131231&amp;lt;/sessionKey&amp;gt;
            &amp;lt;attendeeName&amp;gt;Sud J&amp;lt;/attendeeName&amp;gt;
        &amp;lt;/bodyContent&amp;gt;
    &amp;lt;/body&amp;gt;
&amp;lt;/serv:message&amp;gt;&lt;/PRE&gt;&lt;P&gt;Above XML service API call received below response from server.&lt;/P&gt;&lt;PRE&gt;&amp;lt;?xml version="1.0" encoding="ISO-8859-1"?&amp;gt;
&amp;lt;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"&amp;gt;
    &amp;lt;serv:header&amp;gt;
        &amp;lt;serv:response&amp;gt;
            &amp;lt;serv:result&amp;gt;FAILURE&amp;lt;/serv:result&amp;gt;
            &amp;lt;serv:reason&amp;gt;Null Point Error&amp;lt;/serv:reason&amp;gt;
            &amp;lt;serv:gsbStatus&amp;gt;PRIMARY&amp;lt;/serv:gsbStatus&amp;gt;
            &amp;lt;serv:exceptionID&amp;gt;000000&amp;lt;/serv:exceptionID&amp;gt;
        &amp;lt;/serv:response&amp;gt;
    &amp;lt;/serv:header&amp;gt;
    &amp;lt;serv:body&amp;gt;
        &amp;lt;serv:bodyContent/&amp;gt;
    &amp;lt;/serv:body&amp;gt;
&amp;lt;/serv:message&amp;gt;&lt;/PRE&gt;&lt;P&gt;Can you help or correct me, if I am missing any syntax?&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 09 Jun 2020 11:56:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-collaboration/getjoinurlmeeting-xml-api-response-error/m-p/4100011#M2154</guid>
      <dc:creator>sud</dc:creator>
      <dc:date>2020-06-09T11:56:39Z</dc:date>
    </item>
    <item>
      <title>Re: GetjoinurlMeeting xml API Response error</title>
      <link>https://community.cisco.com/t5/cloud-collaboration/getjoinurlmeeting-xml-api-response-error/m-p/4101830#M2155</link>
      <description>&lt;P&gt;I can reproduce what you're seeing, at least on the apidemoeu.webex.com site.&amp;nbsp; It works fine if you include only &amp;lt;sessionKey&amp;gt; in the body.&lt;/P&gt;
&lt;P&gt;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 &amp;lt;sessionKey&amp;gt; makes sense for the request...?&amp;nbsp; What is the scenario where you need to specify the extra &amp;lt;attendeeName&amp;gt; field?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;Might suggest opening a ticket via email/portal here: &lt;A href="https://developer.webex.com/support" target="_blank"&gt;https://developer.webex.com/support&lt;/A&gt; where they can open a defect and track/notify you on update.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jun 2020 20:17:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-collaboration/getjoinurlmeeting-xml-api-response-error/m-p/4101830#M2155</guid>
      <dc:creator>dstaudt</dc:creator>
      <dc:date>2020-06-11T20:17:45Z</dc:date>
    </item>
    <item>
      <title>Re: GetjoinurlMeeting xml API Response error</title>
      <link>https://community.cisco.com/t5/cloud-collaboration/getjoinurlmeeting-xml-api-response-error/m-p/4101841#M2156</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;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.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jun 2020 20:41:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-collaboration/getjoinurlmeeting-xml-api-response-error/m-p/4101841#M2156</guid>
      <dc:creator>nmorrow</dc:creator>
      <dc:date>2020-06-11T20:41:26Z</dc:date>
    </item>
    <item>
      <title>Re: GetjoinurlMeeting xml API Response error</title>
      <link>https://community.cisco.com/t5/cloud-collaboration/getjoinurlmeeting-xml-api-response-error/m-p/4101976#M2157</link>
      <description>Thank you &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/623201"&gt;@nmorrow&lt;/a&gt;.&lt;BR /&gt;&lt;BR /&gt;It's working fine now.</description>
      <pubDate>Fri, 12 Jun 2020 04:23:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-collaboration/getjoinurlmeeting-xml-api-response-error/m-p/4101976#M2157</guid>
      <dc:creator>sud</dc:creator>
      <dc:date>2020-06-12T04:23:05Z</dc:date>
    </item>
  </channel>
</rss>

