December 7, 2017
Summary
eZuce is pleased to announce the General Availability of sipXcom 17.10.
This release of sipXcom contains only a small set of new features, enhancements and bug fixes.
IANT has contributed high availability paging to the system. A word of caution about using this as the paging service will still open a voice call to each phone in the paging group and is not optimized to use the ‘closest server’.
Dev & QA teams at eZuce have been busy as usual. Much of the on-going work is on the next generation of sipXcom. Stay tuned (or watch the docker branches in Github)!
Highlights
sipXcom New Features:
Highly Available Paging Services
sipXcom Improvements:
New “No Group” user filter in Admin Portal
Add additional verbosity to Proxy Auth Plugin
Add Intercom settings for Snom devices
Notes
Full Beta Release Notes with installation information are located here: 17.10 Full Beta Release Notes
Who Should Install?
This release is recommended for all 4.6 and later installations.
Questions
Please post to the sipXcom-users google group if you have questions.
https://groups.google.com/forum/#!forum/sipxcom-users
Specific Issues Addressed
Specific issues can be located in the detailed release notes in the wiki at: http://wiki.sipxcom.org/display/sipXcom/sipXcom+17.10
New Installs
A new ISO is available for 17.10 at: http://download.sipxcom.org/pub/sipXecs/ISO/
(ISO's are not available for betas)
Update
To update please edit your /etc/yum.repos.d/sipxecs.repo file and reference the new download server (download.sipxcom.org). The repo should look as follows:
[sipXcom]
name=sipXecs software for CentOS $releasever - $basearch
baseurl=http://download.sipxcom.org/pub/sipXecs/17.10/CentOS_$releasever/$basearch
gpgcheck=0
To edit this file, login to your sipX server as root and then use either vi or nano (easier).
vi /etc/yum.repos.d/sipxecs.repo
or
nano /etc/yum.repos.d/sipxecs.repo
Once the repo file is modified, run:
yum clean all
yum update
Issues Resolved
| JIRA name | RN Content | Enhancement/Fix/Known Issue | Key words | |
| SIPX-668 | Intercom/Paging calls for Snom and Fitre | Add support for intercom and paging call to Fitre and Snom devices For Fitre devices it is necessary to add the parameter "intercom=true" to the Request-Line For Snom devices it is necessary to the string ";info=alert-autoanswer;delay=0" to the Alert-Info header | Enhancement | Snom |
| SIPX-676 | sipXpage High Availability | Added high availability for sipXpage (Paging Groups) It can be enabled by checking the Enable High Availability Paging box under Features->Paging Groups->Settings->Show advanced, followed by the service enabling per server under System->Servers->Telephony services. Note that administrator needs to be careful with regards to paging large groups of users and distributed networks. | Enhancement | Paging |
| UC-4505 | Auth plugin log verbosity | An administrator would like additional verbosity to the proxy auth plugin logs. For example, instead of : 2017-01-25T21:33:07.170000Z:2206:AUTH:INFO:sipx.example.com::7fc0d0f72700:sipxproxy:EnforceAuthRules[400_authrules]::authorizeAndModify no permission required for call GWGWb1ecb313-5de8-1235-1c8d-00219b91474e@45.32.76.96 2017-01-25T21:33:07.170178Z:2207:AUTH:INFO:sipx.example.com::7fc0d0f72700:sipxproxy:SipProxy::proxyMessage authoritative authorization decision is ALLOW by 400_authrules for GWGWb1ecb313-5de8-1235-1c8d-00219b91474e@45.32.76.96 .. the improved version of these messages would (preferably at NOTICE proxy verbosity) include the user associated with this dial plan challenge, and the exact rule (or some kind of identifier of the rule) that resulted in the allow or deny. Auth and fallback rules check tools: Both tools should get path to authrules/fallbackrules xml file as parameter. Both tools should get uri as parameter. fallbackrules tool should get location string as parameter Result of this tools call should be same as when proxy uses xml files above. This would allow to check matches of rules offline, without making any calls. | Enhancement | Proxy |
| UC-4518 | sipXbridge should support SRV record lookup for ITSP | An administrator would like to be able to subscribe or route calls to a series of SBC's that are located with SRV records. Previously it was only possible to use an A record or IP address to connect to an ITSP or SBC. | Enhancement | sipXbridge |