Your syntax looks ok for the generic TANDBERG api and also the formputxml uri seems to exist on the VCS.
I tried to find some official API guide for the VCS but I did not succeed. Also the generic VCS doc or online help
is very silent about hat.
I also did not succeed with that request. If its critical for you you could ask Cisco TAC what the expected behavior
should be and then if neccessary file a feature request.
That said, why dont you use putxml and POST?
With your XML in the request and that works fine for me (Off, Direct, ...)
(and I also checked that the value got changed)
From the endpoint api guide:
Using HTTP POST
When sending configurations and commands to the codec, it is important that the HTTP header Content-Type is set to text/xml, i.e. Content-Type: text/xml. The body of the POST should contain the XML content.
Example 1: Changing the system name. Request
If you have questions on how yo use post, check with google first, there should be plenty of guides,
even with CURL or WGET and sure for (scripting) languages or whatever you use as well.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...