Retrieve Errors for a Disable Calling Location Job
Retrieve detailed error information for a disable calling location job. This is particularly useful for jobs that have failed or encountered errors during processing.
Retrieving job errors requires a full administrator auth token with a scope of spark-admin:telephony_config_read.
Possible error codes include:
BATCH-1012002- Unable to delete calling location from Broadworks.BATCH-1012004- Safe delete checks failed.BATCH-1012005- Failed to perform safe delete checks.BATCH-1012006- Trunks in use in the location. Count: {0}BATCH-1012007- Users associated with the location. Count: {0}BATCH-1012008- Workspaces associated with the location. Count: {0}BATCH-1012009- Virtual lines associated with the location. Count: {0}BATCH-1012010- Number order is pending.BATCH-1012011- Features associated with the location. This is a blocking error, use forceDelete to disable the calling location.BATCH-1012012- Not allowed to delete the last calling location. Calling requires at least one active location in the organization, This is a blocking error.BATCH-1012013- Local gateway's associated with the location. Count: {0}. This is a blocking error, use forceDelete to disable the calling location.BATCH-1012014- Location not found.
URI Parameters
Unique identifier for the job to get errors for.
Query Parameters
Organization ID for disable calling location job.
Response Codes
The list below describes the common success and error responses you should expect from the API:
| Code | Status | Description |
|---|---|---|
| 200 | OK | Successful request with body content. |
| 201 | Created | The request has succeeded and has led to the creation of a resource. |
| 202 | Accepted | The request has been accepted for processing. |
| 204 | No Content | Successful request without body content. |
| 400 | Bad Request | The request was invalid or cannot be otherwise served. An accompanying error message will explain further. |
| 401 | Unauthorized | Authentication credentials were missing or incorrect. |
| 403 | Forbidden | The request is understood, but it has been refused or access is not allowed. |
| 404 | Not Found | The URI requested is invalid or the resource requested, such as a user, does not exist. Also returned when the requested format is not supported by the requested method. |
| 405 | Method Not Allowed | The request was made to a resource using an HTTP request method that is not supported. |
| 409 | Conflict | The request could not be processed because it conflicts with some established rule of the system. For example, a person may not be added to a room more than once. |
| 410 | Gone | The requested resource is no longer available. |
| 415 | Unsupported Media Type | The request was made to a resource without specifying a media type or used a media type that is not supported. |
| 423 | Locked | The requested resource is temporarily unavailable. A Retry-After header may be present that specifies how many seconds you need to wait before attempting the request again. |
| 428 | Precondition Required | File(s) cannot be scanned for malware and need to be force downloaded. |
| 429 | Too Many Requests | Too many requests have been sent in a given amount of time and the request has been rate limited. A Retry-After header should be present that specifies how many seconds you need to wait before a successful request can be made. |
| 500 | Internal Server Error | Something went wrong on the server. If the issue persists, feel free to contact the Webex Developer Support team. |
| 502 | Bad Gateway | The server received an invalid response from an upstream server while processing the request. Try again later. |
| 503 | Service Unavailable | Server is overloaded with requests. Try again later. |
| 504 | Gateway Timeout | An upstream server failed to respond on time. If your query uses max parameter, please try to reduce it. |
Header
Query Parameters
- Organization ID for disable calling location job.