Skip to main content

Need Help Using Spok Knowledge? 

Spok

Spok Mobile Release Notes 4.0.x

Spok Mobile 4.0.0 Release Notes (Release Dates: September 2, 2014 (Clients); February 16, 2015 (Server))

New Features and Enhancements

New Product Name

The product that used to be referred to as “Mobile Connect, Powered by Amcom” is now named “Spok Mobile.” This new name is represented in the Google Play store, the Apple Application store, and throughout the Spok Mobile application.

Spok Mobile Public Sphere

A new configuration of the Spok Mobile product was released that allows users who are not connected to a Spok host system to use the Spok Mobile application to send and receive secure, encrypted, HIPAA-compliant messages without being required to register in a Spok host system. After the Spok Mobile Public Sphere product is installed on users’ devices, those users have the ability to contact other users who belong to the public sphere.

The users who elect to use the Spok Mobile Public Sphere version of the product can be invited to join the product or they can manually download and install the application from the Apple App Store (Apple devices) or the Google Play Store (Android devices). 

It’s important to note that users who elect to use the Spok Mobile Public Sphere product will experience limited functionality in comparison to the Enterprise configuration of the Spok Mobile product. For example, Sphere users will not have access to features like status updates. Additionally, Sphere users are limited to sending a message to a maximum of 75 message recipients.

Re-Branded User Interfaces

The Android application, the Apple application, and the web user interfaces were updated to display Spok’s new company name, logo, color scheme, fonts, and images.

Improved Client User Experience

Many updates were made to the user interface to make the product experience usable, efficient, and aesthetically pleasing.

  • Drawer: The menu options are now available in a drawer structure with simplified text and icons to help users find the correct information quickly.
  • Conversation View: The way the application organizes messages was redesigned. The application now organizes messages by conversation instead of by individual message in a message list.
  • Message Inbox: The design of the message inbox (“Messages” screen) has been updated. Now the message inbox displays the message strings that are currently available within the application, organized from the most recent at the top to the oldest messages at the bottom. Additionally, the following additional information displays in the “Messages” screen:
    • Profile picture for the individual to whom you are sending messages
    • Name of the person to whom you are sending messages
    • The time at which the last message was received
    • The number of messages that are included in the message string
    • If the person to whom you are sending messages is a favorite contact
    • A clickable call back number (if the incoming message includes a number)
  • Page Headers: Now when users enter the message thread page for a specific thread, the title for the page changes to reflect the recipient’s name, email address, and/or phone number.
  • Message Response Buttons: The naming and appearance of the buttons were updated and simplified. The buttons now include text without confusing icons.
  • Re-Organized Settings: The labels and organization of the “Settings” screen was updated so users can intuitively find and choose the option that they need.
  • “Recent” Contacts: The label for what were previously referred to as “Favorite” contacts was updated to “Recent” contacts to more accurately describe the feature. The application keeps a record of your 25 most recent contacts that can be chosen by clicking on the “Recent” button. 
  • Unavailable Contacts: Unavailable recipients are now grayed-out to ensure that users do not send messages to individuals or groups that are unavailable.
  • Intuitive Labeling: Throughout the application, the wording of field labels, error messages, and general text throughout were reviewed and updated to straightforward, intuitive text to help users navigate through the application.
  • Removed Redundancies: Redundant text and general information that was previously displayed throughout the application was deleted to simplify the user experience. 

Improved Web User Experience

During the 4.0 release of Spok Mobile, components from various different web interfaces were combined. Because of these additional changes, the web pages now render faster, and menu items are rendered based upon the database and not values built into the software.

  • Menu Structure: The menu options were re-organized, re-named, and consolidated to ensure that the structure is usable and predictable.
  • Removed Print Option: The ability to print various different screens throughout the web interface was removed due to lack of need.

Simplified Application Set Up

The download, install, and register processes for setting up the application were streamlined during the 4.0 release.

     

  • Email Updates: The emails that users receive from Spok are now more detailed and descriptive to help guide users through the downloading, installing, and registering of their devices.
  • File Transfer Service: A service was created that allows users to quickly and easily download the Spok Mobile application from their devices without being required to know which version or build of the software they need. Now, users simply have to click the link that is included in the registration email that they receive from Spok Mobile and their devices automatically download the correct build version for the type of device that is downloading the build.
  • Multi Language Email Support: Support for the French, Italian, German, and Spanish languages are now supported in the email messages that users receive from Spok Mobile. This makes the setup of Spok Mobile devices more accessible for users who prefer communicating in these languages.
  • Welcome Messages: Additionally, after users register their devices, they are sent messages from the Spok Mobile system to give them quick tips and tricks for using the application.

Tenant Management

A concept was introduced during the Spok Mobile 4.0 release that involves managing sets of data in an organizational structure called a “tenant.” A tenant is used as an organizational layer of data between a customer and a site. For example, if the customer “ABC Hospitals,” which has an entire network of hospitals, manages data in two separate data centers for all of its hospital locations, the data centers where the information is stored for all of the sites would be considered a tenant.

A user interface was added into the web portion of the product that allows users to create tenants, add tenants, edit tenants, delete tenants, and apply issued licenses to tenants.

Additionally, an internal user interface is now available for Spok site administrators to create tenants, manage tenants, and generate license blocks in the Hosted environment.

Updated Installers

The installers and installation processes were improved to ensure that users have the ability to install the product as easily as possible.

  • Mobile Services: Because the installer now includes more components, users have the ability to enable or disable the deployment of additional components within the product. Additionally, the installer now gives users the ability to select the drive/path where they would like Spok Mobile to be installed. Window Identity Foundation was also removed from the Spok Mobile installer. Now the required files are added directly into the deployment of the software.
  • Mobile Hosted: A new installer for Hosted configurations of the Spok Mobile product was created.
  • Web: The Web installer now has the following options that users can choose to install as part of the Web installation process: Care Connect (deploys the application tier), Care Connect Services (deploys the service tier), and Care Connect Database (installs the database on SQL Server).

Status Update

Users now have the ability to update their statuses in the Spok Mobile application on their devices from their list of available statuses in the host system. For example, if users have a “Do Not Disturb” status saved for their device in the host system to which they are connected, users can now choose that status on their Spok Mobile client to notify others of their status. This allows users to quickly and easily communicate their availability status to other users with the Spok Mobile client as well as to the host system to which they are configured.

User Profiles

Users now have the ability to update their profile information that is associated with their Spok Mobile application and account. Profile pictures can be added to associate a picture with a user’s profile. Additionally, users can update their first name, last name, and password information after original setup of the application. This information is set up immediately after a device is registered and can be updated at a later time by accessing the “Profile” menu option.

Invites

Users can now invite others to join the application. Within the application, there is now an “Invite” menu option that allows users to enter in the email addresses for the people they would like to sign up for the Spok Mobile application. Please note that this feature is only available to users who are registered to the Public Spheres configuration of the product.

Re-Named Web Interfaces

The two web user interfaces were re-named to the following:

  • Premise Web: “Spok Enterprise Administration”
    • The Spok Enterprise Administration interface allows administrators to manage all of the Spok Mobile devices registered with their tenant. Additionally, support users are able to manage the tenant settings, system settings, Spok Mobile settings, and system integrations.
    • For detailed information on the Spok Enterprise Administration interface, please refer to the “Admin Guide Spok Enterprise Administration” document.
  • Hosted Web: “Spok Hosted Administration”
    • The Spok Hosted Administration interface allows internal Spok administrators to create customers and tenants, manage customers and tenants, and generate license files.
    • For detailed information on the Spok Hosted Administration interface, please refer to the “Admin Guide Hosted Administration” document.

Common API

During the 4.0 release of Spok Mobile, work began on migrating applications to Spok’s common API. The use of a common API will allow for interoperability amongst Spok’s products. Most specifically, migrating to the common API during the Spok Mobile 4.0 release allowed clients to update their status, continue to send attachments (videos and pictures), and perform directory look ups. When looking up message recipients in the directory, a list of the top 25 contacts, groups, and on-call schedules are generated and display in alphabetical order. More specifically, the search results display the following information:

  • Contacts
    • ID (Internal GUID)
    • Type (Contact in this case, used to change an icon on the client)
    • First Name
    • Last Name
    • Department or Departments (Contacts will be in multiple Departments)
    • Forwarding Contact ID (ID that this contact is forwarding all requests to, will be used by MC clients)
  • Groups
    • ID (Internal GUID)
    • Type (Group in this case, used to change an icon on the client)
    • Name
    • Department
  • OnCall
    • ID (Internal GUID)
    • Type (OnCall Schedule in this case, used to change an icon on the client)
    • Name
    • Department

Hosted Web UI Updates

The ability for Spok Administrators to create and manage tenants on hosted was added during the 4.0 release. Administrators can now do the following things in the web component:

  • Create customers
  • Manage customers
  • Create tenants
  • Manage tenants
  • Create new license files
  • Edit existing license files
  • Delete existing license files
  • View expired license files
  • View license count exceeding ordered licenses

Improved Security

During the Spok Mobile 4.0 release, all of the product’s API’s and web pages were secured using the platform security model. Additionally, viral database encryption is now included as part of the 4.0 release.

High Availability Messaging Support

The web service’s framework now supports high availability for sites who cannot allow for downtime in their infrastructure. Now escalation routes within the messaging framework work with multiple other Enterprise and Hosted servers. If one server fails in this situation, another server has the ability to take over for the failed system.

Forgot Password Feature

The “Forgot Password” link and functionality were updated to ensure that users can receive a reminder email with their Spok Mobile password regardless of if they registered with their phone number or email address.

SQL Mirroring Web Support

Support for SQL Mirroring was added to the web component of the product during the 4.0 release. Now the solution can use a secondary server as part of this supported configuration.

In-Product Help

The mobile and web components of the Spok Mobile products now have in-product help information that includes text, screen captures, and videos to help ensure that users can learn the product quickly and easily. When accessing the help information from within the Spok Mobile application, users are directed to a simplified version of the content without screen captures. When viewed in a desktop browser, users are directed to the full help content, including screen captures and videos.

Callback Button Sends “Accepted” Response

Now when users click the “Callback” button on Spok Mobile devices, an “Accepted” response is returned to the sender of the message, indicating that the message receiver has successfully received the message and is responding (by performing a call back) to the message’s content.

End User License Agreement

An End User License Agreement (EULA) was added to the Spok Mobile application to ensure that users of the application know and understand their rights and privileges when using the application. Before users can register their application, they must agree to the terms and conditions outlined in the agreement. If users do not accept the License Agreement, they cannot use the application.

Continued Multi-Site Support

Support for multi-site use within the Spok Mobile application is available in the 4.0 release of the product. This allows users to be registered at more than one site. For example, if Dr. Jones works at three different hospitals that each has its own Spok host system, Dr. Jones can be registered at all three hospitals and have access to the information for each site on her device.

Ability to Control Status Option

The ability for users to control if devices have access to the “Status” feature was added. Now when the feature is disabled for clients, the “Status” feature does not display on the device. When the feature is enabled, the “Status” feature does display.

Provider that Speaks to the Core Database

In order for the Spok Mobile public sphere to function properly, a provider to the Data Repository Service that speaks to the core database and covers all older versions of the Data Repository Service API was created. This ensures that client-initiated messaging works for viral users.

TeleTracking Support

To take advantage of its ability to assist with authentication, querying data, and sending messages, the Spok system continued to maintain its integration with the TeleTracking product.

Authentication Service Configuration User Interface

To simplify the Spok Mobile configuration process, a user interface component was added for some of the configuration options. Now, manual configuration of web.config files is no longer required. More specifically, the following configuration values can now be changed through the simplified user interface:

  • Domain/IP
  • Authentication Service
  • Server Name
  • Message Download URL

Send Message to Groups

Users now have the ability to send messages to previously configured groups of contacts without being required to choose each individual contact when sending messages.

Send Messages to Multiple Destinations

Users now have the ability to send messages to multiple destinations. For example, now users can send information to a mix of contacts, groups, and on-call schedules.

Application Logs No Longer Contain Message Text

To comply with ePHI (Protect Health Information) standards, application logs no longer contain message text. Now, no logs in the Spok Mobile product show or store the text of messages that are sent in the system.

Premise URL with Port 8090 Can Now be Set

The Spok Mobile 4.0 release includes the ability for administrators to set up the Premise URL with port 8090. Now if Spok Mobile is updated for the customer, a checkbox displays for Local Message Delivery. If the Local Message Delivery option is enabled, an input field displays for the enterprise URL and port with the port defaulting to 8091. This URL is sent to the client on GetRegistration requests.

Apple Devices Only Pull Messages from Sites that Initiated Incoming Message(s)

Now Apple devices only pull messages from the site that initiated the incoming message that is being received instead of pulling messages from all available sites. Apple devices only download messages from the URL of the provided Site ID. Additionally, the clients no longer contact the other servers when a push notification is sent.

Interacts with ApnsConnectionPool and Gateway

Spok Mobile Services was updated to now interact with the ApnsConnectionPool and gateway.

Scripts Refactored

The scripts have been refactored to ensure that all schema and global data is properly set up in the database, and the system tenant is populated with all template information needed to create a tenant. This change was required because the concept of a “system tenant” that is a template for creating tenants was updated and the Spok Mobile product needed to be updated as a result.

Apple Device Wi-Fi Only Mode Updates

Apple released a change with a new version of iOS that caused problems for Spok Mobile clients trying to receive messages. The new iOS version automatically turned off the Wi-Fi antenna to conserve battery power, which prevented the Spok Mobile application from receiving messages. A change was made in the Spok Mobile application that ensures that the device running Spok Mobile has persistent Wi-Fi and has the background application refresh enabled. This ensures that the device can maintain connection to a Wi-Fi source.

Adapter Maintains Connectivity

The MXPP connection between the adapter and Spok Mobile Services previously could get lost, preventing the Spok Mobile public sphere users from successfully sending and receiving messages. Changes have been made that now ensure that connectivity is maintained between the adapter and Spok Mobile Services.

Registration and Devices Tables Replaced

The Devices and Registration tables are no longer used with this version of the Spok Mobile product; therefore, the methods that included these tables were replaced.

Asset Upload Directory

Spok administrators now have the ability to select and make changes to the location of the asset directory used to store recordings, images, videos, and the secured asset services in a web user interface.

Sync VDI, LDI, and Registration ID from Registration Table

Spok Mobile users now have the ability to send and receive registration data between the Hosted and Server component for cloud and WiFi-based devices. Registration information is synced from the Server to Hosted as well as from Hosted to the Server by pulling the registration information from the new schema. Additionally, VDI and LDI are now persisted with both registration methods and the VDI, LDI, and RegistrationID are persisted with registration data. This functionality worked in versions 3.5, the functionality was just added to the 4.0 version of the product.

Sending Messages to On-Call Schedules Support Added

Support was added for sending messages to on-call schedules. This allows users to choose an on-call schedule with all of its participants as one contact instead of manually entering each contact into the application.

Support for Host System to Provide Connecting User for Registration

Spok Host Systems can now send a piece of data to the Spok Mobile registration service that links the user and contact of the Host System to the new piece of information provided. As a result, device users are no longer required to enter their directory look-up credentials multiple times when accessing contacts on the device from the host system.

Configuration Setting for Auth/Core Service URL

A configuration setting for Auth/Core Service URLs to be used by Spok Mobile devices was added. Devices with those settings to authenticate against the new service get their profile info, set picture, and status.

Duplicate Customer Name Prevention

The system now prevents Spok administrators from creating customer records with duplicate names. When a duplicate name is entered, the user is notified and is prevented from saving that name.

Entities Report

Administrators now have the ability to generate a report of all entities to which they have rights over. This report lists the departments, entity name, suffix, salutation, aliases, specialties, roles, and profiles for each entity.

“No Status” Update Option

When the server sends a null or empty status to the device, the Spok Mobile clients now display a “No Status” update. This prevents users from trying to change their status when they cannot on their devices.

Application Licensing Updates

After an installation of Spok Mobile, users are automatically directed to a web user interface where they can upload the license file for the site. This ensures that the license file is successfully uploaded before the system can be configured.

SQL Server “AlwaysOn” Support

Support for SQL Server’s AlwaysOn feature is now supported with configurations of Spok Mobile that use SQL Server 2012. This option can be enabled or disabled by adding information to the connection string in the Admin interface. If this feature is enabled, the system utilizes the SQL Server AlwaysOn functionality.

Re-Authentication No Longer Required

Changes were made so users no longer have to authenticate multiple times when using the application. Instead, the system now has the ability to remember the original authentication information.

Configure Assets for CoreService

During the Spok Mobile 4.0 release, support was added for uploading pictures to CoreService.

Globally Unique Site ID

Site IDs are now unique as devices belonging to multiple sites need to be able to identify the different premises using the Site ID.

Upgrade Path from 2.x Defined

When upgrading from version 2.x of Spok Mobile Services to version 4.x of the product, a specific upgrade path must be followed. More specifically, when upgrading from 2.x to 4.x, an upgrade from 2.x to 3.0 must first be performed. Then an upgrade from 3.0 to 4.0 should be performed.

For example, if a customer currently has version 2.3 installed and they would like to upgrade to version 4.0, the customer would be required to follow this defined upgrade path: 2.3 à 3.0 à 4.0.

Tenant Time Zone Setting Update

Updates were made to the application so now when clients are located in a different time zone than where the Spok Mobile server is located, the time displays in the device’s time zone when users receive messages.

For example, if Jack and Mary use the Spok Mobile application in San Francisco, California, and they are registered to a Spok Mobile Server site that is located in Jacksonville, Florida, when a Spok Mobile message is sent in the Jacksonville, Florida, time zone to the clients in San Francisco, California, the time would accurately reflect the San Francisco, California, time zone on the user’s device. Therefore, when Jack and Mary receive Spok Mobile messages on their devices, the time would accurately represent the time zone in which they are located.

Administration Site Includes Three Digits for Client Version

The Spok Mobile web interface now displays the client’s version number--up to three digits. For example, the operating system now includes three numbers (iOS 8.0.1 or Android 4.4.2), and the version of the Spok Mobile application that the user currently has installed also displays three digits (Spok Mobile 4.0.1).

New Installer Dialog Added

A new installer dialog was added to the Spok Mobile Services installer that provides the user with a list of things that are needed by the installer. This helps users identify what needs to be available to the installer before a successful installation can be performed. It is important to note that before users can proceed to the next dialog in the installer, they must acknowledge that they have verified the information by enabling the “I have verified the above information” option in the dialog. An example of the dialog is included below.

Fixed Broken References Due to Microsoft Security Update MS14-059

References to System.Web.Mvc.dll that were caused by a Microsoft Security Update (MS140059) were fixed during this release.

Updated Dates

During this release, all references to the year “2014” were updated to “2015” to better reflect when the software was released.

iOS 8 Layout Issues Fixed

For this release of Spok Mobile, the product was updated to use the latest version of the SDK files for the Apple/iOS clients. This update fixes existing layout issues that were being caused by the product using an older SDK file.

Pingdom Check Added

To improve the ability for Spok’s resources to monitor and maintain the Spok Mobile Spheres environment, Pingdom checks for the Spheres environment were added to ensure that it is running at all times. Pingdom checks provide information on the uptime, downtime, and performance of websites.

Email Updates

Additional changes were made to the emails that users receive from Spok Mobile. In most cases, these emails provide assistance to users during the installation, registration, and overall setup and continued use of the product. The changes that were made to the email text were in response to feedback that indicated that the text could be confusing to some users.  

Changed Update Registration Logic

A change was made to the product’s registration logic that now ensures that when users update their registrations, all records for this registration are updated both in the Hosted and Services environments.

Phantom Row Issue Update

In past versions of the product, phantom rows were being left in the HostSession table. An update was made to the product that now prevents this from happening.

Default Email Address for Hosted Admin User Updated

To help ensure that the information is being sent to the correct people, the default email address that is associated with the system default user account has been updated. Now the default email address for the Hosted administration user account is the following: hosted.monitoring@spok.com. Now when users click the “Forgot Password?” link in the web user interface, the newly configured email address is notified.

Customer Name Added to GetStatistics Command

The http://localhost:9999/GetStatistics link now also includes the customer name. The name of the customer to which a tenant belongs is displayed in a separate column. In the past, it showed the Server ID, Site ID version, and heartbeat. As a result of this change, a quick check can now be performed on a customer instead of being required to log into the database to see if a customer is connected and manually figuring out their Site ID.

Users Do Not have to Re-Register Existing Registrations when Projections Become Enabled

Now when users upgrade their clients to a version that supports projections, those users do not have to re-register their devices to be able to use those features. Instead, the updates are automatically pushed to the device and become available to users without requiring users to re-register the application on their device.

Failover Partners Set Up

As part of this release, failover partners were set up in the Spheres Product and Hosted Production environment.

Corrected Issues

  • US29366: File upload failures
  • US29267: Mobile Enablement Data Connector plugin not changing status
  • US28773: Picture interface not working when page all devices enabled
  • US31121: MXPP process freezes on both web servers
  • US30406: Cannot send emails to devices
  • US29236: CoreGatewayWorker locks up and will not process MXPP handshake requests
  • US28755: Message group security issue
  • US29024: Application crashes when opening on single iPhone
  • US30253: Outage due to page server crashing
  • US29714: iPhone call back cancel button not working
  • US29631: Cisco 792x application does not follow phone device audio settings
  • US29889: Directory Authentication username and password fields should be configurable to numeric for customers who only have numeric user IDs
  • US29737: Pre Populate registration phone number field
  • US32373: Application crashing and not receiving messages after period of not being used
  • US33422: Review log entries related to not finding Spok Mobile device generated by MessageManager
  • US33481: Investigate and address issue related to completed handshake in Hosted environment
  • US33479: Address Message Manager queue build up report as part of hosted outage in Hosted environment
  • US33124: Investigate logs and find a solution to issue of registration ID not found
  • US33539: Fix issue of customers being unable to register a device in their test environment using the same information
  • US33804: Research Hosted Message Broker logs in response to noticing some errors in the Hosted Message Broker’s production logs
  • US33619: Review logs for Core2Core alarms generated with different logging info
  • DE15720: When client version before 3.2 is upgraded to latest version, its old settings are saved and not those of the group
  • DE15907: When starting to install via .exe file, the installation fails
  • DE15918: Core message service overloading system CPU
  • DE15960: Customer and employees have reported registration issues when upgrading their client to 4.0
  • DE15985: Pingdom check on Hosted is generating alarms on Core2Core handshake against port 2001
  • DE16084: Registrations fails with no registrations downloaded error message on IDESK
  • DE16086: The user cannot see the Device Type details in the premise
  • DE16103: All email templates should use Site Name and not Site ID when referencing Site in the content
  • DE16107: Specific errors with registration (FK Constraint on Update)
  • DE16109: The “Settings” screen is not working when the user registers with a 3.5 client with premise v.4.0.1.1187
  • DE16152: Apple devices stop receiving push notifications when message is sent to a device with “Amc.AppStore.Sandbox” APNS Connection Pool
  • DE16183: Messages are not received for newly added registrations for BlackBerry clients (US32800: Push notifications to BlackBerry devices not working)
  • DE16194: Registration is re-added on Hosted under specific conditions (US32809: Spok Mobile re-sending/keeping deleted registrations)
  • DE16196: Deadlocks sometimes occur when executing AmcSqlServerQueue.NextInQueue
  • DE16197: OptimisticConcurrency exceptions sometimes occur in UpdateRegistration and UpdateNotificationAddress
  • DE16232: The user is unable to register after unregistering if the web username for a registration in a Host System with projections is changed
  • DE16235: User that is upgrading to client 4.0 should have ability to set status and manage profiles (When viral registration is confirmed, the profile of the user is empty)
  • DE16251: User that is upgrading to client 4.0 should have ability to set status and manage profiles (When the user re-registers couple of times, the registration fails)
  • DE16260: The user is unable to re-register after he successfully registers the first time
  • DE16197: OptimisticConcurrency exceptions sometimes occur in UpdateRegistration and UpdateNotificationAddress
  • DE16232: The user is unable to register after unregistering, if he changes the web username for a registration in a Host System with projections
  • DE16235: User that is upgrading to client 4.0 should have ability to set status and manage profiles (When viral registration is confirmed, the profile of the user is empty)
  • DE16251: User that is upgrading to client 4.0 should have ability to set status and manage profiles (When the user re-registers couple of times, the registration fails)
  • DE16260: The user is unable to re-register after he successfully registers the first time
  • DE16298: User that is upgrading to client 4.0 should have ability to set status and manage profiles (When the projections are enabled/disables, the device cannot get its command)
  • DE16300: User that is upgrading to client 4.0 should have ability to set status and manage profiles (The user is unable to confirm his registration on Spheres)
  • DE16328: Update Registration is not synced properly to Hosted when MCS is version between 3.5.0 and 4.0
  • DE16336: User that is upgrading to client 4.0 should have ability to set status and manage profiles (After enabling/disabling projections multiple times, the devices are not affected by the change anymore)
  • DE16353: User that is upgrading to client 4.0 should have ability to set status and manage profiles (“Status” and “Profile” are not visible on Smart Suite)
  • DE16357: User that is upgrading to client 4.0 should have ability to set status and manage profiles (Only limited number of devices receives push notifications)
  • DE16366: Updated registration becomes Active without confirmation on the device (MCS 3.5.6, Hosted 4.0)
  • DE16382: Unable to add registration when re-adding same user in host system with projections
  • DE16401: The user is unable to register on a Cisco device if the account is on the latest version of MCS/MCH
  • DE16417: User that is upgrading to client 4.0 should have ability to set status and manage profiles (A registration error appears when the user tries to registered on iOS device)
  • DE16429: When projections are turned on/off, multiple sync registrations are triggered in enterprise server for one and the same registration
  • DE16439: The hosted installer installs enterprise server instead of hosted server
  • DE16454: Multi site registration with Spheres sync issue
  • DE16500: User that is upgrading to client 4.0 should have ability to set status and manage profiles (When the client is reinstalled, it cannot get their projections on the second registration)
  • DE16511: User that is upgrading to client 4.0 should have ability to set status and manage profiles (The 5 minute cache to be removed)
  • DE16512: When sending projections, there are OptimisticConcurrencyException in registration service
  • DE16525: User that is upgrading to client 4.0 should have ability to set status and manage profiles (When projections are enabled after upgrade of MCS to 4.0, devices do not receive push notifications and cannot see the projections (Smart Suite))
  • DE16528: User that is upgrading to client 4.0 should have ability to set status and manage profiles (When a new user is registered, there is error in core service due to multiple rows in with the same extuserid)
  • DE16537: Need to handle synching of change to LocalDeviceID for registrations completed prior to upgrade to 4.0 (Duplicate registrations appear in MCS database after certain conditions)
  • DE16538: (SelfRegistration Form) After Hosted upgrade SelfRegistration form cannot be open
  • DE16540: User that is upgrading to client 4.0 should have ability to set status and manage profiles (When projections are enabled and host system is SS, Android clients cannot change statuses and update profiles)
  • DE16543: (Configuration Service) There are exceptions in configuration service which are caused by specific registrations
  • DE16544: Change in LocalDeviceID should also expire current 4.0 authentication on the device to insure accurate SENDER (When LDI is changed authentication do not expire)
  • DE16585: When Android registration is confirmed on iOS device (and vice versa), this device does not receive pushes
  • DE16592: Messages are not sent to the correct device after the change of LocalDeviceID
  • DE16609: User that is upgrading to client 4.0 should have ability to set status and manage profiles (Error sending projections when HTTPS is enabled, wrong port is used)
  • DE16612: After upgrade from 3.5 to 4.0, upload license page is not loaded
  • DE16621: Changing LocalDeviceID from SS should be handled correctly when projections are enabled (When LDI is changed, push is not sent to the device)
  • DE16635: User that is upgrading to client 4.0 should have ability to set status and manage profiles (SiteID can be changed for a host system with projections)
  • DE16636: Amcom user does not have the right privileges for AmcAmcomPremiseCore db after upgrade to 4.0
  • DE16644: Using iPhone sender of the message receives multiple New Command push notifications
  • DE16652: Unregistered users can still send messages
  • DE16662: “Server.PortNumber” and “Server.Scheme” values (AmcomMeta database) should be migrated after upgrade from 3.5
  • DE16665: Unregistered users can still send messages
  • DE16683: When registration is re-confirmed on another device, changes are not synced from Hosted to Premise
  • DE16696: When messages is received and answered statuses are not returned back - messages stay with status “ENROUTE” in the database
  • DE16731: A deadlock exception occurs when the next item from the Queue Table cannot be retrieved
  • DE16734: Insert a new page that provides user with list of information needed by installer (4.0 installer) - The user is not navigated back to the new text
  • DE16739: MessageBroker: The iOS device does not receive pushes when the connection pool is Sandbox
  • DE16740: Not able to send messages through WCTP to Cisco devices
  • DE16744: Cosmetic issues on the information page
  • DE16747: If no connection with WCTP service, messages fail to be added to the MxppToWctp queue
  • DE16748: Calling “Wipe API” does not work, “Schema specified is not valid”
  • DE16759: When new host system is added in Integrations after upgrade to 4.0, Host Projections change is triggered and 4.0 devices receive pushes when projection value is not changed
  • DE16761: The user is unable to add attachments on NHQA1
  • DE16763: The installer does not clear the default path of the file services and database server

Spok Mobile 4.0.1 Release Notes (Release Date: September 9, 2014)

New Features and Enhancements

Successful Multi-Site Registrations When One Site’s Registration Fails

Users are now allowed to register successfully with multi-site registrations even when some of the site’s registrations fail. In previous versions, the client ignores the failing site and the user is able to register. This means that if the client later receives any commands or messages from this failing site upon re-registration, the client ignores all the commands and messages.

Corrected Issues

  • DE15903: On Android, the status in the drawer is empty
  • US32568: On Android, allow the user to register successfully with multi-site registration even when some of the sites’ registrations fail

Spok Mobile 4.0.2 Release Notes (Release Date: September 9, 2014)

Corrected Issues

  • DE15942: iPhone action sheets not visible on iPad on iOS 8
  • DE15955: On iOS, the buttons in the attachments pop-up have incorrect highlight and text color
  • DE15953: On iOS, the pop-up for the attachments remains floating in the middle of the screen if the user hides the keyboard
  • US32556: On iOS, change the text color in the chat bubbles to black
  • US32567: On iOS, allow the user to register successfully with multi-site registration even when some of the sites' registrations fail

Spok Mobile 4.0.3 Release Notes (Release Date: October 7, 2014)

New Features and Enhancements

Chat Bubble Text Color Updated

In the Spok Mobile clients, the text in the chat bubbles was changed to black for better readability.

Client Version Information in Web Client Updated

The version information that is available for each client in the product’s web interface now displays more detailed version information. For example, only the major and minor release versions for each client were provided in the past (Example: x.x or 4.0). Now, the major, minor, and maintenance release versions for each client are provided (Example: x.x.x or 4.0.3).

Additionally, the device operating system version information is now included in the web interface. For example, if the device is running iOS 8.0.2, that information displays. Please note that this update is only available when both the server and the client(s) have been updated.

Android Contact Search Updated

The Android client now returns search results after two characters are entered into the “Search” field in the “Messages” screen. For example, if a user enters “Katie” into the search field, the application now begins returning search results after just the first two letters (“Ka”) are entered. Please note that the search is not initiated until at least two characters are entered into the field.

Link Color on iOS Updated

The contrast between the color that is used for links within Spok Mobile messages and the background color was increased, improving the readability of information that is presented as links within the message text. 

Re-Positioned Message Response Options

The message response button options (“Accept,” “Decline,” “Call Back”) were re-positioned to be farther apart so users are less likely to accidentally click the wrong button. 

Corrected Issues

  • DE15953: On iOS, the pop-up for the attachments remains floating in the middle of the screen if the user hides the keyboard
  • DE15960: (Server) Registration issues when upgrading client to 4.0
  • DE15981: On iOS, a crash was reported, investigated, and fixed
  • DE15982: On Android, messages are not displayed after upgrade
  • DE16076: On Android devices with multi-site configurations, messages from sites below version 4.0 are not seen after upgrades
  • DE15672: On Android, in some cases messages in the “Messages” screen are not displayed
  • DE15972: On iOS, messages containing numbers are not displayed initially in the “Messages” screen
  • DE14262: On Android, there is a site name cosmetic issue in the drawer
  • DE16086: (Server) The user cannot see the Device Type details in the premise
  • DE16109: (Server) The “Settings” screen is not working when the user registers with a 3.5 client with premise v.4.0.1.1187
  • DE16046: The clients do not receive push notifications or messages after application update
  • DE16078: On Android, application crashed when the user opened the application after certain periods of time (random crash)
  • DE15985: (Server) Pingdom check on Hosted is generating alarms on Core2Core handshake against port 2001
  • DE16107: (Server) Specific errors with their registration (foreign key constraint related to device type)
  • DE15993: On iOS, the text suggestions bar overlaps the text box in the “Compose” screen
  • DE16119: Devices do not receive push notifications or messages after updating application on device (Note: As a result of this defect, if Android and iOS 8 users are not re-registered after an upgrade, they can see new incoming messages. In this case, iOS 6 and 7 users only receive the push notification but cannot see the message before re-registering.)
  • DE16104: On Android, some combinations of numbers are not being parsed correctly
  • DE15444: On iOS, only part of the message is showing if the message is longer on the “New Message” screen
  • DE15925: On Android, the state of the application is being reset after the user changes the device orientation on the “Help” and “Spread the Word” screens
  • DE15836: On Android, the text under the navigation bar in a few screens is too close to the edge of the screen
  • DE15835: On Android, there are low resolution icons in a few screens of the application
  • DE16144: On iOS, the message bubble is not visible when it contains only “123” or “1234” on iOS 8
  • DE16152: On Apple, devices stop receiving push notifications when messages are sent to a device with “Amc.AppStore.Sandbox” APNS Connection Pool

Spok Mobile 4.0.4 Release Notes (Release Date: February 16, 2015)

New Features and Enhancements

BlackBerry 10 Support

The Spok Mobile application can be used on BlackBerry 10 devices. The Spok Mobile BlackBerry 10 application functions in the same way as the Spok Mobile Android application, with the exception of where the application is downloaded from.

Application Access Code Delay

The Spok Mobile application now gives users the ability to extend the amount of time that the application waits before locking the application and requiring an access code to re-open the application. More specifically, you can set the application to only lock and require an access code entry to re-enter the application after 10 minutes, 20 minutes, or 30 minutes. For example, if your device has an access code set and you set the “Access Code Delay” feature to “10 minutes,” you can exit the Spok Mobile application and perform activities outside of the application on your smartphone for up to 10 minutes before the application requires you to enter an access code to re-gain access to the application. If you re-open the application within 10 minutes, you would not have to enter an access code for the application to open.

Message Priority Indication

When a message priority is set for Spok Mobile messages that are received, an icon now displays to indicate what level of priority is assigned to the message. For example, “high priority” and “low priority” messages are marked with the following icons:

     

Increased Font Size

To improve the overall readability of the text that displays in the application, the standard font size that is used throughout the application was increased.

Updated Callback Numbers and Extensions

Updates were made to the Spok Mobile Android and iOS application’s callback number and extension functionality. Now when the Spok Mobile client application receives incoming messages with call back numbers and extensions, the application has the ability to successfully initiate a call with additional number formats than were previously supported.

iOS 8.1 Verification

Apple’s iOS version 8.1 was tested and was proven to work with this version of the Spok Mobile product during this release cycle. Users can now use the Spok Mobile application in iOS 8.1 environments on their devices.  

Spectralink Pivot with Google Push Notification Support

The Spok Mobile application can now be used on Spectralink Pivot 8700 devices. This is supported on Spok Mobile versions 3.5.8 and 4.0+. On the Spectralink Pivot 8700 device, the Spok Mobile Android application is used and functions the same way on the Spectralink phone as it does on Android devices. It is important to note that when Spok Mobile is used on Spectralink Pivot devices, the devices must be connected through a Spectralink certified access point. For detailed information on how to set up and establish a Spectralink certified access point, please refer to Spectralink’s technical documentation. More specifically, these documents can be helpful:

Support for HTML Links in Messages

Support for HTML in Spok Mobile message was added. Now when Spok Mobile messages with links are sent or received in the application, users can click on links to access an HTML site.

Dial Back Number Font Color Updates

During this release, the color that is used to indicate a clickable call back number was updated to a color that has a greater contrast with the background on which is displays. Additionally, the number is now underlined and displays in a bold font to further improve the overall readability of the value.

Updated Chat Bubble Text

To improve the readability of the text that displays in the chat bubbles for incoming messages, the font was updated to now display in black. This ensures that users can easily read all of the available text in outgoing and incoming Spok Mobile messages.

Sign Up Button Clarification Added

To decrease confusion with the “Sign Up” button that some users were experiencing, additional clarification text was added above the button. This text indicates that users should click the “Sign Up” button to try the free version of the application, called Spok Mobile Spheres. The “Sign Up” button should not be used by users who have an existing registration in a system.

End User License Agreement (EULA) Link Updates

The link to the end user license agreement (EULA) that was originally included in the Spok Mobile application was updated to ensure that the link directs users to the most up-to-date, correct version of the agreement.

Users Prevented from Copying Received Message Attachments

As an added security feature, the Spok Mobile application now prevents users from being able to copy message attachments outside of the application. This prevents users from copying private, secure message pictures and videos from the Spok Mobile application into other media for distribution.

More Detail Provided in Notifications

Now when users receive a “New Command” push on their devices, they are provided with additional information on what type of command they are receiving. For example, instead of receiving a “New Command” notification, users could now receive a “Feature Update” command. This provides users with additional information on the type of information that they are receiving to prevent confusion.

Android Operation System 5.0 Lollipop Support

The Spok Mobile application was tested and was confirmed to work with Android’s version 5.0 operating system (“Lollipop”). Spok Mobile users can successfully use the application in an Android 5.0 environment as expected.

It is important to note that when users who are using multi-user support have the Spok Mobile application installed on multiple devices, they should have the same Spok Mobile application version installed on all of their devices. If the same version is not installed on all of the user’s devices, issues may be experienced.

Directory Search Functionality Updated

Now when users search in the directory, the search is initiated and search results are returned after the second character is entered. The new search functionality display list populates with names based on characters typed in alphabetical order beginning with the first name. More specifically, if no letters match the first name, then the search moves onto the last name. Additionally, if no letters match the first or last name, then the search moves onto the department or email (if that information is available).

Further, the list of search results should always display in alphabetical order. Lastly, searches should never return results where the two letters typed are in the middle of the name. For example, if a user enters “on” into the field, the application would not return “Jack Jones” because there is an “on” in the middle of the name.

Error Message Updates

Updates to error messages were made to the application. Every time there is a change on the server side of the product, the device receives a “Get Registrations” command. A server change can be a disabled site, change in settings (like audible tones), enabled/disabled services, etc. If the device gets out of internet coverage, this update may fail and the user needs to be notified. During this release, the text that displays when users receive this command was updated to be more descriptive and intuitive to users.

iOS

Android

The text was also changed in an additional error message. Now instead of saying “Android C2DM registration failed: C2DM registration service is unavailable,” the error message that is returned states the following: “Google Cloud Messaging registration failed. Communication to Google could not be established. Please check your network connections.” This provides users with a clearer idea of what the problem is and how it can be fixed.

Registration Email Updates

The registration emails that the Spok Mobile product sends to users during registration have been updated to prevent confusion. 

Authentication Page Updates

User interface changes were made to the “Authentication” page that displays when users need to authenticate to the contact directory. Now the fields ask users to enter their “Messaging ID/Web Username” and “Password.” Changing the text that is included in these fields offers users more descriptive information on what should be entered into these fields, rather than only providing them with generic description text. They are then asked to click the “Authenticate” button to authenticate to the contact directory.

Corrected Issues

  • DE13026: On Hosted, email flood issue happened due to database access error on AMCS
  • DE13939: On iPhone, when the device receives four messages, the separator is missing for the last one in inbox
  • DE14084: On iPhone, sites get duplicated in UI picker (iOS7)
  • DE14095: When MC database feature is disabled, the installer crashes
  • DE14119: On iPhone, when the settings for the high priority sound are changed, changes are saved for Medium Priority sounds
  • DE14245: Once user with messages is deleted and added again, the messages remain in the message page and the page crashes
  • DE14255: In the iPhone message header, there are cosmetic issues
  • DE14297: When MC is upgraded from 4.0 to next 4.0 version, the configuration URL in app.xml is not updated
  • DE14313: On iPhone, the app crashes when message is received and device's language is different from English
  • DE14341: Installation without deploying database misses the SQL scripts
  • DE14344: When uninstalling services, not all IIS Services folders are deleted
  • DE14394: Validation needs to be added to “Asset Directory Location” field
  • DE14445: Client registration service and worker to use common API (backward compatibility) and exceptions appear when adding registration
  • DE14455: IIS service stopped when platform URL was loaded
  • DE14458: Migrate Customer and CustomerSite to common schema and API (installation fails)
  • DE14498: For the “Asset Upload Directory” field from the configuration web page, if the path exists before upgrade, it should be not changed
  • DE14527: On an upgrade, LumenVox Media Server Services should be set to auto start
  • DE14584: Server error if trying to save first name or last name with space before or after the name
  • DE14585: Special characters in the name are causing errors
  • DE14618: The installer failed within MCS internal upgrade (from 4.0 to 4.0)
  • DE14721: Unable to add registrations through host systems
  • DE14747: When “Email” field is empty, the “Send” button is enabled and two error messages display
  • DE14816: On iPhone, profile photo uploaded by not displayed in directory lookup
  • DE14817: On iPhone, photo uploaded by existing chat view is not updated with profile photo
  • DE14853: The iPhone user cannot be registered
  • DE14872: Messages cannot be received via viral users
  • DE14875: Profile picture file remains open
  • DE14876: When we migrate "Local Core URI" from Customer Site table to "Base Url" in  RegTenant table, Base URL must not be null value
  • DE14879: MCS cannot connect to MCH (MCS is version below 4.0) when the customer is new
  • DE14884: Unable to send messages through WCTP
  • DE14905: On Android, cannot select profile image from gallery or anywhere else on the device
  • DE14937: On Android, EULA needs to be implemented within the MC application
  • DE14949: On iPhone, badge count keeps increasing and doesn't appear to reset
  • DE14964: When message is sent to multiple recipient, sender is only able to answer the last reply
  • DE14976: Failure to load initial web page after new installation
  • DE14978: Installer upgrades
  • DE14988: License upload fails
  • DE14992: Some special characters entered in the fields are causing error on the pages
  • DE15056: ConfirmRegistration failed with business exception (Amcom.Exceptions.BusinessException: AuthCode length cannot exceed 50)
  • DE15070: Host system authentication fails with invalid username/password error message
  • DE15079:  EULAUserTracking table not showing “Date Approved” field
  • DE15125: On iPhone, registration error during sign in, client log shows 401 unauthorized
  • DE15138: On iPhone, unable to authenticate to perform a directory/contact search
  • DE15193: Cannot change the group of the device which is not confirmed
  • DE15207: Options on the Device Group page need to be organized the same order as the clients
  • DE15212: On Android, the “Compose” button disappears sometimes
  • DE15227: On iPhone, when message is delivered, the failed message icon displays
  • DE15240: On iPhone, the ringtone doesn’t sound when outside of the application
  • DE15246: “Templates” field is missing
  • DE15266: Registrations cannot be synced and messages cannot be sent
  • DE15287: When two apps are installed behind load balancer sharing the same database, the user cannot log into the web
  • DE15304: On iPhone, after pre-registration a message is sent to the user which was registered before. When on the home screen, it indicates that it has a new message, but when the application is opened, there is no new message.
  • DE15313: After test meeting SIT08 requirements is executed (login with 1500 users), the console is closed before the user can see the total time
  • DE15330: There are repeating errors in core service (Violation of UNIQUE KEY constraint 'UK_Mapping')
  • DE15365: On Cisco, the application is not responding (stuck on Message screen)
  • DE15368: On Android, when receiving message while on the “Edit Profile” screen, the user is not navigated back to the screen after replying to the message
  • DE15408: System not setting priority arrows
  • DE15422: On iPhone, recent records should be updated when user changes his profile name from host system
  • DE15447: On iOS, the spinner never hides if the drawer is opened
  • DE15451: On iPhone, update profile picture error
  • DE15454: On iOS, app crashed after registration
  • DE15459: Device authentication fails after upgrade from 3.5 to 4.0
  • DE15489: HostSessions table is not cleared properly and sometimes MCS cannot reconnect
  • DE15542: On BlackBerry 10, app froze and did not respond after the callback number is dialed
  • DE15543: On Android, the image is not updated correctly when a message is sent from a host system
  • DE15553: Database encryption not setting to “True”
  • DE15569: On Android, pictures for other registrations do not display
  • DE15577: Incorrect message populated in '[Queue_Amcom.AMC.MessageManager]' blocks processing of the other messages
  • DE15588: On Android, messages from client are not reaching the recipient
  • DE15629: When the license file has multiple sites and is more than 4000 symbols, upload of the license fails and cannot be saved in LicenseKey field in Tenant table (AmcomCore)
  • DE15662: Push notifications are not received after hosted upgrade
  • DE15720: When client version before 3.2 is upgraded to latest version, its old settings are saved and not those of the group
  • DE15729: Cisco device “Compose Message” button does not show up
  • DE15730: On Android, an error message displays when there is a viral registration and an enterprise registration is added to the same device
  • DE15743: Version 3.5 PROD Core2Core and Configuration Service alarms
  • DE15747: On Android, investigate and fix crashes reported (#1) in App Store for 3.5 client in 4.0
  • DE15755: After hosted upgrade, users with 3.5 client cannot attach any image when composing message
  • DE15780: Device confirmation is not synced to enterprise server after registration is confirmed on the device (duplicate SiteID issue)
  • DE15815: On iPhone, when confirming second registration with projection on the device status, profile is disabled from first site
  • DE15844: After upgrading from 3.5 to 4.0, duplicate registrations are seen
  • DE15855: On Android, the user is unable to send a reply to a received message
  • DE15856: On Android, when confirming second registration, sphere sign in page with “First Name,” “Last Name,” and “Password” displays
  • DE15858: On Android, “Authentication” screen keep popping up after valid username and password is entered
  • DE15861: Sometimes attachments cannot be added
  • DE15865: Registration and projection access problems
  • DE15878: On Android, when trying to save a profile picture for IntelliWeb, the site application crashes
  • DE15902: Sometimes after Hosted upgrade, the user cannot log into the Web
  • DE15907: When I start installing via .exe file, the installation fails
  • DE15919: Contact service is throwing exceptions
  • DE15920: Asset Manager service not allowing upload of content
  • DE15946: Registration cannot be completed
  • DE15957: On Android, after upgrading to 4.0 the shortcut of previous version is not upgraded
  • DE15960: Registration issues when upgrading client to 4.0
  • DE15963: Specific errors with their registration (FK Constraint on Insert)
  • DE15968: Android crashes during registration when upgrading from 3.5 to 4.0
  • DE15981: iPhone crash  
  • DE15989: On iOS, the app crashes on iPad Mini iOS 7.0.2 when the user taps the “Attach from gallery” button
  • DE16031: Option to not install the database does not work
  • DE16084: Registrations fails with no registrations downloaded error message on IDESK
  • DE16102: Installer does not prepopulate database settings during installation and defaults to localhost
  • DE16107: Specific errors with their registration (FK Constraint on Update)
  • DE16130: On iOS, there is a small shadow on the messages header  when the user open drawer
  • DE16297: iOS application is not passing the full version number during the registration process
  • DE16429: When projections are turned on/off, multiple sync registrations are triggered in enterprise server for one and the same registration
  • DE16440: On iOS, the device receives a WIPE command while it is on the new message screen, the app continues to ring even though messages is already wiped
  • DE16521: On iOS, when a user updates from an iPhone 5 to a 6+ the application will crash when opened
  • DE16540: When projections are enabled and host system is SS, Android clients cannot change statuses and update profiles
  • DE16592: Messages are not sent to the correct device after the change of LocalDeviceID
  • DE16695: On BlackBerry 10, when the user taps on a button the selection remains visible, and the user is not taken to the next screen
  • DE16716: On Android, when error displays because of failed update of settings and device receives a push, client should respond correct
  • DE16735: On BlackBerry 10, the client doesn't generate a notification address (value 'null')
  • DE16747: If there is no connection with WCTP service, messages fail to be added to the MxppToWctp queue
  • DE16758: On Android, app crashes when closing and re-opening it right away
  • DE16759: When new host system is added in integrations after upgrade to 4.0, Host Projections change is triggered and 4.0 devices receive pushes when projection value is not changed
  • DE16761: Unable to add attachments
  • DE16768: On Android, the “Access Code” screen cannot be closed
  • DE16785: On Android, the application crashes when the user taps on “Message Templates”
     in the “Settings” screen
  • DE16786: On Android, the user is unable to attach files on Nexus 5, Android 5.0
  • DE16789: On Android, the user is requested to enter his access code when he receives a new message while inside the app
  • DE16812: On iOS, after re-registering multiple times, the registration process fails
  • DE16820: Device confirmation is not synced
  • DE16821: Status cannot be changed when the user is missing first name
  • DE16826: When the sync interval is changed to a value that is not allowed, the error message should be changed
  • DE16827: On Android, after the user dials a number through the “callback” option, upon return to the app, the user is required to enter an access code
  • DE16828: On an Android tablet, the user attempts to dial a callback number from the app and it crashes
  • DE16829: On iOS, the health check is not updated after the Wi-Fi is disabled and then enabled
  • DE16836: The settings from the default group are not sent to device
  • DE16837: On Android, the application crashed when opened right after killing it
  • DE16844: For some devices the gateway is set to null in the database and messages cannot be sent from host systems
  • DE16846: On Android, the user is prompted to enter access code when returning to the app after viewing an attachment
  • DE16868: On Android, if the device is rotated on new message screen, it stops ringing
  • DE16869: Old BlackBerry client does not receive push notifications with 4.0 server
  • DE16879: On Android, sometimes the user is unable to register after updating the app from 4.0.3 to 4.0.4
  • DE16880: On Android, the keyboard cannot be triggered if there is an access code after updating from 4.0.3 to 4.0.4 (device specific)
  • DE16884: On iOS, the user receives a command while on the access code screen and after setting it for the first time, he is allowed into the app
  • DE16886: On Android, the “Password” field is not populated when the user updates the app with a multisite registration with viral
  • DE16888: On Android, the authentication is not kept after upgrading from 4.0.3 to 4.0.4
  • DE16899: Exceptions display after registrations are added om MCH and synced with 3.5 server
  • DE16901: On iOS 8, the user updates from 2.3, 3.2, 3.3 with an access code to 4.0.4 and the app crashes
  • DE16922: On Android, if the user has Health Check enabled when updating from 3.5 to 4.0.4, the app crashes when it is opened for the first time
  • DE16923: Incorrect badge number sent to devices
  • DE16925: SmartSuite accounts are being unregistered after updating the client and re-registering
  • DE16931: Optimistic concurrency exception after the status of a user is updated from ACTIVE to ACTIVE
  • DE16948: When installing and upgrading only the database, the installer removes services (both Hosted and Server upgrade)
  • DE16950: Deadlock error in adapter services
  • DE16958: On iOS, the favorite list is not updated with new profile data within more than 30 seconds
  • DE16982: After a setting is changed for iOS registration, the iOS starts re-beeping in 10 seconds and not in the set value
  • DE17141: Installation fails when installing with the bootstrapper
  • DE17190: New message does not pop-up if access code is enabled and settings are received from the admin
  • US34363: When registering an iPad mini with retina display, the messages don't go out

Known Issues

Android
  • DE16275: After the device is locked and the application is open, the app crashes
  • DE15559: Cannot reply to the host system in older message thread in some cases
  • DE15525: The user can upload a “0” size image in “Edit Profile” screen
iOS
  • DE16440: When the device receives a WIPE command while it is on the new message screen, the app continues to ring even though the message is already wiped
  • DE16992: If the user receives a message while on the “Access Code” screen, the message displays above it
  • DE15486: Issues are experienced when receive message while transitioning to a new screen
  • DE15251: On the iOS client, the chat screen has visual issues on the iPad running iOS 7.1.x
  • DE17313: Different multi-site access code requirements are not working properly
BlackBerry 10
  • DE16692: The keyboard does not type anything when the user resumes the app after killing it on the “Access Code” screen
  • DE16693: The user is returned to the “Registration” screen after he is prompted by the administrator to enter an access code
  • DE16695: When the user taps on a button, the selection remains visible and the user is not brought to the next screen
Services
  • DE15927: When MCS is version 2.3, the “Reach Mobile Web Server” health check always displays as “failed”
  • DE16612: After upgrade from 3.5 to 4.0, upload license page is not loaded
  • DE16429: During registration, when projections are turned on/off, multiple sync registrations are triggered in enterprise server for one and the same registration
  • US32613: Automatic failover does not work in 4.0
  • DE16763: On upgrade, service path is not detected by installer
  • DE15927: When MCS is 2.3, “Reach Mobile Web Server” health check is always shown as failed
  • DE16928: MCH configuration page does not update
  • DE16950: Adapter deadlock error in adapter services
  • DE16899: Exceptions display after registrations are added on MCH and synced with 3.5 server
  • DE17141: When the .exe file is started, the installation fails (bootstrapper issue)
  • DE17143: When updating MCS to 3.5.x that is “Local/Hosted” message delivery to the opposite kind causes the version in the app.xml to not be updated
  • DE16282: When user adds a second registration with the same number but different email address, error message is not displayed
  • DE15808: When an SSL certificate is applied, some configurations need to be manually modified
  • DE15834: Showing red field but the error itself is missing on the registration form
  • DE16240: The registration status is not synced in really specific conditions
  • DE16839: Count of registrations in the device group is incorrect
  • DE16198: On the Enterprise Administration’s “Devices” screen, there are inconsistencies between the iOS “Device Settings” screen and the “Devices” page
  • DE16256: When Xtend Suite is configured as the default host system, not all the required data is uncommented in the web.config file
  • DE15460: On the Premise’s “Devices” page, change text of icon from “Enrouted” to “Enroute” when wiping messages
  • DE17375: Adding registrations with a “+” or a “-“ symbols causes issues
  • When the enterprise server is using version 4.0 of Spok Mobile services and a Cisco or BlackBerry Enterprise Server (BES) registration is confirmed on a device that is different than the Cisco or a BES registration, the device does not receive push notifications
  • Mismatched registrations (registering with a different device type than what is being used) causes the incorrect ringtone to sound on the device when a message is received
  • Group statuses are not updated
  • Gateway for iOS registrations is not filled
  • Apple certificates not moved from Notification Service folder to Message Broker folder after upgrade

Spok Mobile 4.0.5 Release Notes (Release Date: April 3, 2015)

Please note that the 4.0.5 Spok Mobile release was not a generally available release. This release was produced and was applied to one specific installation of the Spok Mobile product at one customer site.

Corrected Issues

  • DE17748: A .dll file was provided to one customer site to mitigate a significant performance issue in the status update portion of the Spok Mobile product. After this fix was implemented, status updates now get processed four times faster than they were previously processed.  

Spok Mobile 4.0.6 Release Notes (Release Date: June 22, 2015)

IMPORTANT NOTE: The 4.0.6 version of Spok Mobile requires the latest patch releases of Spok Console and Smart Suite in order for the status information and site location information to function as designed.

New Features and Enhancements

Enterprise Administration Page Now Automatically Re-Directs to New URL

During the 4.0 release of Spok Mobile, the URL format was changed. To ensure that all users are accessing the new URL successfully for their site, users who try to access their Enterprise Administration page by using the old URL format are automatically re-directed to the new URL format for their site.

Further Defined Upgrade Process

The upgrade process when upgrading from version 2.3 of the Spok Mobile product was reviewed, tested, and confirmed. It was confirmed that all sites should now use the following upgrade path: 2.3 à 3.5 à 4.0. For more information, please refer to the Implementation_Guide_Spok_Mobile_Services document.

Corrected Issues

  • DE17864 and DE17436: Fixed an issue with the application starting to initialize without mappings being inserted into a database table when Spok Mobile was used with Spok Console. Additionally, a delay issue that was occurring when Spok Mobile was used with the Device Preference Engine (DPE) and Smart Suite was fixed. To fix these related issues, new user interface elements were added into the “Manage Integrations” screen in the web user interface:
    •  : When this icon displays in the Initialized field, the connection between Spok Mobile Services and the host system being used meets the defined requirements and a successful integration record is established between Spok Mobile Services and the host system and the required database mappings are set up for all registered Spok Mobile users at that site. Additionally, this icon also indicates that the required database mappings for the integration are created.
    •  : When this icon displays in the Initialized field, the connection between Spok Mobile Services and the host system being used meets the defined requirements and a successful integration record is in the process of being established between Spok Mobile Services and the host system. This icon also indicates that the required database mappings for the integration are in the process of being created. When this icon displays, the record cannot be edited or deleted. Additionally, it is important to note that when this icon displays, the Spok Mobile server will experience downtime. This means that basic product functionalities (registrations, messaging, etc.) may not function as designed when the database mapping records are being created and this icon displays.

          More information can be found in the Implementation_Guide_Spok_Mobile_Services document.

  • DE17319: Fixed an issue where some browsers were not supported when users opened the “Welcome to Spok Mobile” email during the registration process.
  • DE17431: Fixed an issue that prevented users from entering the application for the first time when there were too many registrations in the database.
  • DE17489: Fixed an issue where new rows were not created in the database after registering a Cisco device if the account had already been registered on another device.
  • DE17567: Fixed an incorrect URL in the “Implementation Guide Spok Mobile Services” document.
  • DE17575: Fixed an issue that caused a “System out of Memory Exception” error to be generated when an account with over 100 rows in a database table was being synced.
  • DE17577: Fixed an issue that was generating an error when the resend email was being called against the Spok Mobile Server.
  • DE17579: Fixed an issue that was sending a 604 error when a message was sent to a device that was not confirmed in the system.
  • DE17594: Fixed an issue that was causing multiple registrations to display with the same physical device identification number after upgrading if multiple registrations were previously performed on the same device.
  • DE17696: Fixed an issue that was causing Cisco devices to be saved with incorrect notification addresses.
  • DE17697: Fixed an issue where users with an account that had more than 40 rows in a database table were not being cleared on Spok Mobile Hosted or Spok Mobile Services when users unregistered.
  • DE17705: Fixed an issue that was causing problems when synching multiple rows in the database.
  • DE17804: Fixed an issue where synching registration messages caused SQL exceptions to be generated.
  • DE17806: Fixed an issue where some registrations that existed in the system did not have a notification address in the database.
  • DE17813: Fixed an issue where the “Upload License” screen could not be opened after the original installation of the product.
  • DE17814: Fixed an issue that caused a SQL Server deadlock in the Spok Mobile Registration Server.
  • DE17847: Fixed an issue where the logic that processes the message was being executed when a device attempts to get a status for a non-existing message in the system.
  • DE17937: Fixed an issue where unnecessary sync messages were not being sent when more than one registration was confirmed on the same device.
  • DE17981: Fixed an issue where registration records were not being removed from a database table, which prevented registrations from being removed.
  • DE17941: Investigated and fixed an issue that was causing upgrades to fail when upgrading from 3.3.2 to 4.0.5.5 (Upgrade path: 3.3.2 à 3.5 à 4.0.5.5). This was fixed by deleting the “amcom” login and the databases before performing the upgrade.
  • DE18035: Fixed an issue where the passwords that were stored in a database table in DRS were not being encrypted.
  • DE18046: Fixed an issue that was causing push notifications to not be received on iOS devices with version 3.3 and below of the Spok Mobile application.
  • DE18117: Fixed an error that caused the “Reach Spok Mobile Web Server” health check item to fail at sites that had version 2.3 of the Spok Mobile application.
  • DE18212: Fixed an issue that was preventing users from being able to authenticate with lower case user names.
  • DE17928: Fixed an issue that was preventing the user interface from refreshing automatically when the application was successfully initialized.
  • DE16828: Fixed an issue on Android tablets that was causing the application to crash when users attempted to dial a callback number in the application. 

Known Issues

  • When new SSL certificates are applied, the old SSL certificates are not deleted and the Services remain unaffected. The following workaround is available for this issue:
  1. Manually delete the old certificate data.
  2. Manually apply the new certificate.
  3. Restart the Windows services.
  4. Confirm that the new certificates are applied. 

Spok Mobile 4.0.7 Release Notes (Release Date: August 27, 2015)

Corrected Issues

  • DE18964: Fixed an issue that caused users with the “function” listing type in the Smart Suite host system to experience issues because the “function” listing type did not have the ability to support status and site updates on the Spok Mobile client. This caused problems when registering these devices after an upgrade. As part of this fix, the registration and message-sending functionality was fixed for Smart Suite devices with the “function” listing type. Support for status and site updates for users with the “function” listing type in Smart Suite will be added in future releases of the product.
  • DE18538: Fixed an issue where the WCTP delivery notification was not forwarded to the WME if the client’s delivery notification was not received before a read notification or reply message.
  • DE18750: Fixed an issue where the license page failed to open after an installation with an error that stated it cannot connect to the database. As a result of this fix, the bootstrap should now be used to install Spok Mobile.
  • DE18765: Improved Hosted registration logging to now include the date, site ID, and telephone number.
  • DE18638: Fixed an issue where Enterprise upgrades of the Services-only component of the product failed.
  • US35636: Fixed an issue where the host system did not receive acknowledgement responses when users replied to messages.
  • DE18555: Fixed an issue where the Spok Mobile application displayed in Spanish in the Apple Application store and the Google Play store.
  • DE18216: Fixed an issue that caused a Spok Mobile outage. The outage was caused by several database calls that occur every time a device requests its configuration info settings. Several of these calls were asking for data that did not change from one request to another or from one device to another. To prevent future outages, memory caching was added so that the first time calls are requested after the app pool is started, they are retrieved from the database and stored in memory. Any subsequent requests to the service then utilize the cached values and avoid the database lookups.
  • DE18556: References to “USA Mobility” were changed to “Spok Mobile” for messages sent from the Spok Mobile with a Pager Number system. 

Spok Mobile 4.0.8 Release Notes (Release Date: December 8, 2015)

NOTE: In order for this version of Spok Mobile to function with version 5.3.1 of Smart Suite, the DE20667 Smart Suite patch must be applied. This patch can be found in the standard patch location for the 5.3.1 Smart Suite product. 

Corrected Issues

  • US36032: This release includes updates to systems that use Smart Suite integrated with Spok Mobile to support the ability for Spok Mobile clients with the "Function" Smart Suite listing type to update their site and status information. Now, the "Function" listing type behaves in the same way and is treated the same was as the "Person" listing type in the system. It is important to note that Smart Suite versions 5.4.1 and later are required for this functionality to work. Additionally, for instances of Spok Mobile that are integrated with Smart Suite that have registered devices with the “Function” listing type, these devices must be re-registered as part of an upgrade before this fix is effective. There is a tool that can be used that triggers devices to re-register their Spok Mobile application. For more detailed information on this tool, please refer to the "Automated Device Re-registration Process" section in the "Deployment Guide Smart Suite 5.4" or the "Deployment Guide Smart Suite 5.5" documents. 
  • DE17636: Fixed an issue where if the host system unexpectedly lost its connection to Spok Mobile (e.g. due to power outage), it may not reconnect afterwards unless the Spok Mobile services were restarted.
  • DE16996: Two settings were added to the web.config file of the WCTP service to attempt to address the problem where the WCTP service would at some point no longer be able to connect successfully back to USA Mobility’s server with the following error message: “The request timed out.” The settings are:

<add key="ErrorsToUsmoBeforeRestart" value="3"/>

<add key="ErrorTextToUsmoForRestart" value="timed out"/>

These settings tell the WCTP service to automatically restart itself after it fails to connect to USA Mobility's server three consecutive times with an error message containing the text “timed out.” If the settings are missing in the web.config file, add these settings manually under the <appSettings> section. By default, these settings are commented out, which means that the automatic restart of the WCTP service is turned off.

  • DE16839: Fixed an inaccurate number of registrations displaying in the device groups (Admin|Device Groups). It is now based on the count of unique telephone numbers and not the number of registration records.
  • DE19516: Fixed a problem in the upgrade from 4.0.x to 4.0.7 where any personalized user device settings such as ringtone, delivery notification, etc. were lost after the upgrade.
  • US36684: Provided a mechanism to re-register specific client devices by adding a method to ClientRegistration service that accepts a list of telephone numbers to request that they re-register with the server and update their projections status. The method includes the following:

UpdateSiteProjectionsForDevices(string siteId, bool hostProjections,List<string> devicesList)

  • DE20095: Fixed an issue where if one or more devices had multiple mobile client registrations in Spok Mobile 3.5.x, after upgrading Spok Mobile to 4.x they ended up migrated with an incorrect version of the client application.
  • DE20032: The default directory search condition for IntelliSuite has been changed to use the “begin with” option in place of the “contains” to improve the query performance and reduce CPU utilization. To allow using the previous search condition of “contains”, a new setting has been added to the ADRS service (web.config).

<add key="DirectorySearchByContains" value="0" />

This setting goes under the <appSettings console="IS"> section. The default value of 0 indicates the new search condition of “begin with”. Additionally, changing the value to 1 enables the “contains” option in the search query.

  • DE20304: Fixed an issue where registrations failed after a clean install of 4.x and the settings on the Mobile page were changed.
  • DE19223: The DELIVERED status notification will now always be sent to the host system when acknowledging/ignoring/replying to a message and a DELIVERED status has not been received. Previously, this worked only when the "ClientMessaging.GenerateStatusUpdateOnMessageReply” setting was set to True.

Spok Mobile 4.0.9 Release Notes (Release Date: January 6, 2016)

NOTE: In order for this version of Spok Mobile to function with version 5.3.1 of Smart Suite, the DE20667 Smart Suite patch must be applied. This patch can be found in the standard patch location for the 5.3.1 Smart Suite product. 

Corrected Issues

  • DE20133: An issue was fixed where the Core Message Services were using large amounts of CPU. This issue was being caused when there was a socket disconnect and the connection between premise and hosted disconnected, causing an endless loop to execute that was reading 0 bytes endlessly. This caused high CPU utilization. In this release, the product now handles this endless loop by disconnecting gracefully if there are 0 bytes coming in during a socket disconnect.

Spok Mobile 4.0.10 Release Notes (Release Date: March 1, 2016)

NOTE: In order for this version of Spok Mobile to function with version 5.3.1 of Smart Suite, the DE20667 Smart Suite patch must be applied. This patch can be found in the standard patch location for the 5.3.1 Smart Suite product. 

Corrected Issues

  • DE20870: A performance issue related to the contact search query when used with Smart Suite was identified. This query was taking too long to return the search result and caused the contact service to time out. This has been addressed by further optimization of the query.

Spok Mobile 4.0.11 Release Notes (Release Date: May 11, 2016) 

NOTE: In order for this version of Spok Mobile to function with version 5.3.1 of Smart Suite, the DE20667 Smart Suite patch must be applied. This patch can be found in the standard patch location for the 5.3.1 Smart Suite product. 

Corrected Issues

  • DE20338: All 4.x.x released versions were showing as 4.x on the hosted server.
  • DE21351: The Spok Mobile 4.0.10 Installer was pointing to the incorrect MSI Name.
  • DE21504: Resolved a problem with the FAILED DEVICE_TIMEOUT and FAILED USER_TIMEOUT statuses in a multi-server configuration.
  • DE21394: Some users were seeing a generic FAILED error when device/user timeout occurred.
  • DE21571: Spok Mobile Services was not stopping properly.

 

Spok Mobile 4.0.12 Release Notes (Release Date: September 6, 2016) 

NOTE: In order for this version of Spok Mobile to function with version 5.3.1 of Smart Suite, the DE20667 Smart Suite patch must be applied. This patch can be found in the standard patch location for the 5.3.1 Smart Suite product. 

Corrected Issues

  • DE21485: Fixed an issue that caused the alert screen to not pop up following upgrades to 4.2.1. Before the defect fix, when the user opened the app after receiving an alert notification, the message would not appear. The reason for this issue was that the IncomingMessageViewController was not presented for users after the upgrade. Now that the issue is fixed, the alert message will pop up when the user opens the app. 
  • DE19007: Fixed an upgrade issue where the default SQL user account already existing on the server would create a conflict because Spok Mobile should have been using a different SQL user account and/or password.

  • DE21765: Fixed an issue in Spok Mobile where Spok Mobile would not realize that the connection with a Host system was broken so would not accept newer connections from the Host system. This would result in no communication between the two.

  • DE21995: Provided a script to Spok Implementers to allow changing default passwords.

  • DE21431: Fixed a problem where old Asset records could not be automatically removed when there were records with incorrect checksums and/or empty fields.

  • DE21439: Fixed an issue where Asset records with empty DisplayNames  in 3.5 premises were causing a problem with the automatic removal of old Assets in 4.x versions.

  • DE21758: Contact search results in Smart Suite-integrated Spok Mobile environments are now alphabetized.

  • DE22093: Fixed an issue where Spok Mobile Enterprise Administration wouldn't load in the web browser if Spok Mobile was installed in a drive other than the default C: drive.

 

Spok Mobile 4.0.13 Release Notes (Release Date: October 26, 2016) 

NOTE: In order for this version of Spok Mobile to function with version 5.3.1 of Smart Suite, the DE20667 Smart Suite patch must be applied. This patch can be found in the standard patch location for the 5.3.1 Smart Suite product. 

Corrected Issues

  • DE22516: The suffix field in the Spok Mobile database was not long enough to support the suffixes in Smart Center.
  • US39886: Applying a configuration change in the administration interface was causing a time-out.

 

Spok Mobile 4.0.14 Release Notes (Release Date: February 14, 2017) 

NOTE: In order for this version of Spok Mobile to function with version 5.3.1 of Smart Suite, the DE20667 Smart Suite patch must be applied. This patch can be found in the standard patch location for the 5.3.1 Smart Suite product. 

Corrected Issues

  • DE23720: Console/Contact Center users are now prevented from accessing the Spok Mobile Admin page.

  • DE21431: Corrupted data in the Assets table can now be automatically removed if the checksum is incorrect.

  • DE22832: Spok Mobile now starts properly after a Windows restart of the on-premise server.

  • DE22865: The Spok Mobile installer now uses the correct path variable.

Current System Requirements

OS Version

Windows Server 2012 (Standard; 32 or 64 Bit)

Windows Server 2008 R2 SP1 (32 or 64 Bit)

Windows Server 2008 R2 SP2 (32 or 64 Bit)

Windows Server 2008 SP2 (32 or 64 Bit)

Database

Version

SQL Server 2008

SQL Server 2012

Additional

Requirements

Available Space

Microsoft Internet Information Services (IIS) 7

Microsoft .NET 4.0

Configured Microsoft Distributed Transaction Coordinator Settings