---
schema_version: "1"
id: e0c8b62d52a9a48b1d538e2a6bb089babcc0cc7aaca8b21e2bb6b6284a0cf4bc
title: Considerations for Bring Your Own Carrier
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/afcc_sv_byocarrier_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.afcc_sv_byocarrier_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 712e77018281af711c18333a6f1d2be47854086d27e27d622a3d1304b61a5ddd
description: A list of technical and network requirements your carrier must meet for Bring Your Own Carrier trunks to interoperate reliably with Salesforce. Use it to configure signaling, encryption, and call-routing settings correctly from the start, so you can avoid dropped calls, failed connections, and misidentified tenants before they become support issues.
products:
  - Service Cloud
  - Digital Engagement
release: "264"
---
# Considerations for Bring Your Own Carrier

A list of technical and network requirements your carrier must meet for Bring Your Own Carrier trunks to interoperate reliably with Salesforce. Use it to configure signaling, encryption, and call-routing settings correctly from the start, so you can avoid dropped calls, failed connections, and misidentified tenants before they become support issues.

### Required Editions

This article applies to:

Salesforce Voice (Native Telephony)

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=service.voice_editions.htm&amp;type=5&amp;language=en_US" target="_blank">View supported editions</a>.</td></tr></tbody></table>

Bring Your Own Carrier is built entirely on mature standards with these interoperability requirements

- Signalling -  All SIP signaling must use TLS. The system doesn’t support unencrypted TCP or UDP.
- Certificates - You must use valid, CA-signed certificates for your TLS connection. The system will reject self-signed certificates.
- Media Encryption - All media should be encrypted over SRTP.
- Supported Codecs - G.711 (PCMU and PCMA)
- Number Format - Normalize all numbers to the +E.164 format.
- DTMF Method - For IVR compatibility, the system supports RFC 2833/4733 (out-of-band).
- Packetization - Standard 20 ms to ensure consistent audio sample processing.
- SIP Session Timers - Requires RFC 4028 support to prevent hung calls or "ghost" sessions.
- UDP Port Ranges - 1024–65148 for media traffic to clear firewalls.
- Tenant Identification - All calls received by the platform should include the Salesforce orgId in the X-Salesforce-Org-Id SIP INVITE header to identify the Salesforce tenant associated with the call.