-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
- HP Community
- Poly Video Conferencing
- Collaboration & Conferencing Platforms
- XML Format for API on RSS 4000
Create an account on the HP Community to personalize your profile and ask a question
02-09-2012 06:00 AM
I am writing a front end for our RSS 4000 and intend to use the Web Service API.
So far I have a proof of concept which can make a SOAP connection (using ws-security) and call functions.
The problem I have is calling funtions with parameters (there is no example of this in the API Documentation)
Please see below for my XML
Firstly calling getTemplates and getting an expected response and then calling getTemplate with a parameter of templateId = 1 and getting an empty response.
Is my syntax incorrect?
Thanks
Calling getTemplates with NO parameters
INPUT
<env:Envelope xmlns:wsdl="http://services.ws.rss.polycom.com/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ins0="http://services.ws.rss.polycom.com/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Header> <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> <wsse:UsernameToken wsu:Id="UsernameToken-1" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <wsse:Username>xUSERx</wsse:Username> <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">xPASSx</wsse:Password> </wsse:UsernameToken> </wsse:Security> </env:Header> <env:Body> <ins0:getTemplates></ins0:getTemplates> </env:Body> </env:Envelope>
OUPUT
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns1:getTemplatesResponse xmlns:ns1="http://services.ws.rss.polycom.com/"> <return> <autoLivestreaming>false</autoLivestreaming> <layoutType>LARGE</layoutType> <streams> <bitrate>2048</bitrate> <format>ASF1</format> </streams> <streams> <bitrate>1024</bitrate> <format>ASF2</format> </streams> <streams> <bitrate>2048</bitrate> <format>MP4</format> </streams> <templateID>1</templateID> <templateName>Default_Template</templateName> </return> </ns1:getTemplatesResponse> </soap:Body> </soap:Envelope>
Calling getTemplate with paramater templateId = 1
INPUT
<env:Envelope xmlns:wsdl="http://services.ws.rss.polycom.com/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ins0="http://services.ws.rss.polycom.com/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Header> <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> <wsse:UsernameToken wsu:Id="UsernameToken-1" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <wsse:Username>xUSERx</wsse:Username> <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">xPASSx</wsse:Password> </wsse:UsernameToken> </wsse:Security> </env:Header> <env:Body> <ins0:getTemplate> <ins0:templateId>1</ins0:templateId> </ins0:getTemplate> </env:Body> </env:Envelope>
OUTPUT
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns1:getTemplateResponse xmlns:ns1="http://services.ws.rss.polycom.com/"></ns1:getTemplateResponse> </soap:Body> </soap:Envelope>
Solved! Go to Solution.
Accepted Solutions
02-09-2012 07:21 AM
OK it turns out that the SOAP client I was using (savon for ruby) was adding "ins0:" to each of the fields, which was affecting parameters but not function calls.
So some config change removed that and it's now working as expected.
<env:Body> <getTemplate> <templateId>1</templateId> </getTemplate> </env:Body>
02-09-2012 07:21 AM
OK it turns out that the SOAP client I was using (savon for ruby) was adding "ins0:" to each of the fields, which was affecting parameters but not function calls.
So some config change removed that and it's now working as expected.
<env:Body> <getTemplate> <templateId>1</templateId> </getTemplate> </env:Body>
Didn't find what you were looking for? Ask the community