We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It is noticed that currently you are required to handle media in seperate goroutine in order to detect hangup.
This leads into lot of additional goroutines.
Still in some cases you want to handle hangup explicitly, or we need to have a way to register OnHangup where media stack can close it self.
This will probably fix lot of issues, but it could lead also double closing, as it iss needed to close always when caller stops processing call.
The text was updated successfully, but these errors were encountered:
FYI was default behavior for server but not for client
Sorry, something went wrong.
No branches or pull requests
It is noticed that currently you are required to handle media in seperate goroutine in order to detect hangup.
This leads into lot of additional goroutines.
Still in some cases you want to handle hangup explicitly, or we need to have a way
to register OnHangup where media stack can close it self.
This will probably fix lot of issues, but it could lead also double closing, as it iss needed to close always when caller stops processing call.
The text was updated successfully, but these errors were encountered: