Releases: emiago/sipgo
Releases · emiago/sipgo
v0.27.1
v0.27.0
v0.26.0
Highlights:
- Reducing allocs (GC) on creating requests and dialog request
- siptest client tx executor for easier testing client request
GetHostname
is removed and client will not do any IP resolving as UDP will check remote IP
Full Changelog: v0.25.1...v0.26.0
v0.25.0
What's Changed
- Properly use receiver for header parsers by @dennwc in #138
- Return pointer from NewConnectionPool by @dennwc in #139
- Do not use buffer pool for ParseSIP by @dennwc in #142
- Enable GitHub Actions by @dennwc in #143
- Remove deprecated rand.Seed by @dennwc in #147
Full Changelog: v0.24.1...v0.25.0
v0.24.1
v0.24.0
Full Changelog: v0.23.0...v0.24.0
v0.23.0
Highlights
- Decoupling dialog from caching struct
DialogServer
DialogClient
by addingDialogUA
struct and simplifying API. This allows now dialog to be extended and wrapped with caller caching.DialogServer
andDialogClient
maybe moved only for TESTS in future andDialogUA
will provide handing Invites and dialog creation - Testing coverage increased to 50.1 *.
- We are forcing IPV4 either on default IP resolving and also on DNS lookups. DNS lookups need to have exported filtering mechanism in future release
- Client have now
Do
request same like stdhttp.Client
. This allows caller not to deal with transaction and just have request/reply - Dialog Client Server now have
Do
andTransactionRequest
that comply to RFC better as Dialogs need more to comply versus standard Request. It is recomended now to useDialogUA
and sub sessions when have to deal with INVITE requests. - SIP URI is now more generic (Adds SCHEME detection) to allow custom uri conversions like
tel:
#114 - BREAKING CHANGE: CANCEL handling was complex with Dialog. Now Transaction Layer and Dialog handles this correctly without need to have additional logic on caller.
ServerTransaction.Cancels
andClientTransaction.Cancel
is removed and everything is handled by transaction layer. In cases of statefull proxy this may be exposed for better control. For now it is expected that cancel terminates transaction and then proxy should terminate other end.
Per RFC CANCEL only makes sense for INVITE and this is provided with dialog management when cancelingWaitAnswer
.
What's Changed
- Prioritize IPv4 during DNS resolution by @gpi-eaglys in #124
- UAS Dialog BYE request uses wrong transport by @Odinvt in #128
New Contributors
- @gpi-eaglys made their first contribution in #124
- @Odinvt made their first contribution in #128
Full Changelog: v0.22.1...v0.23.0
v0.22.1
What's Changed
- fix: honor lr in record route for dialog clients by @InnovativeUS in #99
- fix: ACK request does not convert the Record-Route headers into Route headers by @hateeyan in #100
New Contributors
Full Changelog: v0.22.0...v0.22.1
v0.22.0
Highlights
Do
request/response stile for client. Same like std http. This avoids need for handling complex transaction request- Fixed racy condition when handling FSM in client transaction.
What's Changed
New Contributors
Full Changelog: v0.21.0...v0.22.0
v0.21.0
Notes:
RespondSDP
to dialog server to avoid missing headerTransactionRequest
on dialog client and server exposed for correct sending Requests within dialog. There is SIP rfc section- Lot of fixes, mainly for dialog
- Dialog
Refer
(transfer) support is in experimental. More is done onsipgox
currently - SIP Uri parsing was failing for
sip://user@host
. Now this is fixed
Full Changelog: v0.20.0...v0.21.0