Hey guys, happy new year. A bit confused on why the agents within this org seems to not be able to hear me, here's one of the call ID's: fd3b7201-e387-4bcc-b790-221bc5361363 Tried: - Duplicating the agent - Creating one from scratch and re-setting the config - Creating on from scratch w/o any config - Mapped provider credentials to a tee with other working orgs/agents - Mapped all the configs to a tee with other working orgs/agents - Billing looks fine, still credits - Redoubled check that config for transcriber is Nova 2 & deepgram (working for all other agents) Not sure what the issue is but none of the agents receive a transcriber output in the call log. Would appreciate help.

@george.l Happy New Year to you too! I'm sorry to hear that you're experiencing issues with the agents not transcribing your calls. Let's try to troubleshoot this together. You've mentioned that you've checked the provider credentials and the configuration, including setting the transcriber to Nova 2 & deepgram, which is working for other agents. Since you've also confirmed that billing is not an issue, it seems like the setup should be correct. To assist you further, I'll need to check a few details: - Can you confirm if the transcriber provider is set to 'deepgram' for the agent associated with the call ID you've provided? - Have you noticed any error messages in the logs or any indications of why the transcriber might not be functioning as expected? If everything seems to be configured correctly, it might be an issue that requires deeper investigation from our support team. Please provide the requested confirmation, and if everything is in order, we may need to escalate this to our technical support for a more thorough examination.

@george.l sorry for the late response, just wanted to check if it's still happening for you?

All good yessir. The whole org's agents can't seem to hear for some reason. Just noticed the same thing for another org. Here's the caller ID: 733e670a-564c-4f6c-aec4-a2bb3d918480

@george.l Try another call with the following and let me know how it goes.

json
    "start_speaking_plan": {
      "waitSeconds": 0.8,
      "smartEndpointingEnabled": true
    },
    "stop_speaking_plan": {
      "numWords": 2,
      "voiceSeconds": 0.2,
      "backoffSeconds": 1
    },

Hey @Shubham Bajaj so it didn't have to do with our start or stop speaking plan but had to do with a 502 error from deepgram. We've since swapped our transcriber to talkscriber but another weird challenge seemed to be popping up where the agent is responding twice to the prospect, e.g. here are two call id's: 3e9e3fe0-415e-496f-a650-ffa68dd9d80c c0e44b62-a779-49a3-bfc6-8cec3ab594b1 Pretty unbearable tbh... The LLM/model must be receiving two inputs which is leading to two outputs. Is there any possibility of either now the agent having two transcribers working simultaneously sending the user input to it or is talkscriber just like not working that well? Please advise.

> Pretty unbearable tbh... The LLM/model must be receiving two inputs which is leading to two outputs. This is not possible case and even not the case. > So everything "should" be working at least with there only being one transcriber and it being talkscriber There is always one transcriber used.