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

Failure to comply with RFC 3311 #253

Open
SouradeepBera opened this issue Mar 29, 2024 · 1 comment
Open

Failure to comply with RFC 3311 #253

SouradeepBera opened this issue Mar 29, 2024 · 1 comment

Comments

@SouradeepBera
Copy link

RFC 3311 states that If an UPDATE is received that contains an offer, and the UAS has generated an offer (in an UPDATE, PRACK or INVITE) to which it has not yet received an answer, the UAS MUST reject the UPDATE with a 491 response. FreeSWITCH sends a 500 Overlapping Offer/Answer response.

To Reproduce
Using Sipp or any simulation tool, establish a session with FreeSWITCH. Decrease the session-timer and when FreeSWITCH sends a reINVITE, instead of responding to it with a final response, send an UPDATE request.

Expected behavior
A 491 response is expected

@briankwest
Copy link
Member

Attach a SIPP scenario that replicates the issue would go a long way.

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

2 participants