New SIP Trunk Settings Now Available in Portal

19, Nov 2026

Mission control portal now gives SIP operators more visibility and control: check registration status on every connection, include hold time in recordings, confirm blind transfers, pick the caller ID a transfer destination sees, keep far ends from dropping on comfort-noise hold, investigate calls with AI troubleshooting, and look up inbound caller names with enhanced CNAM.

What's new

  • SIP registration status: The SIP Connections list shows whether each credential or SIP Attach (UAC) connection is registered, with the same data available from the SIP Registration Status API.
  • Continue recording on hold: Include hold time in call recordings for inbound calls and outbound calls.
  • Confirm blind transfer: Keep the original call up while the destination rings, and release the transferring party only when the destination answers.
  • Caller ID for transfer target: Choose whether the transferee's or the transferor's number is presented to the transfer destination on SIP REFER transfers.
  • Generate RTP on comfort-noise packets : Send silent RTP during comfort-noise gaps so far-end PBXs don't drop calls on hold.
  • AI troubleshooting in the SIP call debugger: Get an AI-generated summary and timeline for a call, then ask follow-up questions in plain English.
  • Enhanced inbound CNAM: Look up caller names for more US calling numbers, including names longer than 15 characters.

Why it matters

SIP Trunking problems are quiet until they're expensive. A dead registration looks like a one-way-audio ticket. A transfer that rings into voicemail looks like a customer who hung up. And root-causing a bad call means replaying packet captures by hand. These controls put registration state, transfer behavior, hold media, and first-pass call analysis directly in Mission Control, so a telephony admin can answer "what happened on that call?" in minutes instead of through escalations.

Example use cases

  • Telephony admins verify a PBX migration actually registered before switching over call routing.
  • Support engineers investigate dropped calls, missing audio, and call quality with an AI summary instead of parsing SIP traces.
  • Compliance-heavy callers like finance and healthcare teams keep hold time in recordings for audit completeness.
  • Support desks control which number a transfer destination sees, so customer callbacks reach the right team.

Getting started

  1. Check registration in Mission Control under Voice → SIP Trunking → SIP Connections.
  2. Record on hold: Voice → Services → Call Recording (inbound) or your Outbound Voice Profile → Configuration (outbound), then select Continue recording on hold.
  3. Configure transfers: open your SIP connection → Configuration → Advanced → Confirm blind transfer and Caller ID for Transfer Target.
  4. Troubleshoot a call: Debugging → SIP Call Flow Tool → open Call Data Debugging → Flow tab → AI troubleshooting.
  5. Enable Enhanced CNAM: Numbers → My Numbers → edit the receiving number → Voice → Services → Inbound caller name lookup → Enhanced.

Enable the connection-level settings with the API:

curl -X PATCH \
  --header "Authorization: Bearer $TELNYX_API_KEY" \
  --header "Content-Type: application/json" \
  https://api.telnyx.com/v2/credential_connections/{connection_id} \
  -d '{
    "bridge_generate_comfort_noise_on_cn": true,
    "transfer_caller_id": "from-transferor"
  }'

Check registration from the API:

curl --header "Authorization: Bearer $TELNYX_API_KEY" \
  "https://api.telnyx.com/v2/sip_registration_status?credential_type=sip_credential_connection&username=your_sip_username"

Support articles