-
null
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the various features of the CMX Engage. This chapter also describes the CMX Engage icons, and pre-requisites to deploy the CMX Engage.
The CMX Engage enables you to do the following:
In the ABC shopping mall, to get free Wi-Fi, the customers must connect to an SSID once they enter the mall. ABC wanted to provide a personalized experience to each customer who connects to the Wi-Fi based on their purchase history and visit frequency. After installing the CMX Engage, ABC could collect the Wi-Fi user’s details through the captive portals, and utilize this details to send notifications to the customers regarding the offers and services available for them. The customers once connected to the Wi-Fi are taken to a captive portal, where they are provided with an option to register themselves by filling details such as name, e-mail address, telephone number, and so on. This information captured is stored in the CMX Engage. When customers re-visit the mall, promotional offers are sent to the customers through push notifications, SMS, or e-mail.
The CMX Engage can also be configured to notify business users such as employees regarding customer activities. For example, You can identify and tag repeat customers as platinum members on the CMX Engage dashboard. When a platinum customer enters a restaurant and their device is detected by a wireless access point or BLE beacon, the restaurant representatives would receive alerts on their devices and can provide personalized services to the customer.
Figure 2-1provides a pictorial representation of how the CMX Engage would be deployed in a location.
Figure 2-1 CMX Engage Deployment Model
The CMX Engage icons are shown in Figure 2-2.
This section describes the port configurations and bandwidth requirements to deploy the CMX Engage.
The CMX Engage is a cloud-based solution and there is no physical installation involved. However, there are certain instances, where the CMX Engage needs to communicate with the CUWN(MSE) and vise versa. You can establish this connection through a public IP or VPN. In addition, you may have to white-list certain CMX EngageIP addresses.
The CUWN must be publicly accessible (For a default CUWN installation, the ports 80 and 443 must be open) for the following scenarios where the CMX Engagecustomer to establish connection to the MSE:
To establish connection between the CMX Engageand CUWN, you must white-list certain CMX EngageIP addresses. To view the IP addresses to white-list, in the CMX Engage dashboard, click the Configuration Instructions link in the SSIDs window.
Note Contact Cisco for establishing a VPN connection.
Note You don’t need to have a publicly resolvable domain name to connect to the CMX Engage.
Certain domains must be white-listed in the customer infrastructure so that the MSE instances deployed with in the customer network must be able to communicate to the CMX Engageanalytical and notification servers. To know the domains to be white-listed, in the CMX Engage, click the Configuration Instructions link in the SSIDs window.
The following table lists the response received for various bandwidth and number of users.
|
|
|
---|---|---|