Release Notes for the Cisco Enterprise Mobility Services Platform Release 3.1.6
Introduction to the Enterprise Mobility Services Platform
Managing Internet Provisioning through Captive Portal Rule
Captive Portal Support for Ruckus
Captive Portal Support for Extreme Networks
Custom 404 Page Implementation
E-mail Input Inline Validation
Country Name Derived from Country Codes
This document describes the system requirements, new features, enhancements, and known issues for the Cisco Enterprise Mobility Services Platform. Use this document in conjunction with the documents listed in the “Support” section.
Cisco Enterprise Mobility Services Platform is a mobile-application platform that enables you quickly create and deploy context-aware experiences that engage people on their mobile devices. The cloud-based Enterprise Mobility Services Platform more securely integrates with your existing Cisco mobile network infrastructure. It uses context-aware data, like location and user profile information, to deliver personalized experiences that engage people on their mobile devices.
With this software platform, you can create captive portals or splash pages for guest Internet access and authentication. You can also develop native and web-based mobile apps, or add context-awareness to your existing mobile apps. Organizations can push personalized content to visitors and customers on their mobile devices to create new opportunities for engagement and revenue.
Enterprise Mobility Services Platform helps you:
The platform includes adapters to interface with Cisco Meraki Cloud controllers, the Cisco Connected Mobile Experience, and Cisco wireless LAN controllers. In this way, it more securely integrates with your existing mobile network infrastructure.
This section lists the hardware requirements, operating systems, software requirements, and browsers for the Enterprise Mobility Services Platform.
To control the internet access through access codes, maximum retry limit is introduced for the access codes. You can now define the maximum number of times a customer can access the internet using a particular access code. A new field, No: of times access code can be used, is added to the Access Code window where you can specify the maximum number of times the customer can access the internet through an access code.Only successful internet provisioning with the particular access code will be counted.
In the location hierarchy, you can now configure the time zone for various locations. In the Locations page, a new option, Time Zone, is added to the drop-down list for each location. The default time zone will be GMT + 00:00(UTC). If you are not configuring a time zone for a location, the default time zone is applied for that location.
You can now create portals that are location-specific. In the Portal window for creating portals, the locations will be listed so that you can select the locations for which the portal must be available. A “This portal is available in all locations” check box is also provided so that you can make this portal available for all the locations.
When creating a captive portal rule, a portal will be available for selection only if you select a location that is configured for the portal. However, the portals created using the earlier versions of the WiFi Engage will be available for selection for all the captive portal rules.
To edit the locations for a portal, an Edit Locations button is provided for each portal listed in the Portals page.
The Captive Portal rule is enhanced to manage the internet provisioning to the customers connecting to the SSID configured for the rule.
In the Action area, the following additional options are provided:
When the customers connect to your SSID, you can now provide direct internet access to them, provided an app that is integrated with the EMSP SDK is installed on customer’s device.After internet provisioning the app will be opened in the device. This feature is currently available only for the iOS devices.
When connecting to an SSID from an iOS device, a “I have an App” button will be shown. When a customer, who has an app that is integrated with EMSP SDK installed on the device, click this button, internet is provisioned immediately and the app gets opened in the device.When a customer, who does not have an app that is integrated with EMSP SDK installed on the device, click this button, internet is provisioned for some time, but will get disconnected after detecting that the app is not installed.
A new module “WiFi Engage App Launcher, is added to the WiFi Engage v3 module group in the EMSP Studio to provide the “I have an App” button in the portal. The WiF Engage App Launcher is a custom module.
The EMSP provides captive portal support for the Ruckus network.You can now configure captive portals, and execute the captive portal rules if you are having a Ruckus network.
As of now you cannot do the network configurations from the WiFi Engage dashboard. You have to do it from the back end.
The EMSP provides captive portal support for the wireless network, “External Networks”.You can now configure captive portals, and execute the captive portal rules if you are having the wireless network, “External Networks”.
As of now you cannot do the network configurations from the WiFi Engage dashboard. You have to do it from the back end.
You can now reuse the access code values of the expired access codes. All the access codes that are expired will be listed in the Access Code page under the area “Expired Access codes”, with its access codes values.
When you reuse an expired access code value, in the Expired Access Codes area, the access code value will be renamed as “[access code value]-expired”. For example, if 5463 is an access code value of an expired access code “A”, and if you are allocating this value to an active access code, then in the Expired Access Codes area, for the access code “A”, the access code value will appear as “5463-expired”.
A network in Meraki may have both security appliances and access points. When you are adding a network to the WiFi Engage dashboard or during network synchronization, now a single network name only will be available for selection for this network. When you add that network, both the security appliances and the access points with that network name are imported.
Previously, for networks having both access points and security appliances, same network name used to appear twice, one for access points, and the other for security appliances. You had to add both separately to the WiFi Engage dashboard.
A custom 404 error page is developed to display when the requested page is not found. In the WiFi Engage dashboard, if you are accessing an URL that is not valid or if any error occurs during accessing a page, the custom 404 error page will be shown. Earlier, the default 404 page used to appear in such cases.
The WiFi Engage is enhanced to support the following SMS Gateways from the WiFi Engage dashboard.
In the SMS Gateway tab, a drop-down list “SMS Gateway Type” is added that lists all the preceding SMS gateways.
The SMS gateway you specify here will be available in the following sections:
The following enhancements are made to the Report feature in the WiFi Engage:
The EMSP runtime now supports the Hard SMS and Soft SMS authentication through the following SMS Gateways:
The Inline validation support is added to validate the e-mail ID entered by the customer for ‘Email Authentication’. The inline validation support is also provided for validating the e-mail ID entered in the Data Capture form. Now the e-mail ID validation happens immediately after the customer enters the e-mail ID. Previously, the e-mail ID was validated after clicking the Submit button.
Now when a customer enters the phone number for Hard SMS authentication or in the Data Capture form, the EMSP runtime derives the country names from the country codes specified. The derived country name will be added as business tags in the User Subscriber system.
The support documentation is available at https://emsp.cisco.com