Use cases:

• Positioning with DNA Spaces

• FMF with DNA Spaces

...

• A mazepos.com subdomain DNS entry pointing to the local private IP of the server where the Proxy-LIPI will be running.

• A network configuration set up that covers the public IP range(s) of the customer that intends to communicate with this LIPI, that points to the dns entry above.Local network topology such that the source IP address of the packets received by the Proxy-LIPI server corresponds with the local IP address of that same client in Cisco Spaces. That means there should be no NAT or proxy between the clients and the Proxy-LIPI server.

• A position configuration with type “MM_POSITION_CONFIG_TYPE_CLOUD_POSITIONING”

• A LIPI Config set up with position provider type “MazeMap Cloud Positioning”, pointing to the position config above and the dns entry above.

...

The CPU and RAM requirements will vary on traffic, but in most cases will not have any specific requirements, as this is a simple nginx proxy. E.g. running a minimum of 1x CPU and 2 GB Ram should cover most use cases.

Local network and WiFi setup requirements

The local network topology needs to be such that the source IP address of the packets received by the Proxy-LIPI server corresponds with the local IP address of that same client in Cisco Spaces.

That means there should be no NAT or proxy between the clients and the Proxy-LIPI server.

Installation, running and basic usage

...