System Setup & Prerequisites
System Setup
To maintain maximum flexibility for the Infinity intercom user and to facilitate integration into existing system infrastructures, VIP must be properly configured.
Configuration is a one-time process when VIP is first switched on. However, if the network addresses need to be changed or any of the system parameters detailed below need to be modified, the configuration process will need to be re-run. The new network configuration will then need to be attached to all VIP services.
When the configuration is complete, Infinity VIP can be rebooted and will be ready for use.
Prerequisites
Certain prerequisites must be met before the initial power-up as outlined below.
Network Connections
It is first necessary to allocate the network switch ports and IP addresses needed for the Infinity VIP system. There are 2 network connections on the VIP hardware:
A WAN connection to the internet
An AoIP connection for transporting audio
Note - While most installations will use both connections, doing so is not required. However, both network connections must be made to 1000BaseT switch ports.
IP Addresses
The following network IP addresses are required:
VIP WAN NIC (1)
VIP AoIP NIC (1)
VIP internal network (telosmacvlan) (1)
Portainer (1)
Infinity VIP Dashboard (1)
Infinity VIP Link Gateway and invitation server (1)
Infinity VIP Panels (up to 64 depending upon how many panels are required)
Additional Link Gateways (1 each)
Note - IP addresses for VIP Dashboard, VIP Server, and all panels must be assigned as a single continuous block. Dashboard must be the first address in the block.
We recommend setting aside a block of 70 IP addresses to allow for expansion to the maximum number of supported VIP Panels.
A typical network allocation will look something like this:
VIP WAN: 192.168.0.178 (IP address from internet router or dedicated public IP address)
VIP AoIP: 10.0.15.100 (IP address on local AoIP/media network)
VIP Internal Network: 10.0.15.101
Portainer: 10.0.15.102
Dashboard: 10.0.15.103
VIP Server and Link IP: 10.0.15.104
VIP Panels: 10.0.15.105 through 10.0.15.xxx (1 address per panel)
Important Network Considerations
While Infinity VIP offers a great degree of flexibility in terms of networking configuration, certain considerations must be kept in mind as you plan your system:
If only the WAN NIC is used, all VIP IP addresses must be outside of the range of any DHCP addresses.
If only the AoIP NIC is used, there must be an internet gateway on the AoIP network and this gateway must be entered into each panel's network configuration.
If the existing AoIP media network has multicast streams that will connect to Infinity VIP, either now or in the future, all of the AoIP media device IP addresses must share the same subnet.
If the Infinity VIP installation is part of a Grass Valley AMPP system, both the VIP and AMPP AoIP networks must be in the same subnet.
Domain Name
A public domain name is needed in order for users to securely connect to the VIP system and must resolve to the public IP address of the VIP server.
Alternatively, the domain name can point at a network load balancer (NLB) or to your Internet router’s public IP address.
In either case, VIP traffic needs to forward to the VIP server and the domain must have a security certificate.
A DNS name can be obtained as soon as the dedicated public IP address of the VIP server (or NLB or Internet router) is known. The Domain name is typically entered during the VIP setup process but may be added later if necessary.
If you are unfamiliar with how to obtain a DNS name or ssl certficiate, Telos Alliance can provide these for you.
Access to Quay.io
Quay.io is a secure container repository used to distribute VIP software updates, and a Quay.io account is required to access them. If you do not currently have a Quay account, instructions for setting one up can be found at https://docs.telosalliance.com/docker-deployment/quay.io
Network Security
The following ports must be opened to the VIP server:
TCP 443 (HTTPS) - Provides access to the VIP Client WEB
TCP 80 (HTTP) - Needed during the setup of Letsencrypt, or other security certificate validation
Depending on the particular use case, the facility’s Internet router may require an internal DNS entry to redirect internal traffic sent to the VIP domain name to the VIP system local IP address.
Last updated