From Snom ONE wiki
At this point, we support Windows 32/64 bit, snom ONE mini, CentOS 32/64 bit and Debian 32/64 bit versions and Apple MacOS (10.6.3).
For new installations instructions are available on the Installations page.
Before upgrading make a backup of the working directory. If anything goes wrong with the upgrade, you can restore the file system and resume operations from that backup. We suggest that you prepare for an upgrade, so that the impact on your users are minimized. You can perform the upgrade while the system is running, then schedule a reboot at midnight. The system will then perform an upgrade only if there is no call active; otherwise it will wait. See Configuration Schedule for more information.
If you have made changes to the templates (web pages, email templates or PnP templates), please double check which of those changes are still necessary. New versions introduce bug fixes or new features that make such changes superfluous or even counterproductive. Keeping modifications of old versions may cause problems.
Upgrades from Version 5
For upgrades from version 5 you need to log in as administrator to the web interface of snom ONE and then navigate to the system tab. There is a field called Software Update.
All you need to do is copy & paste the following URL into your input field: http://snomone.com/downloads/snomONE/version-5.1.0.xml. After hitting the Save button, the system will start downloading the new software. The web interface will notify when the software update was finished. On the same page you can schedule a reboot or perform the reboot from the operating system. After the system boots up, you should be running the new software.
Also check how to licenses your snom ONE Version 5 Licensing your snom ONE.
Upgrades from 4.5
After upgrading to version 5 you need a new license key. You can get a license key from http://snomone.com. WE STRONGLY RECOMMEND THAT YOU GET THAT KEY BEFORE YOU UPGRADE. Your server needs to have access to the internet during the installation phase and it needs to be able to resolve DNS addresses. As with every upgrade, you should make a backup of the PBX installation, so that if anything should go wrong, you can revert back to the previous installation.
For upgrades from version 4.5 you need to log in as administrator to the web interface of snom ONE and then navigate to the system tab. There is a field called Software Update. Then copy & paste the following URL into your input field: http://snomone.com/downloads/snomONE/version-5.1.0.xml. After hitting the Save button, the system will start downloading the new software. Give it one or two minutes, then check the log file for messages. On the same page you can now schedule a reboot or perform the reboot from the operating system. After the system boots up, you should be running the new software.
If you want to perform a "manual" upgrade, you can just swap out the executable. The link in the executable is contained in the above XML file. In order to do this, you should first download the new executable, rename the old executable and then rename the new executable to the original name. There is no need to reboot the server for a software upgrade.
Please notice that for the snom ONE SoHo (AKA snom training kit) you need to perform a manual upgrade. Please visit http://forum.snomone.com/index.php?/topic/6448-upgrading-to-v5-from-v45-on-soho/ for more information.
Upgrades from other version 4 releases and version 3 releases
Upgrades from other version 4 releases are similar. If you have the Software Update field, you can use that the same way it is being used with version 4.5. Because the trunk header settings may have changed during the upgrade, you have to pay special attention to the trunk header settings after the upgrade. If the Software Update field is not available in the used version, you must first use the upgrade procedure to upgrade to version 4.5 and then perform another upgrade from there.
New Features 5.0.0
- Fax2Email. When a call hits the mailbox, the PBX now detects the fax CNG tone and attempts to change the codec to T.38. If that succeeds, the PBX will receive the email and send it out as PDF document attached in an email to the owner of the mailbox.
- Microsoft Lync Integration. snom ONE is now able to register accounts with Microsoft Lync and publish presence state when the call state changes. This makes it possible to see on Lync when someone is on the phone on snom ONE. This requires that the user enters the Lync username and password in snom ONE.
- Windows Attendant Console. Version 5 supports the new attendant console, which will be released separately. The attendant console is a native Windows application with a WPF front-end and a softphone included.
- Browser Support. For incoming calls, a Windows helper application can be used to open a web browser with a definable URL. This makes integration with many CRM-tools significantly easier. The new tool is available from http://wiki.snomone.com/index.php?title=Csta_Browser and requires CSTA support.
- On hunt groups an established call could get disconnected when a ringing phone gets offline (e.g. reboots).
- Alternative names in certificates were ignored. Wildcard certificates were processed correctly.
New Features 5.0.1
- Domains may now have account limitations like the system has on global level. This makes is possible to rent domains with better control over what features users are using
- The private virtual assistant that could be used with the cell phone has been reworked. Now it uses fixed menu items.
- There could be problems with client certificate requests when registering on Microsoft Lync accounts.
- When placing outbound calls from the calling card account or from the private virtual assistant, it could be that the call was not placed when calling from certain extensions.
New Features 5.0.2
- Respond to OPTION for registered extensions. This is to deal with some third-party servers that register with snom ONE. If the PBX does not respond to OPTION requests, those servers consider the registration dropped.
- The attendant console should now be able to see when another extension is on DND.
- External applications can now set a "shadow" call state for extensions through HTTP. This is useful for example when cell phones publish directly or indirectly their presence state through an app or the carrier provides that service.
- Check IPv4 records before IPv6 records for HTTP and SMTP clients. This is because most servers are still using IPv4. This makes the email integration with popular services like gmail who advertize IPv6 addresses a lot easier when IPv6 connectivity is not available.
- Automatically try to re-apply the activation code when the license will expire. This makes is possible to come up with rental license model for the PBX.
- Emails may now contains additional, customer-defined headers. This makes it possible to set email headers like Bcc, Subject or completely proprietary headers. For example, text to speech gateways can use these headers to control the rendering of the content.
- In the Linux server editions, PCAP tracing was not enabled in the 5.0 builds.
- When an extension was on DND, the PBX was checking the redirect all settings for the extension. This was hard to use, because extensions would have to set and clear the redirection all target every time they want to go to DND. The new version uses the redirection on busy target then the extension is on DND. This is not completely backward compatible with previous versions; however we think that this is a bug fix and not a new feature.
- Reset the trunk status after a restart. The trunk status was not reset after a restart. Usually that was not problem; however trunk status change emails were not triggered after a restart and the snom ONE mini LED was not set properly because of this.
- For sending FAX attachments, the user had to select the option to attach voicemails as well. That was confusion and unnecessary. Now fax messages are always send as attachment, regardless of the voicemail selection.
- The 5.0.2 XML upgrade file now contains the file be_ced.wav, which is required to receive FAX messages. The FAX receiver was optimized for better interoperability with some service providers and manufacturers. This includes a change in the port strategy; now the PBX re-uses the RTP port for T.38, so that NAT-bindings don't have to be changed.
New Features 5.0.3
- snom XML RPC added. The snom proprietary API for central provisioning redirection can now be set up from the PBX interface. When a MAC address is associated with an extension, it automatically updates the snom XML RPC server. This makes it possible to plug and play phones in hosted environments and large installations where option 66 is difficult to implement in all sites.
- Buttons can now have device-specific defaults. When setting up and extension, the administrator does not have to specify any more what button profile has to be used on that extension. Instead, the system will pick the default profile for the device and domain. Administrators can still override this on extension-basis like before.
- Added more commands to the trunk headers. Now the generation of the headers may include conditions. This makes it possible for example to set headers only when the call comes from an extension. See http://wiki.snomone.com/index.php?title=Trunk_Custom_Headers for more information.
- Accept PIN in the mailbox also when the mailbox is full message is being played out. In previous versions, the user had to first stop the announcement with *. Many users did not know that and accepting the PIN immediately does not break any other functionality.
- Several optimizations for the UC client. The UC client can now show who is in the ACD or in a conference room. When starting the UC client up, the probability that it gets accidentally blacklisted is now much lower.
- Mailbox may now be explicitly marked as FAX mailbox. In that case, it does not play back any announcements until it receives the CNG tone. If there is no tone, it does not record any voice message by accident.
- Allow area code "-" for countries that don't have a domestic prefix (e.g. Denmark).
- Automatically allow OPTIONS refreshes on trunks. When a trunk is registered, it accepts OPTIONS request on that registration connection. With this new feature, it is not necessary to explicitly enable the answering of OPTIONS. This reduces the vulnerability in situations when OPTIONS are required.
- Extension status changes may now be published with HTTP/JSON request in addition to emails.
- Cell phone menu now automatically disconnects when user does not press any key for more than 20 seconds in menu. The same is true for other IVR like setting redirections where the user does not interact with the system.
Bug Fixes 5.0.3
- Cc and Bcc headers should now work with the email templates. The previous versions did set the headers in the email itself, but was ignoring them in the SMTP protocol.
- More optimizations for FAX servers that need explicit silence indicators. Non-Windows builds had problems with the FAX header in the PDF document.
- Locations can now be set from a list of locations added by user, as well as from the domain.
- snom 3xx series revert back to 8.4.35. This step was done because there the 3xx series seems to have problems with the 8.7 firmware versions and there was no immediate benefit from moving to 8.7 for these devices.
New Features 5.0.4
- Implemented ActiveSync to get contacts and calendar from Exchange servers. Now extensions can poll periodically for changed in the address book, using ActiveSync.
- Also include ActiveSync contacts to appear on devices through LDAP. That means devices can search for names and numbers using LDAP.
- Establish conference calls based on ActiveSync calendar. Conferences can now be set up in a convenient way using Outlook.
- Added more features to the auto attendant dial-by-name mode. For example, the PBX may now search on word boundaries in names.
- Report idle duration. In addition to the times how long a call was connected, ringing, the PBX now also reports how long the extension was idle before the call. This makes it possible to measure inactivity in groups.
- Domains can now have their own administrators, without having to use an extension for that.
- Split the administrator into two account types: The super-admin and delegated administrators. This makes it possible to have multiple administrators for the whole system with separate login data.
- The login type detection was removed. Every account now has only one role.
- 64 bit builds have by default a lot more SIP and HTTP connections. This should help reducing subtle problems when registering more than a hundred phones using TCP/TLS.
- Domains and extensions can now define the ringback WAV file when the extension is ringing while not connected to someone else and with separate settings, when already connected. This makes it possible to tell the caller when the extension is busy.
- The HTTP client can now accept wildcard certificates.
- The IP access list can now deal also with 23/22 bit netmasks.
- The RTP port range can now be defined on a per trunk level. This makes it possible to provide special QoS settings for trunks and for some service providers, this is a requirement.
- JSON: Added method to set up domain and domain metering.
Bug Fixes 5.0.4
- Fixed update, so that other updates, besides executable, are also taken into account. Previously, updates could fail that did not include an executable, for example language packs.
- Fixed trunk tabs like rates. Fixed column selection on some pages. The web interface was not showing those. Fixed "More Actions" for accounts, so that things like remote rebooting the phones etc. work.
- Improved loading of account pages, so that all the columns including pictures don't appear for a while on loading before going to selected columns.
- Button provisioning on snom 8 series phones fixed. There were some problems when using snom 821 and 870 phones.
- Some more optimizations for certain FAX types. The PBX was repeating the startup sequence in version 5.0.3. However on certain answers it kept on repeating.
- Refresh license for domain when changing the domain limits. This was causing subtle problems when purchasing more extensions and applying the activation code with no success.
- For hosted PBX clients, the previous version did not report the usage every 24 hours. This makes it necessary to upgrade to 5.0.4.
- The snom XML RPC could get out of sync if multiple MAC addresses were used. Also, when saving the settings again, the password could get lost/overwritten.
- The codecs names in the SDP are now in a better format, as they are according to the RFC case sensitive.
Bug Fixes 5.0.5
- show disabling of accounts
- copy username to account in trunks
- ActiveSync improvements: additional support for older version of ActiveSync 12.1; better handling of 451 error code; support for other languages of Exchange Server; more reporting of errors; improved description of setting names
- some web page description improvements
- correct copyright year
- more dictionary entries
- Setting the super-administrator password checks if the password matches the password policy
- When the RTP ports in the trunk settings are empty, it now falls back to the system settings
New Features 5.0.6
- Each domain now contains its own log. This is an important step into further virtualization of the PBX (multi-tenant). Now tenants are able to troubleshoot simple problems with their own log.
- The cell phone twinning feature was enhanced with a list of exceptions. Now users can specify which numbers may always and never include the cell phone. This is an extension of the time-based rule that can be set by the user.
- The new release used websocket for communicating real-time updates to the web browser. That is used for showing active calls on system and domain level and for showing account related information (attendant console in the web interface).
- The provisioning now associates MAC addresses with passwords. This makes it possible to open the provisioning for devices for a few minutes and provision the phone without certificates and without passwords. This is important for snom 3xx series, but also for other 3rd party devices.
- We have added a traffic graph to the status screen and the status emails. This makes it easier to detect situations where there might be DoS attack on the PBX.
- A button profile that is chosen for a particular user by the admin can be changed by the user now.
- Apart from the custom ringtones, to play custom tones, you can now access the phone's local ringtones from the phone as well.
- The display of the idle time of the agents was buggy and has been fixed in several places.
- The presentation of the idle duration was buggy in the emails and in the web interface.
- ActiveSync had problems with large numbers or contacts. Also, LDAP did not search all ActiveSync contacts.
- Email with Microsoft Office 365 was working only if the certification check was turned off. Now it should also work with certificate check on.
- For ACD login and logout, the LED was not updated correctly.
- The cell phone button was not working properly anymore and has been fixed.
- For the metered hosted PBX, disabled accounts are not counted any more.
- Large TFTP files (more than 32 MB) were not transferred correctly.
- Switching to video did not work in all cases. Now callers can switch video on again after the audio session has been established.
- The domain account web interface was redone, using latest JSON technology. This makes it possible to do further changes and improvements in the web client. This adds a lot more flexibility for this task. Further improvements will come in the upcoming revisions of the software.
- We changed the default port for LDAP. The reason behind is that the port is automatically provisioned anyway and when running on public IP, there is no reason to expose it on the default port.
- We removed the ability to measure the gain of the call. Today’s PSTN gateways have no more gain problems; turning the flag on was consuming significant CPU resources and was very difficult to troubleshoot.
- When an external call was are ported through the HTTP interface and the extension does not allow call waiting, the PBX now rejects new calls although the PBX itself does not have active calls.
- CDR for anonymous calls were represented by the domain name in the simple CDR format, which was confusing. Now it uses a localization-specific value, typically "Anonymous".
- The Spanish texts were reviewed for completion.
New Features 5.0.7
- The address book has now a field for storing the cell phone number.
- The minimal duration for a mailbox message was previously hard coded to one second, now it is a setting. The default is still one second.
- The provisioning for Polycom phones has been redone. Now users can use version 4.0.3F of the Polycom firmware. The Polycom phones can now also be provisioned by temporarily open accounts for provisioning. Polycom phones now use LDAP to query the PBX address book.
- When a user calls from a cell phone into the auto attendant, gets into virtual private assistant and selects the auto attendant, the user now uses the auto attendant that was called. Previously, the PBX would pick a random auto attendant in the domain, which could be confusing.
- The default certificate for all builds is now snom ONE. Previous builds were still using the pbxnsip certificate.
- The default TCP keep alive time was changed to 60 seconds. This was necessary to make Polycom phones stay registered without dropping the connection; potentially also problems with other devices behind will also benefit from this change.
- When a language pack is loaded through the web interface, it now automatically shows up in the drop-down list without restart of the service.
- When the snom XML RPC redirection server settings is empty, the PBX now provisions the domain name. This makes operation in hosted environments easier, especially for moving domains from one server to another.
- For the CSTA browser, the PBX now provides information about the call type. This makes it possible to have the browser pop-up only for example for calls to an agent group, but not for internal calls.
- The service flag status was cleaned up, at least internally. There was a lot of confusion about what it means when it is set.
- When trunks had to represent the number, it was assumed that the dial plan presents the number in the global format starting with “+”. In most of the cases that was not the case. Now the PBX is more tolerant and also accepts numbers in the domains country format.
- The LDAP functionality was significantly improved. Now the PBX is able to process requests with more operators than before.
- When forking calls to the hunt group or to the agent group and when the user has selected to confirm the call, pressing “1” had no effect. This has been fixed.
- Intercom with buttons was not working with snom phones.
- When testing the dial plan from the web interface, disabled entries were not ignored. In the new version, the test mode should behave like the real mode.
- The log messages could easily break the output format. Now they should stay inside the table cell.
- The private keys for the certificates are not encrypted on the file system.
- When rendering IP addresses during the provisioning process, the PBX was sometimes still using the IP address instead of the DNS name.
- On MacOS the PBX could crash when using G.729A codec.
- MIME documents for DND and redirection were not formatted correctly.
New Features 5.0.8
- Added new code *56 that allows callers to listen to the automatic recordings of accounts. For example, this feature can be used to listen to the recordings in a ACD using the cell phone on the way home.
- The web interface shows the DID and the ANI of users in the account overview.
- Added JSON CDR reporting (see JSON CDR for more information)
- The ACD has a new option for announcing recording. It was also possible in previous version, but the new option makes it a lot easier.
- Added the possibility to call the user's cell phone from the mailbox instead of leaving a voice-mail. This requires that the prompt is available in the language set.
Changes in 5.0.8
- Changed the email templates and included general email header and footer files.
- Intercom now shows the BLF state of the extension
- The fix for sticking to the auto attendant that was called in the first place did not entirely solve the problem. Now when someone calls in from the cell phone and selects auto attendant in the private virtual assistant, it really takes the called auto attendant.
- There was still confusion in the web interface if version 4 or version 5 files should be used. This should be clearer now.
- The DoS protection for the web interface in 5.0.7 was too aggressive. 5.0.8 should reduce the number of false alarms significantly.
- The websocket could easily timeout.
- There were several problems when compiling the image for little-endian machines.
- The license warning was sent also for expired features.
- Hunt groups and ACD groups were mixed up when setting the night mode redirection with *80.
- The password for the XML RPC password was not stored. This bug was introduced in a previous version; users that had already the password stored were not affected.
- The cell phone exception list was obviously working only for internal numbers
New Features in 5.0.9
- The user login screen now shows the active calls and calls can be terminated and transferred from there.
- Park orbits reminders may now be sent to a predefined destination, not just the extension which has parked the call
- Accounts may be made invisible to shield them from the address book and from the auto attendant dial by name directory.
- We added the call delete button back in the domain and administrator call view.
Bugfixes in 5.0.9
- The Polycom template was not suitable for multi-domain deployments
- When renaming an account in multi-domain deployments and another domain had a matching name, the renaming failed.
- Some versions of the snom phones abort the PnP if the first file gets redirected. That broke the PnP process.
- CDR attachments for the email were not in properly formatted HTML
- Inline CDR email had the wrong encoding
- Since we have upgrades the tool chain for Windows, it seems that Windows XP support became a problem. We added that back for the 32-bit versions.
- The page usr_recordings.htm was missing and has been added back
New Features 5.0.10
- Polycom phones can now park and pickup calls using the BLF buttons. The provisioning uses the button profiles for setting up the Polycom phone buttons when one of the BLF modes is being used.
- The domain view of the user’s mailbox settings now also shows the mailbox messages. The messages can be deleted from that view as well. Listening to the messages is not supported on purpose.
- The web interface now also shows in the domain how long the phones in that domain are registered. Along with that information, there is a list of the used firmware and the IP addresses from where the phones are registering.
- The web interface also now makes it easier for selected SIP trunk providers to set the trunk up. The list of available SIP servers has been reviewed and extended, so that also SIP headers can automatically be set up the right way.
- User Page Control
- Show active calls and its status.
- Manipulate active calls, like cancel, hangup, blind transfer, hold, attended transfer, recording etc.
- Dial from the page.
- Calls can now be terminated from admin and domain login from active calls.
- Fixed a PnP issue with phones not sending their MAC address.
- Fixed user settings to be available both at user and admin level.
- Fixed presence showing of extensions on user page.
- The duration for dialog-based subscriptions has been changed to one hour. This was necessary to reduce the overhead for large number of subscriptions. As a side effect, it may now take up to one hour for the phones to synchronize the dialog state information, e.g. when the server was rebooted.
- The provisioning for Yealink phones was redone. Now they are able to use the DND and redirection synchronization, BLF keys and time zone provisioning.
Bug Fixes 5.0.10
- Unlicensed accounts can now be deleted from the web interface.
- When the callback number of an orbit was assigned to an extension, that callback was ignored. Now it calls the specified extension back.
- When snom phones were using a path that included /prov, following files could have the prov path component included twice. This resulted in “not found” errors during the provisioning.
- When the PBX received an initial SDP offer with video, that could lead to a codec negotiation problem with rejected calls. When the audio stream changed the SSRC, but the media address remained the same, the PBX could consider that moving back in time with the result of discarding the media.
- Under certain circumstances, the PBX might receive outdated REGISTER responses that were being processed. This was happening especially if the registration interval was less than 60 seconds. That could result in confusing status messages or unregistered trunks.