We are excited to announce the general availability of sip:providerCE mr6.0.2 and sip:providerPRO mr6.0.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 mr6.0.2?
The most important changes for mr6.0.2 compared to mr5.5 are:
- NOTE: Optimized default ports for NGCP components. It is necessary to prevent lack of RTP ports in production. IMPORTANT: check new defaults and tune firewall settings if necessary! See new port details in /usr/share/ngcp-cfg-schema/cfg_scripts/config/16341_refactor_media_port_ranges.up on your NGCP system. [TT#22016]
- Store MOS values returned by rtpengine in CDRs: MOS score, average jitter,
packet loss and round trip time are saved in the ‘cdr_mos_data’ table [TT#7525].
- Preparation for migration on systemd. CE users can start playing with it and report the noticed issues.
Run “sudo ngcp-toggle-init-system –enable-systemd” and reboot the server.
IMPORTANT: THIS IS FOR TESTING/RESEARCH ONLY! IT IS NOT PRODUCTION READY!
- A lot of stabilization fixes after migration to Debian stretch.
Most of them are also available as mr5.5.2
- Set ‘net.ipv6.ip_nonlocal_bind = 1’ to force nginx listens non-available IPv6 HA/VIP IPs. [TT#25550]
- All Sipwise authored architecture dependent packages come now with matching
debugging symbol packages (ending in ‘-dbgsym’, the old ‘-dbg’ packages have been migrated).
- ngcp-status reports BIOS version/release date/manufacture. [TT#26854]
- Add notification about maintenance mode into motd (message of the day). [TT#23506]
- [PRO/Carrier] ngcp-backup has been redesigned to improve the speed and CPU/IO usage. [TT#24414]
- Allow grafana admin access via ngcp-panel. [TT#23755]
- Increase default ‘min_expires’ for kamailio proxy from 60 to 600 seconds. [TT#24216]
- [PRO/Carrier] Carrier’s command ‘ngcpcfg push all’ is available on PRO now. [TT#24095]
- Add cleanup script for voicemails in the database. [TT#23290]
- The ‘sipwise’ Admin UI/API user is not removable once created or already exists, it can be
only enabled or disabled. The user is mandatory for customers with an active Sipwise support contract.
- Add cdr costs rating split peak periods support [TT#24111]
- Address an issue with cdr costs rating for scenarios with forwarded prepaid calls [TT#23153]
- Address an issue causing duplicate calls in the call lists representation [TT#16675]
- New API /api/conversations method to fetch calls,voicemails,faxes,sms at once [TT#20315]
- Add invoices generation support by using the /api/invoices POST method [TT#23705]
- Default port ranges have changed for media (RTP), in particular for external RTP from 30000-40000 to 30000-44999 [TT#22016]
See the list of all changes in PDF Changelog mr6.0.2
Is mr6.0 LTS (long time supported) release?
No. Release mr6.0 is no longer supported as build mr6.0.2 has been published.
How do I test-drive the new version?
- AMI ID for region us-east-1: ami-028c55023637b8311
- AMI ID for region us-west-2: ami-001f1dcafc3837b80
- AMI ID for region us-west-1: ami-07f8bcd37350c8413
- AMI ID for region eu-central-1: ami-00f40848b995f8726
- AMI ID for region eu-west-1: ami-0928628ebb01f7bfd
- AMI ID for region ap-southeast-1: ami-00c88fa997305b3c9
- AMI ID for region ap-southeast-2: ami-0d4d338b100faeef1
- AMI ID for region ap-northeast-1: ami-03e4605c9f5d65b16
- AMI ID for region sa-east-1: ami-03aac9105082c9609
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.0.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!