Spok Mobile Server Release Notes 4.6.x
Spok Mobile with Pager 4.6 (June 12, 2022)
New Features and Enhancements
-
Migration from Windows 2008 R2 to 2016 and new server hardware infrastructure (upgrade from 4.0 to 4.6)
-
HTTP/2 based support for Apple Push Notification Services (APNs) route to Premise - this moves traffic from Hosted to Premise. Hosted will serve as back-up and this will reduce the load on Hosted.
Corrected Issues
- Some device types received an 'Input string not in the correct format error, resulting in slow message queue processing. This error has been fixed.
- Space-only messages from USMO should return 304: Cannot Accept Message.
- Enabled port 8090 and HTTP.
- Premise Server drops valid message read notification.
- Restrict WSDL access to client registration and client messaging URL
Spok Mobile Hosted 4.6.1 (May 16, 2021)
New Features and Enhancements
- Added change and forgot password enhancements.
Corrected Issues
- Fixed issue where APNs connection error was not logged in the notification table on the hosted database.
Spok Mobile Hosted 4.6.0 (February 21, 2021)
New Features and Enhancements
- Added HTTP/2 based support for Apple Push Notification service (APNs).
Corrected Issues
- Some device types received an 'Input string not in the correct format error, resulting in slow message queue processing. This error has been fixed.
For more information, see Frequently Asked Questions: Spok Mobile Hosted.
Server 4.6.0 (March 2, 2020)
New Features and Enhancements
- Support for mute switch override feature for iOS versions 11 and above.
- Support for Do Not Disturb (DND) override feature for iOS versions 11 and above.
-
- Various security fixes.
Corrected Issues
- The Standalone Registration form related to Messenger did not work in some circumstances.
- If the Principal and Mirror servers changed their roles in the Care Connect installer, the installation would fail.
- If the Mirror option was enabled in the Care Connect installer, Test Connection would return an error and High Availability settings would be lost following the installation.
- When using Spok Console, the first message sent from Spok Mobile to an on-call recipient would always be sent to only the first assigned user in the group.
- When attachments were enabled or disabled in Group Device Settings, Android devices did not reliably receive the updated setting.
- When using Smart Suite with on-call groups and v3fix enabled, on-call groups in Smart Suite would appear as unavailable in mobile search results, even though the groups had assigned on-call users.
- When using Smart Suite with v2fix, more than 25 records were returned by SpokDRS when searching from the mobile application with more than 1 search term.
- An exception would be generated when integrating a host system with projections disabled.
- The "Amcom.AMC.MessageLibrary.SynchRegistration" message type remained in QUEUED Status, even though registrations were being synced and delivered.
- The "ENROUTE" status was not being updated in the Premise Database.
- The "No Response from device" mechanism did not work properly.
- When projections were enabled or disabled, user devices would not receive a push notification, which prevented them from updating their device settings.
- Unexpected Spok Mobile messages were received with the text "The message you replied to is no longer available” even if the user did not reply to a message.
Known Issues
- None.
System Requirements
The hardware and software requirements listed below and in the following links are the only supported hardware and software for Spok Mobile. Spok cannot guarantee that any other hardware and software configuration will work, and Spok is not responsible for supporting any configuration not listed in the requirements.
OS Version |
|
Database Version |
|
For full hardware and operating system requirements for Care Connect 1.9, see the Care Connect 1.9 Hardware Requirements.