Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
I'm very encouraged by the coming improvements announced in XML API v10, SP12...primarily because we can now get to interact with the Trash via the API.The documentation theoretically can be found here: Cisco DevNet: WebEx Conferencing - XML API - Re...
The nbr2mp4 command line tool for Linux is available here: Utilities | WebExHowever it does not work properly after following the posted instructions. There is no support available through the traditional channels for this tool - one support tech tol...
We need to manage (add / edit / remove) tracking codes programmatically via the XML API. The documentation I have is incredibly unclear on how / if this is possible.I see that we can access information on tracking codes with site.GetSite, but how can...
I just want to retrieve our site's recording storage limit via the API. I have checked through the Site service GetSite endpoint and cannot find anything about getting the recording storage limit...though I can find the file storage limits just fine ...
We have a problem with the new feature introduced in 31.5 - recordings can now be moved to "Trash".Problem is, once this happens, the API returns "Not Found" when querying for the recording. Yet it still counts against our site quota.One of the thing...
Well it looks like sometime over the weekend SP12 was added to the listCisco DevNet: WebEx Conferencing - XML API - Release NotesSo I'm happy for the moment.
Martin,We are doing the same, applying tracking codes to users. The XML was a bit tricky for us to implement, but here's how I ended up structuring it.As part of the user.CreateUser or user.SetUser endpoints, include something like this:<tracking>
...
No problem! Let me know if you have any questions. It's been reliable for us. I should specify that we are creating all of our accounts via API, if that makes any difference.
