---
title: Typical setups
url: https://doc2.pstreamer.tv/en/manual/planning/hotels/setups.html
lang: en
product: Perfect Streamer
version: 2.0.2.423
---

# Typical setups

## A single hotel

![Diagram of a single hotel: satellite and terrestrial channels, channels from the internet and the welcome video file come to a Perfect Streamer node; the node sends UDP multicast in the IPTV VLAN to the room TVs and HLS into the guest Wi-Fi to the guests' phones.](../../../_images/hotel_single.svg)

*A single hotel: one node receives all sources and delivers multicast to the room TVs and HLS to the guests’ devices.*

**Sources.**

- Satellite and terrestrial channels — the node’s DVB adapters. Pay channels of the local operator — through a CAM module with the operator’s card; channels with a key — through BISS ([DVB receiver](../../streamer/dvb.md#streamer-dvb), [Descrambling](../../streamer/dvb.md#streamer-dvb-descrambling)).
- Channels from the internet — SRT, RIST, HLS and other inputs ([Choosing a transmission protocol](../index.md#planning-choose)).
- The hotel’s welcome channel — a video file that plays in a loop (the file input, [Files and devices](../../streamer/other_io.md#streamer-other-io-file)). The clip itself is produced by the hotel or its studio.
- The programme guide — from the broadcast or from XMLTV; the node inserts it into the stream (EIT), and the TVs show it in their own guide ([EPG/EIT](../../streamer/epg/index.md#streamer-epg)).

**Room TVs.** For each channel — a UDP multicast output in the IPTV VLAN, with its own group and a common port ([Multicast network in a hotel](network.md#planning-hotels-network)). The channel list for set-top boxes and IPTV apps can be exported to M3U ([M3U export and import](../../webui/streams.md#webui-streams-m3u)).

**Guests’ devices.** The same channels are served over HLS or DASH into the guest Wi-Fi ([OTT and DVR](../../streamer/ott_dvr.md#streamer-ott-dvr)). So that guests do not have to enter a login and password, create an account by IP address with the guest network range in the “IP address / CIDR” field and restrict it to the allowed channels ([Users / Logins](../../webui/configure.md#webui-users)). Such an account opens the channels only from the hotel network: the rights to show channels are usually limited to the hotel premises. Each simultaneous viewer needs a session of their own, and a new account has “Max connections, HTTP/HLS” set to 1: set it to “Unlimited” or to a number no lower than the expected number of viewers ([User: add and edit](../../webui/configure.md#webui-user-editor)).

**Server** — sized as in [Server sizing](sizing.md#planning-hotels-sizing), **redundancy** — as in [Redundancy](redundancy.md#planning-hotels-redundancy).

## A hotel chain from a single headend

![Diagram of a hotel chain: the central headend receives the sources and sends the channels across the internet over SRT, RIST or PS1 to the hotel nodes; each hotel node delivers UDP multicast to the TVs; all nodes are in one Meshwork domain.](../../../_images/hotel_chain.svg)

*A hotel chain: the central node receives the channels and sends them across the internet to the node of each hotel; all nodes are in one Meshwork domain.*

For a hotel chain, a management company or an operator that sells a channel package to hotels, the channels are received once — at the central headend: satellite, terrestrial, pay cards, channels from the internet.

- **Delivery to the hotels.** The central node sends each channel across the internet to the hotel node over a protocol with retransmission — SRT, RIST or PS1 ([Choosing a transmission protocol](../index.md#planning-choose); bandwidth and buffer — [Planning bandwidth, latency and ports](../index.md#planning-bandwidth-latency)). The link to the hotel is sized for the sum of the bitrates of the channels carried, with headroom for retransmission. If the hotel node is behind NAT, it connects to the central node itself: for example, SRT in caller mode ([SRT](../../webui/io/peer.md#webui-io-srt)).
- **In the hotel**, its own node receives these channels and delivers them as multicast into the local IPTV VLAN, as in the single-hotel setup, and, if needed, over HLS to guests. Local channels can be added to the central ones: terrestrial DVB-T2 or the hotel’s own welcome channel.
- **If the internet goes down.** Give the hotel’s channels backup inputs: the local terrestrial broadcast, or the welcome video file as the last input ([Backup sources](redundancy.md#planning-hotels-redundancy-sources)).
- **Monitoring from a single window.** All nodes are joined into one Meshwork domain: the state of each node, the shared catalogue of addresses and ports, and the alerts of all hotels are visible on any node ([Meshwork](../../meshwork/index.md#meshwork)). Meshwork does not carry streams — channels travel through the configured inputs and outputs. A hotel node behind NAT joins the domain by itself, without port forwarding ([Nodes behind NAT](../../meshwork/setup.md#meshwork-nat)).

Each node is a separate Perfect Streamer installation with its own licence; a hotel node is sized by its own number of channels and viewers ([Server sizing](sizing.md#planning-hotels-sizing)).