Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- :
- About nmorrow
nmorrow
Cisco Employee
Jack of all trades, master of most
Recent Badges
Stats
Member since
02-06-2014
355
Posts
107
Helpful
105
Solutions
08-05-2019
09:41 AM
This error just means that the siteName value was incorrect for the XML service URL being used. You should be sure to include the entire subdomain of your Webex site URL, if your site URL is webExSiteURL.my.webex.com, your siteName would be "webExSiteURL.my". Note that *.my.webex.com sites are not officially supported for the developer program, but the API should still work if all variables are correct.
... View more
Created by
nmorrow
in Cloud Collaboration
in Cloud Collaboration
08-13-2018
04:36 PM
08-13-2018
04:36 PM
Hello,
The service is designed so that a change like this should not have impacted production services, but unfortunately NBR API usage was not considered. I have followed up with engineering on a solution for future changes.
... View more
Created by
nmorrow
in Cloud Collaboration
in Cloud Collaboration
08-13-2018
01:20 PM
08-13-2018
01:20 PM
Hello,
Service URL is site wide, it would not be different for encrypted only. If the service URL did change, there is a chance that older recordings are still present on the older service URL location but you should still update the service URL going forward to ensure you can continue to download new recordings.
... View more
Created by
nmorrow
in Cloud Collaboration
in Cloud Collaboration
08-13-2018
01:02 PM
08-13-2018
01:02 PM
Hello,
That error message most likely means that the NBR service URL you are using is incorrect. It is possible that NBR service URLs may have been silently changed at some point to rebalance recording usage globally. You may request your NBR service URL information by emailing devsupport@webex.com with your WebEx site URL and asking for your NBR service URL.
... View more
Created by
nmorrow
in Cloud Collaboration
in Cloud Collaboration
07-02-2018
11:11 AM
07-02-2018
11:11 AM
Hello, This part of the forum is specific to WebEx Meetings API development and it might not be monitored or reviewed by any WebEx Teams API developers or support reps. You may seek additional support for your bot development questions by visiting https://developer.webex.com or sending your question to devsupport@webex.com .
... View more
06-25-2018
05:26 PM
Thanks, I think this will show that the NBR API isn't necessarily the faulty part of the equation, it serves to reason that the ARF cannot be packaged because the recording has become corrupted in some way. I can really only guess at the explanation of any corruption, NBR is a collection of multiple pieces of data when stored in the WebEx cloud and moving that data to the recycle bin may not be as simple as moving a file in a directory tree or setting an inactive flag in a database table. It would be best to contact the technical support team via the contact methods provided when signing in to http://support.webex.com , they may have previous experience with this exact issue, or have an established escalation procedure to correct corrupted recordings or create a bug report for recovered recordings. Feel free to refer to this forum thread, it is publicly accessible.
... View more
06-25-2018
04:26 PM
Hello, Thanks for the additional information. There is one more thing I will need to know before I can recommend the best course of action. Are you able to manually download the same recording from the WebEx user interface? If so, do the lstRecording fileURL and streamURL both work and play back properly? If all yes, I will need to report to engineering on a possible NBR API bug. If all no, technical support may be a better resource to properly escalate as a corrupted recording that might be recoverable.
... View more
06-25-2018
11:14 AM
Hello, I have seen this error in the past when the recording owner account has been deactivated. There could also be an issue with the record ID, depending on how you are retrieving it. You may try calling the NBR API request getRecordIdList to see if your record ID is present in the list. You may also try calling XML API request lstRecording with one or more serviceType values specified, and again with no serviceType element to try the differing record IDs that it provides. Unfortunately, the error doesn't provide much information to go on, other than some data is missing from the record entry to properly package the ARF file for download.
... View more
Created by
nmorrow
in Developer General Discussions
in Developer General Discussions
06-22-2018
09:35 AM
06-22-2018
09:35 AM
Hello, That error usually means that the WebExID and/or password are incorrect for the site you are using. You should try to use the exact same values to log on directly to the site. Traditional WebEx sites don't typically use the full email address as the username, although it is supported, but I suspect that this site does not use the full email address.
... View more
Created by
nmorrow
in Cloud Collaboration
in Cloud Collaboration
06-21-2018
11:42 AM
06-21-2018
11:42 AM
Hello, XML API request user.SetUser can be used to reactivate inactive accounts. You can review usage of this request in the XML API reference guide's User Service chapter.
... View more
Created by
nmorrow
in Cloud Collaboration
in Cloud Collaboration
06-19-2018
01:45 PM
06-19-2018
01:45 PM
Hello, I cannot help with the CWMS API service, but I can answer your concern from the cloud based WebEx Meetings API perspective. XML API service error messages will appear as successful HTTPS requests if you are only checking HTTP status code. The actual error message would be needed to determine the cause of failure, but the example XML in your code is definitely using an incorrect siteName value, WebExID value, password value, and meetingType value. I cannot confirm the XML service URL, but you may also try launching the service URL in a web browser inside your network to see if a default XML service response is returned.
... View more
Created by
nmorrow
in Cloud Collaboration
in Cloud Collaboration
06-08-2018
11:13 AM
06-08-2018
11:13 AM
Thank you for providing the exact link that is failing, it makes more sense now. The link to that file is broken and I am able to duplicate that 404. You can use the following PHP code as a minimalist example of sending a XML document to the XML Service and displaying the response data. <?php header( "Content-Type: text/xml" ); $sitename = "apidemoeu" ; //Sitename is the subdomain of a WebEx URL. ex: sitename for https://apidemoeu.webex.com is apidemoeu $username = "username" ; $password = "password" ; $XML = "<?xml version=\"1.0\" encoding=\"UTF-8\" ?> "; $XML . = "<serv:message xmlns:xsi=\" http://www.w3.org/2001/XMLSchema-instance \">" ; $XML . = " <header>" ; $XML . = " <securityContext>" ; $XML . = " <webExID>$username</webExID>" ; $XML . = " <password>$password</password>" ; $XML . = " <siteName>$sitename</siteName>" ; $XML . = " <returnAdditionalInfo>TRUE</returnAdditionalInfo>" ; $XML . = " </securityContext>" ; $XML . = " </header>" ; $XML . = " <body>" ; $XML . = " <bodyContent xsi:type=\"java:com.webex.service.binding.site.GetSite\">" ; $XML . = " </bodyContent>" ; $XML . = " </body>" ; $XML . = "</serv:message>" ; $request = stream_context_create( array ( "http" => array ( "method" => "POST" , "header" => "Content-Type:text/xml" , "content" =>$XML))); $response = file_get_contents( " https://$sitename.webex.com/WBXService/XMLService " , false, $request); echo $response; ?>
... View more
Created by
nmorrow
in Cloud Collaboration
in Cloud Collaboration
06-05-2018
03:55 PM
06-05-2018
03:55 PM
Meetings API documentation can be found by browsing to http://www.webexdeveloper.com and following the drop down menus from Develop & Test to XML API, then XML API Reference or Sample Code. I am able to browse to these pages outside of the Cisco network currently. If you continue to experience 404s, please clear your browser cache and try again. If still failing, you may also want to try clearing your cookies. If you still have an issue, you will want to start troubleshooting probable network communication issues, such as bad proxy or firewall rules, or network outage.
... View more
Created by
nmorrow
in Cloud Collaboration
in Cloud Collaboration
05-11-2018
02:59 PM
05-11-2018
02:59 PM
Hello, That is due to a security enhancement a while back that disallows sensitive data in HTTPS GET strings because they are more easily human readable in browser history. You will need to issue this request in HTTPS POST format to ensure the event password is not ignored. This security restriction applies to any password value and partner ID, as they are all sensitive data.
... View more
Created by
nmorrow
in Cloud Collaboration
in Cloud Collaboration
05-08-2018
01:30 PM
05-08-2018
01:30 PM
Hello, The meetingTypes list that you provide in your SetUser request will overwrite whatever is there, so a null set will remove all types; <meetingTypes><meetingType/></meetingTypes>. For audio, If you wish to remove a personal teleconference account, you would simply add <delete>TRUE</delete> to the audio account details as below; <personalTeleconf> <account> <accountIndex>1</accountIndex> <delete>TRUE</delete> </account> </personalTeleconf>
... View more
08-05-2019
This error just means that the siteName value was incorrect for the XML
service URL being used. You ...
Created by
nmorrow
in Cloud Collaboration
08-13-2018
08-13-2018
Hello, The service is designed so that a change like this should not
have impacted production servic...
Created by
nmorrow
in Cloud Collaboration
08-13-2018
08-13-2018
Hello, Service URL is site wide, it would not be different for encrypted
only. If the service URL di...
Created by
nmorrow
in Cloud Collaboration
08-13-2018
08-13-2018
Hello, That error message most likely means that the NBR service URL you
are using is incorrect. It ...
Created by
nmorrow
in Cloud Collaboration
07-02-2018
07-02-2018
Hello, This part of the forum is specific to WebEx Meetings API
development and it might not be moni...
06-25-2018
Thanks, I think this will show that the NBR API isn't necessarily the
faulty part of the equation, i...
06-25-2018
Hello, Thanks for the additional information. There is one more thing I
will need to know before I c...
06-25-2018
Hello, I have seen this error in the past when the recording owner
account has been deactivated. The...
06-22-2018
Hello, That error usually means that the WebExID and/or password are
incorrect for the site you are ...
06-21-2018
Hello, XML API request user.SetUser can be used to reactivate inactive
accounts. You can review usag...
06-19-2018
Hello, I cannot help with the CWMS API service, but I can answer your
concern from the cloud based W...
06-08-2018
Thank you for providing the exact link that is failing, it makes more
sense now. The link to that fi...
06-05-2018
Meetings API documentation can be found by browsing to
http://www.webexdeveloper.com and following t...
05-11-2018
Hello, That is due to a security enhancement a while back that disallows
sensitive data in HTTPS GET...
Public Statistics
| Date Registered | 02-06-2014 04:38 PM |
| Date Last Visited | 08-15-2019 11:55 PM |
| Total Messages Posted | 355 |
| Total Helpful Votes Received | 107 |
Helpful Votes From
