Skip to main content
Older versions of Internet Explorer will not support certain site features. Chrome, Safari, Firefox, and Edge will provide the best experience.

Spok Mobile Release Notes 3.3.x

Spok Mobile 3.3.0 Release Notes (Release Date: March 7, 2013)

New Features and Enhancements

Mobile Connect Administration Interface Updates

  • Access Codes
    • Administrators now have the ability to configure access codes in the Mobile Connect Administration page that display on Mobile Connect devices. Therefore, site administrators have the ability to set an access code and require that it is entered on a chosen device by the end user.
  • Templates
    • Device templates can also be configured in the Mobile Connect Administration page. This allows site administrators to set message templates in the Mobile Connect Administration page that become available for use on a chosen device by the end user.
  • Feature-Level Settings
    • Preference settings can now be set for devices by site administrators in the Mobile Connect Administration page. This allows site administrators to control preference settings in the Mobile Connect Administration page that become available on a chosen device by the end user. For example, if a device’s ringtone is set in the Mobile Connect Administration page, that preference setting is automatically set on the device.
  • Device Groups
    • Devices that are managed in the Mobile Connect Administration page can now be assigned to defined device groups. When devices are assigned to a device group in the Mobile Connect Administration page, a standard set of preference settings can now be configured for the chosen devices.
  • Added Remark Field
    • A Remark field was added next to the Client Gateways ports field. This allows you to add text to further clarify the information that is configured in the Client Gateways field.

Chat View

A chat view feature was added to the Android and iPhone platforms during the 3.3 release. This allows device users to view incoming and outgoing Mobile Connect messages in a chat view format. In this view, messages sent by the device owner display on the right-hand side of the screen while messages received on the device display on the left-hand side of the screen. Each messages displays the date, time, if the message was sent or received, and different colored check marks indicating which messages were sent, failed to send, or were received. Even though users now have the ability to view messages in chat view, they still have the ability to view messages in standard list view. This setting is managed in the Preferences screen on the device.

Simplified Registration Form

  • When users choose the Cisco, Android, or Apple options, the Gateway field is automatically populated with the correct value. Further, when the BlackBerry option is chosen, BIS and BES options automatically display, to further define the device type. This prevents users from spending time choosing options from drop down menus when only one option is available; the form now automatically populates the information.
  • Drop down menu options have been combined and simplified. For example, users now only have to choose the Android option, instead of choosing between a GCM and C2DM option.
  • The iPhone option was changed to an Apple option to be more consistent with the other available options.
  • The SMS and SMTP options were removed for Android and BlackBerry device types.
  • The Carrier drop down menu was removed from the form.

Message Priority

Mobile Connect devices now have the ability to display message priorities that are assigned by the sending systems. For example, if a message is sent from a console to a Mobile Connect device, the device now displays if the message was sent as a high, medium, or low priority message.

Message Status Updates

  • The Mobile Connect clients now display message status information after a message is sent. Messages with the following statuses display status information: delivered, failed, acknowledged, or ignored. For example, if a message is sent to another person and the message receiver acknowledges the message, an acknowledgement status update displays.
  • Please note that in the 3.3 version of Mobile Connect, if multiple devices are registered under one user or profile, all devices that are registered under that user or profile are sent message status updates. For example, if a user or profile is created for Josh Miller and multiple devices are assigned to that profile, all devices that are assigned to that profile receive message status updates regardless of which device the message status update applies to.

Improved Server

The reliability, performance, and message throughput was improved for the Mobile Connect server. As a result of these changes, Mobile Connect now has the ability to deploy a server in active/passive clustered environments on Premise and Hosted servers, it has the ability to deploy in an active/active clustered environment on Premise and on a Hosted server, and has the ability to send thousands of messages per minute.

Format Lookup Items

Directory lookup items now display the returned items as one of three different contact types: contact, team, or on call. Now when users search for contacts and contacts are returned on the device, an icon displays next to the contact indicating its device type. For example, if a user searches for a contact that is defined as a contact in the console system, the contact icon displays next to the contact’s name.

Database Script Upgrade

Now, Mobile Connect transitions single row ConfigurationInfo to multi-row ConfigurationInfo for devices that are registered to multiple sites. Additionally, clients are registered to multiple Mobile Connect Services and clients are able to download and update their mobile device configurations independently of each other when registered to multiple Mobile Connect Service sites without exceptions being created. This change allows Mobile Connect 3.2 and 3.3 to use the same 3.3 database, allowing transition from 3.3 to 3.2.

Message Queuing

Messages are now guaranteed to be delivered through Message Broker through the use of persisted queuing.


A new component was added to the Mobile Connect installer that allows Mobile Connect to connect to Care Connect, allowing the sending and receiving of Mobile Connect messages to and from the Care Connect application. This feature is automatically installed with all new versions of Mobile Connect. However, the feature is automatically disabled during installation. To enable this feature, you must configure information in the Mobile Connect Administration page.

Tab Structure

The application interface was reorganized and restructured to display in a tab layout on Apple devices.

Cosmetic Client Changes

  • Android
    • Redesigned Registration screen.
    • Redesigned Login/Authentication screen.
    • Redesign application header.
    • Added menu icons.
    • The Android Market was renamed to Google Play in the Health Check form.
  • Cisco
    • The Close button was removed to prevent end-user confusion.
  • iPhone
    • Redesigned Registration screen.
    • Redesigned Login/Authentication screen.
    • Redesign application header.

Wipe Message Service

Mobile Connect messages can now be deleted through a web service API.

Android GCM Support

Support for Android’s transition from C2DM to CGM is now supported in Mobile Connect.

Detected Apple Silent Settings

Mobile Connect now has the ability to detect if a silent setting is set on an Apple device. This allows the application to vibrate instead of sounding a ringtone when silent mode is enabled on the device.

Altered Android Preferences

Mobile Connect now has its own custom preference activity, removing the reliance on Android’s custom preferences.

Get Messages Pull Down Command

On Android devices, users now have the ability to pull down on the message list to refresh the message list.

Apple Repeat Interval

The settings on Apple devices were altered. Now Apple users have the ability to configure how often a ringtone repeats and the number of repeats.

Call Back Button Updates

When a user presses the Call Back button on the device, an acknowledgement message is sent to the sending system.

Automatic Get Messages Command

On Cisco devices, the Mobile Connect application automatically checks for new messages when the application is first launched or is re-launched.

Communication Requests Delivery

Users who have defined Mobile Connect devices in their communication profiles now have the ability to receive text messages when a voice request or communication request from a web portal is initiated. Now, Mobile Connect is used for delivering the message in these cases.

Time Zone Management Per Site

A time zone control has been added to the Hosted system. Now we have the ability to set the time zone on a per site basis.

Bria Auto Dial

When using SIP dialing with Bria Auto Dial, users now have the ability to press the Call button and have the device perform a call immediately without being required to perform additional steps.

Corrected Issues

Updates were made to address issues that were found in various versions of Mobile Connect. Defects were fixed in the following areas of the product:

  • Registration
  • Hosted
  • Clients
  • Services
    • Mobile Connect Administration Page
  • Messenger
  • Database
  • Data Repository Service
  • Message Broker

Spok Mobile 3.3.3 Release Notes

Corrected Issues

  • Load Balancer Defect: An issue was found involving a Load Balancer configuration that prevented replies from successfully sending. This issue was fixed during this release.
  • Default Tone Defect: An additional issue was found that forced devices to play the incorrect ringtones. This issue was fixed.
  • Fixed Memory Leak

Spok Mobile 3.3.4 Release Notes (Release Date: June 25, 2013)

Corrected Issues

  • US25736: Updated the Amc.AppStore.Production.p12 certificate in the Notification service
  • DE12580: Fixed the rebeep badge count when sending several messages to iPhone while in background
  • US25704: Removed the transaction that can be serialized in UpdateLastNotificationTime
  • US25704: Fixed the deadlock that happened when updating the LastNotification time of a record in AmcHostMessages
  • US24210: Reverted the .pfx file
  • US24210: Fixed many compilation warnings

Spok Mobile 3.3.5 Release Notes (Release Date: October 10, 2014)

Corrected Issues

  • DE15985: BlackBerry and Cisco port and notification address fix
  • US32728: Fixed an issue with the XmlMessagingDaemon not firing properly (disconnect events upon stop)
  • US32576: Updated DAL ServiceFramework_2010 to no longer include the VB Properties files
  • US29932: DOConnect method is fixed
  • US31231: Archive service intermittently fails
  • US31475: Rebranded additional dlls that are shared components. Dll names and code within were unchanged.
  • US31684: Fixed an issue where Procedures were too large for JSON serialization
  • DE15593: Update AdHoc Provisioning Profile for iPhone
  • DE15258: Updated web on-call edit past schedule to allow you to edit a record and set the date into the past. Fixed issue where it wouldn't show the past schedule in the multi-day save select options.
  • US31123, US31124, US31195: Added functionality for DPE. Always send message to DPE device when one is defined, and do not give option to select any other device. Do not allow user to set device preference on personal tab if DPE device exists. In the device edit grid, do not allow a DPE device to be edited.
  • DE14807: Replace \r\n with \n instead of an empty string
  • US28085, DE13916, US28308: Some potentially looping routines are fixed in TCPDataConnector. MobileEnablementDataConnector and TCPDataConnector will create more informative and understandable logs now. Restore original file content.
  • US25372: Fix the date/time conversion issue when the regional setting is anything other than the United States
  • DE14053 (From US28665): (IntelliDesk Archive Service) Message history gets stripped on archive
  • US28673: Added more extensive logging when the MessagingDaemonClient BeginConnection fails and throws AmcomException
  • DE14043: Removed some excessive logging and added some more tracking information for when the logger crashes
  • US28216: Adding Maven clean plugin to parent pom xml file to clean up older build artifacts in the local maven repository
  • US27691: iPhone AMC Select Rebeeps have multiple alerts
  • US27884: Investigate issue with connections to port 2001
  • US18109: iPhone: instead of pulling messages from all sites, it needs to only reach the site that initiated the message
  • DE13659: (IntelliWeb) Web.ini commented out the "EnableViewPermission=true" so that it will be disabled by default
  • DE13631: (IntelliWeb) Fixed type with the word "Deparment" on the security screen and in a couple help file pages
  • DE13553: (IntelliWeb) Modified the OnCall person search forms so that they would order by ln, fn, dept 
  • US27691: Multiple alerts fix in active/active
  • DE13262: The registrations are not synced on AMCS per site and reverted sdc.snk.pfx
  • US26773: Added the Amc.B2BStore.Enterprise.Production.p12 certificate to the solution and the installer
  • US27348: Change Migrate script not to create settings for Volume and Vibrate and in Migrate script update all sound names to title case
  • DE13150: Removed an extremely verbose logging of an array of bytes in MessagingDaemonClient.vb
  • DE12892: Memory leak continues to happen and has resulted in reset (related to US26350 & US26133)
  • US25967: Updated the URLs for amcomqahost2 to be with "devsmm"
  • DE13023: Default tone/rebeep is played even when user has its own preferences
  • DE13029: Memory leak changes. Exception appears in AMCH services.
  • DE13025: Use Host IP and Host port as well when removing customer from HostSession. Removed the old method that used only PremiseIp and PremisePort.
  • US26628: Updated the project file to use the new mobile provisioning profiles
  • DE12812: AMCS sends UPDATED status for registration, instead of ACTIVE
  • US25310: Deploying to B2B store requires ASPNS certificate
  • DE3143: Premise core stop/start does not properly stop and start

Spok Mobile 3.3.6 Release Notes (November 4, 2014)

Corrected Issues

  • US33384: USMO Push notifications are not working
  • US33290: MC Select Errors received through WCTP interface
  • US33359: Sending an empty or space-only alphanumeric message to the WCTP interface results in “Object not set to an instance of an object” error

Spok Mobile 3.3.7 Release Notes (Release Date: February 3, 2015)

Corrected Issues

  • US34341: When registering an iPad Mini with retina display, the messages do not go out in Premise version 3.3