While Talkdesk BYOC is an advanced and highly adaptable solution, we recommend taking into account the following requirements and limits:
Availability |
BYOC is currently available in the following regions: US, EU, APAC, and LATAM. |
Number format conventions |
Talkdesk BYOC SIP trunk establishment requires the E.164 number format with the following number convention:
CC = Country Code NDC = National Destination Code, identifying one or part of a PLMN (Public Land Mobile Network) SN = Subscriber Number |
Media and Signaling Cyphers and Crypto |
|
Security & Encryption |
|
SHAKEN/STIR |
Inbound and Outbound verification are not provided by Talkdesk as this is the carrier’s responsibility. Only applicable in the US. |
Outbound calls to extensions |
|
Transcoding |
Transcoding is not accepted to ensure the architecture's scalability and resilience. |
CNAM (Caller Name) |
Not supported. |
Outbound calls via toll-free numbers |
Not recommended. |
Redundancy |
Redundancy with Talkdesk Points of Presence (PoP) is mandatory for BYOC adoption. Applicable to all Talkdesk PoP regions. |
Distinct IP addressing for media and signaling |
No media anchoring on the SBC is allowed to ensure scalability and resilience. All the media must be anchored on the architecture media servers, which means that distinct IP addressing for the signaling and the media must be supported by the carrier. |
MKI (Master Key Identifier) |
The MKI is currently not supported by our Media Server. This parameter must not be presented in the SDP crypto. |
Lower case RFC MD5 |
The MD5 key configuration must be lower case. Upper case MD5 is not compatible. |