Hello Dirk,
I looked at the trace and the message flow (modified not to have real names / numbers).
- send: {"mt":"Initialize","api":"RCC"}
- send: {"mt":"UserInitialize","api":"RCC","cn":"test-2"}
- send: {"mt":"UserCall","api":"RCC","e164":123,"cn":"Some Name","rc":0,"user":"some.name","audio":false,"srce164":"01234567890","h323":"some.name"}
- recv: {"api":"RCC","mt":"UserInitializeResult"}
- recv: {"api":"RCC","mt":"UserCallResult","call":0,"error":"user unknown"}
- recv: {"mt":"InitializeResult","api":"RCC"}
Some thoughts, when comparing with the documentation of the RCC API:
http://sdk.innovaphone.com/doc/appwebsocket/RCC.htm
- I'm not sure if the application should better wait for the result messages, so the flow would then look like follows: Initialize/InitializeResult, UserInitialize/UserInitializeResult, UserCall/UserCallResult. But I'm not sure if this is a problem here.
- Between the Initialize and the InitializeResult, I would expect some UserInfo messages. So no users are visible to the app? This could be a configuration problem. There are some hints in the docu about different configuration options.
- UserInitialize seems to be the first thing that fails. If "cn":"test-2" would be found, we should see an attribute "user" in UserInitialize result, that's the handle that can be used for UserCall later on.
- In UserCall you use a string "user". From the docu it looks like "user" should be the integer ID returned by UserInitializeResult.
Hoping this was helpful.
Best regards
Matthias
