未呼叫Sinch已接呼叫事件回调(ACE) [英] Sinch Answered Call Event Callback (ACE) not called

问题描述

我已在Sinch门户中添加了回调，以通过我们的服务器处理应用之间的调用.当呼叫到达Sinch平台时，系统会向我们服务器的呼叫回调URL(即被呼叫来电事件回调(ICE))发出POST请求.

I have added a Callback in Sinch portal to handle app to app calls via our server. When a call reaches the Sinch platform, the system makes a POST request to our server's calling callback URL i.e. Incoming Call Event Callback (ICE) called.

响应ICE事件，我们的服务器将其响应为

In response to ICE event our server response it as

{
  "instructions": [],
  "action": {
    "name": "connectMXP"
  }
}

，被叫方会收到来电通知.当被呼叫者代答呼叫时，呼叫会接通，但不会请求我们服务器的回叫URL，即未调用ACE事件.

and callee receive incoming call notification. When Callee pick-up call the call get connected but it doesn't request to our server's callback URL, i.e. ACE event not called.

但是如当被叫方(接听电话的人)接听电话时，将进行此回调.这是对指定的调用回调URL的POST请求.

This callback is made when the call is picked up by the callee (person receiving the call). It is a POST request to the specified calling callback URL.

所以问题是接收ACE事件回调需要什么，是否有任何缺失应在代码的Sinch端或我们的服务器端启用?谢谢 ！

So the question is what is required to receive ACE event callback, is there anything missing which should be enable at Sinch side or our server side in code ? Thanks !

推荐答案

App2APp调用仅支持ICE和DICE事件.如果您授权呼叫者呼叫被呼叫者用户，为什么还需要另一个事件通知?由于呼叫主要基于peer2Peer，因此我们目前不支持ACE或PIE事件进行数据呼叫.

App2APp calls only support ICE and DICE events. If you authorized the Caller to Call the Callee user, why do you need another event notification? As the calls are mostly peer2Peer based we currently do not support ACE or PIE events for Data calls.

这篇关于未呼叫Sinch已接呼叫事件回调(ACE)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！