back to all Sipwise CE - News

sip:provider mr6.2.1 Released

We are excited to announce the general availability of sip:providerCE mr6.2.1 and sip:providerPRO mr6.2.1.

What’s the sip:provider platform?

sip:provider PRO Architecture Overview

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.2.1?

The most important changes for mr6.2.1 compared to mr6.1 are:

  • Migrated from sysv (System Five) to systemd [TT#18774]
  • Replaced the kamailio MySQL backend for location and accounting data by Redis, tremendously lowering disk I/O and improving overall system performance [TT#32971]
  • Introduced RTP transcoding for G711, G729, G722, G723, Opus, Speex, AMR and AMR-WB in rtpengine [TT#26752]
  • Introduced new feature ngcpcfg patch to simplify customtt handling [TT#24920]
  • Streamlined ngcpcfg options by renaming enabled to enable to follow common naming [TT#17987]
  • Introduced release-specific Install-CD [TT#28952]
  • Introduced new feature ngcp-service summary to see the status of all services on a node [TT#18774]
  • Improved IMS ISC interface for call-forwarding scenarios [TT#33981]

See the list of all changes in PDF Changelog mr6.2.1

Is mr6.2 LTS (long time supported) release?

No. Release mr6.2 will be out of support once build mr6.2.2 has been published. You can find the dead-lines in the Sipwise releases calendar.

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-0a317c59d66759abe
  • AMI ID for region us-west-2: ami-09d5d0423735dc720
  • AMI ID for region us-west-1: ami-040483834fc016f77
  • AMI ID for region eu-central-1: ami-097a7f355d1d16eaf
  • AMI ID for region eu-west-1: ami-030152e48fe0f837b
  • AMI ID for region ap-southeast-1: ami-0611a0c3a4981ccf5
  • AMI ID for region ap-southeast-2: ami-0ae901a8c62e4ef8b
  • AMI ID for region ap-northeast-1: ami-04d74fa21cc692907
  • AMI ID for region sa-east-1: ami-03e33450fd819d8c6

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.2.1 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 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


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!