-
Notifications
You must be signed in to change notification settings - Fork 148
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
Incoming SIP provisional responses with SDP marked as retransmitted #151
Comments
Please assign me to this issue. I will make a PR in a while. |
gfigiel
pushed a commit
to ProIDS/jain-sip
that referenced
this issue
Jun 16, 2017
This was referenced Jun 16, 2017
jaimecasero
added a commit
that referenced
this issue
Sep 7, 2017
kpouer
pushed a commit
to kpouer/jsip
that referenced
this issue
Jan 8, 2023
(cherry picked from commit aff2eb22f0d5af240c9c2f6382d8b189d064c82e)
kpouer
pushed a commit
to kpouer/jsip
that referenced
this issue
Jan 15, 2023
(cherry picked from commit aff2eb22f0d5af240c9c2f6382d8b189d064c82e)
deruelle
pushed a commit
to mobius-software-ltd/corsac-sip
that referenced
this issue
Jan 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is an issue in Jain SIP RI that causes SIP11 RA does not deliver events to JSLEE application when provisional response (100 -200) is repeated with new content or header. The response is marked as retransmitted what prevents SIP11 RA from delivering the event towards SBB.
The issue is caused by comparing only response code (toString output) when checking response
retransmission:
jain-sip/src/gov/nist/javax/sip/stack/SIPClientTransactionImpl.java
Line 1548 in b79cba1
A piece of the log message for the second 183 - with SDP
The text was updated successfully, but these errors were encountered: