Skip to end of metadata
Go to start of metadata

2N® Helios IP intercom is natively intended for an audio and video communication with the other party, such for ex. 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 intercoms.

Note

Icon

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 loss or delays with a direct impact on the communication smoothness.

Wi-Fi usage recommendation

Icon

In order to avoid any potential issues of poor or inappropriate wireless connectivity and network parts, we strong recommend to use:

  • Unicast video streaming for all wireless units (unless you are sure about a full multicast support of your Wi-Fi access point)
  • Max. 3 wireless units per installation site/area covered by the Wi-Fi AP can get the video stream from the intercom at the same time (unless you are sure about the bandwidth capabilities of your Wi-Fi access point and interference levels)


Table of content:

Bandwidth requirements for LAN/Wi-Fi
LAN requirements

Wi-Fi requirements

Wi-Fi interference

Typical examples

There are two ways how the 2N Helios IP intercoms can communicate with the 2N® Indoor Touch units:

  1. 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.)

  2. With SIP Proxy (suitable for 50+pcs of 2N® Indoor Touch)
     easy integration with an existing communication solution, 2N Helios 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  

Bandwidth requirements for LAN/Wi-Fi

  1. Without SIP Proxy | peer to peer mode

    Way of communicationCodecs | ProtocolsBandwidth
    2N Helios IP → 2N® Indoor Touch/2N® Helios IP MobileMJPEG multicast/JPEG unicast (preview*), H.264 (in call), G.722 | SIP, proprietary~2-15* Mbit/s per each 2N Helios IP
    2N® Indoor Touch/2N® Helios IP Mobile application 2N Helios IPG.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 quality set on the intercom side.

     

  2. With SIP Proxy

    Way of communicationCodecs | ProtocolsBandwidth
    2N Helios IP  2N® Indoor Touch/2N® Helios IP MobileH.264 (in call), G.711/G.722 | SIP~2-5 Mbit/s per each 2N Helios IP
    2N® Indoor Touch/2N® Helios IP Mobile application 2N Helios IPG.711/G.722 | SIP~85 kbit/s per each 2N® Indoor Touch

2N® Helios IP Mobile application for mobile phones, tablets & 2N® Indoor Touch

Icon

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 recommended to use the multicast communication for wired connectivity.

For further details see please this FAQ 2N® Indoor Touch - How to deal with the Unicast x Multicast settings?

LAN requirements

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.

List of tested managed switches:

Dynamic IP addressing

Icon

It is high 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.
Dynamic IP addressing is also supported by the device name calling mechanism w/o SIP proxy (eg. device:IDT, see 2N® Indoor Touch - How to setup call from/to 2N® IP Intercom?), so you don't need to worry about the reachability of 2N® Indoor Touch/Helios IP Mobile if the IP gets changed.

Wi-Fi requirements

Wi-Fi usage recommendation

Icon

In order to avoid any potential issues of poor or inappropriate wireless connectivity and network parts, we strong recommend to use:

  • Unicast video streaming for all wireless units (unless you are sure about a full multicast support of your Wi-Fi access point)
  • Max. 3 wireless units per installation site/area covered by the Wi-Fi AP can get the video stream from the intercom at the same time (unless you are sure about the bandwidth capabilities of your Wi-Fi access point and interference levels)

In the w/o SIP proxy (peer to peer) mode the video from the 2N® Helios IP intercom can be sent to the 2N® Indoor Touch/2N® Helios 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.

Luckily, there is a simple solution for this issue - if the Wi-Fi access point supports the multicast helper feature (alternative names eg.: Wi-Fi multicast, Multicast Routing across Wi-Fi etc.), it can easily translate the multicast stream to a unicast stream and increase the transfer rate straight away. Therefore we have created a list of tested Wi-Fi access points recommended for the wireless installation. Further details about an implementation of the Wi-Fi multicast solutions can be also found here.

List of tested Wi-Fi access points:

Wi-Fi interference

Icon

If your Wi-Fi signal seems to be strong, but the communication suddenly drops for periods of time (eg. audio or video blackouts), that may be a symptom of signal interference. It happens when another wireless signal passes through your home that is on a similar bandwidth to your Wi-Fi network, overpowering or corrupting the communication. There are a lot of potential sources of the interference, featuring:

  • Neighbors Wi-Fi Networks - the most common source, powerful Wi-Fi networks in a close proximity can detract from each other's performance
  • Microwave - if the access point is located near a microwave, massive network interference will often be experienced while the oven is up. Many microwaves operate on the 2,4 GHz spectrum, which is the same spectrum as many wireless routers.
  • Other Wireless Devices - cordless phones, wireless speakers, baby monitors, remote controllers etc.

Make please sure your wireless network is sufficiently designed and all potential sources of strong interference are eliminated. For closer details see this article Cisco - 20 Myths of Wi-Fi Interference.

Typical examples

Family House
2x 2N® Helios 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 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