We are excited to announce the general availability of sip:providerCE mr3.8.6 and sip:providerPRO mr3.8.6.

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 mr3.8.6?

The most important changes for mr3.8.6 compared to mr3.7.x are:

  • Direct upgrade from 2.8 LTS to mr3.8.6 LTS is now possible
  • General component stability improvements and REST API enhancements
  • The RTP bridging and transport protocol (DTLS-SRTP or SDES) for rtpengine can now be configured by user preference.
  • Update Redis to latest stable version 2.8.17
  • Update Prosody to latest stable version 0.9.10
  • Move Sipwise Debian repository from 1024bit GPG key to 4096bit key
  • Improve services security (listen appropriate interfaces only)
  • CloudPBX improvements and fixes for PRO/CARRIER customers with PBX module

Is mr3.8 LTS (long time supported) release?

Yes, release mr3.8 is the current LTS release. Release mr3.8 LTS is going to be supported for 3 years.

Is it possible to upgrade directly from 2.8 LTS to mr3.8 LTS release?

Yes, the procedure also takes care of updating Debian from 6.0 to 7.0. Check the relevant section in the Handbook for detailed instructions.

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-172bca7a
  • AMI ID for region us-west-2: ami-e15fac81
  • AMI ID for region us-west-1: ami-0e3f466e
  • AMI ID for region eu-central-1: ami-260be949
  • AMI ID for region eu-west-1: ami-268a0255
  • AMI ID for region ap-southeast-1: ami-ba12c5d9
  • AMI ID for region ap-southeast-2: ami-5d5d713e
  • AMI ID for region ap-northeast-1: ami-bb3b21d5
  • AMI ID for region sa-east-1: ami-99a029f5

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.8.6 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 mr3.8.6 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 since mr3.8.5

MT#19199 use correct lbrtp_set id instead of default on call to voicemail&fax
MT#19565 Use index on kamailio.subscriber.uuid
MT#19159 kamailio: upgrade version to 4.1.9 for ngcp mr3.8.6+
MT#19157 Please prepare and release mr3.8.6
MT#19057 ngcp-status reports annoying warning “Warning: Permanently added ‘…’ (ECDSA) to the list of known hosts.”
MT#19047 ngcp-status claims on missed /var/log/mysql/slow-queries2.log on Carrier proxy nodes
MT#18985 302 Moved Temporarily not working
MT#18977 Freezed screen and wrongly formatted page pushing Flash Dialogic button
MT#18965 Add abilty to ngcp-status check LVM
MT#18907 asterisk is not creating core dump
MT#18879 CDR Exporter exports 5000 cdrs in one file and only 1 cdr into another
MT#18803 Glusterfs unmoung /mnt/glusterfs if second “start” action has been called.
MT#18843 wrong dispatcher ID is used for PBX MoH
MT#18797 [PBX] acc_caller_domain is not set correctly on call to huntgroup member
MT#18777 [PBX] When provisioning only a 2nd line on a Panasonic KX-UT113/KX-UT123, the line cannot be used to call
MT#18757 sending faxes from PBX users using ngcp-faxserver is broken
MT#18659 core ERRORs in kamailio-proxy.log
MT#18649 app_lua [app_lua_sr.c:100]: lua_sr_log(): central:del[1:13] counter was -1
MT#18643 ssh process is not listening on ha_int shared IP
MT#18637 REST API call “customerzonecosts” not working
MT#18625 [PBX] Add T38 RE-INVITE options for linksys-spa3xx cloudpbx-device
MT#18605 Collectd NGCP plugin causes high load even on standby node
MT#18563 Panasonic does not send Register with Expires:0 when reprovisioned
MT#18555 approx-gc cleans unnecessary (from it’s point of view) files from approx carrier cache every week
MT#18463 Prevent false lua error while decreasing counters on blocked calls
MT#18471 Call Forward loops are not detected for PBX users
MT#18417 [PBX] BLF funtion should not be available on Yealink T19P
MT#18395 use ajax lazyloading for values shown in panel dashboards
MT#18255 create index on usr_preferences (attribute, value)
MT#17955 cdr-exporter does not clean up /tmp
MT#17953 rebuild sems-pbx with thread pool
MT#17895 Unknown caller in call from PBX in HPBX-LAB
MT#17887 Fix update of interceptions
MT#17877 Call from pstn to pbx user and reffered back to peer causes source_acc to null
MT#17837 update P-NFCP-Callee-Info user on Call Forward
MT#17807 monit service is trying to start /etc/ngcp-config/templates/etc/ngcp-www-csc/csc.conf.services
MT#17805 Panel (?) seems not able to correlate PCAP files with PBX calls
MT#17783 Wrong CLI is shown for different customers
MT#17753 Extension dialing not possible if destination subscriber has preference force_inbound_calls_to_peer set to True
MT#17727 Last-Modified: Http header filled not according to rfc2616
MT#17709 Redis counters issue in case of multiple call forwards
MT#17681 collective check fails to detect lb running on passive node
MT#17645 Mediator is not handling field already containing PIPE symbol and the CDR fields are shifted in this case
MT#17507 ‘500 Internal server error’ configuring Off-peak-times
MT#17491 REST API: speeddials documentation without actual format
MT#17405 ngcp-status check mounted root partition
MT#17309 REST API call to get “Customer” -> “Contract Balance” -> “Spent this interval” missing?
MT#17125 Sbc incorrectly changes C= in SDP for IPv6
MT#16955 API – query params and null values
MT#16855 Call history is loading too slowly
MT#16719 network.yml for Carrier deployment
MT#16273 Voisniff-ng integration with EVE Pine, Utimaco and Lima Group2000
MT#18547 LI Pine Testing: direct pickup does not deliver X3
MT#16121 REST API call GET /api/callforwards?rows=200 takes > 35 seconds
MT#15875 Improvement of Diversion header acconrding to RFC5806
MT#15553 Destination-URI is not reset after 302 reply from UA
MT#15705 [PBX] Removed line still active on Cisco ATA
MT#15201 [PBX] e164_to_ruri does not work if the susbcriber is part of PBX group and I call the group
MT#13387 [PBX] Ring Timeout on Hunt Group CFT should prevail over the Ring Timeout of individual HG members
MT#14659 Editing subscriber details produces multiple slow queries to CDR