Skip to content

Bumping emiago/sipgo - #829

Open
genseric-ghiro wants to merge 2 commits into
mainfrom
genseric/bumping_emiago_sipgo
Open

Bumping emiago/sipgo#829
genseric-ghiro wants to merge 2 commits into
mainfrom
genseric/bumping_emiago_sipgo

Conversation

@genseric-ghiro

Copy link
Copy Markdown
Contributor

Summary

@genseric-ghiro genseric-ghiro self-assigned this Sep 2, 2026
@genseric-ghiro
genseric-ghiro requested a review from a team as a code owner September 2, 2026 21:48

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Devin Review found 1 potential issue.

Devin Review

Comment thread go.mod
github.com/docker/go-connections v0.7.0 // indirect
github.com/docker/go-units v0.5.0 // indirect
github.com/emiago/sipgo v1.4.0
github.com/emiago/sipgo v1.5.0

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟡 Oversized message poisons its connection

When a streaming message exceeds 65,535 bytes, v1.5.0 returns ErrMessageTooLarge, but parseStream keeps reading. Lost framing can reject every later call on that connection.

Prompt for agents
The v1.5.0 stream parser returns ErrMessageTooLarge for an incomplete oversized message after discarding its buffered state, and its contract requires the caller to close the connection because no message boundary remains. The TCP/TLS read loop in the pinned github.com/livekit/sipgo version, transport/tcp.go readConnection/parseStream, logs every non-partial parser error and continues. Update that transport integration to propagate ErrMessageTooLarge and terminate the read loop/connection, or consume a livekit/sipgo revision that implements the v1.5.0 parser contract. Add a TCP stream test that sends an oversized incomplete message followed by a valid SIP request and verifies that the connection closes rather than parsing trailing bytes.
Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Yes, this is the plan, to do in a separate PR

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.

2 participants