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

sip: add RFC 3311 support #425

Merged
merged 3 commits into from
Jul 16, 2022
Merged

Conversation

maximilianfridrich
Copy link
Contributor

@maximilianfridrich maximilianfridrich commented Jul 7, 2022

This PR adds support for RFC 3311 - the SIP UPDATE method.

Related:

@maximilianfridrich maximilianfridrich changed the title sip: add RFC 331 support sip: add RFC 3311 support Jul 7, 2022
@maximilianfridrich
Copy link
Contributor Author

maximilianfridrich commented Jul 8, 2022

I am currently working on adding tests to retest to get the coverage above the threshold again. Will submit the PR to retest soon.

Retest PR opened. Coverage above threshold again.

@maximilianfridrich maximilianfridrich marked this pull request as ready for review July 13, 2022 07:50
sess->modify_pending = false;
tmr_cancel(&sess->tmr);
mem_deref(desc);
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the difference to the reinvite_handler()? Maybe we could avoid some code duplication.

Copy link
Contributor Author

@maximilianfridrich maximilianfridrich Jul 14, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Combined in 2fb5cf3.

(void)sipsess_update(sess, true);
else
sess->desc = mem_deref(sess->desc);
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here. Maybe code duplication with reinvite_resp_handler() can be avoided. Also it might be more readable with a few if for the differences.

Copy link
Contributor Author

@maximilianfridrich maximilianfridrich Jul 14, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Combined in 2fb5cf3.

If a UAS receives an UPDATE without SDP, it MUST NOT send SDP in the
response body. I.e. the target_refresh_handler only calls the offer
handler (which sets the SDP) if it has received an INVITE or the request
contained an SDP body.
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

Successfully merging this pull request may close these issues.

3 participants