The following table lists the HTTP status codes that are used by the Call Setup API to denote the success or failure of a request made to the Call Setup API:

HTTP Status Code and Text

Usage

200 OK

The request was successful.

400 Bad Request

Invalid contextual information passed for the request. For example:

Invalid call delay period.

Invalid user extension.

403 Forbidden

The server understood the request but is refusing to fulfil it. For example:

Pre‐call authorization failed

Unable to end a call that is already ending.

404 Not Found

Resource is not accessible. For example:

Badly formed request URI.

A resource identified in the URI is invalid or does not exist. For example: version, contact ID, phone number, session token

Call could not be started.

Call session does not exist (or has gone away).

405 Method Not Allowed

HTTP method is not supported for the request.


Copyright © 1997, 2016 Oracle and/or its affiliates. All rights reserved. Legal Notices