We were using sesame voice for a test agent a9a1e738-3613-44d2-ba7b-2c7a91abf6e1 and it was working fine on Friday April 25, but now when we test the agent through the Web UI or call, there is no longer any voice output (example test session:a9a1e738-3613-44d2-ba7b-2c7a91abf6e1). We have tried changing the specific Sesame voice but they all seem to no longer work. If we switch to another voice provider the agent works fine.

Hey! To help track down this issue, could you share: - The call ID This would really help us figure out what went wrong!

I am having the same issue

There was one in the original ticket but here is another: 3fe64c01-c27f-477e-9519-21505e491967

{
  "transcriber": {
    "model": "nova-2",
    "language": "en",
    "provider": "deepgram",
    "endpointing": 300
  },
  "startSpeakingPlan": {
    "waitSeconds": 0.4,
    "smartEndpointingPlan": {
      "provider": "livekit",
      "waitFunction": "20 + 500 * sqrt(x) + 2500 * x^3"
    }
  }
}

Hey Josh, could you try two to three test calls with the following changes: 1. Transcriber end pointing set to 300ms 2. Start speaking plan smart endpointing plan live kit wait function change to an updated value What's happening is the Endpointing model is waiting a long time before considering the user has finished speaking.

For some reason Sesame started working again yesterday and I did not make the above changes yet

I am glad it's working for you, and marking this ticket as resolved.

Sorry but this stopped working again. It has nothing to do with endpointing as you cant even hear the starting message through its shows in the log. I even tried creating an Alex agent from scratch and it still doesnt work . Here is a new call id: 23fce376-6907-40d9-9553-20d394b9ef14

This ticket has been marked as solved, and as a result, you will no longer receive any further responses. Kindly create a new support ticket to escalate your inquiry.