From 3.3 upstream:
rr(k): fixed offset in building new route header
- related to the previous fix done to strict routing intermediary hop
(cherry picked from commit e154b2fb9f02d56d9c6a4b2d285791151ae0c8a3)
Keep 3.3 as kamailio version, not 3.3.1 as we
might update to other 3.3 releases within the
same ngcp version.
Set Sipwise version to ngcp2.6.0 for branching per ngcp release.
It does not contain ./pkg folder yet.
If a patch is sent upstream we can remove afterwards.
It makes also easier to sync with upstream and
just apply the list of patches.
Con: Each change to kamailio code will need to be
stored as patch too. Do you read me Richard and Andi? :)
This makes reviews and diffs easier and helps in avoiding duplicate entries.
devscripts's wrap-and-sort ftw.
Closes: https://bugtracker.sipwise.com/view.php?id=1845
Acked-by: Jon Bonilla
From: Michael Prokop <mprokop@sipwise.com>
This new module will provide an interface for sending
PacketCable Event Messages, e.g. for driving a
policy server or for doing Lawful Interception.
It will serve the same purpose as the legacy li.so
module used in upc.ro, but will hook directly into the
tm and rr API to do as much automatically as possible.
We ship /etc/init.d/kamailio-proxy and /etc/init.d/kamailio-lb
and don't use /etc/init.d/kamailio at all. It's just confusing.
Acked-by: Jon Bonilla
From: Michael Prokop <mprokop@sipwise.com>
modules_k/presence_xml Xcap auth reason when user deleted from list
The reason in Subscription-Status header in Notify when a user is
deleted from the contact list can be decided by the admin by setting
presence_xml module parameter xcapauth_usedel_reason. Default value is
"probation".
dialog(k): proper unlock of profile for mi list command
- the profile was unlocked in a wrong place, before finishing listing
the its content and could cause a race in accessing it
- reported by Ricardo Martinez
(cherry picked from commit 3a2e929c63c656fe2db78e746546af05c66740ea)