The details of Meraki network such as organization, networks, APs and so on will now be fetched to Cisco Spaces using a Meraki Service account. Previously, Meraki customer account was used for fetching Meraki details, and for network synchronization thereafter.

To avail this support, customers using Cisco Meraki network must invite the Meraki service account from their Meraki customer account. You can invite the Meraki Service account using the Organization > Administrators > Add Admin option in the Cisco Meraki dashboard for the filtered Organization. You can contact the Cisco Spaces support team for the e-mail ID of Meraki Service account.

However, to connect Cisco Spaces to Cisco Meraki, you must still use your Meraki customer account. The customer's Meraki account is used for importing the networks into location hierarchy, for which the user has access to. The service account is used for background network synchronization to keep the Location Hierarchy up-to-date.

The OpenRoaming app is now available for the customers who have opted for it.

The OpenRoaming app enables you to allow the mobile users to automatically and seamlessly roam across Wi-Fi and Mobile networks. The Identity Provider (IDP) will identify and authenticate the Wi-Fi users through the integration mechanism defined by the customer, and share the profile details of the users with the Cisco Spaces OpenRoaming platform.

Openroaming supports both Cisco AireOS and Cisco Meraki networks. For both networks, you must use a Cisco Spaces Connector for utilizing this app. To enable OpenRoaming, you must contact the Cisco Spaces support team.

The Open Roaming app provides various reports based on the data it collected. The details such as total number of devices connected to the OpenRoaming enabled network, the internet traffic (data exchange occurred through the network), total number of connections, average visit duration, Unique Devices chart, Devices by IDP, Monthly Internet Traffic (Data Exchange on the network during the particular month), Daily Average Visit Duration, and Data used per Customer (these can be filtered for a specific time duration such as daily, weekly, monthly or a custom duration) are displayed in the report.

The Phone number validation for the Brazil is now enhanced to include area code validation. Phone number with dial code "+55" must be followed by any of the area code for Brazil. Only valid area codes are accepted. For example, +5500xxxxxxx is invalid as 00 is not a valid area code. This validation is applicable for mobile numbers captured anywhere in the captive portal.

In the Data Capture form, the CPF field is now enhanced to convert the value entered in it to the "000.000.000-00" format. The number will be formatted automatically as the user enters the CPF number value. So now the captive portal users do not have to add dots or hyphen manually to maintain the required format.

The captive portal runtime now supports data exchange between the enterprise captive portals and Cisco Spaces. This allows the customers to have their own enterprise captive portal, and store the data it collects with Cisco Spaces. This enables the customer to provide personalized experiences to their end users.