Skip to content

Cannot call 'send' once a close message has been sent. #1511

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
abrar360 opened this issue Apr 2, 2025 · 2 comments
Open

Cannot call 'send' once a close message has been sent. #1511

abrar360 opened this issue Apr 2, 2025 · 2 comments

Comments

@abrar360
Copy link

abrar360 commented Apr 2, 2025

Once the LLM hangs up a phone call, and closes the websocket connection. Pipecat still continues to try to send packets over it which causes issues:

Image
@markbackman
Copy link
Contributor

How are you shutting down your Pipeline?

You can either:

  • push an EndTaskFrame upstream, which results in the source sending an EndFrame downstream to shut down processors (recommended)
  • push an EndFrame from the PipelineTask

@abrar360
Copy link
Author

abrar360 commented Apr 2, 2025

Right now, I'm just providing a tool called hang_up_phone whose handler makes an API call to the phone provider to end the call. The transition handler then transitions to the end node (which is basically just a dummy node) which is probably pushing the end frame via the end_conversation post action. Based on what you're suggesting I might need to swap the order of that so that end_conversation action is called before making the API call to hang_up.

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants