-
Notifications
You must be signed in to change notification settings - Fork 972
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
[bug]: res_pjsip: Mediasec requires different headers on 401 response #48
Labels
Comments
maximilianfridrich
added a commit
to maximilianfridrich/asterisk
that referenced
this issue
May 2, 2023
When using mediasec, requests sent after a 401 must still contain the Security-Client header according to draft-dawes-sipcore-mediasec-parameter. Resolves: asterisk#48
jcolp
added
support-level-core
Functionality with core support level
and removed
triage
labels
May 2, 2023
maximilianfridrich
added a commit
to maximilianfridrich/asterisk
that referenced
this issue
May 2, 2023
When using mediasec, requests sent after a 401 must still contain the Security-Client header according to draft-dawes-sipcore-mediasec-parameter. Resolves: asterisk#48
maximilianfridrich
added a commit
to maximilianfridrich/asterisk
that referenced
this issue
May 2, 2023
When using mediasec, requests sent after a 401 must still contain the Security-Client header according to draft-dawes-sipcore-mediasec-parameter. Resolves: asterisk#48
gtjoseph
pushed a commit
that referenced
this issue
May 2, 2023
When using mediasec, requests sent after a 401 must still contain the Security-Client header according to draft-dawes-sipcore-mediasec-parameter. Resolves: #48
asteriskteam
pushed a commit
that referenced
this issue
May 2, 2023
When using mediasec, requests sent after a 401 must still contain the Security-Client header according to draft-dawes-sipcore-mediasec-parameter. Resolves: #48
asteriskteam
pushed a commit
that referenced
this issue
May 2, 2023
When using mediasec, requests sent after a 401 must still contain the Security-Client header according to draft-dawes-sipcore-mediasec-parameter. Resolves: #48
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Severity
Minor
Versions
16.29.0, 18.15.0, 20.0.0
Components/Modules
res_pjsip, res_pjsip_outbound_registration
Operating Environment
Debian 11
Frequency of Occurrence
Constant
Issue Description
The Deutsche Telekom requires certain headers in SIP requests which are based on draft-dawes-sipcore-mediasec-parameter. This draft requires different headers in requests sent after a 401 as compared to 494. Specifically, in requests sent after a 401 response, the Security-Client header must still be present (see section 6.1 in the draft) while in requests after a 494 it should not be present.
The original mediasec implementation didn't consider that.
Relevant log output
No response
Asterisk Issue Guidelines
The text was updated successfully, but these errors were encountered: