IPTV and hospitality TV

How it fits together

An IPTV system receives satellite or terrestrial channels at a headend, converts them to IP streams and distributes them over the network to TVs or set-top boxes. Multicast means one stream serves every viewer of a channel, but only if the switches are configured for it (IGMP snooping and a querier). A network that isn't configured this way floods every port with every channel; that's the most common cause of IPTV failures.

Hospitality features

Hotel systems add a welcome screen with the guest's name from the PMS, hotel information, room service menus, secure casting from guests' phones that resets at check-out, and the hotel's own content. Channel rights and licensing for public display are the operator's responsibility; we highlight them early so the channel plan matches what the hotel is licensed to show.

How the system works end to end

IPTV is used in hotels and serviced apartments, hospitals, staff accommodation, residential compounds and offices with lobby or canteen screens. The chain is the same everywhere. Channels arrive from satellite dishes, terrestrial antennas, in-house content players or internet streams. Receivers and encoders turn each channel into an IP stream, and a middleware server builds the channel list, the welcome screen and the interactive menus. The streams travel over the building network to a TV in each room, either one with the client built in or one fed by a small set-top box (STB). Guest requests, such as room service or a language change, go back to the server, and the property management system (PMS) tells the server who is in which room.

Because everything runs on the data network, the quality of the TV service is the quality of that network. That is why we plan IPTV together with the network team and not after it.

Main parts and what each does

Choosing the delivery method

Not every property needs a full IPTV platform. The choice depends on the existing cabling, the size and what guests expect to do with the screen.

Network planning figures

These are planning values to size the network before the final channel plan is fixed.

• Stream rate: an HD channel is typically in the range of 4 to 8 Mbps depending on encoding, and a 4K stream is several times that. A 100-channel HD line-up therefore puts roughly 400 to 800 Mbps at the headend output, so headend uplinks are planned at 10 Gbps.
• Room ports: only the channel being watched reaches a room under multicast, so a 1 Gbps room port has ample space. Planning one to two streams per room plus on-demand playback is the usual basis.
• Multicast settings: IGMP snooping on every switch and a querier on each VLAN. If streams cross routers, multicast routing is configured and tested between those networks.
• Separation: IPTV runs in its own VLAN with quality-of-service marking, so a large download in the lobby cannot freeze a television.
• Channel change time: a delay of one or two seconds is normal. Longer delays point to encoder or switch settings, and are checked at commissioning.

Integration with the other systems

• PMS: guest name, language and room status flow to the TV, and check-out clears messages, casting sessions and any personal data on the screen.
• Wi-Fi: casting works only on a surveyed wireless network, with guest devices separated from the TV network. See Wi-Fi and wireless links.
• Telephony: message-waiting and guest-service numbers can appear on the screen, see IP telephony and PBX.
• AV and meeting rooms: conference displays and digital signage can share the same platform, see AV and meeting rooms.
• Public address: lobby music and screens can follow the same schedule, see public address.
• Video surveillance: on request, a camera view such as the entrance can be put on a staff channel, see video surveillance.
• Villas: in larger homes the TV system joins the wider home design, see villa low-current.
• Power: the headend and core switches sit on a UPS, covered under power continuity.

Commissioning and handover checklist

• Every channel is checked for picture, sound and language on a sample of rooms on each floor.
• Multicast is verified at each switch, with no flooding on unrelated ports.
• Channel change time is measured and recorded.
• The PMS link is tested for check-in, room move, language and check-out.
• Casting is tested from different phones and cleared at check-out.
• Remote controls, volume limits, start-up channel and start-up volume match the property standard.
• The headend restarts by itself after a power cut with all services running.
• Handover includes the channel plan, IP and VLAN list, passwords, a backup of the middleware configuration and training for the staff who update content.

Common mistakes and how to avoid them

• Switches left on defaults: multicast floods the network and the TVs freeze. Agree the settings with the network team before installation.
• Channel plan before licensing: check what the property may display publicly, then build the list.
• Casting on the guest Wi-Fi VLAN: devices cannot find the TV, or guests see each other's rooms. Design the separation deliberately.
• Too many headend inputs on one device: when it fails, every channel goes. Spread the load and keep spares ready.
• Nobody owns the content: menus and offers go stale. Decide who updates what, and give them simple access.
• Different TV models per floor: they behave differently and complicate support. Standardise on one model per type of room.

Maintenance and testing

Under a maintenance contract we check the headend inputs and encoder health, review the stream logs, test a sample of rooms every visit and update the channel line-up when a provider changes it. Software updates are applied in a planned window with a rollback copy, never during peak hours. The middleware backup is refreshed after every change, so a failed server can be restored quickly. We also review a few of the rooms with the most complaints, because they often show the real fault: a loose cable, a bad port or an out-of-date TV.