The /reject endpoint is a POST method, not DELETE
Wrong method
DELETE /v1.0/account/~/telephony/sessions/s-a78cc422b5db2z19590b054e4z385af420000/parties/p-a78cc422b5db2z19590b054e4z385af420000-2/reject
You can/should use the drop call session API for all call status (Setup | Proceeding | Answered)
E.g.
DELETE /v1.0/account/~/telephony/sessions/s-a78cc422b5db2z19590b054e4z385af420000
If you get the error “403 Forbidden”
"errors": s
{
"errorCode": "TAS-106",
"message": "Operation is not allowed"
}
]
It seems you try to drop a call which does not belong to the user who authenticated the app. Only the owner (the call party) of the call can control his calls.
Good catch. I updated the reject to use POST and this resolved the AGW-404 error, but now I’m just getting TAS-106 errors.
How can I create a service that can terminate the calls of any extension? Should I open a new topic for this question?
Good catch. I updated the reject to use POST and this resolved the AGW-404 error, but now I’m just getting TAS-106 errors.
How can I create a service that can terminate the calls of any extension? Should I open a new topic for this question?
You can authenticate your app with the main super admin user (normally the user extension 101). Only that super admin can control calls of other users under the same account.
