We are excited to announce the general availability of sip:providerCE mr3.8.8 and sip:providerPRO mr3.8.8.
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 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.8?
The most important changes for mr3.8.8 compared to mr3.7.x are:
- Direct upgrade from 2.8 LTS to mr3.8.8 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?
- AMI ID for region us-east-1: ami-e83872ff
- AMI ID for region us-west-2: ami-a04398c0
- AMI ID for region us-west-1: ami-e3256d83
- AMI ID for region eu-central-1: ami-fec43a91
- AMI ID for region eu-west-1: ami-53eeac20
- AMI ID for region ap-southeast-1: ami-052e8966
- AMI ID for region ap-southeast-2: ami-7d1a281e
- AMI ID for region ap-northeast-1: ami-e603d987
- AMI ID for region sa-east-1: ami-97ea77fb
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.8 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.
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.8 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.7
MT#22945 Mediator not able to process some CDRs related to call-through service
MT#22804 Bulk-loading PBX devices data for a Reseller fails
MT#22776 Uninitialized variables EXPORT_FAILED and EXPORT_UNRATED in /usr/sbin/event-exporter
MT#22629 NGCP MySQL VULNERABILITY issue
MT#22177 Extend live-cycle of call record to final end after call park
MT#22063 API does not allow setting “friday-sunday” (6-1) in cftimesets/
MT#22007 sems-pbx 2.3.0~20150224~c41565d-1+0~mr188.8.131.52 crashed
MT#21871 500 Internal server error with setting allowed_ips preference
MT#21827 Wrong closing class in Model::InterceptDB
MT#21775 Interception REST API call should write a regex in the sip_username DB field
MT#21763 ngcp-sems segfault due to sbc.so
MT#21693 Notify is missing if subscriber has queue enable
MT#21519 cdr_export: no check for “export_failed” and “export_incoming”
MT#21513 peer_auth_register parameters not correctly evaluated by SEMS
MT#21499 Backport to mr3.8 slave_type_conversions=ALL_NON_LOSSY and slave_skip_errors=1032
MT#21435 API: pbxdevices GET fails for the reseller account
MT#21401 Creating a reminder via API throws a 500 Internal Server Error
MT#21355 voisniff-ng integration with PINE: ability to parse From/To instead of P-NGCP-* headers
MT#21325 After upgrade to 3.8.7 Asterisk is crashing in voicemailmain()
MT#21303 After upgrade cdr-export does not work
MT#21177 Upgrade 2.8->mr3.8.6 failed due to missing file /etc/apt/trusted.gpg.d/sipwise.gpg
MT#20913 IC-Test DTAG / wrong index and content of HIST-INFO-HEADER ( sequential call-forwarding )
MT#20889 Cancel Request contains Route header.
MT#20573 NGCP RO to HPBX with CFU to HPBX (no X2/X3)
MT#20525 Set callee lbrtp_set to caller on BLF pickup call
MT#20511 NGCP discards received History Info Header ( sequential call-forwarding )
MT#20499 CDR cleanup mechanism is required to prevent filling up the cdrexport file system
MT#20441 Wrong CLI presented when call is coming in via an Auto Attendant
MT#20395 NGCP does not send 200ok after client phone sends replaces
MT#20315 API PATCH method for the customers is broken
MT#19939 Use Anonymous / Privacy Mechanism based on RFC3323 for outbound calls to PSTN
MT#19733 batch size/row limit for cdr-exporter
MT#19731 prevent cdr-exporter from simultaneous execution/piling up cron invocations
MT#19623 Create an Invoice failed with 504 Gateway Time-out
MT#19295 Bug with internet explorer 11 in Web panel
MT#19277 NGCP-Sems crashed: “AmRtpAudio.cpp: No such file or directory” (AmRtpAudio::receive at AmRtpAudio.cpp:114)
MT#18999 Invoice generator doesn’t like & symbol
MT#18839 Calls to Conference Rooms have bad QoS
MT#18561 LI rest API do not reply 40x on LLID change attempt
MT#16623 Content of frame for editing invoice template is empty for google chrome > 48
MT#16273 Voisniff-ng integration with EVE Pine, Utimaco and Lima Group2000
MT#15659 sems-pbx/dsm: keep same call-id for outgoing call from AA and callqueues
MT#15343 CFU not working if destination has PBX Call Queue enabled
MT#15341 When calling to AA the subscriber see from 00311 displaying in second leg call.
MT#15201 e164_to_ruri does not work if the subscriber is part of PBX group and I call the group
MT#13749 Caller ends up in wrong VM box, after CFT
MT#13573 CallList incorrect for records of terminated subscriber
MT#8041 ngcp-sems v.1.6 crashes randomly during nightly builds