All Collections
Connect FAQ
Activating a Public IP or Unmanaged Network
Activating a Public IP or Unmanaged Network

How to activate a Public IP or Unmanaged Network for your clients

Anthony Johnson avatar
Written by Anthony Johnson
Updated over a week ago

How to set up and install a Public IP with a clients own Router or Firewall

For a customer to be able to manage their own network they would need to supply their own router or firewall, which they will configure. We strongly recommend that the client uses internal or 3rd party IT for this process.

A Public IP is needed for each device that requires a separate public address. This firewall/router will be configured with a public IP address which is ordered through Connect, and is then displayed on their Service Guide to understand why a client would require a Public IP. Please see this guide here.

Configuring Services in Connect

The client may require one usable Public IP address or if they have several devices they might require five usable Public IP addresses, be aware that you can only have either 1 x Public IP or 5 x Public IPs per client these services cannot be mixed due to the network setup.

Please see this section here about adding services to Active Clients on Connect.

Giving the Customer their Public IP details

The customer would require to have the Public IP details, so they can set this up on their Router or Firewall to get the Public IP. You can find this within the client Service Guide, to see how to export the client service guide please see here.

Activating the Public IP Port

Once the client becomes active on Connect you need to assign the switch port with the role of Public IP, once the client has been made active you will need to activate a port for the client on Connect this can either be done in Building Manager here or via Switches here.

Connecting the Devices

Now the client has got an active port Public IP Port we need to connect their device(s) to the Public IP note this setup is normally completed by the client with their own Router or Firewall.

The WAN side (Wide Area Network) of their configured router/firewall will need to connect to the Public IP port on the switch.

However, if the client would like to connect their computers to the back of the phones, you need to assign a LAN Only port on the Connect Switches page, and connect this port to the LAN side (Local Area Network) of the router. All other ports are then configured for ‘Voice, LAN, Internet’ as per usual.

essensys recommend that the client manage their own DHCP, you can disable the DHCP on their VLAN from the Network Info page on Connect. From the Clients menu, highlight the specific Client, click the More drop down menu and select Network Info. In here you are able to disable the DHCP provided by essensys so the Client is able to manage their own. (More information can be found on DHCP here).

The above shows how a client with a Public IP should be set up if a client is using the centre's LAN network (WiFi Secure, Switch ports)

If the client has their own switch, they would connect this to the LAN side of their configured router/firewall. All floor ports in the office would then connect to the client’s switch.

The above shows how a client with a Public IP should be set up if a client is using their own devices for their network (their own switch, WiFi, phones etc.)

It’s a good idea to test the client’s public IP address and network, before they connect their router/firewall to the switches. Details of how to do so are found here - Testing a Public IP Address in Connect

If the client's router has wifi capability, this should be disabled in order to reduce the possibility of interference in the building.

Did this answer your question?