We are excited to announce the general availability of sip:providerCE mr4.1.2 and sip:providerPRO mr4.1.2.
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 mr4.1.2?
This is the last build of mr4.1 release series. This includes only fixes from mr4.1 series. mr4.1 is out of support, please upgrade to the latests mr4.2 version available.
How do I test-drive the new version?
As usual, we’re providing a VMWare Image, a Virtualbox Image and a Vagrant Box for quick evaluation testing. For those of you using Amazon Cloud we provide the EC2 AMIs in the following regions:
- AMI ID for region us-east-1: ami-4b506a21
- AMI ID for region us-west-2: ami-f7ea0597
- AMI ID for region us-west-1: ami-af7506cf
- AMI ID for region eu-central-1: ami-b59b7fda
- AMI ID for region eu-west-1: ami-4a1ea739
- AMI ID for region ap-southeast-1: ami-702de513
- AMI ID for region ap-southeast-2: ami-ee0d2c8d
- AMI ID for region ap-northeast-1: ami-b1fff0df
- AMI ID for region sa-east-1: ami-e1dc518d
Check the relevant section in the 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 mr4.1.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?
Over the last months we’ve started to publish our software components at github.com/sipwise. This is still an on-going effort, which is done on a component-per-component basis. Please check back 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.
Acknowledgements
We want to thank our PRO customers and the SPCE community for their feedback, bug reports and feature suggestions to make this release happen. We hope you enjoy using the mr4.1.2 build 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!
Full Changelog of Bugfixes and Enhancements
MT#17575 Captagent init script is wrong MT#17523 cleanup-tools cron job sends a warning mail MT#16795 Missing inetd.conf.services template file MT#16763 Incorrect ID column in reseller MySQL query MT#16463 provide ngcp-libswrate0-dbg captagent-dbg MT#16369 Save cores by default MT#16307 [PRO] add option to disable early media in mobile_push.dsm MT#16163 [PRO] Add priority=high to pushd messages MT#16075 [PRO] Moving apns PUSH parameter to config.yml MT#15111 move defualt ring timeout in config.yml MT#14243 Implement missing gaps for libswrate for balance underrun MT#13669 support kwalify tool in our ngcpcfg checks MT#12707 Feature Malicious Call Identification ( MCID )