SIPWISE CE - NEWS

back to all Sipwise CE - News

sip:provider mr3.8.7 Released

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

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

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

  • Direct upgrade from 2.8 LTS to mr3.8.7 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 till May 31, 2018.

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-bdd15caa
  • AMI ID for region us-west-2: ami-2234f642
  • AMI ID for region us-west-1: ami-56d99f36
  • AMI ID for region eu-central-1: ami-89c732e6
  • AMI ID for region eu-west-1: ami-0187e672
  • AMI ID for region ap-southeast-1: ami-fccd119f
  • AMI ID for region ap-southeast-2: ami-ec33198f
  • AMI ID for region ap-northeast-1: ami-11b44a70
  • AMI ID for region sa-east-1: ami-404ade2c

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

MT#21177 Upgrade 2.8->mr3.8.6 failed due to missing file /etc/apt/trusted.gpg.d/sipwise.gpg
MT#21001 cloud_pbx_callqueue feature does snot work. Sems-pbx does not find audio file (queue_waiting_music) from db
MT#20889 Cancel Request contains Route header.
MT#20847 Collectd plugin NGCP.pm is not thread safe
MT#20737 [from|to]_tag field size in “all other table that store tag”
MT#20695 After manual switchover, ngcpcfg status order to “execute ‘etckeeper commit”
MT#20557 Update NGCP prompts: IT RO RU US DE
MT#20493 Rtpengine module creates double newline in SDP after have extraced the SDP part from a multipart body
MT#20465 ngcp-approx-cache-helper works improperly if current folder has a file ends with ‘list’
MT#20463 fix detecting strict router
MT#20369 API “Internal Server Error” code 500 trying to save an already used number as an alias number to the subscriber
MT#20349 kamailio LB doesn’t work on CE while works well on PRO
MT#20315 API PATCH method for the customers is broken
MT#20235 Yealink devices not upgrading firmware on FW version >V80
MT#20229 Transfer button does not work on a Panasonic device (UT136/UT248) does work on UT113
MT#20207 Sound set failover (fallback to system sound set for call queues)
MT#20191 Re-starting  “ngcp-upgrade” fails after it stopped during upgrade process
MT#20163 Wrong information message ‘trunk’ at the end of the upgrade to 3.8.6
MT#20151 Fixed MySQL error: Data too long for column ‘from_tag’
MT#20135 Callqueue resets P-headers
MT#20131 Fixed call waiting, call holding and call transfer. Following Panasonic UT-series
MT#20117 File /etc/hylafax/hosts.hfaxd has wrong permissions after installation
MT#20005 collective-check: Emits warnings when exim_queue.rrd has undefined values
MT#19993 ngcp collective check repors wrong hostname
MT#19887 Permanent registration problems on upgrade 2.8->mr3.8.6
MT#19881 Typo in german translation: “Sprachnachriten und Sprachbox” instead of “Sprachnachrichten und Sprachbox”
MT#19821 May Controller::SubscriberProfile::profile_edit delete cc for all customers
MT#19697 API documentation: wrong description in “3.40 NcosPatterns” sub-chapter
MT#19657 Fixed problems creating rewrite rules in mr3.8.6
MT#19627 The NCOS level with brackets in name causes error on a subscriber.
MT#19565 Use index on kamailio.subscriber.uuid
MT#19401 allow_ips_grp id got screwed after upgrade from 3.4 to 3.5.1
MT#19301 After upgrade to 3.8.4 BLF pickup doesnt work
MT#19231 Hosts file for hylafax should contain IP address of MGMT node
MT#19157 Please prepare and release mr3.8.6
MT#19089 introduce new type to avoid sip_ext duplicates in network.yml
MT#19075 Remove ability to provision 30 key on Yealink SIP-T48G
MT#18985 302 Moved Temporarily not working
MT#18665 The collectd NGCP plugin handles redis errors incorrectly
MT#18601 Web pannel pbx groups shows wrongly the susbcribers that have CF enabled-cosmetic
MT#18375 FAX to email problem no suitable MTA found to send the envelope at /usr/share/hylafax/faxrcvd line 730.#012
MT#18235 db_mysql [km_dbase.c:122]: db_mysql_submit_query(): driver error on query: Data too long for column ‘caller_contact’ at row 1
MT#18105 Ngcp-sems-pbx component is crashing
MT#16985 Add possibility to connect to a different DB for interception data
MT#16619 improve outbound_socket fetching from replies
MT#16443 API: fix creation of customercontacts as reseller
MT#16415 Documentation improvement for mr4.2
MT#15367 panel shows wrong zones
MT#13531 Cannot terminate reseller in trunk/mr4.0 (Can’t locate object method “email_templates”)
MT#12939 How to define the hutgroup order
MT#12819 FAX received as TIFF. TIFF isn’t readable on Windows
MT#9759 Add more checks to ngcp-status
MT#6969 ngcp-panel: trigger SPA device resync via SIP NOTIFY
MT#6235 FAX orientation is wrong (sending portrait but received landscape on email)