Meraki Integration

About this Document

The purpose of this document is to display how these various solutions offered by Kloudspot can be integrated with Meraki.

It covers the following Kloudspot solutions that can be integrated.

  • KloudPortal - Wi-Fi Guest Portal
  • KloudCampaign - Campaign management
  • KloudVision- Camera Integration
  • KloudInsights - Event Wi-Fi & BLE receivers

Guest Portal and Campaign Management

Guest Portal

Captive Portals or Guest Portal is a multi-channel platform that enables you to connect and engage with visitors on your premises.

Guest portal screen page allows to create and design a customizable portal from scratch.

A sample of templates will be given as an option to choose to create a portal, layout will be available as a part of the template.

Following are the steps to configure the Guest Portal.

Captive Guest Portal Configuration

The captive portal is designed with following terms that are described below:

  • Social Authentication

Needs authentication using social platforms as Facebook, Twitter, Linked, Google and Instagram.

  • Email Authentication

It will ask the user for their Name and Email address to be able to Authenticate.

  • SMS Authentication

It asks the user for their contact number and authenticate over a SMS.

  • Multi device Token

A token is generated by the admin. User can use this token for authentication. One or multiple devices can be configured to use a single token.

  • Username/Password

A guest user can be created by generating a unique username and password which is used for authentication. One or multiple devices can be configured using individual username/password combination.

  1. Third party

Kloudspot can integrate with various third-party applications such as,

  • ERP
  • PMS
  • POS

  • Enter ‘Wireless’ à ‘Access Control’
  • Choose the SSID to which the Captive portal will be configured.

  • In Network Access, Association requirement, Select ‘Open (no encryption)’.
  • In Network Access, Splash page, Select ‘Click-through’.

  • In Network Access, Captive portal strength, Select ‘Block all access until sign-on is complete’
  • In Network Access, Walled garden ranges, Enter the following domains:
_.kloudspot.com _ .facebook.com _ .facebook.net _ .akamaihd.net _ .fbcdn.net _ .atdmt.com _ .fbsbx.com _. twitter.com \* .twimg.com

Note: You have to separate them only with a space, as shown in the image.

  • In the end Save changes.

  • Enter Wireless, click on ‘Splash page’.
  • Choose the SSID to which the captive portal will be configured.

  • On ‘Splash page’, Custom splash URL, enter the url below;
https://mx01.kloudspot.com/cp/lacomer/index.htm
  • Save changes and Exit.

For more details on how to create template and workflow driven portal, please refer to the relevant Kloudspot documentation.

Campaign Management

Kloudspot has a powerful workflow and policy driven campaign management solution centered mostly around Wi-Fi which offers both online and offline campaigns. These online campaigns can be created and managed using Captive Guest Portals. Creation of Captive guest portals is extremely easy using one of many templates supported by KloudCampaign Editor. KloudCampaign Editor can help guide the user to create a captive portal for the hardware they have deployed on the network.

For more details on how to create Campaigns, resources and configure dynamic policies and workflows, please refer to relevant Kloudspot documentation.

Meraki WiFi and BLE Event Receivers

The Kloudspot Analytics Engine can receive events from many types of Meraki Wi-Fi network.

One or more of event sources can be configured in the ‘Configuration - > System -> System Configuration’ screen.

Validate the Receiver URLs

Most of the receivers below ‘push’ to a specific URL. The protocol (HTTP/HTTPS) used varies depending on the source. We support both HTTP and HTTPS protocols using port 48082 and 48083. Refer to the specific data source below to determine the correct one to use.

If you have set a SSL certificate for the UI, that will be used instead of the self-signed one.

You can check access to both the HTTP and HTTPS urls with a ‘ping’:

Meraki Location Scanning API

To enable, the Meraki scanning API feed, follow the following steps:

  1. First, follow the Meraki Standard instructions in the Meraki manual to set up the Scanning API on each Meraki account.

Location Analytics - Cisco Meraki

https://documentation.meraki.com/MR/Monitoring_and_Reporting/Location_Analytics

When enabling the API, set the following parameters:

  • API Version : 2
  • Post URL : https://{server}:48083/meraki/{name}
  • Secret : for example - kloudspot12345678

For ‘{name}’ use a friendly alphanumeric label for the account.

  • Next go to the Kloudspot Web UI and select ‘Cisco Meraki’ source in the Event Sources.
  • Add an entry for each account (one is enabled by default) by clicking the ‘+’ sign.
  • Enter the ’name’, ‘validation’ and secret’ from above for each account and click ‘Save’.

  • Restart the stream processing job.

Integrating Meraki Cameras

Kloudspot supports integration with both RTSP (MV*2 cameras only) and MV Sense APIs. RTSP video stream from Meraki second generation camera’s can be streamed on-prem to Kloudspot vision controller for complex actionable use cases including Object detection, PPE, Mask, Social distancing, capacity counts and management, demographics, and fingerprinting.

Insights inferred from RTSP stream

For more details on KloudVision __ please check out the KloudVision document.

RTSP Integration

Please refer to Meraki documentation on how to setup Meraki RTSP configuration to stream live video

https://documentation.meraki.com/MV/Advanced_Configuration/External_RTSP

Also refer to Kloudspot documentation on how to setup Meraki RTSP configuration

Add cameras to the controller

MV Sense Integration

Step 1: Port number 6666(TCP) should be exposed to send Meraki camera payloads to the Insights.

Step 2: On UI, go to configurations and click on locations. Add the location (Region/site) where the cameras need to be deployed. Then navigate to the ‘Cameras’ section.

Step 3: Click on the ‘Cameras’, select the floor and the zone to which you want to add the camera and click on ‘add/edit a camera’ and then click on “Add a Camera” as shown in figure below.

Step 4: ‘Add/Update Cameras’ dialogue box needs to be filled with following information.

  • Choose the vendor as ‘Third Party Camera’.

Enter the Unique Id of the Meraki Camera in ‘camera name’ section.

  • Upload the image that is seen by the camera in “PNG” format in the “camera Image” section (Image size less than 2MB).
  • Choose the grid resolution for the camera through the slider (default value is 50px) in the advance settings.
  • Click on ‘Save’ to add the camera.

NOTE: Grid resolution is the resolution of each grid in pixels the image would be divided for heatmap calculations.

Adding widgets which use Meraki payloads to the dashboard

Step 1: On the homepage, navigate to ‘My Dashboards’ and select an existing dashboard or create a new dashboard.

Step 2: On the selected dashboard scroll down to the bottom and click on the ‘+’ symbol to add widgets to the dashboard.

‘Live Movement on a Camera Image’ Widget

Step 1: To add the ‘Live Movement on a Camera Image’ widget navigate to the ‘Camera’ section and select ‘Live Movement on a Camera Image’ widget.

Step 2: Select the location in which the camera is configured through the ‘Settings’ option by clicking on the gear symbol.

Step 3: Select the camera for which you want to see the live movements.

Step 4: Once the camera is selected the live movements of the objects are seen on the camera image in the form of rectangles. User can hover over the rectangle to get more details of the object.

NOTE: User can Zoom in and out using the ‘+’ and ‘-‘symbols respectively.

‘Live user heatmap on floor camera image’ Widget

Step 1: To add the ‘Live User Heatmap On Floor Camera Image’ widget navigate to the ’Maps’ section and select ‘Live User Heatmap On Floor Camera Image’ widget.

Step 2: Select the location in which the camera is configured through the “Settings” option.

Step 3: Select the camera for which you want to see the heatmap.

Step 4: Clicking on the “Live Option” enables the user to view the live heatmap.

Step 5: Clicking on ‘history’, allows the user to view the heatmap for a specific day. The user can choose/pick any day from the date-picker.

Step 6: Clicking on the “Show Hour” checkbox enables the user to view the heatmap data for any hour of the day.

Step 7: A tooltip with the ‘count and dwell time’ can be seen when the user just hovers over the heatmap.

NOTE: User can Zoom in and out using the “+” and “-” symbol, respectively.