v1.2.0

What's Changed

• Fix ACK request address handling to preserve connection information by @pablodz in #284
• fix: register dialog state read channel before sending 200 OK by @alexbakker in #285
• fix: memory leak in UDP transport acceptedAddr slice by @udzin in #286
• Make header and URI parameters ordered by @dennwc in #282

New Contributors

• @pablodz made their first contribution in #284
• @alexbakker made their first contribution in #285
• @udzin made their first contribution in #286

Highlights

• header URI params are not map anymore

Full Changelog: v1.1.2...v1.2.0

v1.1.2

Full Changelog: v1.1.1...v1.1.2

Highglights

Routing ACK on UDP was broken due to latest refactoring on remote addr resolving. This should fix many problems.
Folks using TCP or other reliable transports were probably not affected.

Also some fixes arround CSEQ for dialog is added.

v1.1.1

Full Changelog: v1.1.0...v1.1.1

v1.1.0

Highlights

• Fixes around routing Server responses correctly, some minor bugs were introduces in later stage
• 🚀 BIG Improvement on Parsing SIP Stream now with less allocations(less GC work) and lot of code improvements by @dennwc .

What's Changed

• Improve SIP message parsers by @dennwc in #271

Full Changelog: v1.0.2...v1.1.0

v1.0.0

🚀 SIPgo v1.0.0 is here 🚀

SIPgo had a long journey, and API was challenged with many different projects and used by big names out there. There hasn’t been any significant need for breaking changes lately, so there is pretty high confidence this API will remain stable going forward.

What does 1.0.0 mean?

• A stable and predictable API
• No breaking changes planned in the near future
• It will make more stable API for Diago lib
• More Confidence for production deployments

Future ✈️

There are open things regarding performance and small features that will probably land into 1.0.0 API. To mentioned few

• PR for Parser improvements
• Gracefull shutdown
• Transport more control like deadlines

Lib has opportunity to be more improved but even with current state it excels in performance of handling high loads of traffic.
You can always check proxysip example and running locally with docker-compose sipp stress where on this limited container (4 cores) we can achieve high throughput on modern CPU ~2000rps with no latency impact.

✋ v2
Many Big things or issues that we may not be good fit for current API are moved to v2 Milestone and I would like to see this happening as well.

🙌 Thank You

Huge thanks to everyone who contributed, submitted issues, provided feedback, or used SIPgo as a building block in their own systems.
Your input has shaped the API and helped bring SIPgo to this milestone.

Thank you all for your contributions and for keeping this project alive!

What's Changed

• fix: ParserStream handling StartLine and incomplete Header by @j-licht in #255
• fix according RFC3261 12.1 Creation of a Dialog by @zusrut in #262

New Contributors

• @j-licht made their first contribution in #255
• @zusrut made their first contribution in #262

Full Changelog: v0.33.0...v1.0.0

v1.0.0-beta-3

Highlights

• Fixing Cseq generation
• Adding IPV6 support as SIP uri requirements

v1.0.0-beta-2

Full Changelog: v1.0.0-beta-1...v1.0.0-beta-2

v1.0.0-beta-1

Highlights v1.0.0-alpha-2...v1.0.0-beta-1

• Transports are exposed for more configuration like swapping net.Dialer creation.
• CSEQ randomization added
• CSEQ dialog is compared/validated now with remote and local per RFC. This caused on BYE using wrong cseq counter

What's Changed

• fix: ParserStream handling StartLine and incomplete Header by @j-licht in #255
• fix according RFC3261 12.1 Creation of a Dialog by @zusrut in #262

New Contributors

• @j-licht made their first contribution in #255
• @zusrut made their first contribution in #262

Full Changelog: v1.0.0-alpha-2...v1.0.0-beta-1

v1.0.0-alpha-2

Highlights

• suport sips SRV
• fixed wait answer inifinite loop with bad proxy auth

More on
Full Changelog: v1.0.0-alpha-1...v1.0.0-alpha-2

v1.0.0-alpha-1

Adding some security fixes, but it is very small change.

Full Changelog: v1.0.0-alpha...v1.0.0-alpha-1

FYI, by mistake it was created as 1.0.1-alpha over weekend. I hope this did not disrupt to many people.
We are going to 1.0.0