innovaphone Forum

You are here

Help with Search (new window)
Picture of marcorcau
Registered 5 years 321 days
marcorcau Monday, 16 August 2021, 06:00 PM
Agenda SDK Dialog: Meaning and flows of the CallInfo messages in RCC API

Hello,


we are developing an app that triggers internal phonecalls under certain conditions and monitors those calls making use of the RCC API.


Phonecalls are done with the UserCall method and after execution of UserInitialize our app is successfully informed of all call events via CallInfo messages.


After some try and test we have obtained basic knowledge of the CallInfo messages received in different situations but it would be of great help to get more information on the different flows of this CallInfo messages.


Information is contained in field "msg": Name of signaling message related to this update


Specifically we are interested in detection of following situations regarding the call destination:


- It does not exist or is not available on any device

- Phone rings but no answer

- Phone is picked

- Phone is hung


Are those signaling messages documented somewhere in the API docs?


The nearest information we found is in the "state" field of the CallAdd method:


The call state 0 - init, 1 - setup, 2 - setup-ack, 3 - call-proc, 4 - alert, 5 - conn, 6 - disc-sent, 7 - disc-received, 8 -parked

Add 128 for outgoing, add 256 for hold, add 512 for held, add 1024 for waiting

 

But It would still be of great help some better explanation about the different possible flows, that's why we propose you do some explaining about this in a friday's Dialog, unless some documentation which I didn't find exists.


Thank you !!!

Marc ///



p, li { white-space: pre-wrap; }
2013
Moderator Registered 16 years 15 days
Guntram Diehl (innovaphone) Friday, 20 August 2021, 09:19 AM
Re: Agenda SDK Dialog: Meaning and flows of the CallInfo messages in RCC API
Hi,
I think most can be found in the SDK documentation, but maybe not explained yery well.
For your concrete questions:
  • call destination does not exist, does not answer: There should be different cause codes found in the CallInfo messages in theses cases
  • call is picked: I am not shure if this can be seen different then just a call which is answered. You could look at the CallInfo in this case. If you are not shure, please ask how to interpret what you get here
  • phone is hung. You mean a normal termination of the call. The state changes back to 0, no cause or a cause code 16 (normal clearing) should be seen.
← You can define your color theme preference here