WebEx Calling API answer, requires optional "endpointId" parameter

[thomc]

Hey,

I try to answer an existing call on webex calling over the API out of WebEx Contact Center with Agent credentials.
(https://developer.webex.com/docs/api/v1/call-controls/answer)

The documentation says, the "endpointId" parameter is optional. The issue I'm facing is, the request returns with an error 400 (No Endpoint for call) if I don't provide an endpointId as a parameter.

I'm sure, this worked in the past. Are there any changes, that are not documented yet?

Second issue is to gather the Endpoint ID from Webex (Calling)
(https://developer.webex.com/docs/api/v1/user-call-settings/get-preferred-answer-endpoint)
I'm not allowed to access this with my WxCC Agent token.
Is there a workaround for this?
Is it possible to assign the scope (spark:telephony_config_read) for the wxcc agent?
This would solve the issue explained above.

Thank's and have a good day

[carlbidwell]

Thanks for posting this; it’s really useful to see others running into the same optional endpointId behavior when calling the Webex Calling Answer API and wondering why it suddenly seems required even though docs say it’s optional. In some cases it turns out to be tenant-specific or related to how the call is routed, but it’s great that folks are troubleshooting scopes and token permissions together so we can understand how preferred endpoints and answer behavior really work in practice. community.cisco.com

[upchaurasia]

It seems endpointid required. After passing endpointid it's working fine.

Thanks,

Umesh

[thomc]

Sorry for the delay,
In the end it was just an issue with our test tenant. The integration system worked and we couldn't find the issue on our test tenant.
Now it works without an endpoint parameter and the call is answered on the "default" device.
Thank you for your help
Regards
Christian

[sandiban]

Hi @thomc,

Thanks for checking over the Community Forum!
For the first one, you're getting a 404 error message for the /answer API while you're not providing the "enpointId" parameter in your request payload, is it possible to share an error trackingId please.
That'd help here to investigate further.
I'm not very sure if that request Body parameter has been made as mandatory, because I don't see anything on the API changelog recently - https://developer.webex.com/docs/api/changelog
But if so, at least there is a need of API documentation update then. 
And for this one, kindly share the details over devsupport@webex.com and it'd raise a Support case to our queue. That way, it'd be better to keep track of the progress and communicate further.

And regarding the second request, Yes for the API - /get-preferred-answer-endpoint - at least you should have the "spark:telephony_config_read" scope in your Token and this API is not configured to work with the WxCC agent token.
What you can do is, you can create a Webex Integration from here - https://developer.webex.com/my-apps/new and in the scope list, you can have the Contact Center scope/s as well as the "spark:telephony_config_read" scope.
And then use that Integration credentials to generate an Access Token following the documentation here - https://developer.webex.com/docs/integrations
Or, you can check this Blog post as well to generate an Integration Access token in just few minutes from POSTMAN - https://developer.webex.com/blog/generating-an-oauth-token-pair-using-a-webex-integration
Now use that Access Token for the API request and it should work! Let us know if you have any further queries.

Regards!
Sandip

[upchaurasia]

Hi Sandip,

I am facing same issue with Webex Calling Answer API, I am not setting any endpointId in body JSON. Below is the response I am getting from Webex -

Response: {"message":"No Endpoint for call","errors":[{"description":"No Endpoint for call","code":100020}],"trackingId":"CXAPI_65e38055-9b6f-48a2-9d65-32030f4abeac"}

Can you let me know what is the issue with our Answer method call?

Other API like Make Call, Reject, Disconnect, Hold & Resume working fine.

Is there any way to check Webex logs for our integration?

Thanks & Regards,

Umesh Chaurasia

[upchaurasia]

Hello Community Member & Cisco Support Team,

Waiting for response.

Thanks,

Umesh