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

Server and client can have different CSeq sequence #187

Open
serfreeman1337 opened this issue Feb 11, 2025 · 1 comment
Open

Server and client can have different CSeq sequence #187

serfreeman1337 opened this issue Feb 11, 2025 · 1 comment
Labels
bug Something isn't working critical Critical issue

Comments

@serfreeman1337
Copy link

Example valid call flow:
Image
10.0.3.16 started from 2693 and 10.0.3.1 started from 111. This is okay.

A here is sipgo (10.0.3.1) fails to handle BYE request after sending re-invites:
Image

The following check fails because the same CSeq counter is used when sending and receiving requests:

sipgo/dialog_server.go

Lines 393 to 395 in 2d0a819

if req.CSeq().SeqNo < dt.lastCSeqNo.Load() {
return ErrDialogInvalidCseq
}

@emiago
Copy link
Owner

emiago commented Feb 11, 2025

ok it should be based on origin then. Thanks for this extensive reporting. It really speeds stuff up.

TODO:

  • validate BYE request based on origin cseq not internal counter.

@emiago emiago added bug Something isn't working critical Critical issue labels Feb 17, 2025
@emiago emiago added this to the Stable API design milestone Feb 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working critical Critical issue
Projects
None yet
Development

No branches or pull requests

2 participants