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.
Created by: Erik Nordgaard on 12-01-2011 10:25:01 PM Hello
I am trying to integrate a Codian MCU 4501 with a Crestron controller. Posting messages to the MCU seems to work but I always get the same fault message in return from the RPC server. I have tried the examples presented in the “Codian Remote Management API V5.1” document without any result. I have pasted the XML code I try to send at the bottom of the mail. At the moment I am using a TCP client program to test the communication with the MCU.
I have sent a mail regarding the problem to one of your colleges, he returned this answer that he copied from another thread in the same forum: -------------------------------------------------------------------------------------------------------------------------------- It looks like they are missing the operation scope parameter, this is from that thread: The operationScope parameter specified in section 4.20 of the API document is not optional. You must include it to get the result you expect from the MCU. In your case, since you want to know about current active calls, this parameter should be set to the value "currentState". So the part of your code inside the <struct> tag should look like the following: 1 2<member> 3 <name>authenticationUser</name> 4 <value><string>admin</string></value> 5</member> 6<member> 7 <name>authenticationPassword</name> 8 <value><string>BLABLA</string></value> 9</member> 10<member> 11 <name>enumerateFilter</name> 12 <value><string>connected</string></value> 13</member> 14<member> 15 <name>operationScope</name> 16 <value> 17 <array> 18 <data> 19 <value> 20 <string>currentState</string> 21 </value> 22 </data> 23 </array> 24 </value> 25</member> ---------------------------------------------------------------------------------------------------------------------
I have already seen this thread and tested it with the same error result. It mentions the Operationscope specified in section 4.20. I can’t find any section 4.20 in the API documentation. Looking at the conference.create method in the API document there is nothing mentioning any operationscope. I have neither found any topic that mentions that an opertionscope is “not optional” in every message sent to the MCU.
My question: The example I have pasted in this mail is just a test, I don’t need that function in my program. I have just tried to use your example-code from the API documentation to test that I am sending the correct syntax to the MCU. Any XML code that makes the MCU answer something correct is good, I can than continue working out from that XML form who I know works ok.
Could you please take a look at the code at the bottom or just send me an example that you have confirmed by testing against the MCU that will respond without a faultcode? It would be greatly appreciated.
MCU Setup: In the MCU I added a test user: api_test with password: 123456. The MCU IP address: 10.0.0.30 Changed the conference date from 2005 to 2011 in the XML code.
I use a TCP client with the following setup: IP : 10.0.0.30 Port : 80 Timeout in 5 sec.
This is the code I send from the client and the return answer I always receive no matter the XML example I use: -------------------------------------------------------------------------------------------------- Attempting TCP Client Connection... Windows is attempting to connect... TCP Client Connected... Sending the following header = :
POST /RPC2 HTTP/1.1 User-Agent: Frontier/5.1.2 (WinNT) Host: 10.0.0.30 Content-Type: text/xml
---------------------------------------------------------------------------------------------- The response answer from the MCU: HTTP/1.1 200 OK Connection: close Content-Type: text/xml Content-Length: 404
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
