Table 13-1: Mandatory User Configuration ............................................................................................ 37
Table 15-1: All cX-UM Configuration Parameters .................................................................................. 43
Installation Manual 6 Document #: LTRT-40732
Installation Manual Notices
Notice
Information contained in this document is believed to be accurate and reliable at the time of
printing. However, due to ongoing product improvements and revisions, AudioCodes cannot
guarantee accuracy of printed material after the Date Published nor can it accept responsibility
for errors or omissions. Updates to this document can be downloaded from
This document is subject to change without notice.
Date Published: July-15-2020
WEEE EU Directive
Pursuant to the WEEE EU Directive, electronic and electrical waste must not be disposed of
with unsorted waste. Please contact your local recycling authority for disposal of this product.
Customer Support
Customer technical support and services are provided by AudioCodes or by an authorized
AudioCodes Service Partner. For more information on how to buy technical support for
AudioCodes products and for contact information, please visit our Web site at
Each abbreviation, unless widely used, is spelled out in full when first used.
Version 0.1.4 7 cX-UM Connector
cX-UM Connector
Related Documentation
Document Name
Document Revision Record
LTRT Description
40732 Initial document release for Version 0.1.4
Documentation Feedback
AudioCodes continually strives to produce high quality documentation. If you have any
comments (suggestions or errors) regarding this document, please fill out the
Documentation Feedback form on our Web site at
Pay attention to download the cX-UM platform version (SfB Online/Teams)
Unzip the file to a temporary directory.
Installation Manual 8 Document #: LTRT-40732
Installation Manual 1. Introduction
1 Introduction
Office 365™ Microsoft Exchange Online Unified Messaging (UM) has reached End-ofSupport as of February 28, 2020.
cX-UM (Cloud X-UM) provides MWI notifications for Cloud VoiceMails. The application is
useful for users using non-MS telephony systems (e.g. Cisco), and at the same time using
Microsoft Cloud Voicemail as their voicemail systems. These users can use cX-UM to receive
standard SIP MWI notifications for any change in their voicemail status (new voicemail
deposited, voicemail read or voicemail deleted).
To allow telephony (PBX) equipment to communicate securely with the Office 365 network,
customers are required to deploy AudioCodes' Mediant Session Border Controllers (SBCs)
with CCE for SfB Online or SBCs with Direct Routing for Teams Users.
This document details the installation procedure for cX-UM Connector as a standalone
server. For Skype for Business 2015 and Skype for Business 2019 for X-UM Standard
based on CloudBond Standard Plus, refer to LTRT-26791 AudioCodes X-UM
Configuration Ver.0.1) or for X-UM Connector Installation, refer to LTRT-40729 AudioCodes
X-UM Standard Installation Ver. 0.1.
Note: This document describes MWI notifications for Cloud VoiceMails; however, it does
not describe Microsoft Direct Routing functionality which is handled by AudioCodes SBC
devices.
Version 0.1.4 9 cX-UM Connector
cX-UM Connector
This page is intentionally left blank.
Installation Manual 10 Document #: LTRT-40732
Installation Manual 2. cX-UM Data Flow
2 cX-UM Data Flow
This section summarizes the steps for the cX-UM Data Flow:
1. cX-UM uses Graph API change notifications
voicemail folder.
2. The subscription requires a publicly open https webhook, that is called upon a change.
3. Since the cX-UM application is located on the customer premises behind a firewall, and
cannot be reached from outside, a dedicated Azure App Service notification handler is
configured as the notification webhook.
4. Cloud Voicemail sends notifications to the notification handler.
5. The notification handler pushes the notification to an Azure Service Bus queue.
6. The cX-UM application listens to the Azure Service Bus queue and recieves the
notifications.
7. cX-UM sends a corresponding SIP MWI notification.
to subscribe changes to each user’s
Version 0.1.4 11 cX-UM Connector
cX-UM Connector
This page is intentionally left blank.
Installation Manual 12 Document #: LTRT-40732
Installation Manual 3. Azure Notification Handler App Service and Service Bus
3 Azure Notification Handler App Service
and Service Bus
Graph API change notifications can only be sent to publically open HTTPS servers. Since
the cX-UM application is located on customer premises behind a firewall and cannot be
reached from outside, a dedicated Azure App Service receives the notifications and forwards
them to cX-UM. The notification handler is a very basic application that simply receives the
HTTPS notification and pushes it to an Azure Service Bus queue. Each cX-UM server listens
to a single service bus queue with the hostname of the cX-UM server. The queue is
automatically created by cX-UM upon startup, if required. While there may be multiple cXUM servers per customer, only a single App service is required per customer.The App service
pushes the notification to the correct queue, based on the URL which called it.
For example:
1. cX-UM server1 registers for change notification with webhook:
4. App service pushes the notification to queue ‘server1’ based on URL suffix.
5. cX-UM server1 receives the notification.
Version 0.1.4 13 cX-UM Connector
cX-UM Connector
This page is intentionally left blank.
Installation Manual 14 Document #: LTRT-40732
Installation Manual 4. SIP Interface
4 SIP Interface
cX-UM provides SIP interfaces only for receiving message-waiting indicators (MWI)
notifications. It does not support phone registration and calling. cX-UM provides two
methods for sending MWI:
unsolicited MWI
subscribe-based MWI
Note: cX-UM SIP interface supports TCP transport only. It does not support UDP.
4.1 Unsolicited MWI
cX-UM sends unsolicited MWI for all users who do not subscribe for MWI events. All
unsolicited MWIs for all these users are sent to the same SIP host. See an example for
Unsolicited MWI in Section D.1.
4.1.1 Backup SIP Hosts
cX-UM supports an optional configuration for multiple backup hosts, where notifications are
sent to the first available backup host. Once the primary host is up again, cX-UM resumes
sending the notifications. Availability is determined by periodically sending SIP Options
messages.
4.2 Subscribe-Based MWI
cX-UM supports subscribe-based MWI to which phones subscribe for MWI events. When cXUM needs to send an MWI, it sends it directly to the phone within the subscription session.
See example Subscribe-Based MWI message in Section D.2.
Version 0.1.4 15 cX-UM Connector
cX-UM Connector
This page is intentionally left blank.
Installation Manual 16 Document #: LTRT-40732
Installation Manual 5. cX-UM Connector System Requirements
5 cX-UM Connector System Requirements
The X-UM Connector's minimum requirements are described in the table below:
Table 5-1: cX-UM Connector System Requirements
System Requirements
Operation System Windows 2012 R2/2016 standard
Processor 4 Core
Memory 6 GB
Disk size Minimum 50 Gb. We recommend 80 Gb.
Version 0.1.4 17 cX-UM Connector
Loading...
+ 39 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.