fix: wait_for_participant waits until participant is fully active#5271
fix: wait_for_participant waits until participant is fully active#5271
Conversation
requires livekit v1.1.4
chenghao-mou
left a comment
There was a problem hiding this comment.
should we update the pyproject and uv lock files?
yup, waiting for python sdk release before doing so.. |
* upstream/main: fix: add PARTICIPANT_KIND_CONNECTOR to default participant kinds (livekit#5339) feat: expose service_tier in CompletionUsage from OpenAI Responses API (livekit#5341) feat: answering machine detection (livekit#4906) fix: wait_for_participant waits until participant is fully active (livekit#5271) (gemini realtime): add warnings in update_chat_ctx and update_instructions (livekit#5332) fix: convert oneOf to anyOf in strict schema for discriminated unions (livekit#5324) fix(voice): make function call history preservation configurable in AgentTask (livekit#5288)
* fix(voice): make function call history preservation configurable in AgentTask (livekit#5288) * fix: convert oneOf to anyOf in strict schema for discriminated unions (livekit#5324) * (gemini realtime): add warnings in update_chat_ctx and update_instructions (livekit#5332) * fix: wait_for_participant waits until participant is fully active (livekit#5271) * feat: answering machine detection (livekit#4906) Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com> * feat: expose service_tier in CompletionUsage from OpenAI Responses API (livekit#5341) * fix: add PARTICIPANT_KIND_CONNECTOR to default participant kinds (livekit#5339) --------- Co-authored-by: Gopal Bagaswar <67310594+GopalGB@users.noreply.github.com> Co-authored-by: Long Chen <longch1024@gmail.com> Co-authored-by: Tina Nguyen <72938484+tinalenguyen@users.noreply.github.com> Co-authored-by: David Zhao <dz@livekit.io> Co-authored-by: Chenghao Mou <chenghao.mou@livekit.io> Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: Piyush Gambhir <90608533+piyush-gambhir@users.noreply.github.com> Co-authored-by: Anunay Maheshwari <anunaym14@gmail.com>
|
hi @davidzhao , this breaks my implementation! I was using wait_for_participant to setup the agent according to participant metadata, and this used to work because I had time to do so, while the telephone was ringing. Now I am losing that precious time to do the setup. |
|
@IngLP can you clarify what actually happens in your use case? this should introduce less than 500ms of latency to wait_for_participant in the typical case. |
|
@davidzhao maybe that's true for incoming calls, but for outgoing calls, it's not. I had plenty of time while the other extension was ringing, now wait_for_participant only unlocks when the callee has actually answered. |
|
@IngLP can you share a code snippet of what you are doing? and describe the current behavior that you are observing? |
|
Before:
Now:
|
|
@IngLP please share example code snippet.. that'll make it easier for us to see what's going on. if you are calling specific APIs, include the actual calls with the parameters |
|
@davidzhao it's just like this: |
|
@IngLP where do you perform the outbound dial? |
|
@davidzhao in the backend, a separate deployment from the agents runner. |
|
This change also hangs the |
requires livekit v1.1.4