Skip to main content
Click here if you are having trouble viewing this site
Older versions of Internet Explorer will not support certain site features. Chrome, Safari, Firefox, and Edge will provide the best experience.
Resources
Spok

MediCall Integrations: Post-Upgrade Steps

  1. Last updated
  2. Save as PDF
After upgrading Spok Mobile Server to version 4.6 in a Care Connect Suite environment that also includes a MediCall Suite (MediCall console and/or WebXchange) upgrade to version 11.10, there are additional steps to perform to ensure functionality of Profile, Status, and chat-style messaging.

Ensuring Profile and Status Functionality

After upgrading Spok Mobile Server to version 4.6 in a Care Connect Suite environment that also includes a MediCall Suite (MediCall console and/or WebXchange) upgrade to version 11.10, a SQL query must be executed in the Care Connect Suite Core database to ensure mobile users have Profile and Status functionality.

After upgrading MediCall to version 11.10 and Spok Mobile server to version 4.6, on the platform server: 

  1. Execute the following SQL query on the Core database:

UPDATE [Core].[dbo].[Application]

SET [Initialized] = '0'

WHERE NAME = 'Name_of_Integration_Record'

Note: The name of the integration record was specified when adding a MediCall integration during the Care Connect Suite implementation. You can find the name for this implementation on the Spok Enterprise Administration interface.For more information, see Adding a MediCall Integration.

  1. Reset the Core IIS service by resetting IIS on the platform server.

Enabling Chat-Style Messaging for MediCall Suite 

Support for the Mobile Chat Messaging is defined by the following XtendMeConnector configuration parameter:

<add key="Custom_FreeFormatted_MessageType" value="Mobile.Chat"/>

This parameter is in the config file beginning with MediCall 11.10. If you are performing an installation at a site that is upgrading from an earlier version of MediCall, you will either need to add the parameter to the config file or replace the entire config file at the site with the new file.