Skip to content
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

Client calls FS2 via FS1. If FS2 rejects, no info is given to the client. And the call stays open on FS1, missing BYE or NOTICE/REASON #2428

Open
Outme1 opened this issue Apr 12, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@Outme1
Copy link

Outme1 commented Apr 12, 2024

Describe the bug
A client connects on FS1 and calls a conference on FS2.
A channel gets created for Client -> FS1 and a CS_EXCHANGE_MEDIA channel gets created for FS1 -> FS2. This is the correct behaviour. If the client now hangup both channels will end correctly.

But if the channel from FS1 to FS2 gets rejected, there is no hint in the clients connection.
So the channel "FS1->FS2" gets destroyed and the channel "Client -> FS1" stays active.

This means that the client has no connection to the conference, but there is no indication of this on the client side.

To Reproduce
Steps to reproduce the behavior:
Connect two FS together.
Create a Conf on FS2.
Register a User on FS1.
Call the Conference.
Let the ACL in FS2 empty, so the Call from FS1 gets rejected.
The User should now be connected to FS1 but is not in the conference with no indication of this failure.

Expected behavior
Either the call is ended with BYE. Or rejected with the reason CALL_REJECTED on the Clientside.

Package version or git hash

  • Version 1.10.11
@Outme1 Outme1 added the bug Something isn't working label Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant