You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: