-
Notifications
You must be signed in to change notification settings - Fork 84
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
dialog: fix rtags of forking INVITE #1023
Conversation
A similar PR (#947) resulted in no ACKs being sent in some scenarios - see baresip/baresip#2772. I tested this patch with the attached SIPP scenario (bob_100rel_hold.txt) and the BareSIP selftest (which checks for pending ACKs). Still, ideally, this patch could be tested in a few different setups to ensure that ACKs are always sent correctly. |
@maximilianfridrich please could you add a retest for re-INVITE which also checks that an ACK is sent/received? |
Apparently there's still issues with ACKs to re-INVITEs, as stated by juha-h in baresip/baresip#2819. I have looked into that in the past and could not find the cause. I will try again. |
680444d
to
5d8fc5d
Compare
I have finally found the ACK issue! The issue was that the |
This test helps to detect missing ACKs: #1027 |
@maximilianfridrich can you rebase against main to check if ACK tests are passed. |
5d8fc5d
to
600f544
Compare
@sreimers Done. Looks good. |
Thanks! |
Resolves: baresip/baresip#2819