Pairing a handset with Inno Caller — and testing it without waiting for a call

Generating a code rotates the secret. Here is what that breaks, how to set who a handset belongs to, and what the diagnostics screen separates.

Pairing a handset

Generate a pairing code from the telephony sources screen and scan or paste it into the app. Two things about that button are worth knowing before pressing it.

• Generating ROTATES the secret. Any handset already paired to that source stops working immediately. The warning is shown before the button, not after.
• A code cut short by the copy is named as that — an ellipsis in the middle is reported as a truncated paste, not decoded and rejected as a bad code, because those send somebody looking in two different places.

Whose handset is this?

Set the owner from the source’s own screen. A username typed where a user id was expected used to raise inside the transaction and roll the whole call back — the symptom being that nobody appeared to have called at all. Now the field draws a picker, the save resolves a username, and an unresolvable value is refused by name.

Testing it without waiting for a call

Use Test the connection. It prints the status, the machine reason, the milliseconds and the server’s own sentence, inline and selectable, because whoever is debugging a handset has that screen and nothing else.

What the diagnostics screen separates

Refused-all-day and a quiet day used to look identical. They do not now: a refusal is recorded against the source and moves its counter, so “nothing has ever arrived” is a different sentence from “nothing arrived today”.