### Answer A SIP 486 error means "Busy Here" — the destination rejected the call. [(1) ]() Common causes with Telnyx integration: 1. Destination number format — Ensure your numbers are in proper +E.164 format (e.g.,

+14157774444

) . One user resolved this exact issue by changing the destination number format to +E.164. [(2) ]() 2. Duplicate SIP trunk configuration — Check if you've added the same SIP trunk to multiple Retell accounts, which can cause conflicts. [(3) ]() 3. Channel limitations — Telnyx imposes a channel limitation of 10 concurrent calls, while Retell allows 20. You may be hitting Telnyx's limit. [(2) ]() Troubleshooting steps: - Check your call history and detailed log in Retell — it contains the SIP error code and error message to help identify the root cause. [(1) ]() - Verify your SIP trunk configuration is correct. [(4) ]() - If configuration issues persist, delete the imported number and re-import it. - Contact Telnyx support to check for errors on their side. Could you share: - Is this for inbound or outbound calls? - The detailed call log from your Retell dashboard?

​ To learn more, see the sources I considered: [[1] SIP Call Rejected with 486 from Retell – Request for Debug Assistance](https://discord.com/channels/1186424376300679209/1395745675307778180) [[2] Call rejected for numbers imported via telnyx sip trunk](https://discord.com/channels/1186424376300679209/1395110793262928013) [[3] 486 Rejected Error](https://discord.com/channels/1186424376300679209/1389966501011787897) [[4] Debug outbound connection issues](https://docs.retellai.com/reliability/debug-outbound-call) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

### Answer If your calls aren't appearing in Call History, here are a few things to check: 1. Data storage settings If you've opted out of data storage, Retell can't guarantee complete call history/analytics. [(1) ]() The workaround is partial retention or using real-time webhooks. 2. Try clearing cache or switching browsers Some users have resolved call history access issues by clearing their browser cache or trying a different browser. [(2) ]() 3. Filter settings Make sure you're using the correct filters in the dashboard — try filtering by agent ID and time range to locate your calls. [(3) ]() Navigate to the dashboard and select the "Call History" tab, then use the filtering capabilities to search. [(4) ]() 4. SIP trunk configuration issues Since you're using Telnyx integration and getting 486 errors, the calls may be failing before they're fully registered. Check your call logs for

dial_failed

,

dial_busy

, or

dial_no_answer

disconnection reasons. [(5) ]() To troubleshoot further: - What's your org ID? (You can share via DM if preferred) - Have you opted out of data storage? - Do the calls show any errors in your Telnyx dashboard?

​ To learn more, see the sources I considered: [[1] Call History Error](https://discord.com/channels/1186424376300679209/1384697578532110497) [[2] I can't access Call History](https://discord.com/channels/1186424376300679209/1418295043579711488) [[3] Receiving calls from Retell that don't show up in call history](https://discord.com/channels/1186424376300679209/1398386380949819442) [[4] Monitor sessions via dashboard](https://docs.retellai.com/features/session-history) [[5] Debug outbound connection issues](https://docs.retellai.com/reliability/debug-outbound-call) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

### Answer If Telnyx shows a 486 rejection from Retell, this typically points to a misconfiguration on the Retell side. [(1) ]() Key things to verify: 1. Number format — Ensure your number is properly formatted. One user resolved this exact issue because the "Copy number" button in Telnyx gives an incompatible format, regardless of E.164 settings configured. 2. FQDN configuration — Double-check that the FQDN matches your Telnyx region. 3. Credentials — Verify your username and password are correct. 4. Inbound settings in Telnyx — Confirm you have: [(2) ]() -

+E.164

as the number format -

G722

,

G729

,

OPUS

as codecs -

TCP

as transport method (UDP temporarily not supported) - Your SIP region selected 5. Agent assignment — Make sure an agent is assigned to the imported number in Retell. [(1) ]() Next steps: - Delete the number from Retell and re-import it with correct settings [(3) ]() - Check the Retell call detailed log for the SIP error code and error message — this should identify the root cause Can you confirm your Telnyx inbound settings and whether an agent is assigned to the number?

​ To learn more, see the sources I considered: [[1] SIP busy all the time](https://discord.com/channels/1186424376300679209/1395859555740553268) [[2] Telnyx](https://docs.retellai.com/deploy/telnyx) [[3] SIP Call Rejected with 486 from Retell – Request for Debug Assistance](https://discord.com/channels/1186424376300679209/1395745675307778180) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.