Equipment Comparison Chart

Device configuration : Mikrotik

Open Winbox application to access Mikrotik or you may use a web browser to connect to your Mikrotik. Connect to Mikrotik using it’s IP address or MAC address if you are using Winbox.

To start setting up the hotspot network, click on IP-Hotspot and click on Hotspot Setup under Servers tab. Go through the Hotspot Wizard by selecting the desired interface to run the hotspot network.

Create a gateway for your hotspot network and masquerade the network.

Create a DHCP pool range for your hotspot network.

Select none for SSL Certificate.

Leave the SMTP server address as default

Add Google DNS Servers and

Leave the DNS name empty.

Skip the local hotspot user by clicking next.

Now you have successfully created a hotspot network on your Mikrotik. The next step is to point your hotspot network to RADIUS server which is Kiwire. To do that, first, click on the Server Profiles tab and select the hotspot server profile that you just created. Go to the Login tab and tick only HTTP PAP and HTTPS.

Next, go to RADIUS tab and tick on use RADIUS.

Next, go to User Profiles tab and click on the default profile. Edit the Shared Users box by putting 1000.

Go to Walled Garden, add new Walled Garden at the Dst. Host section, select your hotspot server and allow it on the Action. This setting is for allowing the social login and pre-login campaign videos or URLs.
Type Walled Garden List

Synchroweb social gate
Facebook Login *facebook*
Wechat Login **
Twitter Login *twitter*
Instagram *Instagram*
Google+ *google*


Next, go to Walled Garden IP List and add Kiwire IP address in the Src. Address and Dst. Address and select your hotspot server.

Click on the RADIUS menu and add new RADIUS. Put Kiwire IP address and create a secret. Tick on hotspot for Service.

On the Incoming tab in the RADIUS menu, tick on Accept and use port 3799.

Next, go to System-Identity and set an identity for your Mikrotik. This will be the NAS ID of your Mikrotik.

Next, go to Files, copy below login.html into the existing login.html and edit the url part as http://kiwire-ip/user/index.php. For example,




$(if chap-id)


<center><b>JavaScript required. Enable JavaScript to continue.</b></center>



<center>If you are not redirected in a few seconds, click 'continue' below<br>

<form name="redirect" action="" method="post">

<input type="hidden" name="mac" value="$(mac)">

<input type="hidden" name="ip" value="$(ip)">

<input type="hidden" name="username" value="$(username)">

<input type="hidden" name="link-login" value="$(link-login)">

<input type="hidden" name="link-orig" value="$(link-orig)">

<input type="hidden" name="error" value="$(error)">

<input type="hidden" name="chap-id" value="$(chap-id)">

<input type="hidden" name="chap-challenge" value="$(chap-challenge)">

<input type="hidden" name="link-login-only" value="$(link-login-only)">

<input type="hidden" name="link-orig-esc" value="$(link-orig-esc)">

<input type="hidden" name="mac-esc" value="$(mac-esc)">

<input type="hidden" name="nasid" value="$(identity)" />

<input type="hidden" name="vlan" value="$(interface-name)" />

<input type="submit" value="continue">


<script language="JavaScript">










Open your web browser and type in http://kiwire-ip/admin to access your Kiwire admin panel.

Go to Device-NAS and click add NAS to add your Mikrotik.

  • Device type is Mikrotik
  • NAS ID is your Mikrotik identity
  • IP address is your Mikrotik IP address
  • Shared Secret Key is your Mikrotik RADIUS secret
  • COA Port is Mikrotik Incoming port 3799
  • NAS username and password is your Mikrotik username and password
  • Address is your Mikrotik location
  • Description is remark of your Mikrotik

Next, we go to Device-Zone to assign which zone we want to assign splash page. We can assign zone based on NAS ID, VLAN ID, IP address, or SSID. Create a new zone by clicking Create Zone. Put a name to it, Link To User and Limit Connected User can be empty. Then enable the Status.

After that, edit the zone by clicking Add.

Finally, you have completed the configuration of both Kiwire and Mikrotik. Next is you need to design a landing page, create user profile and create user and assign the landing page to the zone desired. You may refer to for setting up landing page, user profile, users, and other details of Kiwire.


Setup rate limit / bandwidth control for Mikrotik PPPOE

Kiwire can also support dialup pppoe services for Mikrotik as controller, with Mikrotik as PPPOE server is an popular option for fixed fiber or wifi always on internet services for telco or internet service provider .

One of the requirement is to provide bandwidth or rate limit to the subscriber , the default profile by Kiwire is for WISPr ( Wireless ISP ) which use Wispr attribute , however you can use policy-> radius attribute to add PPPOE rate limit attribute to the profile. the step are

    1. create a profile as usual for your subscriber
    2. Access Radius attribute editor by going to Policy-> Radius Attribute
    3. Add the attribute “Mikrotik-Rate-Limit” ,select “:=” as operator and value in K or MB as you desire in upload/download format as the screenshot.


Schedule script

The schedule script will enable automatic download of wallgarden list and firewall list into the mikrotik nas on an interval.


  1. Login to winbox
  2. Go to System > Scheduler and add a new task by pressing the plus sign.
  3. Under the field Name type “firewall”
  4. set the Interval to 01:00:00 
  5. Paste the following text into it, replace the ip of “” with your kiwire server ip.

Omaya Changelog


version 2.0 [ 2017-02-01 ]

  • fixed : unable to add web user , button not responsive.
  • Enhancement : heat map .


Omaya : Chapter 4 Setting

The setting module let your configure and customise the omaya platform to your organisation needs.

4.1 Web user

The web user module let you add additional administrator or operate to omaya platform. When you access the module, it will list existing administrator or operator exist in the system.

The column data are:
username – the username of the administrator or operator
Email – the email for the user
Company – the company account associated with the users
Created – the date the user is created
Last seen – the last the user login to omaya platform
Role – the role assign to the user
Act – delete or edit the users.

4.1.1 Add new user

To add new administrator or operator click on the + Add New User button.

Fill in the input box with the required data:
Username – the username given to the new user
Email – the email address for the new users
Password – the password for the new users
Company – the company id associated with the new user
Role – the role assign to the new user , for more information on role refer to role module.

4.2 Role 

All administrator or operator added to system are govern by the role and privileges assigned. You can fine-tune the role and privileges assigned to per user basis.

To add new role and privileges , please create a role first by click on the + Add New Role fill in the role name and its descriptions click Save to save the role , the newly created role is an empty container which does not have any privileges continue by click on the privileges tab and click on + Add new Privileges button. Select the privileges you allowed the role to have and click Save to save the privileges.

4.3 Venue 

The Venue module let you manage the entire venue you have with sensor installed within your company.

4.3.1 Add venue

Click on the + Add venue button to add venue. Fill in the venue name with the name of your venue, select the venue type
Mall – if this venue is part of a mall
Outlet – if this is outlet within a mall or shop
Zone – if this venue is a zone, which consist multi sensor.

4.4 Venue Device 

Venue devices are list of sensor that is compatible with omaya platform; this can be wireless access point or Wi-Fi sensor. The venue device listing will list the entire sensor associated with your company account. You have option to edit or delete the sensor associated with your company account.

Note: only superadmin can add and assign new sensor to company id. Refer to omaya 2: platform owner guide.

the listing will show the data as
Company – the company id associated with the sensor
Venue – the venue the sensor is installed in
Alias – the alias or name for the sensor
DevTag – the sensor serial no or tag no
Type – the sensor type it could be access point or cloud beacon.
Rssi min – the min RSSI set
Rssi max – the max RSSI set
Dwell – the dwell time setting to constitute a user as engaged
Map Axis – the placement of sensor on the map uploaded
Map – the map id of the map associated with the venue.

4.4.1 Edit venue device

The edit venue device screen let you re-assign the sensor to new venue or change the sensor alias, tag or type.
the signal strength slider is use to manipulate dbm of the device , example if -85 dbm to -25 dbm ( lower dbm is nearer to sensor ) , we ignore any device that is more than -85 dbm and user with dbm -25 and bellow are classified as visit type users.

The dwell slider is use to determine how long a user stayed in the venue constitute as engaged users. In a fast food industry we may set the dwell to be 3 minute as the user who stay more than 3 minutes and are nearby to sensor are already a client however in a museum venue we may set the dwell time to be higher as a longer dwell time constitute user interacting with the exhibit.

4.5 Venue Map

The venue map module let you upload, manage and sensor placement of sensor onto the map.

The column listing of the venue map
Venue name – the venue name assign to the map
Company – the company id assign to the map
Type – the type of venue
Level – the level for the map within venue
Address – the address of the venue.

4.5.1 Upload map

Click on the icon to upload your map you may drag and drop the map into the upload box or click  choose file  button to select the map, please put the scale of their the map scale example 2m:1px this is for rendering of the heat map as accurate as possible .Click  save to save the map.

4.5.2 AP placement

Click on the icon for placement of sensor into the map. Drag and drop the sensor and drop them on the approximate location within the map. In addition, click save button  to save.

4.6  Automatic filtering

Omaya have a built in filtering engine that can automatically filter other sensor or Wi-Fi equipment and distinguish between users and permanent devices such as Wi-Fi printer or Wi-Fi CCTV and others wireless enabled equipment.  You may enable auto filtering per venue or select “all venue”. Automatic filtering will compute the statistic without data of permanent device to provide an accurate analytics reports that is consist of actual user only.

4.7 API 

The API module let you integrate your omaya platform data with other third party software platform, click enable to enable the API and key in your secure API key or click generate to let omaya generate the API key for you.  The API key & company id is required by third party software to access the omaya API to collect data from omaya platform. Refer to omaya API document on using the API.

Chapter 3 : Operations

The operation module provide you and operations function of omaya platform

3.1 View device status

The view devices status provide you the health status of the sensor within your omaya platform. It will show health status as well as the last reported time by the devices.

3.2 View web logs

To view administrator and operator activity on omaya platform use the view web logs function to view the activity perform by the users. You may select date range or by username.

3.3 Track User location

The track user location will locate users by the mac address of the mobile devices the user carry. mac address is an unique serial no that is associated with each mobile device.

Chapter 2 : Analytics

The analytics module is your primary reporting screen for your venues.

2.1 Benchmark

Benchmark provide a key comparison among all your venues. It will display the average record of total pass by, total visit, total engaged and calculate the conversation rate from total visit to engaged.


The  default date range is the last 7 days to select a different date range, use the date range selector to select the date, the selected will be highlighted.

2.1.1 Benchmark heat map

you can further view the average data to get a pulse of the venue crowd data by clicking the weekly view

The weekly heat map view will use colour-coded display and show the highest users crowd density by red and blue for the lowest.

2.2 Unique visit

Unique visit is your primary report of the user’s behaviour within your venues, it will do comparison between pass by, visit and engaged users.

To view specific venue, use the drop down venue list as well the date range to view the analytics data.

Click on the bar view to view the graph in bar chat format.

Click on the detail view if you wish to view further detail on the data as daily breakdown view.

To export the data click on the copy / csv / excel and pdf menu.

You may view the unique visit analytics for the day by clicking on view on the selected days, the graph will provide statistic by hourly basis.

You can change the graph to bar chart format by click on the bar icon.

Click on the data view to view the data in table format.

From the daily, you can click on the weekly view icon to see the user’s crowd heat map statistic on from the date selected.

2.3 Entry & Exit

The entry & exit analytics report provide churn rate on users entry, exit and bounce rate for the venue. You can select the venue, date range and reporting interval hourly or daily reports.

For the hourly report, the table report bellow the graph will show entry, exit, bounce rate and the percentage of entry vs exit in hourly view.

For daily report, it will show the data group by dates.

2.4 Dwell time

Dwell time analytics provide you analysis of your venue engaged user dwell time; you may select the venue you wish to view interval (daily, weekly or monthly) view and date range using the date range selector.
Click on the detail icon will show the dwell time data of user in table format group by key index such as less than 15 minutes, 15 to 30 minutes, 30 min to 1 hour, 1 hour to 2 hour and more than 8 hours. We opinion the more engaged the users the more likely the user will interact with your venue.

From the table report, you can further zoom into the daily view in a pie chart grouping for ease to view.

Click on the funnel graph to view the funnel of users dwell time in your venue.

2.5 Venue Map

The venue map provide you overlay of crowd density via heat map over your venue floor plan. Depend on the number of sensor deployed you can have a zonal heat map or presence heat map. The presence heat map provide heat map of user density nearby the single sensor while zonal edition uses triangulation between all the sensor and display the density between the sensors., click on the green view icon to view the map.

The map heat map page includes a “playback” function – by pressing the show button, it is possible to see how the client density changes throughout the course of the day. Dates can also be toggled to see client density on a specific day in the past.

Underlying Metrics

The heat maps are calculating using two metrics – (a) the number of devices were detected during the time, and (b) how long those devices dwelled in the area. The colours represent the areas on the map where there is the most “presence.” The intensity is based both on how many devices were detected during the time and on how long those devices dwelled in the area. Areas may be dark red either because there were many devices detected, or because there were a few devices that all stayed in the area for the entire hour.

2.6 Loyalty & Distributions

The loyalty & distributions analytics provide distributions statistic on new user’s vs return users to your venue. You may select the venue and date range for reports. On the main screen, there is three primary tab.

The first tab is new users versus repeat users analysis, which inform you how many new user is detected and how many return users are detected at venue

The second tab is repeat count report, which inform the frequency of the users group by 1, 2, 3 to 5 or more than five visit to the venue.

The third tab will show the return users visit frequency group by 1 ~ 3 days, 3 ~ 1 week, 1 ~ 2 week and more than 3 weeks.

2.7 Cross visit

The cross visit report will provide you trend of your users return to and movement across the entire venue you have. You can select the date range and view the user cross visit report.

Click on detail view-to-view movement of user count at each venue and dates.

You may view the hourly report of user movement count from the table listing.

Chapter 1 : Login & Dashboard

Logging into KIWIRE

Omaya is a web-based platform, to access omaya platform open your internet browser and go to to login. If this is onsite edition use the ip assign to omaya onsite.

Default Access for Standalone Omaya Platform

Access Default Credential
Company ID superuser
username admin
Password manager7890



Dashboard provide an overview snapshot of crowd analytics of your venue.

Your dashboard is the first thing you will see when you login to the omaya Portal. It gives you an overview of activity and reports on a weekly basis. The dashboard gives you the following information:

Total pass by – Total no of unique users detect walked by your venue

Total return user – Total users detected return to venue

Total visit by – Total users who is detected near the sensor

New User – Total new users to venue

Average dwell time – Average dwell time for all engaged users.

Pass by vs Visit vs Engaged Graph – a graph of the data overlaps of pass by, visit and engaged statistic.

Reset password

To reset password, click on the avatar on the top right, click on reset password to access the change password screen

Input your old password and your desire new password twice into the new password, confirm password box, and click   Submit  to change your password.

Omaya 2.0 Preface

This User Guide describes how to configure and utilise omaya 2.0 location based system. Those responsible for managing Omaya System intend this guide for use. Consequently, it assumes a basic working knowledge of local area networking, wireless networking and wireless devices.

About Omaya

Omaya is a location based platform helps you understand how people move around your venue. The paths they take, choke points, entry or exit points and even queue lengths are not only possible but also made easy with it.

Conventions in Text

We use various conventions in text to help you more quickly identify special terms. The following table describes those conventions and provides examples of their use.

Convention Meaning
Bold Bold typeface indicates terms that are defined in the text or terms that appear in a glossary, or both.
Italics Italic typeface indicates emphasis.


Conventions in Icon Graphic

Omaya  uses a common icon to represent a function

Icon Function
Edit an entry
Delete an entry
View an entry
weekly view of entry

Platform overview

Omaya administration platform consist of few pane

Navigation pane for navigation menu to access a operation or module within Omaya administration platform.

Main Screen
Main screen:  the main display of module and function

Waiting screen
if you have large data to compute, a waiting screen will be displayed, please wait until the compute is complete to review your data


There are a few key terminology used by omaya system, please get accustomed and familiar to the term for ease of operating omaya. The condition for the users associated with the correct term can be set by venue device screen.

Users – mobile device with wifi chip detected , each device is assumed to be one user, while the trend of single user with multi device is in trend its only minimal users having more than 1 mobile devices

Pass by – Users detected walk by at venue

Visit – User who is detected nearer to sensor

Engaged – total no of user that dwell at venue more than no of minutes thus is converted from pass by to engaged

Daily loyalty users – users who is detected by system 5 days out of 1 week.

Weekly loyalty users – users who is seen more than 4 days a month

Bounce rate – users who spend less than 5 minutes

Churn – the relative number of user that appear and disappear during a time window

Dwell Time – determined the amount of queuing or the average time spend in zone or outlet

Crowding factor – determined the potential bottlenecks or where extra resources are needed

Dominant direction – the most typical direction of travel through an area by users

New visitor – user who is detected 1st time at venue

Repeat visitor – users who is detected within venue 2nd time the next day onward

Device state – all mobile device emit wifi signal , the frequency of signal emitted are based on the state of the device

Device state Probe/emit request interval
Asleep ( screen off )  ~once per minute
Standy (screen on ) 10 ~ 15 times per minute
Associated with SSID varies , but higher frequency.

Omaya 2.0

Get Started

Please Select A Topic Below :
Omaya 2.0 Preface
Chapter 1 : Login & Dashboard
Chapter 2 : Analytics
Chapter 3 : Operations
Chapter 4 : Setting

kiwire 2 Changelogs

Note : all added feature for the build is term beta till next update or release.

Kiwire 2.0 build 4 [2017-05-28]

  • [Fixed]
    • rewrite of Reports module ( login ~ Logs )
    • fixed reports module to use timezone define by setting
    • fixed survey engine to use timezone define by setting
    • integration cloud email provider  madmini and mailchimp using cloud id
    • fix integration Pms oracle opera heartbeat issue causing disconnect every 30 mins
    • Santize username when user signup prevent white space
    • fix dashboard display with timezone
    • fix help > database > MRO , campaign purge error
    • fix Ruijie wifidog incoming and outgoing counter
    • fix forget administrator password failure
    • fix voucher creation as per Kiwire 1.6 method
    • fix auto suspension of user expiry using local time
    • fix spelling mistake in reporting “bandwidth”
    • fix user control panel transaction report by username.
    • fix height display box for error notification on administrator navigation
    • fix module id in lbs reports
    • fix module profile advance error
  • [Added]
    • Added column for account summary report.
    • Error message when users login without profile associated
    • Error message for page maker when slider is not able to save
    •  implement cache for reporting engine via scheduling
    • Added support for Fortigate security gateway as NAS
    • Ruijie wifidog counter support for counter(s) as per new firmware requirement
    • Add Nas via batch
    • seamless login for ruijie wifidog access point
    • support for administrator to login using email
    • added zone column in reporting
    • voucher creation need compulsory information
    • campaign engine support of minutes instead of just hour
    • if nas device is down more than 30 minutes disconnect all user session
    • added download transaction to csv file in report transaction
    • added email synchronisation is 30 minutes cloud email provider
    • added audit trail log for administrator
    • added zone login snippet
    • added log for api request
  • [Updated]
    • voucher view as per version 1.6 view
    • added close to database connection engine for stability and performance
    • latest ajax reporting for integration sms , radiuslog , visitor self registration, coupon view ,email transaction and sms transaction
    • enhanced EULA screen
  • [Depreciated]
    • insight tab in account view until further notice

Kiwire 2.0 build 3 [2017-04-28]

  • [Fixed]
    • Admin login with special character
    • Admin : forget password
    • PMS , password percentage.
    • NAS : Xirrus on public ip
    • Cloud management : fix warning when add user
    • Integration -> PMS : oracle fidelio fixed last name
    • Integration -> Ldap , authentication failure on rare case.
    • login engine -> page maker guest sign up.
    • Report -> Bandwidth -> top user , Missing username on listing
    • Report -> Bandwidth , Data missing when apply zone
    • Report -> login -> Dwell time : fix graph problem
    • Report -> Login -> Return user, fix error on report
    • Tools : diagnostic account , bug on user with multiple output
    • Tools : log purge fail on certain condition
    • Wechat : Change of authority (COA ) not using UTC time.
    • Campaign : wrong display of ads during time interval
    • Login Engine : Terms & condition always display
    • account->user view , Last 10 activity to user local time
  • [Added]
    • Dynamic Menu : operator account will only see menu assign to their role.
    • Campaign : Mobile apps promote or push install
    • Allow administrator username using email address
    • Declare multiple {{Page}} tag within a page
    • NAS : Aruba IAP series
    • High Availability : Public & Private key for synchronisation of files
    • Report -> Date format for chart.
    • Tools-> Software update : manual update button
    • Kiwire Software : EULA when administrator login the first time.
    • High availability : Logs.
    • Email verification during login and save.
    • Campaign can now trigger external server using GET request
    • Pop up error message due to device down
    • Zone auto-login snippet
    • Social login using SSL connection
    • Email using HTML format instead of text
    • Generate public key and bind the slave key for HA connection
    • Database backup moved to non-root folder and using random string for security
  • [Updated]
    • Campaign : Random advertisement if there is no sort order.
    • Campaign Ads : full screen display for IAB standard image format.
    • Login page sign up , checking of space when user select username , which cause radius to fail.
    • Kiwire API Updated to include new feature
    • Default : language english if no language selected.
    • NMS  : Agent , ping if only valid IP is saved.
    • Changed of Microsoft Login method to use Microsoft Graph instead of OAuth
  • [Depreciated]
    • Report -> real time log, due to nature of multi tenant , real time logs deem security risk.


Kiwire 2.0 build 2 [2017-03-15]

  • [Fixed]
    • Dashboard : timezone of date displayed
    • Integration -> Radius : wrong text for validity
    • Integration -> SMS : Twillio error handling
    • Device -> monitoring : bypass check for device if ip address is missing.
    • Device -> Monitoring : zone listing lessen rules
    • Device -> monitoring -> Agent Ruijie wifi monitoring
    • Login Engine->T&C : fix always on function
    • Login Engine->Page maker -> coupon : path error for image display
    • Login Engine->Page Maker : load external image from remote site fixed.
    • Login Engine->Page Maker : scan local filename instead global for saving
    • Login Engine->Guest Login : fix path for login
    • Report -> Survey report : data display
    • Report engine : kiwire syslog
    • Report -> Campaign : click thru was wrongly worded
    • Report -> Login concurrency partition reporting
    • Report -> Device availability.
    • Report -> Graph date accuracy
    • Tools -> Database MRO : fixed download backup.
    • Tools -> service healthcheck for SMS & Email services
    • Login -> redirection using for duplicate username
    • Login -> Check for MSAD/LDAP during inactive user check function
  • [Added]
    • More debug log option for user captive portal flow.
    • Account -> User : list suspended account as well
    • Seamless roaming for ruijie wifdog wifi access point
    • High availability : bi direct  synchronisation  between 2 kiwire.
    • Integration -> Microsoft/Office 365 : authentication of user with Microsoft live/Azure/Office 365 services with restriction on allowed domain
    • Integration -> Microsoft Active directory , added support for Active directory user groups to local kiwire profile mapping functionality .
    • Device -> NAS : FortiAP ( Fortigate Wireless ) & Controller as NAS
    • Account -> Profile : check min speed cannot be higher than max speed restriction.
    • Logs : added detail log for zone detection engine to kiwire_userlog.log
    • Logs : updated email services for error tracking
    • Alarm notification on Primary page
  • [Updated]
    • Mac security : support upper or lower case mac address format
    • integration -> social network : Added default drop down box in event of no profile available
    • Device ->NAS rujie wifi : support Free profile
    • Login engine -> Media add support display MP4,PDF,png,jpg,gif and ogg.
    • Login engine->Survet : ability to use ip or domain if host does not have valid FQDN
    • Login Engine->Page maker : renamed snippet from snippet 1.. to the function of the snippet when mouse over.
    • Campaign -> ADS , support full screen image display for Image media ads on mobile device
    • Report -> Who is online , disconnect function for Ruijie Wifi
    • Report -> Bandwidth reporting , extend from GB to mb
    • Report -> survey : display no data if there is no data available.
    • Detect signup if user use blank username and prompt error.
    • Radius : Fallback , in event of Authorisation request packet does not contain NAS-ID, system will use called-station-id as NAS-ID
    • Social Network : WeChat , for ruijie wifi , user will use default assign profile and granted 5 minutes to complete authentication with WeChat server. For non ruijie wifi , user will be granted 5 minutes with temporary profile which have restriction and upon validation change to assigned profile on the fly.
    • Command line apps are set to use UTC timezone.
    • Bypass survey if already answer before
    • PDO -> MYSQL : added Ping functionality
    • Agent : ruijie wifi added health capture from wifi ping
  • [Depreciated]
    • None

Kiwire 2.0 build 1 [ 2017-02-27 ]

  • [Fixed]
    • Finance : date display format is not correct
    • Radius : sql core error on certain profile
    • Integration -> LBS : test function
    • Device -> monitoring MAP : missing google map api key
    • Device -> Zone : update and delete button unresponsive
    • Device -> Zone : fix change tenant
    • Login Engine -> Journey : screen adaptation on smaller screen size
    • Login Engine -> Journey : post login unable to change default destination
    • Login Engine -> Media : fail of upload media via drag and drop
    • Campaign -> Ads : upload video
    • Account -> Profile : not properly seelct.
    • User : campaign continue button not responsive on certain device
    • LBS : test function not responsive
    • Report : graph charset for language
    • Report : missing username text on username search option
    • Report : Graph on safari browser not rendered
    • Report : timezone
    • DHCP : spelling mistake for DHCP
    • License engine that display error on rare occurrence
    • Account -> Profile : wrong display for “Pay As You Use” profile
    • Installer : corrected path to local path
    • Login -> Video at prelogin
    • Multi tenant -> role created wrongly when add new tenant.
  • [ Added ]
    • Account -> Profile : added WISPR specification for  QOS services . support minimum upload and download bandwidth for supported access controller.
    • Device -> NAS : support Xirrus access controller and wifi access point captive portal
    • Account -> Auto reset : added 30mins and hourly options
    • Integration -> Social network : VK+ and Microsoft Live.
    • OTP : Based on password security level , if set high OTP password will be alphanumeric if low it be numeric only.
    • Configuration : Auto update function, kiwire will now support auto update to latest edition.
    • Campaign -> Ads : only allow media mp4,jpg & ogg for file uploaded
    • Control panel for users accessible by /cpanel
    • New API engine for 3rd party integration
    • Policy : Cookies Auto-login , auto login user using cookies during login process , return user will not required to key in login credential for prevention of captive portal fatique
    • Report-> Campaign -> Survey.
  • [ updated ]
    • New Changelog format for change log
    • Updated graph engine with more dynamic colour and  focus on  graph while print friendly
    • Social network login : new login flow screen design to be more lively and graphical.
    • Login Engine-> Page Maker : change survey option selection to dropdown list for easy to manage .
    • Mobile & browser brand & type detection engine signature updated
    • Software update module : support auto update function
    • Licensing : update license engine only master account require license
    • Rename : Omaya module to LBS
    • Account -> Auto reset : added hourly and 30 minutes option to system
    • Login engine -> Page maker : update preview custom page.
  • [ Depreciated ]
    • Remove example text “synchrowebtech” in integration->social network to be generic example

Kiwire 2.0

  • Platform : expanded industry type catergory into organisation setup as per 802.11u base for WBA WRIX-L ( wireless roaming intermediary exchange for location )
  • Platform : change cloud tenant password display masked.
  • Platform : added memcached engine to user custom generated page for optimised and fast rendering.
  • Device monitoring : added wifi access api , display total received and send by wifi access point & load
  • Zone monitoring , monitoring based on zone beside by nas/device
  • Dashboard : bugfix on 24 hour activity
  • integration : Radius , rewrite : support local profile override as well as proxy carry forward profile . added keyword or tag check from radius response for profile grouping check. refer to documentation for more info.
  • Zone restriction function : added to integration ( radius , active directory,ldap ,social network , sms , pms )
  • Bulk user manager , added phone no on export
  • Page maker : added email verification sign up snippet , user can signup and given 5 minute access to verified the email to complete the sign up process.
  • Page maker : added forget password (based on user profile , sms or email option )
  • Page maker : radius login snippet
  • Page maker : sponsored login via email snippet
  • Page maker : public sign up snippet
  • Page maker : sms signup snippet
  • Page maker : various button snippet
  • Page maker : coupon snippet
  • Page maker : survey snippet
  • Page maker : added box picture snippet.
  • Page maker : buy plan snippet
  • bugfix  : Reports & analytics engine for date format
  • bugfix  : SMS api
  • bugfix : applied default tenant id to PMS socket api for backward compatibility.
  • bugfix : oem logo placement
  • bugfix : wrong notification on exceed volume quota
  • DB api : added db is alive ping
  • wifidog api : optimised volume detection
  • platform : remove link to google fonts
  • Account diagnostic , change engine from radtest to radius client .
  • CLI tools  : added support incident log collector to /tmp
  • Removed : feature license key , for now Kiwire will have only onsite / hosted , multi or single tenant editions.
  • Campaign & Ads manager , simplified verification and approval , if single admin , its auto approved by default if more than 1 admin for the  cloud id , approval process is required, default edit/add campaign & ads will be disabled till approved .
  • Reports & analytics : added coupon redemption report
  • Reports & analytics : login history support same day and archive reporting.
  • accounts : updated integration profile to have sms , radius , email beside pms , msad and internal

Kiwire 2.0 beta

  • Multi-lingual support & internationalisation , internal timezone set to UTC and support of DST timezone
  • bug fix : wifidog api
  • Dynamic Zone , now zone can be define by client ip , nas id , vlan and ssid
  • User journey engines
  • Additional snippet for page maker ( sms )
  • Omaya integration via API
  • report & analytics : omaya lbs reporting.
  • Platform : high or low password security level when dealing with passwords.
  • Cross platform attack protection xcss

Kiwire 2.0 alpha

  • Rewrite of core engine
  • Support  true multi-tenant, each tenant have own partition of data
  • New theme based on google material design
  • Simplification of admin interface
  • Login & Page maker , drag and drop interface
  • Renamed EDX to integration
  • Renamed user’s plan to profile
  • Integration : SMS have built generic sms gateway api connector builder.
  • bug fix : QR login for voucher