Request Syntax URI Request Parameters Request Body Response Syntax Response Elements Errors Examples See Also

DeleteProxySession

Deletes the specified proxy session from the specified Amazon Chime Voice Connector.

Important

This API is no longer supported and will not be updated. We recommend using the latest version, DeleteProxySession, in the Amazon Chime SDK.

Using the latest version requires migrating to a dedicated namespace. For more information, refer to Migrating from the Amazon Chime namespace in the Amazon Chime SDK Developer Guide.

Request Syntax


DELETE /voice-connectors/voiceConnectorId/proxy-sessions/proxySessionId HTTP/1.1

URI Request Parameters

The request uses the following URI parameters.

proxySessionId

The proxy session ID.

Length Constraints: Minimum length of 1. Maximum length of 128.

Pattern: .*\S.*

Required: Yes

voiceConnectorId

The Amazon Chime voice connector ID.

Length Constraints: Minimum length of 1. Maximum length of 128.

Pattern: .*\S.*

Required: Yes

Request Body

The request does not have a request body.

Response Syntax


HTTP/1.1 204

Response Elements

If the action is successful, the service sends back an HTTP 204 response with an empty HTTP body.

Errors

For information about the errors that are common to all actions, see Common Errors.

BadRequestException

The input parameters don't match the service's restrictions.

HTTP Status Code: 400

ForbiddenException

The client is permanently forbidden from making the request.

HTTP Status Code: 403

NotFoundException

One or more of the resources in the request does not exist in the system.

HTTP Status Code: 404

ServiceFailureException

The service encountered an unexpected error.

HTTP Status Code: 500

ServiceUnavailableException

The service is currently unavailable.

HTTP Status Code: 503

ThrottledClientException

The client exceeded its request rate limit.

HTTP Status Code: 429

UnauthorizedClientException

The client is not currently authorized to make the request.

HTTP Status Code: 401

Examples

In the following example or examples, the Authorization header contents( AUTHPARAMS ) must be replaced with an AWS Signature Version 4 signature. For more information about creating these signatures, see Signature Version 4 Signing Process in the AWS General Reference.

You only need to learn how to sign HTTP requests if you intend to manually create them. When you use the AWS Command Line Interface (AWS CLI) or one of the AWS SDKs to make requests to AWS, these tools automatically sign the requests for you with the access key that you specify when you configure the tools. When you use these tools, you don't need to learn how to sign requests yourself.

Example

This example deletes a proxy session from your Amazon Chime Voice Connector.

Sample Request


DELETE /voice-connectors/abcdef1ghij2klmno3pqr4/proxy-sessions/123a4bc5-67d8-901e-2f3g-h4ghjk56789l HTTP/1.1 Host: service.chime.aws.amazon.com Accept-Encoding: identity User-Agent: aws-cli/1.18.39 Python/3.8.0 Windows/10 botocore/1.15.39 X-Amz-Date: 20200415T161710Z Authorization: AUTHPARAMS Content-Length: 0

Sample Response


HTTP/1.1 204 No Content x-amzn-RequestId: 05a30cbd-828d-4913-8c26-0d1d3252a406 Content-Type: application/json Date: Wed, 15 Apr 2020 16:17:10 GMT Connection: keep-alive