Retrofitting Legacy Vessels with Modern Communication: A Project Guide

The Retrofit Context

Newbuild vessels have a clean slate for communication infrastructure. Legacy vessels — built before 2015 and often before 2010 — have existing PBX systems, aging network infrastructure, and crew accustomed to established (if imperfect) workflows.

Retrofitting a modern communication platform onto a legacy vessel is a different project from a newbuild deployment. It has specific challenges and a specific project sequence.

Pre-Project Assessment

Before touching any system, the assessment phase determines the scope:

Network survey

• Coverage map of WiFi access points and signal strength in crew areas, accommodation, and working spaces
• Cable infrastructure: is there Cat5e/Cat6 run to the locations where the server needs to be installed?
• Existing VLAN configuration and firewall rules
• Bandwidth available on VSAT connection

Existing PBX assessment

• Make and model of PBX system
• Number of active extensions
• SIP compatibility: can the existing PBX register as a SIP trunk, or does it need replacement?
• Analog handset quantity: how many need FXS adapters?

Crew device landscape

• Most common device models in use
• Android vs. iOS mix
• Browser versions on existing devices
• Current OS versions

Connectivity baseline

• Satellite provider and connection type (VSAT, Iridium, Inmarsat)
• Average available bandwidth
• Typical latency
• Connectivity hours per day (if on metered plan)

Phase 1: Infrastructure Preparation

The server hardware needs to be physically mounted and networked before any software is installed.

Server placement — Ideally in the existing server room or IT cabinet, on a UPS. Secondary server (for HA) in a physically separate location (fire station, different deck from primary).

Network integration — The communication platform server needs: a static IP on the vessel LAN, port forwarding for STUN/TURN (if required), and VLAN segmentation from passenger/guest networks.

WiFi gaps — If the coverage survey revealed gaps in crew areas, access points need to be installed before deployment. Crew device adoption rates drop significantly in areas with poor WiFi coverage.

Phase 2: Software Deployment

With infrastructure ready, software deployment on a legacy vessel follows a standard sequence:

Deploy Synapse (Matrix homeserver) + PostgreSQL

Configure Keycloak with first admin account

Import crew roster (from crewing software or manual CSV)

Configure SIP proxy (Vodia or FreeSWITCH)

Connect existing PBX via SIP trunk

Configure FXS adapters for analog handsets

Set up Coturn (TURN server for WebRTC)

Configure on-vessel push notification service

Configure alarm system integration (depends on alarm system type)

Deploy monitoring stack (Prometheus + Grafana)

Timeline: 2 full IT deployment days on the vessel, preceded by preparation work ashore.

Phase 3: Parallel Operation

Critical: Do not cut over the existing PBX system immediately. Run old and new systems in parallel for the first 2–4 weeks.

During parallel operation:

• All existing phone numbers remain active on the old PBX
• New extensions are provisioned on the new SIP system
• Crew are trained on the new communication app
• Incident management workflows are tested with drills
• Issues are identified and resolved without operational impact

Only after confirmed stable operation during parallel period should the old PBX be decommissioned.

Phase 4: Crew Onboarding

Legacy vessel crew onboarding has a specific challenge: existing habits. Crew accustomed to calling cabin phones and using PA announcements need to understand why the new workflow is better.

Effective onboarding approach:

• Demonstration during safety drill (show how medical drill notification reaches crew faster)
• Short printed card: "Your new extension, QR code to install the app"
• Peer onboarding: identify 2–3 crew members per department as champions
• Old PBX still available as fallback during transition

What not to do:

• Don't mandate the new system without demonstrating value first
• Don't remove the old PBX before crew are comfortable with the new one
• Don't over-train — three minutes to onboard, five minutes to learn core features

Common Retrofit Problems and Solutions

SIP trunk compatibility — Some older PBXs (Panasonic, Avaya) have non-standard SIP implementations. Solution: interpose a SIP proxy (Kamailio) as a translator layer.

WiFi dead zones discovered during rollout — Solution: temporary WiFi extenders during the access point procurement/installation cycle.

iOS home screen prompts being ignored — Without Home Screen installation, push notifications don't work on iOS. Solution: clear printed visual instructions at crew check-in.

Crew defaulting to WhatsApp for everything — Solution: ensure push notifications for operational alerts go exclusively to the new platform. Make the incentive concrete ("you get your duty notifications here, nowhere else").

Project Timeline Summary

| Phase | Duration | When | |---|---|---| | Pre-project assessment | 1 day remote, 0.5 day on vessel | 4 weeks before deployment | | Infrastructure preparation | 1 day on vessel | 2 weeks before deployment | | Software deployment | 2 days on vessel | Deployment week | | Parallel operation | 2–4 weeks | Post-deployment | | Full cutover | 1 day | 4+ weeks post-deployment |