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
This Issue tracker is only for reporting bugs and tracking code related issues.
Before posting, please make sure you check community.jitsi.org to see if the same or similar bugs have already been discussed. General questions, installation help, and feature requests can also be posted to community.jitsi.org.
Description
Seems the jigasi doesn't recalculate the authorization header when it hangup the call.
Current behavior
When I try to hang up it, the jigasi send BYE to PBX, in the Proxy-Authorization, it still using the same "response" value as the INVITE.
Expected Behavior
As the RFC3261, section 22.1: For BYE, you should recalculate the authorization header since the method is changed.
So we will need recalculate the "response" when sending the BYE, shouldn't use the same response as the INVITE.
This Issue tracker is only for reporting bugs and tracking code related issues.
Before posting, please make sure you check community.jitsi.org to see if the same or similar bugs have already been discussed. General questions, installation help, and feature requests can also be posted to community.jitsi.org.
Description
Seems the jigasi doesn't recalculate the authorization header when it hangup the call.
Current behavior
When I try to hang up it, the jigasi send BYE to PBX, in the Proxy-Authorization, it still using the same "response" value as the INVITE.
Expected Behavior
As the RFC3261, section 22.1: For BYE, you should recalculate the authorization header since the method is changed.
So we will need recalculate the "response" when sending the BYE, shouldn't use the same response as the INVITE.
Possible Solution
Below is the log:
Steps to reproduce
Environment details
The text was updated successfully, but these errors were encountered: