TEN-framework / TEN-framework/ten-framework
[BUG] After successful connection, interaction is not possible
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11.1k
- Forks
- 1.4k
- Avg merge
- 2d 15m
- Merged PRs (30d)
- 22
Description
Description
After a successful launch, text transmission works fine, but voice interaction cannot be carried out. Observing the logs does not reveal any specific errors either. The LLM used is Dify. This situation does not occur every time, but it happens quite frequently.
Environment
docker, centos8
Steps to reproduce
After starting the container, connect to the frontend.
Expected behavior
The connection is successful, but there is no interaction information.
Severity
Critical
Additional Information
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reproducing the intermittent failure after connecting to the frontend in the Docker/CentOS 8 environment, then compare the working text path with the voice-interaction path while inspecting logs. Done means voice interaction works reliably after a successful connection and the failure has a reproducible diagnosis.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- centos, docker
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100