We are excited to announce the general availability of sip:providerCE mr6.4.1 and sip:providerPRO mr6.4.1.
What’s the sip:provider platform?
The Sipwise sip:provider platform is a highly versatile open source based VoIP soft-switch for ISPs and ITSPs to serve large numbers of SIP subscribers. It leverages existing building blocks like Kamailio, Sems and Asterisk to create a feature-rich and high-performance system by glueing them together in a best-practice approach and implementing missing pieces on top of it.
Sipwise engineers have been working with Asterisk and Kamailio (and its predecessors SER and OpenSER) since 2004, and have roles on the management board of Kamailio and are contributing to these projects both in terms of patches and also financially by sponsoring development tasks. The sip:provider platform is available as a Community Edition (SPCE), which is fully free and open source, and as a commercial PRO appliance shipped turn-key in a high availability setup.
The SPCE provides secure and feature-rich voice and video communication to end customers (voice, video, instant messaging, presence, buddy lists, file transfer, screen sharing, remote desktop control) and connect them to other SIP-, Mobile- or traditional PSTN-networks. It can therefore act as open Skype replacement system, traditional PSTN replacement, Over-The-Top (OTT) platform and also as a Session Border Controller in front of existing VoIP services in order to enable signaling encryption, IPv6 support, fraud- and Denial-of-Service prevention. Another use-case is to act as a Class4 SIP concentrator to bundle multiple SIP peerings for other VoIP services.
What’s new in mr6.4.1?
The most important changes for mr6.4.1 compared to mr6.3 are:
- Enable new customer self-care interface by default [TT#37657]
- Implement topology hiding on load-balancer [TT#40617]
- [PRO/Carrier] Enable licensing restrictions by default [TT#39650]
- Add Sipwise C5 support for Hyper-V [TT#39302]
- Install systemd dbus and libpam-systemd by default [TT#36228]
- Add ngcp-service –group to act with group of services [TT#38753]
- Manage /etc/hosts and /etc/network/interfaces via ngcpcfg tt2 templates [TT#36756]
- Optimize performance for billing customers, contracts, subscribers, billing_profiles, fraud checks and callrating on large data sets [TT#23701]
- Remove restrictions for switching billing profiles from postpaid to prepaid and vice versa [TT#40512]
- Improve libinewrate logging for scenarios with inactive external subscribers [TT#39358]
- [PRO/Carrier] Fix Panasonic RPS provisioning [TT#39605]
- [PRO/Carrier] Enhance LNPD and add support for Furnished Charging Info in TCAP [TT#38156]
- Export Furnished Charging Info data and P-Asserted-Identity headers into CDRs [TT#38155]
- Introduce new Call Forwardings type “Rerouting” [TT#14596]
- Support B-number regex matching in Call Forwards [TT#14600]
- Add outbound socket lb_set support for permanent registration entries [TT#37459]
- Introduce new clip_no_screening and pai_clir subscriber preferences [TT#40081]
See the list of all changes in PDF Changelog mr6.4.1
Is mr6.4 LTS (long time supported) release?
No. Release mr6.4 is no longer supported as build mr6.4.2 has been published.
How do I test-drive the new version?
- AMI ID for region us-east-1: ami-0945231e36c62d289
- AMI ID for region us-west-2: ami-0c17565797c4546f2
- AMI ID for region us-west-1: ami-0efeb81856fecf608
- AMI ID for region eu-central-1: ami-04d721872accc7f19
- AMI ID for region eu-west-1: ami-0f3d8ce3eec5d6030
- AMI ID for region ap-southeast-1: ami-068276866a2939d19
- AMI ID for region ap-southeast-2: ami-0af76b9e1d78d0b9c
- AMI ID for region ap-northeast-1: ami-0609d761cbdc4a8b8
- AMI ID for region sa-east-1: ami-07a608db95d58549d
Check the relevant section in SPCE Handbook for detailed instructions.
How do I install the new version or upgrade from an older one?
For new users, please follow the Installation Instructions in the Handbook to set up the SPCE mr6.4.2 from scratch.
For the users of the previous version of the SPCE, please follow the upgrade procedure outlined in the Handbook. If you have customized your configurations using customtt.tt2 files, you must migrate your changes to the new configuration files after the upgrade, otherwise all your calls will most certainly fail.
How can I contribute to the project?
Sipwise is publishing software components at github.com/sipwise. Please check it regularly for new projects to appear there, and feel free to fork them and send us pull requests. For development related questions, please subscribe to our SPCE-Dev Mailing-List at lists.sipwise.com/listinfo/spce-dev.
We want to thank our PRO/Carrier customers and the SPCE community for their feedback, bug reports and feature suggestions to make this release happen. We hope you enjoy using our software and keep your input coming. A big thank you also to all the developers of Kamailio, Sems and Prosody, who make it possible for us to provide an innovative and future-proof SIP/XMPP engine as the core of our platform! And last but not least a HUGE thank you to the Sipwise development team, who worked insanely hard to create this release. You are awesome!