Spok Mobile Server Release Notes 5.1.x

New Features and Enhancements 

No new features or enhancements.

Corrected Issues

• The issue with requests to the Spok Mobile servers on the "/auth" URL causing an HTTP 503 error to be returned and the request to loop has been resolved.
• Resolved a security issue by providing stronger access control and enhanced web security. See the Security Updates section below for more information.
• Volume control when iOS mute switch override is enabled: Server side changes were made to support updates made to iOS volume control functionality. The iOS application was updated to align the volume control functionality when mute switch override is enabled to the Android “do not disturb” configuration. Previously, iOS users were unable to adjust the volume on an alert in this situation. A toggle button for each tone option (High, Medium, Low) has been added so the user can control the volume. Optionally, the site mobile admin can configure tone options for a device group. Spok Mobile application for iOS 4.7 (or later) is also required for this update.

Security Updates

• Stronger access control has been implemented for API endpoints to eliminate possible exposure of configuration information. Spok Mobile application for iOS 4.7 or Android 4.7 (or later) is required for this fix.
• Web security has been enhanced to prevent possible exposure of data when the application queries the database. Spok Mobile application for iOS 4.7 or Android 4.7 (or later) is required for this fix.
• Password complexity requirements are now enforced for all password changes throughout the mobile application.

New Features and Enhancements

• Enabled the hosted service to respect the password complexity guidelines set forth on the customer's Spok Mobile server.

Security Update

• Enhanced security for all saved passwords.

New Features and Enhancements

Corrected Issues

• iPhone users are not receiving their repeat alerts after initial notification.
• Spok Mobile event handling updated to align to Apple's best practices when device notification address changes occur.
• Alerting & Mobile - Spok Mobile Directory is not producing correct results for certain search combinations.

Known Issues

• If a user is assigned to an Oncall group in Smart Suite and a login-logout device group, then their status change on logout will not be reflected on Smart Suite. Their status will still be active.
• If a user with logout enabled is logged into device A, then logs into device B without first logging out of device A, all messages will be delivered only to device B. To resume message delivery to device A, the user must log out of both devices, then log into device A.  Messages are delivered only to the most recently logged in device.
• If a user with logout enabled turns in their shared device without first logging off, the next user to receive that shared device could see messages from the previous user and not receive their own messages. The new user of the shared device should first logoff the previous user, then log in with their own mobile credentials.