Skip to main content
Use Sinch Elastic SIP Trunking as a provider configuration candidate. There is no Sinch-specific Threetone import variant or released Sinch adapter. A generic SIP record does not establish carrier connectivity.

​
Before you begin

Identify the Sinch project, trunk, intended number, provider administrator, and current routing destination. Sinch’s Elastic SIP Trunking setup separates management access keys, the EST environment, trunk creation, outbound settings, and number preparation.

​
Prepare the route

1

Record the provider identity

Collect the project and trunk identifiers and confirm which number is associated with the candidate. Keep management access keys separate from the SIP authentication details required by the trunk.
2

Review both call directions

Document where incoming calls go and the outbound settings that apply to the trunk. Confirm any destination restrictions and required account setup with the Sinch administrator.
3

Map signaling and media

Obtain the actual carrier destination, authentication method, network requirements, transport, encryption, and codecs. Compare them with the SIP reference; do not infer these values from an API access key.
4

Prepare a controlled release

Require a released runtime ingress, usable credential handoff, and an executable agent version before rerouting numbers. Plan inbound and outbound tests and restoration of the previous destination.

​
Failure handling

If provider administration succeeds but calls fail, verify the number assignment and outbound configuration rather than repeatedly replacing the management access key. Capture direction, trunk identifier, timestamp, and the carrier result. Investigate signaling and media separately when the call connects without usable audio. Provider account setup can include additional number and address requirements. Review those with the account owner. Emergency-calling capability needs a separate provider and deployment review.

​
Frequently asked questions

No. Phone import stores workspace configuration and does not provision provider resources.
Do not assume that it is. Obtain the trunk’s required authentication details and keep management credentials in their intended server-side context.