CallId not retained in history for Webex API

[IrinaFai]

Hi, 

I am new to WebexAPI and I cannot seem to figure out the following:

In https://developer.webex.com/docs/api/v1/call-controls/dial after sending the post request for the dial endpoint, I receive a callId and a callSessionId in the response.

If I then go here https://developer.webex.com/docs/api/v1/call-controls/answer I need to provide a callId in the body of the request. So I use the one I received in the dial response, however the response is 400/Bad Request and

{
"message": "Call not found",
"errors": [
{
"description": "Call not found",
"code": 101002
}
],
"trackingId": "CXAPI_916e5007-f267-414c-a8d5-2cb058f5e722_1"
}

How come the callId cannot be used? Eventually, I want to be able to have a response that is not empty in call history at https://developer.webex.com/docs/api/v1/call-controls/list-call-history

I hope this makes sense, thank you in advance!

[Jeff Marshall]

The /answer API is meant to be used answer a call on a user's primary hardware phone and answering through the Webex app is not officially supported yet. At this time it may or may not work if the user has the Desktop app as the only option selected for their "Webex application assignments".

When one Webex Calling user uses /dial to call another Webex Calling user in their org the callId that's returned by the dial request will not be the same callId that the receiving end will have. The receiving end would either need a webhook setup to trigger when they receive a call and pull the callId from the webhook payload or use the List Calls API to get the incoming call's callId in order to use it with /answer.