Link SIP Trunk
Link a BYOC number with SIP username and password or IP-based authentication.
When to use this
- Keeping an existing number: your business number already lives with another carrier and you want DialNexa agents to answer or dial from it.
- Regulatory or cost constraints: your carrier relationship must stay in place, so purchasing through Buy Phone Number is not an option.
- Migrating call infrastructure: route existing SIP trunks through DialNexa without renumbering.
400 Bad Request means the trunk credentials or number failed validation; see API errors for the standard error format.
Authentication Modes
sip: prefix. After the request succeeds, place a controlled inbound and outbound test, then confirm routing, audio, recording, and Call History evidence. Do not retry after an uncertain timeout until List Phone Numbers confirms whether the number was created.
Related endpoints
- SIP Trunking: configure BYOC routing in the dashboard.
- Buy Phone Number: purchase a provider number instead.
- Delete Phone Number: remove the SIP trunk number and routing credentials.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
E.164 phone number
"+14155552671"
SIP termination host[:port]; must not use a sip: URI prefix
"31974861099010243.zt.plivo.com:5060"
How the SIP provider authorizes the trunk. userpass requires sipTrunkUserName and sipTrunkPassword. ip requires both credentials to be omitted and the provider to allowlist the DialNexa signaling IP.
userpass, ip SIP authentication username. Required for authMode=userpass and forbidden for authMode=ip.
SIP authentication password stored encrypted. Required for authMode=userpass and forbidden for authMode=ip.
Display nickname for this trunk