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

Get the 403 response when hang up the call #333

Open
portsip opened this issue Jan 6, 2021 · 0 comments
Open

Get the 403 response when hang up the call #333

portsip opened this issue Jan 6, 2021 · 0 comments

Comments

@portsip
Copy link

portsip commented Jan 6, 2021

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:


INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 172.22.24.22:5060;branch=z9hG4bK-373839-162117a7c6066c49ac24eff5ede407cc
Max-Forwards: 70
Contact: "1015" <sip:[email protected]:5060;transport=udp;registering_acc=cc_io>
To: <sip:[email protected]>
From: "1015" <sip:[email protected]>;tag=1038b30b
Call-ID: 4be92b221c80eb0c8f197d3011cf3841@0:0:0:0:0:0:0:0
CSeq: 2 INVITE
Content-Type: application/sdp
Proxy-Authorization: Digest username="1015",realm="cc.io",nonce="1609816938:2dd392e4c30feb5fdb393466d5aec126",uri="sip:[email protected]",response="de5db6f912d68d7ef9bb0dde3b7e8cb3",algorithm=MD5
User-Agent: Jigasi1.1.126-g6df3db2Linux
Jitsi-Conference-Room: [email protected]
JigasiCallDirection: out
Content-Length: 439

v=0
o=1015-jitsi.org 0 0 IN IP4 172.22.24.22
s=-
c=IN IP4 172.22.24.22
t=0 0
m=audio 10002 RTP/AVP 96 9 0 8 97 101
a=rtpmap:96 opus/48000/2
a=fmtp:96 usedtx=1
a=ptime:20
a=rtpmap:9 G722/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:97 iLBC/8000
a=rtpmap:101 telephone-event/8000
a=extmap:1 urn:ietf:params:rtp-hdrext:csrc-audio-level
a=extmap:2 urn:ietf:params:rtp-hdrext:ssrc-audio-level
a=rtcp-xr:voip-metrics


BYE sip:[email protected]:5060;ob SIP/2.0
Via: SIP/2.0/UDP 172.22.24.22:5060;branch=z9hG4bK-373839-eabd0936978a6213133865d17e55bcb4
Max-Forwards: 70
Contact: "1015" <sip:[email protected]:5060;transport=udp;registering_acc=cc_io>
To: <sip:[email protected]>;tag=1aee2721
From: "1015" <sip:[email protected]>;tag=1038b30b
Call-ID: 4be92b221c80eb0c8f197d3011cf3841@0:0:0:0:0:0:0:0
CSeq: 3 BYE
Proxy-Authorization: Digest username="1015",realm="cc.io",nonce="1609816938:2dd392e4c30feb5fdb393466d5aec126",uri="sip:[email protected]",response="de5db6f912d68d7ef9bb0dde3b7e8cb3",algorithm=MD5
User-Agent: Jigasi1.1.126-g6df3db2Linux
Content-Length: 0

Steps to reproduce


Environment details


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

1 participant