No matter the type of connection i make the voice input for my agent is with heavy static and very

[subtle lark]

AI-generated Answer for andreis_mb

Thanks for the details. Here’s the fastest way to eliminate muffled/static input with ElevenLabs Agents over telephony.

1. Ensure your agent’s audio formats match the telephony path

• For Twilio connections (native integration or register-call/custom server), set BOTH:
  • TTS output format: μ-law 8000 Hz (Agent Settings → Voice)
  • User input audio format: μ-law 8000 Hz (Agent Settings → Advanced)
    This prevents unnecessary transcoding that degrades quality. (elevenlabs.io)

2. If you’re using a SIP trunk, verify codec negotiation and media path

• ElevenLabs SIP endpoints send/receive only G.711 (8 kHz) or G.722 (16 kHz). Your trunk/PBX must negotiate one of these or resample on your side. (elevenlabs.io)
• For poor audio quality, check:
  • At least ~100 Kbps per call and low latency/jitter for RTP
  • Packet loss on the UDP RTP path
  • Codec match on both ends (no unintended transcoding)
  • If SRTP is enabled, confirm both ends handle it efficiently; try disabling media encryption temporarily to isolate issues
  • Firewall/NAT allow RTP UDP ports (typically 10000–60000); one‑way/no audio often points to blocked RTP
    These are the documented SIP troubleshooting steps. (elevenlabs.io)

3. Signaling/transport notes for SIP

• Use TCP or TLS for SIP signaling (UDP signaling isn’t available on ElevenLabs SIP), and ensure TLS/SRTP settings match your provider before enforcing. (elevenlabs.io)

If the above is set and input is still heavily distorted, please share:

• Example call timestamp, called number, and the Twilio Call SID (available in webhook payloads) or your SIP Call-ID
• Whether the call used Twilio or SIP, and which codec was negotiated
  We can investigate further with these identifiers. (elevenlabs.io)

You can open a support ticket and attach this information (and a short recording if possible) here: Submit a request (help center). (help.elevenlabs.io)

References:

• Twilio register-call: agent must use μ-law 8000 Hz for both input/output. (elevenlabs.io)
• Twilio custom server: same μ-law 8000 Hz configuration steps. (elevenlabs.io)
• SIP trunking: supported codecs, RTP ports, bandwidth, encryption and audio-quality troubleshooting. (elevenlabs.io)
• Twilio call personalization: includes call_sid you can pass/inspect.

[frigid barn]

I appreciate the answer, but it does not address the Twilio connection. I intentionally purchased a Twilio number to test if there are improvements since the connection is native.
Is there anything that can be done to improve de quality of the imput via Twilio connection ?
Thanks!

[subtle lark]

AI-generated Answer for andreis_mb

Short answer: Yes—there are a few Twilio‑specific settings in ElevenLabs that materially affect input quality.

Do this first

• Set both your agent’s Input format and TTS Output to μ-law 8000 Hz to avoid double transcoding on Twilio calls. In the agent settings: Voice → “μ-law 8000 Hz” (output) and Advanced → “μ-law 8000 Hz” (input). (elevenlabs.io)
• Use the native Twilio integration (not a custom TwiML flow) so ElevenLabs auto‑configures the number correctly and minimizes misconfigurations. (elevenlabs.io)

If audio is still “static/muffled”

• Follow the Troubleshooting → “Audio Quality Issues” guidance for the Twilio integration: confirm μ-law 8 kHz is set, check network path, and review the call in Twilio Voice Insights. (elevenlabs.io)
• Be aware that telephony audio is narrowband. ElevenLabs explicitly supports μ‑law at 8 kHz for Twilio/telephony; higher‑rate input won’t help if the PSTN leg is 8 kHz. (elevenlabs.io)

About regions (your US–US vs IE–IE tests)

• Twilio numbers default to the US region (us1) unless you explicitly configure regional routing. If you expect IE routing, set regional routing so the call and SDK both target the intended region. (elevenlabs.io)

If you need higher fidelity than PSTN can provide

• For the cleanest microphone capture (echo/noise suppression, wideband), use a WebRTC client to your agent instead of a phone call. WebRTC support is built in. (elevenlabs.io)

If you’d like us to review specifics, share the Twilio Call SID(s) and your Agent ID with Support so we can check configuration and logs. (help.elevenlabs.io)

Sources:
Register Twilio calls | ElevenLabs Documentation
Connect Twilio to ElevenLabs Conversational AI Voice Agents
Connect Twilio to ElevenLabs Conversational AI Voice Agents
Text to Speech | ElevenLabs Documentation
Twilio regional routing | ElevenLabs Documentation
ElevenLabs Conversational AI now supports WebRTC
How can I contact support? – ElevenLabs

[frigid barn]

compresion is 8kHz. thiss not an issue. WebRTC is not an option.
here is a call id: conv_3101kjcnecjdfnj8c40ffthpj85j and agent id: agent_6301kgm8y3j9ecwbnqne3g14cwxb