Phoenix - Your AI AssistantFinish Twilio ↔ Retell AI SIP setup (screen-share / config)
- Posted:
- Proposals: 17
- Remote
- #4441087
- Open for Proposals
Chandigarh 
Description
Experience Level: Entry
Estimated project duration: 1 day or less
Summary
• Twilio Elastic SIP Trunk + Retell AI already linked; inbound works. Outbound from Retell is not reaching Twilio. Need an expert to screen-share, review both sides, and guide a clean fix. If we’re impressed, there’s follow-on work.
Project description
• Current state
(1) Twilio: UK number purchased and attached to an Elastic SIP Trunk. Termination host and Credential List configured. Origination set to sip.retellai.com.
(2) Retell AI: Custom Telephony “phone number” added; inbound agent answers test calls. Outbound attempts show “telephony provider permission denied”.
(3) We enabled UK geo permissions and, if applicable, verified caller IDs.
• What we need in a live session (30–60 minutes)
(1) Review Twilio trunk (General / Termination / Origination / Numbers) plus Retell number/provider settings.
(2) Make one successful outbound test from Retell to a UK mobile (we’ll provide the destination).
(3) Document exactly what changed and why.
(4) Leave us a repeatable checklist so we can add more numbers without help.
• Nice-to-have follow-on (phase 2)
(1) Push call summaries into a Google Sheet or our Odoo Community ERP via webhook/API.
(2) Log/update Activities against contacts.
(3) Configure agent to leave a callback line so callers can continue a thread.
Acceptance criteria
(1) Outbound from Retell rings our UK mobile and the agent speaks.
(2) Twilio shows a matching outbound call record.
(3) We receive a change log + 1-page checklist.
(4) We can repeat on a second number.
• Twilio Elastic SIP Trunk + Retell AI already linked; inbound works. Outbound from Retell is not reaching Twilio. Need an expert to screen-share, review both sides, and guide a clean fix. If we’re impressed, there’s follow-on work.
Project description
• Current state
(1) Twilio: UK number purchased and attached to an Elastic SIP Trunk. Termination host and Credential List configured. Origination set to sip.retellai.com.
(2) Retell AI: Custom Telephony “phone number” added; inbound agent answers test calls. Outbound attempts show “telephony provider permission denied”.
(3) We enabled UK geo permissions and, if applicable, verified caller IDs.
• What we need in a live session (30–60 minutes)
(1) Review Twilio trunk (General / Termination / Origination / Numbers) plus Retell number/provider settings.
(2) Make one successful outbound test from Retell to a UK mobile (we’ll provide the destination).
(3) Document exactly what changed and why.
(4) Leave us a repeatable checklist so we can add more numbers without help.
• Nice-to-have follow-on (phase 2)
(1) Push call summaries into a Google Sheet or our Odoo Community ERP via webhook/API.
(2) Log/update Activities against contacts.
(3) Configure agent to leave a callback line so callers can continue a thread.
Acceptance criteria
(1) Outbound from Retell rings our UK mobile and the agent speaks.
(2) Twilio shows a matching outbound call record.
(3) We receive a change log + 1-page checklist.
(4) We can repeat on a second number.
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
Could you confirm whether outbound calls from Retell AI are using SIP registration or IP authentication to connect with Twilio? That would help clarify if the “telephony provider permission denied” issue is tied to credential validation or geo-permission settings.