-
Right now these are my logs from a recent call
```
Server running on port 3000
Twilio -> Starting Media Stream for MZ1cbaeb64da6297ccb08a8cf316d2fe6c
Interaction 1: TTS -> TWILIO: Hello! I under…
-
## Proposed changes
## Context
## Possible Implementation
## Other information
https://developers.deepgram.com/reference/create-key
-
-
**Setup**
Frontend : https://agents-playground.livekit.io/ with Livkit Cloud Connected to a project in LiveKit Cloud account
Livkit Server : via LiveKit Cloud
Agent main.py file below
```
i…
-
Great work, thank you for your contribution!
For cost purposes I tried using Neets.ai and Deepgram's TTS but cant get them to work. Terminal seems to log GPT-->TTS but not TTS --> Twilio despite…
-
## Issue
* Specifically related to TTS implementing Chunking is a bit challenging for users.
## Acceptance Criteria
* Chunking by having a native interface for different LLM responses
* Re…
-
## Issue
* Specifically related to TTS implementing Chunking is a bit challenging for users.
## Acceptance Criteria
* Chunking by having a native interface for different LLM responses
* Re…
-
## Issue
* Specifically related to TTS implementing Chunking is a bit challenging for users.
## Acceptance Criteria
* Chunking by having a native interface for different LLM responses
* Re…
-
## Proposed changes
The daily build should call and exercise against the real API endpoint.
This is implemented in Go. You can use this as a reference:
https://github.com/deepgram/deepgram-go-s…
-
## Proposed changes
The unit tests should call and exercise against the Mock responses generated by the DG endpoint and be updated regularly.
This is implemented in Go. You can use this as a ref…