We are excited to announce the general availability of sip:providerCE mr3.6.2 and sip:providerPRO mr3.6.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 mr3.6.2?
The build mr3.6.2 contains the set of fixes for release mr3.6. No new features added to mr3.6.2. See the full list of changes at the end of the announce.
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-a07710c8
- AMI ID for region us-west-2: ami-53f0a663
- AMI ID for region us-west-1: ami-7b5e4c3e
- AMI ID for region eu-west-1: ami-a2279bd5
- AMI ID for region eu-central-1: ami-da91a0c7
- AMI ID for region ap-southeast-1: ami-61cbe733
- AMI ID for region ap-southeast-2: ami-2f7b1315
- AMI ID for region ap-northeast-1: ami-fa111cfb
- AMI ID for region sa-east-1: ami-2369d93e
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 mr3.6.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.
What’s coming up next?
The mr3.6.2 build is stabilization/bugfixes build, so contains no new features. We are preparing some exciting new features for the upcoming mr3.7.1. Also, there will be some further enhancements to the REST-API, so any feedback on the current state is highly appreciated. The SOAP/XMLRPC APIs have been migrated to Nginx and disabled by default in the previous build mr3.6.1. You may switch it on using config.yml setting ossbss->frontend:fcgi, but those obsolete APIs are going to be deleted in the upcoming release(s).
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 mr3.6.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#9949 compile fix for the tcp idle timer in db_postgres kamailio module
MT#9763 configure the NGCP push notification for chat (XMPP)
MT#9643 safety catch inside t_check_trans() of tm module (fixes deadlock e.g. on 302)
MT#9637 cdr-exporter: implement dynamic field selection and sftp transfer
MT#9603 lintian errors on captagent package
MT#9567 ngcp-panel: listen on all ips not only the shared ones; Add web_int handling to ngcp-eaddress
MT#9547 ngcp-ossbss migration to nginx: improved access perms, don’t try to generate ssl certs if it’s already there
MT#9287 Improve ngcpcfg to handle Carrier 3.x configs from central place (mgmt node)
MT#8613 API: add LI functions to REST
MT#7793 cdr/event-exporters: fix alias handling and merge updates
MT#10421 Prepare and release mr3.6.2
MT#10381 add concurrent_max and concurrent_max_out contract preferences
MT#10363 ngcp-collective-check complains on missed apache2 on management node
MT#10331 Carrier 3.x NGCP elasticsearch cron cleanup cannot connect elasticsearch server
MT#10309 Cannot set password_min_length in Panel to less than 6.
MT#10273 Fixed NPN setting on call from Faxserver
MT#10257 SPCE Installation from ISO fails (ngcp-asterisk failed to install on CPU without PrefetchW instruction
MT#10213 Check content of /etc/ngcp_nodename before upgrade (CE should use ‘spce’ in DB also)
MT#10135 [CloudPBX] Disregard CFNA for Subscriber when called within a HuntGroup (fixed loop)
MT#9941 [CloudPBX] Add cloud_pbx_hunt_* fields to rest api.
MT#10319 [CloudPBX] fixed Call Forward from the hunt group
MT#10077 [CloudPBX] “Anonymous call rejection for call between subscribers of same customer
MT#10117 soap api doesn’t work under nginx
MT#10093 be able to install the same set of packages on CARRIER nodes
MT#10065 ngcpcf-api: network interfaces order
MT#10045 unable to uncheck the box saying “Charge VAT”
MT#10041 REST API: can’t get subscriberregistrations as non-administrator
MT#10355 REST API: fixed clir preference inserted into DB as empty string
MT#10021 [PRO] Change the ha.cf pingnodes building