This guide shows how to configure Cisco Meraki wireless environment to work with Amplespot.

1. Prerequisites

Before you start you need to contact Cisco Meraki and ask to enable following two options for your account:

RADIUS Accounting

We use RADIUS accounting protocol to receive information about your WiFi client's movements throughout your venues. This information is then used to generate a variety of analytics reports.

Open a ticket or give a ring to Meraki support and ask to enable RADIUS accounting for your Meraki dashboard account. Once this option is enabled you will see the RADIUS accounting option under RADIUS for splash page section on the Access control page:

Hostnames support for RADIUS

Cisco Meraki allows only IP addresses and not DNS names as host configuration option for RADIUS for the splash page. While you can still use the IP addresses we recommend using the names as this is a safer option.

Open a ticket or give a ring to Meraki support and ask to enable hostnames as the configuration option for external RADIUS servers.

You will stop getting the error when trying to add DNS name of the RADIUS server as soon as Meraki support fulfills your request.

2. Configuring SSID and Access Controls

Login to your Meraki dashboard, on the left-hand menu bar, click on Wireless and select Access Control

In the drop-down select the SSID you would like to use with Amplespot. You will be able to repeat this process with other SSIDs you may want to use.

Under the Network access, select the Open (no encryption) option.

Under the Splash page, select the the option Sign-on with. In the drop-down menu, select my RADIUS server.

Scroll down and look for RADIUS for splash page. Click on Add a server and enter the following details in the necessary fields:

Host1: see doc
Host2: see doc
Port: 1812

Secret: see doc at: http://docs.amplespot.com/hardware-integrations/amplespot-captive-portal-and-radius-settings

Scroll down to RADIUS accounting. In the drop-down select RADIUS accounting is enabled. Insert the same configuration as for RADIUS for splash page.

Host1: same radius authentication
Host2: same radius authentication
Port: 1813

Scroll further down and look for Failover Policy. Set option "If none of your RADIUS servers are reachable, should clients be allowed to use the network?" to Deny access.

Scroll down to Load balancing policy. Set it to Strict priority order

Scroll further down to Captive portal strength. Set it to Block all access until sign-on is complete.

Scroll further down and look for Walled Garden. Make sure Walled garden is enabled and add the Walled Garden entries to the Walled garden ranges.

The list of domain names in the walled garden ranges shall include: 

(1) Relevant domain names depending on Social Login Options you would like to select in Amplespot Captive Portal(s).

(2) Any website addresses you would like your WiFi Users to be able to access before they completed logging in to your guest WiFi.

(2) Any domain names you might be using to serve external content, CSS styles or fonts for your splash pages.

You can find the most up to date list of Walled Gardens here.

!! IMPORTANT !! Click Save at the bottom right yellow pop up to ensure all your changes have been made.

3. Add Meraki Access Points to your Amplespot Account

We now need to add the MAC addresses of your Meraki access points to you Amplespot account. To do this, click on the Wireless tab on the left-hand menu and select Access Points.

The MAC address of your Access Point(s) will show here:

Copy the MAC addresses (and, optionally names) of your Access Point(s) and head to Amplespot Admin Portal, click on Access Points in the left-hand menu and then on Add new Unmanaged Access Point

Select the Access Point make and model, type in MAC Address and Name, Select the Country and the Captive Portal Zone where you would like to add this Access Point. You will be able to your access point to other Zones later.

!! IMPORTANT!! Make sure that the name of the SSID used by the Captive Portal Zone you are selecting exactly corresponds to the name of the SSID in your Meraki Dashboard.

4. Configure External Splash Page in Meraki Dashboard

Now we need to configure the (guest) SSID in your Meraki Dashboard to use Custom Splash URL. Go to Wireless, then select Splash page

Select the SSID you've been editing in previous section (Access Control)

Scroll down to Custom splash URL and enter

https://cp.amplepsot.com/mrki/<name of your SSID>

The name of SSID shall be inserted URL Encoded. For example, spaces shall be replaced with %20, full stop characters (,) - with %2E.

!! IMPORTANT !! Click Save at the bottom right yellow pop up to ensure all your changes have been made.

5. Summary of Settings

Here is the summary of all Meraki settings described in this article:

Access Control:

Network access; Association requirements:

Open (no encryption)

Splash page:

Sign-on with -> my RADIUS server

RADIUS for splash page:

Primary: 
See this doc - http://docs.amplespot.com/hardware-integrations/amplespot-captive-portal-and-radius-settings

Secondary:
See this doc - http://docs.amplespot.com/hardware-integrations/amplespot-captive-portal-and-radius-settings

RADIUS accounting:

same as radius authentication, port 1813

RADIUS Failover policy:

Deny access

RADUIS Load balancing policy:

Strict priority order

Splash Page

Custom splash URL:

https://cp.amplespot.com/mrki/<SSID name url encoded>

6. Meraki Location Analytics API

Meraki RADIUS Accounting does not provide accurate information about client devices roaming between the Access Points. 

The inter- Access Point roaming information is required in order for Amplespot for analytics and engagement tools to work correctly.

Meraki supplements the luck of RADIUS Accounting information with its Location Analytics API which has to be configured to send data to Amplespot in order for the entire integration to work correctly.

Please follow the steps below in to configure Meraki  Location Analytics API

In your Meraki dashboard, on the left-hand menu bar, select the Network you would like to edit (Amplespot Demo in our case), click on Network-wide and select General

Scroll down to Location and Scanning, in the drop-down set Analytics to Analytics enabled and Scanning API to Scanning API enabled.

Take note of the Validator ID

Next, leave Meraki Dashboard open and head to Amplespot Admin Portal. Select Integrations in the left-hand menu and scroll down to Meraki Location Analytics API

Click Show Settings

On the subsequent (Integration Keys) page click New Secret

Enter your Meraki network name and paste the Validator ID you copied from Meraki dashboard earlier into the validator field.

Click Create button

You will be redirected back to Integration Keys page with your new secret key created. Take note of Post URL and Secret

Now you need to go back to Meraki dashboard, click Add a Post URL and paste the Post URL and Secret to relevant fields. Make sure you selected API version 2.0

Click Validate to check test your configuration. You shall see the following message in the yellow box above Post URLs configuration section.

Now Click Save at the right-bottom corner of the page to save your changes.

Connect to your Meraki WiFi network to initial Location API call to Amplespot API. 

Wait for 3 minutes and go back to Amplespot Admin Portal to check if your Integration is working.

You have now successfully completed setting up the integration of Meraki Cloud Controller and Amplespot!

Did this answer your question?