Custom SIP Trunks
Create SIP Trunk
Register a custom SIP trunk for your environment
POST
Create SIP Trunk
Register a custom SIP trunk for your environment. Once created, you must verify the trunk via Verify SIP Trunk before it can be used.This feature is available only on plans where
allow_custom_sip_trunks is enabled.Endpoint
Request headers
Bearer token. Format:
Bearer talq_your_environment_token_hereMust be set to
application/jsonRequest body
Human-readable trunk name. Max 255 characters.
Identifier of your carrier or SIP provider.
SIP domain or proxy host (e.g.,
sip.carrier-x.com).SIP authentication username.
SIP authentication password. Stored encrypted.
SIP port. Range:
1–65535. Default depends on transport (5060 UDP/TCP, 5061 TLS).Transport protocol. Options:
udp, tcp, tls. Default: tls.Optional outbound proxy host.
Optional SIP auth realm if your carrier requires one.
Whether the trunk is active. Default:
false (you must verify before activating).Examples
Response
Notes
passwordis never returned in responses after creation.- Run Verify SIP Trunk to test connectivity before activating.