

# Managing Amazon Chime SDK Voice Connectors
<a name="voice-connectors"></a>

**What is an Amazon Chime SDK Voice Connector?**  
An Amazon Chime SDK Voice Connector provides Session Initiation Protocol (SIP) trunking service for your existing phone system. You can manage your Voice Connectors from the Amazon Chime SDK console and access it over your internet connection, or you can use AWS Direct Connect. For more information, see [What is Direct Connect?](https://docs.aws.amazon.com/directconnect/latest/UserGuide/Welcome.html) in the *Direct Connect User Guide*.

**Important**  
Voice Connectors do not support SMS.

**Voice Connector outbound and inbound calling**  
After you create a Voice Connector, edit the termination and origination settings to allow outbound or inbound calls, or both. You then assign phone numbers to the Voice Connector. You can use the Amazon Chime SDK console to port in existing phone numbers or provision new phone numbers. For more information, see [Porting existing phone numbers](porting.md), [Provisioning phone numbers](provision-phone.md), and [Assigning and unassigning Amazon Chime SDK Voice Connector phone numbers](assign-voicecon.md).

**Note**  
Amazon Chime SDK Voice Connectors have outbound international calling restrictions. For more information, refer to [Outbound calling restrictions](outbound-call-restrictions.md).
Voice Connectors support outbound calling in E.164 format and do not require an international dialing access code, such as 011. You pay a per-minute rate based on the destination country of the call. For a current list of supported countries, and the per-minute rate for each country, see [ https://aws.amazon.com/chime/voice-connector/pricing/](https://aws.amazon.com/chime/voice-connector/pricing/). Voice Connector PSTN calling does not support private numbering schemes such as 4, 5, or 6-digit extension numbers.

**Voice Connector groups**  
You can also create an Voice Connector group and add Voice Connectors to it. You can use Voice Connectors created in different AWS Regions. This creates a fault-tolerant mechanism for fallback if availability events occur. For more information, see [Managing Amazon Chime SDK Voice Connector groups](voice-connector-groups.md).

**Logging and monitoring Voice Connector data**  
Optionally, you can send logs from your Voice Connector to CloudWatch Logs, and turn on media streaming from your Amazon Chime SDK Voice Connector to Amazon Kinesis. For more information, see [CloudWatch logs for the Amazon Chime SDK](monitoring-cloudwatch.md#cw-logs) and [Streaming Amazon Chime SDK Voice Connector media to Kinesis](start-kinesis-vc.md).

**Topics**
+ [Before you begin](#vc-prereq)
+ [Creating an Amazon Chime SDK Voice Connector](create-voicecon.md)
+ [Using tags with Voice Connectors](use-tags-voice-con.md)
+ [Editing Amazon Chime SDK Voice Connector settings](edit-voicecon.md)
+ [Assigning and unassigning Amazon Chime SDK Voice Connector phone numbers](assign-voicecon.md)
+ [Deleting an Amazon Chime SDK Voice Connector](delete-voicecon.md)
+ [Configuring Voice Connectors to use call analytics](configure-voicecon.md)
+ [Managing Amazon Chime SDK Voice Connector groups](voice-connector-groups.md)
+ [Streaming Amazon Chime SDK Voice Connector media to Kinesis](start-kinesis-vc.md)
+ [Using Amazon Chime SDK Voice Connector configuration guides](config-guides.md)

## Before you begin
<a name="vc-prereq"></a>

To use an Amazon Chime SDK Voice Connector, you must have an IP Private Branch Exchange (PBX), Session Border Controller (SBC), or other voice infrastructure with internet access that supports Session Initiation Protocol (SIP). Make sure that you have enough bandwidth to support peak call volume. For information about bandwidth requirements, see [Bandwidth requirements](network-config.md#bandwidth).

To ensure security for calls sent from AWS to your on-premises phone system, we recommend configuring an SBC between AWS and your phone system. Allow list SIP traffic to the SBC from the Amazon Chime SDK Voice Connector signaling and media IP addresses. For more information, see the recommended ports and protocols for [Amazon Chime SDK Voice Connector](network-config.md#cvc).

Amazon Chime SDK Voice Connectors expect phone numbers to be in E.164 format.

# Creating an Amazon Chime SDK Voice Connector
<a name="create-voicecon"></a>

You use the Amazon Chime SDK console to create Amazon Chime SDK Voice Connectors.

**To create a Voice Connector**

1. Open the Amazon Chime SDK console at [https://console.aws.amazon.com/chime-sdk/home](https://console.aws.amazon.com/chime-sdk/home).

1. In the navigation pane, under **SIP Trunking**, choose **Voice connectors**.

1. Choose **Create new voice connector**.

1. Under **Voice connector name**, enter a name for the Voice Connector.

1. Under **Encryption**, select **Enabled** or **Disabled**.

1. Under **Network Type**, select **DUAL\$1STACK** or **IPV4\$1ONLY**.

   1. You can apply **DUAL\$1STACK** (IPv4/IPv6) only to newly created Voice Connectors.

   1. Existing Voice Connectors use **IPV4\$1ONLY** as the Network Type.

1. (Optional) Under **Tags**, choose **Add new tag**, then do the following.

   1. Under **Key**, enter the tag's key.

   1. Under **Value**, enter the tag's value.

   1. As needed, choose **Add new tag** to add more tags to the Voice Connector.

   For more information about tags, refer to [Adding tags to Voice Connectors](use-tags-voice-con.md#add-tags-voice-con).

1. Choose **Create Voice Connector**.

**Note**  
Enabling encryption configures your Voice Connector to use TLS transport for SIP signaling and Secure RTP (SRTP) for media. Inbound calls use TLS transport, and unencrypted outbound calls are blocked.

# Using tags with Voice Connectors
<a name="use-tags-voice-con"></a>

The topics in this section explain how to use tags with your existing Amazon Chime SDK Voice Connectors. Tags allow you to assign metadata to your AWS resources, such as Voice Connectors. A tag consists of a key and an optional value that stores information about the resource, or the data retained on that resource. You define all keys and values. For example, you can create a tag key named `CostCenter` with a value of `98765` and use the pair for cost allocation purposes. You can add up to 50 tags to a Voice Connector.

## Adding tags to Voice Connectors
<a name="add-tags-voice-con"></a>

You can add tags to existing Amazon Chime SDK Voice Connectors.

**To add tags to Voice Connectors**

1. Open the Amazon Chime SDK console at [https://console.aws.amazon.com/chime-sdk/home](https://console.aws.amazon.com/chime-sdk/home).

1. In the navigation pane, under **SIP Trunking**, choose **Voice Connectors**.

1. Choose the name of Voice Connector that you want use.

1. Choose the **Tags** tab, then choose **Manage tags**.

1. Choose **Add new tag**, then enter a key and optional value.

1. As needed, choose **Add new tag** to create another tag.

1. When finished, choose **Save changes**.

## Editing tags
<a name="edit-tags-voice-con"></a>

If you have the necessary permissions, you can edit any tags in your AWS account regardless of who created them. However, IAM policies may prevent you from doing so. 

**To edit tags**

1. Open the Amazon Chime SDK console at [https://console.aws.amazon.com/chime-sdk/home](https://console.aws.amazon.com/chime-sdk/home).

1. In the navigation pane, under **SIP Trunking**, choose **Voice Connectors**.

1. Choose the name of Voice Connector that you want use.

1. Choose the **Tags** tab, then choose **Manage tags**.

1. In the **Key** or **Value** boxes, enter a new value.

1. When finished, choose **Save changes**.

## Removing tags
<a name="remove-tags-voice-con"></a>

If you have the necessary permissions, you can remove any tags in your AWS account regardless of who created them. However, IAM policies may prevent you from doing so. 

**To remove tags**

1. Open the Amazon Chime SDK console at [https://console.aws.amazon.com/chime-sdk/home](https://console.aws.amazon.com/chime-sdk/home).

1. In the navigation pane, under **SIP Trunking**, choose **Voice Connectors**.

1. Choose the name of Voice Connector that you want use.

1. Choose the **Tags** tab, then choose **Manage tags**.

1. Choose **Remove** next to the tag that you want to remove.

1. Choose **Save changes**.

# Editing Amazon Chime SDK Voice Connector settings
<a name="edit-voicecon"></a>

After you create an Amazon Chime SDK Voice Connector, you must edit the termination and origination settings that allow outbound and inbound calls. You can also configure a number of other settings, such as streaming to Kinesis and using emergency call routing. You use the Amazon Chime console to edit all settings.

**To edit Amazon Chime SDK Voice Connector settings**

1. Open the Amazon Chime SDK console at [https://console.aws.amazon.com/chime-sdk/home](https://console.aws.amazon.com/chime-sdk/home).

1. In the navigation pane, under **SIP Trunking**, choose **Voice connectors**.

1. Choose the name of the Amazon Chime SDK Voice Connector to edit.

1. The Amazon Chime console groups Voice Connector settings on a set of tabs. Expand the sections below for information about using each tab.

## Editing general settings
<a name="edit-general"></a>

Use the **General** tab to change a Voice Connector's name, enable or disable encryption, and import the wildcard root certificate into your SIP infrastructure.

**Note**  
If the Voice Connector is dual-stack and you use a host name that supports IPv6, media and signaling will go over IPv6.
If the Voice Connector is IPv4 it will not fall back or attempt IPv6, it is only IPv4.

**To change general settings**

1. (Optional) Under **Details**, enter a new name for the Voice Connector.

1. (Optional) Under **Encryption**, choose **Enabled** or **Disabled**. For more information about encryption, expand the next section.

1. Choose **Save**.

1. (Optional) Choose the **Download here** link to download the wildcard root certificate. We assume that you know how to add it to your SIP infrastructure.

## Using encryption with Voice Connectors
<a name="use-encryption"></a>

When you enable encryption for an Amazon Chime SDK Voice Connector, you use TLS for SIP signaling and Secure RTP (SRTP) for media. The Voice Connector service uses TLS port 5061.

When enabled, all inbound calls use TLS, and unencrypted outbound calls are blocked. You must import the Amazon Chime root certificate. The Amazon Chime SDK Voice Connector service uses a wildcard certificate `*.voiceconnector.chime.aws` in US Regions, and `*.region.vc.chime.aws` in other Regions. For example, the service uses `*.ap-southeast-1.vc.chime.aws` in the Asia Pacific (Singapore) Region. We implement SRTP as described in [RFC 4568](https://datatracker.ietf.org/doc/html/rfc4568).

**Note**  
Voice Connectors support TLS 1.2

For outbound calls, the service uses the SRTP default AWS counter cipher and HMAC-SHA1 message authentication. We support the following cipher suites for inbound and outbound calls:
+ AES\$1CM\$1128\$1HMAC\$1SHA1\$180
+ AES\$1CM\$1128\$1HMAC\$1SHA1\$132
+ AES\$1CM\$1192\$1HMAC\$1SHA1\$180
+ AES\$1CM\$1192\$1HMAC\$1SHA1\$132
+ AES\$1CM\$1256\$1HMAC\$1SHA1\$180
+ AES\$1CM\$1256\$1HMAC\$1SHA1\$132

You must use at least one cipher, but you can include all of them in preference order at no additional charge for Voice Connector encryption.

We also support these additional TLS cipher suites:
+ AES256-GCM-SHA384
+ AES256-SHA256
+ AES256-SHA
+ AES128-GCM-SHA256
+ AES128-SHA256
+ AES128-SHA
+ ECDHE-RSA-AES256-GCM-SHA384
+ ECDHE-RSA-AES128-GCM-SHA256
+ ECDHE-RSA-AES256-SHA384
+ DHE-RSA-AES256-GCM-SHA384
+ DHE-RSA-AES256-SHA256
+ ECDHE-RSA-AES128-SHA256
+ DHE-RSA-AES128-GCM-SHA256
+ DHE-RSA-AES128-SHA256

## Editing termination settings
<a name="edit-termination"></a>

You use the **Termination** settings to enable and configure outbound calls from your Amazon Chime SDK Voice Connector.

**Note**  
Your **Outbound host name** resolves to a set of IP addresses that may change as EC2 instances go in or out of service, so don’t cache records for longer than the DNS Time to Live interval. Caching for longer may result in call failures.

Choose **Save** again.

**To edit termination settings**

1. Select **Enabled**.

1. (Optional) Under **Allowed hosts list**, choose **New**, enter the CIDR notations and values that you want to allow, then choose **Add**. Note that the IP address values must be publically routable addresses.

   —OR—

   Choose **Edit** and change the CIDR notation.

   —OR—

   Choose **Delete** to remove the host.

1. Under **Calls per second**, select another value, if available. 

1. Under **Calling plan**, open the **Countries** list and choose the countries that the Voice Connector can call.

1. Under **Credentials**, choose **New**, enter a username and password, then choose **Save**.

1. Under **Caller ID override**, choose **Edit**, select a phone number, then choose **Save**.

1. Under **Last options ping**, view the last SIP options message sent by your SIP infrastructure.

## Editing origination settings
<a name="edit-origination"></a>

Origination settings apply to inbound calls to your Amazon Chime SDK Voice Connector. You can configure inbound routes for your SIP hosts to receive inbound calls. Inbound calls are routed to hosts in your SIP infrastructure by the priority and weight you set for each host. Calls are routed in priority order first, with 1 the highest priority. If hosts are equal in priority, calls are distributed among them based on their relative weight.

**Note**  
Encryption-enabled Voice Connectors use TLS (TCP) protocol for all calls.

**Warning**  
If your voice connector is configured for encryption, starting February 13, 2026 calls from Chime SDK to your SIP infrastructure will gradually begin using a certificate issued by a new certificate authority. All calls from Chime SDK to your SIP infrastructure will use this certificate by March 1, 2026. If your SIP infrastructure requests and validates client certificates, it is important that you import the new certificate authority's root certificate into your SIP infrastructure prior to February 13, 2026. Download the new certificate from the Voice Connector Console under origination settings.

**To edit origination settings**

1. Select **Enabled**.

1. Under **Inbound routes**, choose **New**.

1. Enter the values for **Host**, **Port**, **Protocol**, **Priority**, and **Weight**. Note that IP address values used for **Host** must be publicly routable addresses.

1. Choose **Add**.

1. Choose **Save**.

## Editing emergency calling settings
<a name="edit-emergency"></a>

To enable emergency calling, you first need to enable termination and origination. See the sections above for information about doing so.

You need at least one emergency call routing number from a third-party emergency service provider to complete these steps. For more information about obtaining numbers, see [Setting up third-party emergency routing numbers](chime-voice-connector-emergency-calling.md).

Choose **Add**. 

**To edit emergency calling settings**

1. Choose **Add**.

1. Under **Call send method**, select an item from the list, if available.

1. Enter the emergency routing number.

1. Enter the test routing number. We recommend obtaining a test routing number. 

1. Under **Country**, choose the routing number's country, if available.

1. Choose **Add**.

## Editing phone numbers
<a name="edit-phone"></a>

You can assign and unassign Voice Connector phone numbers. The following steps assume you have at least one phone number in your Amazon Chime inventory. If not, see [Provisioning phone numbers](provision-phone.md).

**To assign phone numbers**

1. Choose **Assign from inventory**.

1. Select one or more phone numbers.

1. Choose **Assign from inventory**.

The selected number or numbers appear in your list of numbers.

**To unassign phone numbers**

1. Select one or more phone numbers.

1. Choose **Unassign**.

1. When asked to confirm the operation, choose **Unassign**.

## Editing streaming settings
<a name="edit-streaming"></a>

The **Streaming** settings enable Amazon Kinesis Video Streams. The service stores, encrypts, and indexes your streaming audio data. 

**To edit streaming settings**

1. Under **details**, choose **Start**.

1. Under **Streaming notification**, select one or more targets from the lists.

1. Under **Data retention period**, choose **No data retention**, or set a retention interval.

1. Under **Call Insights**, choose **Activate**, then do the following:

   1. Under **Access permissions**, select a role from the list.

   1. Under **Kinesis Data Stream**, select a stream from the list.

   1. (Optional) Under **Amazon Transcribe custom language model**, select a model from the list.

   1. Under **Personally identifiable information type**, choose an option.

   1. Under **Filter partial results**, choose an option.

   1. Under **Send real time notification**, choose **Start**, then choose an option from the **Call direction** and **Speaker** lists.

   1. As needed, choose **Add a word/phrase**, then enter the word or phrase that you want to be notified about.

1. Choose **Save**.

## Editing logging settings
<a name="edit-logging"></a>

The Amazon Chime SDK disables logging for Voice Connectors by default. When you enable logging, the system sends the data to an Amazon CloudWatch log group. For more information about logging, see [Monitoring the Amazon Chime SDK with Amazon CloudWatch](monitoring-cloudwatch.md)

**To edit logging settings**

1. Under **SIP metric logs**, choose **Enabled**.

1. Under **Media metric logs**, choose **Enabled**.

## Editing tag settings
<a name="edit-tags"></a>

You can add 50 tags to a Voice Connector, and you can choose the keys and optional values for the tags.

**To edit tag settings**

1. Choose **Manage tags**.

1. Do any of the following:
   + To add a tag, choose **Add new tag**, then enter a key and an optional value.
   + To remove a tag, choose **Remove** next to the tag that you want to delete.

1. When finished, choose **Save changes**.

# Assigning and unassigning Amazon Chime SDK Voice Connector phone numbers
<a name="assign-voicecon"></a>

You can assign and unassign phone numbers to and from an Amazon Chime SDK Voice Connector.

**To assign phone numbers**

1. Open the Amazon Chime SDK console at [https://console.aws.amazon.com/chime-sdk/home](https://console.aws.amazon.com/chime-sdk/home).

1. In the navigation pane, under **SIP Trunking**, choose **Voice connectors**.

1. Choose the name of the Voice Connector.

1. Choose **Phone numbers**.

1. Select one or more phone numbers to assign to the Voice Connector.

1. Choose **Assign**.

You can also choose **Reassign** to reassign phone numbers with the **Voice Connector** product type from one Voice Connector or Voice Connector group to another.

**To unassign phone numbers**

1. Open the Amazon Chime SDK console at [https://console.aws.amazon.com/chime-sdk/home](https://console.aws.amazon.com/chime-sdk/home).

1. In the navigation pane, under **SIP Trunking**, choose **Voice connectors**.

1. Choose the name of the Voice Connector.

1. Choose **Phone numbers**.

1. Select one or more phone numbers to unassign from the Voice Connector.

1. Select **Unassign**.

1. Select the check box, and choose **Unassign**.

# Deleting an Amazon Chime SDK Voice Connector
<a name="delete-voicecon"></a>

Before you can delete an Amazon Chime SDK Voice Connector, you must unassign all phone numbers from it. For more information on unassigning phone numbers from a Voice Connector, see the previous topic.

**To delete a Voice Connector**

1. Open the Amazon Chime SDK console at [https://console.aws.amazon.com/chime-sdk/home](https://console.aws.amazon.com/chime-sdk/home).

1. In the navigation pane, under **SIP Trunking**, choose **Voice connectors**.

1. Choose **Phone numbers**, **Delete voice connector**.

1. Select the check box, and choose **Delete**.

# Configuring Voice Connectors to use call analytics
<a name="configure-voicecon"></a>

**Note**  
To complete the steps in this section, you must first create a call analytics configuration. For information about creating configurations, see [Creating call analytics configurations](create-ca-config.md).

You can use Amazon Chime SDK Call Analytics with Amazon Chime SDK Voice Connector to automatically generate insights with Amazon Transcribe and Amazon Transcribe Call Analytics with voice analytics. You do this by associating your call analytics configuration with an Amazon Chime SDK voice connector. For each call, the Voice Connector invokes call analytics in accordance with the configuration that you specify. You can associate one configuration with multiple Voice Connectors, or create a unique configuration for each Voice Connector.

Call Analytics uses the [Amazon Chime Voice Connector service-linked role](using-service-linked-roles-stream.md) to invoke the [https://docs.aws.amazon.com/chime-sdk/latest/APIReference/API_media-pipelines-chime_CreateMediaInsightsPipeline.html](https://docs.aws.amazon.com/chime-sdk/latest/APIReference/API_media-pipelines-chime_CreateMediaInsightsPipeline.html) API on your behalf.

**To configure a Voice Connector**

1. Open the Amazon Chime SDK console at [https://console.aws.amazon.com/chime-sdk/home](https://console.aws.amazon.com/chime-sdk/home).

1. In the navigation pane, under **SIP Trunking**, choose **Voice Connectors**.

1. Choose the name of the Voice Connector that you want to associate with a configuration, then choose the **Streaming** tab.

1. If it isn't already selected, choose **Start** to begin streaming to Kinesis Video Streams.

1. Under **Call Analytics**, select **Activate**, and on the menu that appears, choose your Call Analytics Configuration ARN.

1. Choose **Save**.

**Note**  
After enabling, disabling, or modifying a configuration associated with a Voice Connector, allow 5 minutes for the new settings to propagate through the service and take effect.

# Managing Amazon Chime SDK Voice Connector groups
<a name="voice-connector-groups"></a>

**How an Amazon Chime SDK Voice Connector group works**  
 Voice Connector groups only handle inbound PSTN calls to your SIP based phone system. The groups provide fault-tolerant, cross-region call routing. A Voice Connector group contains two or more Voice Connectors, and can include Voice Connectors created in different AWS Regions. This allows incoming PSTN calls to fail over across AWS Regions if availability events affect service in one region. 

 For example, say that you create a Voice Connector group and assign two Voice Connectors to it, one in the US East (N. Virginia) Region, and the other in the US West (Oregon) Region. You configure both Voice Connectors with origination settings that point to your SIP host(s).

Now say that a call comes in to the Voice Connector in the US East (N. Virginia) Region. If that Region has a connectivity issue, the call automatically reroutes to the Voice Connector in the US West (Oregon) Region.

**Get started with an Amazon Chime SDK Voice Connector group**  
To get started, first create Voice Connectors in different AWS Regions. Then, create a Voice Connector group and assign the Voice Connectors to it. You can also provision phone numbers for your Voice Connector group from your Amazon Chime SDK **Phone number management** inventory. For more information, see [Provisioning phone numbers](provision-phone.md). For more information about creating Amazon Chime SDK Voice Connectors in different AWS Regions, see [Managing Amazon Chime SDK Voice Connectors](voice-connectors.md).

**Topics**
+ [Creating an Amazon Chime SDK Voice Connector group](#create-voicecon-group)
+ [Editing an Amazon Chime SDK Voice Connector group](#edit-voicecon-group)
+ [Assigning and unassigning phone numbers to a Voice Connector group](#assign-voicecon-group)
+ [Deleting an Amazon Chime SDK Voice Connector group](#delete-voicecon-group)

## Creating an Amazon Chime SDK Voice Connector group
<a name="create-voicecon-group"></a>

You can create up to three Amazon Chime SDK Voice Connector groups for your account.

**To create a group**

1. Open the Amazon Chime SDK console at [https://console.aws.amazon.com/chime-sdk/home](https://console.aws.amazon.com/chime-sdk/home).

1. In the navigation pane, under **SIP Trunking**, choose **Voice connectors**.

1. Choose **Create group**.

1. In the dialog box that appears, under **Voice connector group name**, enter a name for the group.

1. Choose **Create**.

## Editing an Amazon Chime SDK Voice Connector group
<a name="edit-voicecon-group"></a>

After you create an Amazon Chime SDK Voice Connector group, you can add or remove Amazon Chime SDK Voice Connectors for it. You can also edit the priority for the Voice Connectors in the group.

**To add Voice Connectors to a group**

1. Open the Amazon Chime SDK console at [https://console.aws.amazon.com/chime-sdk/home](https://console.aws.amazon.com/chime-sdk/home).

1. In the navigation pane, under **SIP Trunking**, choose **Voice connectors**.

1. Choose the name of the Voice Connector group that you want to edit.

1. Choose the **Voice connectors** tab, open the **Actions** list, then choose **Add**.

1. In the dialog box that appears, select the checkbox next to the Voice Connector that you want to use.

1. Choose **Add**.

1. Repeat steps 4 through 6 to add Voice Connectors to the group.

**To edit Voice Connector priority in a group**

1. Open the Amazon Chime SDK console at [https://console.aws.amazon.com/chime-sdk/home](https://console.aws.amazon.com/chime-sdk/home).

1. In the navigation pane, under **SIP Trunking**, choose **Voice connectors**.

1. Choose the name of the Amazon Chime SDK Voice Connector group that you want to edit.

1. Under **Actions**, choose **Edit priority**.

1. In the dialog box that appears, enter a different priority ranking for each Voice Connector. 1 is the highest priority. Higher priority Voice Connectors are attempted first.

1. Choose **Save**.

**To remove Voice Connectors from a group**

1. Open the Amazon Chime SDK console at [https://console.aws.amazon.com/chime-sdk/home](https://console.aws.amazon.com/chime-sdk/home).

1. In the navigation pane, under **SIP Trunking**, choose **Voice connectors**.

1. Choose the name of the Voice Connector group that you want to edit.

1. Open the **Actions** list and choose **Remove**.

1. In the dialog box that appears, select the check boxes next to the Voice Connectors that you want to remove.

1. Choose **Remove**.

## Assigning and unassigning phone numbers to a Voice Connector group
<a name="assign-voicecon-group"></a>

You use the Amazon Chime SDK console to assign and unassign phone numbers to a Voice Connector group.

**To assign phone numbers to a Voice Connector group**

1. Open the Amazon Chime SDK console at [https://console.aws.amazon.com/chime-sdk/home](https://console.aws.amazon.com/chime-sdk/home).

1. In the navigation pane, under **SIP Trunking**, choose **Voice connectors**.

1. Choose the name of the Voice Connector group to edit.

1. Choose **Phone numbers**.

1. Choose **Assign from inventory**.

1. Select one or more phone numbers to assign to the Voice Connector group.

1. Choose **Assign from inventory**.

You can also choose **Reassign** to reassign phone numbers with the **Voice Connector** product type. This lets you reassign these numbers from one Voice Connector or Voice Connector group to another.

**To unassign phone numbers from a Voice Connector group**

1. Open the Amazon Chime SDK console at [https://console.aws.amazon.com/chime-sdk/home](https://console.aws.amazon.com/chime-sdk/home).

1. In the navigation pane, under **SIP Trunking**, choose **Voice connectors**.

1. Choose the name of the Voice Connector group to edit.

1. Choose **Phone numbers**.

1. Select the phone numbers that you want from the Voice Connector group, and choose **Unassign**.

1. Choose **Unassign**.

## Deleting an Amazon Chime SDK Voice Connector group
<a name="delete-voicecon-group"></a>

Before you can delete an Amazon Chime SDK Voice Connector group, you must unassign all Amazon Chime SDK Voice Connectors and phone numbers from it. For more information, see the previous section.

**To delete a Voice Connector group**

1. Open the Amazon Chime SDK console at [https://console.aws.amazon.com/chime-sdk/home](https://console.aws.amazon.com/chime-sdk/home).

1. In the navigation pane, under **SIP Trunking**, choose **Voice connectors**.

1. Choose the name of the Voice Connector group to delete.

1. Choose **Delete group**.

1. Select the check box, and choose **Delete**.

# Streaming Amazon Chime SDK Voice Connector media to Kinesis
<a name="start-kinesis-vc"></a>

You can stream phone call audio from Amazon Chime SDK Voice Connectors to Amazon Kinesis Video Streams for analytics, machine learning and other processing. Developers can store and encrypt audio data in Kinesis Video Streams, and access the data using the Kinesis Video Streams API operation. For more information, see the [https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/what-is-kinesis-video.html](https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/what-is-kinesis-video.html).

**Note**  
Voice Connector streaming does not restrict phone number formats. You can stream calls from numbers in E.164 and non-E.164 formats. For example, Voice Connector streaming can support 4, 5, or 6-digit extension numbers, or 11-digit private wire numbers. For more information, refer to [SIP-based media recording and network-based recording compatibility](#siprec), later in this guide.
Voice Connector streaming supports G.711 A-law and G.711 µ-law audio encoding.

Use the Amazon Chime SDK console to start media streaming for your Voice Connector. When media streaming begins, your Voice Connector uses an AWS Identity and Access Management (IAM) service-linked role to grant permissions to stream media to Kinesis Video Streams. Then, call audio from each Voice Connector telephone call leg is streamed in real time to separate Kinesis Video Streams.

Use the Kinesis Video Streams Parser Library to download the media streams sent from your Voice Connector. Filter the streams by the following persistent fragments metadata:
+ TransactionId
+ VoiceConnectorId

For more information, see [Kinesis Video Streams Parser Library](https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/parser-library.html) and [Using streaming metadata with Kinesis Video Streams](https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/how-meta.html) in the *Amazon Kinesis Video Streams Developer Guide*.

For more information about using IAM service-linked roles with Voice Connectors, see [Using the Amazon Chime SDK Voice Connector service linked role policy](using-service-linked-roles-stream.md). For more information about using Amazon CloudWatch with the Amazon Chime SDK, see [Logging and monitoring in the Amazon Chime SDK](monitoring-overview.md).

When you enable media streaming for your Voice Connector, the Amazon Chime SDK creates an IAM service-linked role called AWSServiceRoleForAmazonChimeVoiceConnector. If you have configured call detail record logging for Voice Connectors in the Amazon Chime SDK console, streaming detail records are sent to your configured Amazon S3 bucket. For more information, see [Amazon Chime SDK Voice Connector streaming detail records](manage-global.md#vc-sdr).

## Starting media streaming
<a name="start-kinesis"></a>

You use the Amazon Chime SDK console to start media streaming for a Voice Connector.

**To start media streaming**

1. Open the Amazon Chime SDK console at [https://console.aws.amazon.com/chime-sdk/home](https://console.aws.amazon.com/chime-sdk/home).

1. In the navigation pane, under **SIP Trunking**, choose **Voice connectors**.

1. Choose the name of the Voice Connector.

1. Choose the **Streaming** tab.

1. In the **Details** section, under **Sending to Kinesis Video Streams**, choose **Start**.

1. Under **Data retention period**, choose **Retain data for**, and enter a retention period.

1. Choose **Save**.

You use the Amazon Chime SDK console to turn off media streaming. If you no longer need to use media streaming for any of your Voice Connectors, we recommend that you also delete the related service-linked role. For more information, see [Deleting a service-linked role for Amazon Chime SDK Voice Connectors](using-service-linked-roles-stream.md#delete-service-linked-role-stream).

**To stop media streaming for your Voice Connector**

1. Open the Amazon Chime SDK console at [https://console.aws.amazon.com/chime-sdk/home](https://console.aws.amazon.com/chime-sdk/home).

1. In the navigation pane, under **SIP Trunking**, choose **Voice connectors**.

1. Choose the name of the Voice Connector.

1. Choose the **Streaming** tab.

1. In the **Details** section, under **Sending to Kinesis Video Streams**, choose **Stop**.

1. Choose **Save**.

## SIP-based media recording and network-based recording compatibility
<a name="siprec"></a>

You can use an Amazon Chime SDK Voice Connector to stream media to Kinesis Video Streams. You can stream from a SIP-based media recording (SIPREC) compatible voice infrastructure or the network-based recording (NBR) feature associated with Cisco Unified Border Element (CUBE).

You must have a Private Branch Exchange (PBX), Session Border Controller (SBC), or contact center that supports the SIPREC protocol or NBR feature. The PBX or SBC must be able to send signaling and media to AWS public IP addresses. For more information, see [Before you begin](voice-connectors.md#vc-prereq).

**To set up streaming of RTP audio streams forked with SIPREC or NBR**

1. Create a Voice Connector. For more information, see [Creating an Amazon Chime SDK Voice Connector](create-voicecon.md).

1. Start media streaming for your Amazon Chime SDK Voice Connector. For more information, see [Starting media streaming](#start-kinesis).

1. Open the Amazon Chime SDK console at [https://console.aws.amazon.com/chime-sdk/home](https://console.aws.amazon.com/chime-sdk/home).

1. In the navigation pane, under **SIP Trunking**, choose **Voice connectors**.

1. Select the Voice Connector and note its **Outbound host name**. For example, `abcdef1ghij2klmno3pqr4.voiceconnector.chime.aws`.

1. Do one of the following:
   + **For SIPREC** – Configure your PBX, SBC, or other voice infrastructure to fork RTP streams with SIPREC to the **Outbound host name** of your Voice Connector.
   + **For NBR** – Configure your PBX, SBC, or other voice infrastructure to fork RTP streams with NBR to the **Outbound host name** of your Voice Connector. Send an additional header or URI parameter of `X-Voice-Connector-Record-Only` with the value `true` in the `SIP INVITE`.

# Using Amazon Chime SDK voice analytics with Voice Connectors
<a name="use-ca-with-vc"></a>

You use Amazon Chime SDK call analytics with your Voice Connectors to automatically generate insights into your calls. Specifically, you can identify users and predict their tone, either positive, negative, or neutral.

Call analytics works with Amazon Transcribe, Amazon Transcribe Call Analytics, and Amazon Chime SDK voice analytics.

The process follows these broad steps:

1. Create a call analytics *configuration*, a static structure that contains the instructions for processing data.

1. Associate the configuration with one or more Voice Connectors. You can associate one configuration with multiple Voice Connectors, or create a unique configuration for each Voice Connector.

1. The Voice Connector invokes call analytics in accordance with the configuration.

Call analytics uses the [Amazon Chime Voice Connector service-linked role](using-service-linked-roles-stream.md) to invoke the [https://docs.aws.amazon.com/chime-sdk/latest/APIReference/API_media-pipelines-chime_CreateMediaInsightsPipeline.html](https://docs.aws.amazon.com/chime-sdk/latest/APIReference/API_media-pipelines-chime_CreateMediaInsightsPipeline.html) API on your behalf. 

**Note**  
The following steps explain how to associate a call analytics session with a Voice Connector. To complete them, you first need to create a call analytics configuration. To do that, see [Creating call analytics configurations](create-ca-config.md) in this guide. The creation process assigns an ARN to the configuration. Copy the ARN for use in these steps.

1. Open the Amazon Chime SDK console at [https://console.aws.amazon.com/chime-sdk/home](https://console.aws.amazon.com/chime-sdk/home).

1. In the navigation pane, under **SIP Trunking**, choose **Voice Connectors**, then choose a Voice Connector.

1. Choose the **Streaming** tab.

1. Under **Sending to Kinesis Video Streams**, choose **Start**.

1. Under **Call Analytics**, choose **Activate**, choose a configuration from the list, then choose **Save**.

# Using Amazon Chime SDK Voice Connector configuration guides
<a name="config-guides"></a>

We test Amazon Chime SDK Voice Connectors on a wide range of private branch exchange, session border controller, and contact center systems. We publish those tested configurations in a set of Configuration Guides.

The Configuration Guides cover the configuration steps used for each system test. We perform these types of tests:
+ Enable SIP trunking over a Voice Connector from a third-party SIP platform.
+ Enable SIPREC over a Voice Connector for use with audio streams.

For more information, see the [ Amazon Chime SDK Configuration Guides](https://aws.amazon.com/chime/chime-sdk/resources/#Configuration_Guides). 