Loading
Contact Center
Considerations for Bring Your Own Carrier

You are here:

  1. Salesforce Help
  2. Docs
  3. Contact Center

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)

View supported editions.

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.
 
Chargement
Salesforce Help | Article