back to all News

Sip:provider mr3.4.2 is Now Available!

Sip:provider mr.3.4.2 has been released!

We are excited to announce the general availability of sip:provider mr3.4.2, CE and PRO, aka the next build of release v3.4 Version.

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 connects 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 signalling 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 Sip:provider mr3.4.2?

The build Sip:provider mr3.4.2 contains the set of fixes for release mr3.4. No new features added to mr3.4.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-0c0ba464
  • AMI ID for region us-west-2: ami-7d15554d
  • AMI ID for region us-west-1: ami-d1dbd294
  • AMI ID for region eu-west-1: ami-c258fcb5
  • AMI ID for region ap-southeast-1: ami-922f0bc0
  • AMI ID for region ap-southeast-2: ami-6f137055
  • AMI ID for region ap-northeast-1: ami-e11539e0
  • AMI ID for region sa-east-1: ami-61b41e7c

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.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 customised your configurations using custom tt.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 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 to pull requests. For development related questions, please subscribe to our SPCE-Dev Mailing-List at

What’s coming up next?

The mr3.4.2 build is stabilisation/bugfixes build, so contains no new features. We are preparing some exciting new features for the upcoming mr3.5.1. Also, there will be some further enhancements to the REST-API, so any feedback on the current state is highly appreciated, as it is the first version we consider stable and feature-complete. The SOAP/XMLRPC API does not receive any new features anymore, so this is a good time to consider switching to the new API.


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.4.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#9085 $avp(s:acc_state)  not always set
MT#9003 upgrade problem still exists after changing SPCE hostname
MT#8981 Non descriptive error on wrong user name in subscribers put api request
MT#8915 Double Record_route entry in INVITE after Failure Route cause ACK getting lost
MT#8873 ngcp-panel subscriber dashboard doesn’t show number of recent calls
MT#8871 Prepare and release mr3.4.2 (release mr3.4 build 2)
MT#8859 Fix $rU, $tU handling on blind transfer
MT#8793 After upgrade to 3.4, new preference “music_on_hold” is set to 0 by default
MT#7007 Use dom/usr outbound_* preferences when force_outbound_calls_to_peer=1
MT#8741 Remove unnecessary [- IF PRO -] checks in case of using ngcp-check_active
MT#8711 review contact masking using advertised address
MT#8709 API REST: Deletion of a subscriber return an ERROR 500
MT#8707 optimize EC2 AMI for public usage
MT#8699 kamailio: debugger reset_msgid fails when the message has been processed already
MT#8653 Unable to register to peer via sems reg_agent
MT#8649 callforwards link missed in subscriber api info
MT#8633 is_primary flag in provisioning.voip_dbaliases not set when creating new subscriber
MT#8621 0008559: CallFowardings give Internal Server Error (incident 1388773ED7B6F750)
MT#8609 REST API: CFT – description and half empty objects after deleting.
MT#8563 Fix style errors and typos in documentation
MT#8529 sems/sems-pbx fails to compile against Debian/jessie
MT#8523 Present alias number in edr
MT#8449 Missing entry in kamailio.dbaliases if subscriber is created via REST API
MT#8441 CE ngcp-eaddress moves ssh_ext to $IFACE, so we cannot connect SSH to previous address anymore.
MT#8433 Invoice does not show all information
MT#8401 Encoding problem with special characters in invoice generation
MT#8387 There seems to be a rounding problem in invoice pdf totals
MT#8367 rest api: Mysql error on reseller login
MT#8359 disable INFO support in Allow header if it’s not supported
MT#8353 Increase number of digits after the decimal point for printed invoices
MT#8329 add allowed_clis as customer preference
MT#8309 Get rid of JSON::Types::bool()
MT#8225 HA not working for Cloud PBX [PRO only]
MT#8195 rate-o-mat selecting wrong billing profile if peers have same host name
MT#8067 create /etc/ngcp_nodename
MT#7867 Logo inside PDF invoice can’t be changed
MT#7769 CloudPBX: NOTIFY message has a CALLID not compliant [PRO only]
MT#6299 Challenge domain deletion with security dialog in old www_admin panel
MT#5879 Improved PDF Invoice generation