SIPWISE CE - NEWS

back to all Sipwise CE - News

sip:provider mr3.8.5 Released

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

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

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

  • Direct upgrade from 2.8 LTS to mr3.8.5 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.8
  • 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-e993a283
  • AMI ID for region us-west-2: ami-c87794a8
  • AMI ID for region us-west-1: ami-8186f7e1
  • AMI ID for region eu-central-1: ami-813a20ed
  • AMI ID for region eu-west-1: ami-0dc4797e
  • AMI ID for region ap-southeast-1: ami-96b27bf5
  • AMI ID for region ap-southeast-2: ami-4970562a
  • AMI ID for region ap-northeast-1: ami-c58f8eab
  • AMI ID for region sa-east-1: ami-991f9cf5

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.5 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.5 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.4

MT#17685 Prepare and release mr3.8.5
MT#9759 Add pre-upgrade checks to ngcp-status
MT#5349 NGCP-API: Implement domain handling
MT#17837 update P-NFCP-Callee-Info user on Call Forward
MT#17709 Redis counters issue in case of multiple call forwards
MT#17645 Mediator is not handling field already containing PIPE symbol and the CDR fields are shifted in this case
MT#17623 Fix reloading dialplan cache on cloning/deleting rwr set
MT#17619 prosody process needs mysql service to be up
MT#17523 cleanup-tools cron job sends a warning mail if “default” folder in /var/spool/asterisk/voicemail/ doesnt exist
MT#17517 vmnotify uses wrong via and binds to wrong local ip on carrier
MT#17373 wrong extra_socket selected for replies
MT#17199 user_agent information not returned in API fuction subscriberregistrations
MT#17153 The root filesystem contains a file named &STDOUT
MT#17025 2.8 cannot be upgrade to 3.0/mr3.8* due to updated MySQL: E: Could not perform immediate configuration on ‘mysql-client-5.5’
MT#17023 Fake Alarm rtpengine processes running, more than 1 or less than 1
MT#16959 Redis counters are not descreased
MT#16933 Rest API 400 Bad Request The SSL certificate error
MT#16883 CFB to voicemail set a CF to vmuXXXXX in DB instead of vmbXXXXX
MT#16795 Missing inetd.conf.services template file
MT#16773 kamailio counters: don’t allow negative values
MT#16763 Incorrect ID column in reseller MySQL query (was: UTF-8 encoded reseller name cause empty EDR files)
MT#16587 Brocken UTF encoding in field “alert” sent to Apple Push server (APNS)
MT#16491 calls query and index for group by
MT#16467 “Create Sound Set” dialog should allow to select only the Cloud PBX customers
MT#16387 Tracking and reporting of required reboot
MT#16365 Reverse Media Negotiation not working when first INVITE is without RTP – rtpengine not in mediapath
MT#16355 NGCP (panel) version not shown in web interface
MT#16337 SOAP Error after Upgrade to 3.8.3
MT#16231 Panel is not applying rewrite rules in Received Fax Journal web page
MT#15803 check pull before ngcpcfg apply
MT#15489 REST API for sending faxes (POST /api/faxes/) has problems with German Umlauts
MT#15455 IPv6 call fails because of a loop in ACK
MT#15175 Change behavior of packet ngcp-support-access
MT#14479 ngcp-status: provide support for checking ntp setup
MT#12013 Kamailio bug – kamailio set $au=NULL to ACK and CANCEL
MT#10199 Add NCOS Level in Subscriber Profile
MT#16321 REST API call GET /api/subscribers?username=xxx takes too long (> 1.5s)
MT#16121 REST API call GET /api/callforwards?rows=200 takes > 35 seconds
MT#16985 Add possibility to connect to a different DB for interception data
MT#17125 Sbc incorrectly changes C= in SDP for IPv6
MT#16463 [PRO] please build ngcp-libswrate0-dbg, captagent-dbg
MT#17887 [PRO] Fix update of interceptions
MT#16273 [PRO] Voisniff-ng integration with EVE Pine, Utimaco and Lima Group2000
MT#17577 [PRO] LI (captagent or voisniff) is not under SNMP
MT#17575 [PRO] Captagent init script is wrong
MT#17783 [CloudPBX] Wrong CLI is shown for different customers
MT#17753 [CloudPBX] Extension dialing not possible if destination subscriber has preference force_inbound_calls_to_peer set to True
MT#17727 [CloudPBX] Last-Modified: Http header filled not according to rfc2616
MT#17953 [CloudPBX] rebuild sems-pbx with thread pool
MT#17895 [CloudPBX] Unknown caller in call from PBX
MT#17563 [CloudPBX] DB_ONLY mode for presence broke PBX in mr3.8.4
MT#17477 [CloudPBX] Supporting new hardware version of Yealink SIP-T21P
MT#17473 [CloudPBX] Button “Add another range” in creation panel of pilot subscriber doesn’t work
MT#17383 [CloudPBX] Supporting new hardware version of Yealink SIP-T19P
MT#16983 [CloudPBX] Panel/API set new subscriber as part of all the PBX groups
MT#16877 [CloudPBX] set colp and sca rr params in branch route
MT#16829 [CloudPBX] wrong CLI for inter customers extension transfers
MT#17027 [CloudPBX] sems-pbx fails to relay 183 with dlg->reply() failed
MT#16775 [CloudPBX] Call to Offline user ends up in a double announcement
MT#15519 [CloudPBX] Wrong number displayed at callee after blind call transfer
MT#13155 [CloudPBX] Audible ringing for calling user continues for 3 minutes even when huntgroup member ringing stops after 10 seconds
MT#12937 [CloudPBX] Order of huntgroup member in API call

Leave a Reply

Your email address will not be published. Required fields are marked *