Serial is not an afterthought here

Most terminals treat serial as a bolt-on to SSH. That is fine until the thing you have to fix is a PBX with a DB9 on the back that has been up since 2011, a craft port that says nothing until it gets an Enter, and a manual that assumes you have done this before.

What it looks like here

Baud rate, data bits, parity, stop bits, hardware or software flow control — the settings you would expect on the front of a console server, because 9600 8N1 is right until the day it is not. A serial connection is a connection like any other: same tab, same buttons attached.

The wake-up sequence — the Enters, the login, the terminal settings that never persist — is a button you press once instead of a ritual you half-remember. So is the one that takes twenty minutes and cannot be interrupted: give it a pause so it waits for you, and a message that says what to check before continuing.

The parts that matter on old kit

• Long waits are expected, not a timeout. Saving translations on older hardware genuinely takes three minutes. A step can wait that long without anybody deciding the session has hung and pulling the cable.
• A gate in front of a restart. Restarting telephony services drops calls in progress. That is the sort of thing to be asked about, once, in a sentence naming the system — not something to discover from the ticket queue.
• Nothing is bundled that touches the driver. Serial ports are used through the OS. If your USB-to-serial adapter works in Device Manager, it works here.

Where to start

There is a PBX serial set on the exchange — console wake-up, trunk status, extensions, saving translations — with every command visible before you download it. Read it, take the two buttons that match your kit, and change the prompt patterns to suit.

It is the SmartCOM heritage, and it still works the way you expect.