2N® Helios IP 2N® IP intercom is natively primarily intended for an audio and video communication with the other party, such for ex. example 2N® Indoor Touch, as the answering unit on the end-user side. The multimedia stream needs a dedicated bandwidth to provide smooth communication to both sides. Following guide summarizes network requirements necessary for installations of 2N® Indoor Touch units (with running 2N® Helios IP Mobile application) together with 2N® Helios IP 2N® IP intercoms.
In order to perform correctly, all components are required to be interconnected over appropriate Ethernet/Wi-Fi network parts as described in this FAQ.
It is highly recommended to use a physically dedicated LAN or a virtually dedicated VLAN with corresponding parameters. Insufficiently dimensioned network infrastructure and active network parts may cause an overload of the network communication such as packets packet loss or delays with a direct impact on the communication smoothness.
In order to avoid any potential issues of poor or inappropriate wireless connectivity and network parts, we strong strongly recommend to useusing:
Table of content:
There are two ways how the 2N Helios IP intercoms can communicate with the 2N® Indoor Touch units:
- Without SIP Proxy | peer to peer mode(suitable for up to 50pcs of 2N® Indoor Touch)
easy to setup, live video view available at any time, no need for an additional 3rd party HW/SW
higher bandwidth requirements, operational in LAN only, no WAN usage (eg. for distant locations), no advanced Proxy/PBX features (call transfer/forwarding, audio/video recording etc.)
- With SIP Proxy (suitable for 50+pcs of 2N® Indoor Touch)
easy integration with an existing communication solution, 2N Helios IP 2N IP intercoms and 2N® Indoor Touch units are reachable from other IP phones in the proxy, support of multiple distant locations
video view in alerting state/during an active call only
Without SIP Proxy | peer to peer mode
Way of communication Codecs | Protocols Bandwidth 2N Helios IP → IP intercom→ 2N® Indoor Touch/2N® Helios IP Mobile MJPEG multicast/JPEG unicast (preview*), H.264 (in call), G.722 | SIP, proprietary ~2-15* Mbit/s per each 2N Helios IP intercom 2N® Indoor Touch/2N® Helios IP Mobile application → 2N Helios IP intercom G.722 | SIP, proprietary ~100 kbit/s per each 2N® Indoor Touch
Please note that a transparent broadcast and multicast communication has to be allowed in the whole network to guarantee the operability of the 2N system.
* Depending on the scene complexity and video qualityset on the intercom side.
With SIP Proxy
Way of communication Codecs | Protocols Bandwidth 2N Helios IP IP intercom→ 2N® Indoor Touch/2N® Helios IP Mobile H.264 (in call), G.711/G.722 | SIP ~2-5 Mbit/s per each 2N Helios IP intercom 2N® Indoor Touch/2N® Helios IP Mobile application → 2N Helios IP intercom G.711/G.722 | SIP ~85 kbit/s per each 2N® Indoor Touch
The 2N® Helios IP Mobile application version 2 for mobile devices supports unicast communication exclusively, therefore it is intended for installations of up to 3 devices to watch the video stream from the 2N Helios IP intercom simultaneously.
The 2N® Helios IP Mobile application version 3 for 2N® Indoor Touch supports multicast communication exclusively. Therefore there is no limitation of the end-points quantity, however the local network has to support multicasting.
The version 4 of the 2N® Helios IP Mobile application for both (mobile devices & 2N® Indoor Touch) has an option to switch between the multicast and unicast communication to adjust the stream. If your network infrastructure does not support multicasting, you can use unicast in a case of a small setup (up to 3 devices in the network) or WiFi connectivity. Otherwise it is high highly recommended to use the multicast communication for wired connectivity.
Image RemovedImage Added
For further details please see please this FAQ Application, 2N® IP Mobile v.4 2N® Indoor Touch - How to deal with the Unicast x Multicast settings?
In the w/o SIP proxy (peer to peer) mode the video from the 2N® Helios IP intercom is sent to the 2N® Indoor Touch/2N® Helios IP Mobile using a multicast stream. Therefore it is highly recommended to use a smart managed switch with the IGMP Snooping support for the local communication to avoid overloading of the switch throughput.
It is high highly recommended to use dynamic IP addresses assignment from a DHCP server running in the local network, because it takes all of the manual work out of IP addressing and you don't have to configure each device one by one. When DHCP is enabled, any new 2N® Helios IP intercom or 2N® Indoor Touch connected to the network asks the server for an address and all the IP settings gets configured automatically. The server itself tracks which addresses are used and which addresses are available, and keeps a record of which addresses have been assigned to the various devices. This ensures that addresses don't conflict with each other and their management is accessible from one place.
In order to avoid any potential issues of poor or inappropriate wireless connectivity and network parts, we strong recommend to use:
In the w/o SIP proxy (peer to peer) mode the video from the 2N® Helios IP 2N® IP intercom can be sent to the 2N® Indoor Touch/2N® Helios IP 2N® IP Mobile using a unicast or multicast stream. If you choose multicast and the device is connected via Wi-Fi (802.11b/g/n) wireless network, there is a security mechanism of the Wi-Fi standard itself to ensure the multicast data transfer due to a lack of the IGMP protocol for wireless. The mechanism works the way that the Wi-Fi access point decreases the data transfer rate to the minimum level (~7Mbit/s) and floods it to all connected devices, to make sure the information is received by everyone. Once the transfer rate is decreased to such a low-profile mode, it becomes a bandwidth bottleneck for multiple video streams to be received. It can cause issues with the packet loss and video blackouts.
2x 2N® Helios IP 2N® IP intercoms (front and back entry)
4x 2N® Indoor Touch units in total (1 on Ethernet in the Main Hall, 3 on Wi-Fi in the Bedrooms)
Calculation for p2p: 2x 5Mbit = 10Mbit, 4x 0,1Mbit = 0,4Mbit
Recommendation: Shared 100Mbit/s infrastructure with a dedicated VLAN, managed switch with the IGMP Snooping support and Wi-Fi access point with the Multicast helper support
Mid-size residential building
5x 2N® Helios IP 2N® IP intercoms (front entry, back entry, side entry, service entry, garage)
40x 2N® Indoor Touch units (one indoor unit in each apartment)
Calculation for p2p: 5x 5Mbit = 25Mbit/s, 40x 0,1Mbit = 4Mbit/s
Recommendation: Shared 100Mbit/s infrastructure with a dedicated VLAN if no other heavy traffic expected, otherwise a dedicated LAN, managed switch with the IGMP Snooping support
Large residential apartments complex
18x 2N® Helios IP intercoms (one intercom unit at each entry of several building in the complex)
150+ 2N® Indoor Touch units (one indoor unit in each apartment)
Calculation for p2p: 18x 5Mbit = 90Mbit/s, 150x 0,1Mbit = 15Mbit/s
Calculation for SIP Proxy: 18x 2Mbit = 36Mbit/s, 150x 85kbit = 12,75Mbit/s
Recommendation: Dedicated 100Mbit/s or shared 1Gbit/s infrastructure with a dedicated VLAN, managed switch with the IGMP Snooping support