Interoperability and legacy protocols
These references cover older and less common interfaces. Check the supported version, device role and limitations before using them in an integration.
On this page
Overview#
These technologies remain important when maintaining installed estates or joining systems from different eras. “Open,” “standard,” “compatible,” and “supports protocol X” aren't interchangeable claims. Pin the edition, profile/subset, product, firmware, transport, security mode, extensions, and evidence.
| Reference | Current posture | Use |
|---|---|---|
| PSIA specifications | Mixed: current access/credential work plus legacy video specifications | Shared service, security, metadata/event, area control models |
| PSIA PLAI | Active PSIA focus; Area Control including PLAI v3.1 is the published baseline listed by PSIA | Synchronize identity, credentials, roles, and privileges across PACS/logical systems |
| Pelco D and Pelco P | Legacy, variant prone | Serial PTZ and auxiliary camera commands |
| Sony VISCA | Active in supported cameras; serial and IP forms differ | Camera command, inquiry, PTZ and preset control |
Adapter rule#
Keep a capability matrix for every endpoint. Unknown fields and commands must round trip or fail explicitly, never default to a privileged state. Separate protocol receipt, acceptance, completion, observed device state, and operator outcome. Make command paths opt in and read only by default.
Legacy transports frequently lack encryption, authenticated identity, replay protection, or granular authorisation. Put them behind a hardened gateway, isolate the segment, allowlist exact controllers and operations, protect management, and audit the translated identity. Don't label the downstream side “secure” merely because the upstream API uses TLS.