Documented specifications
2N · 2N maintained live product, installation, configuration and support pages and listed OS 3.3.1 dated August 31, 2026 at review. This does not establish which main-unit or module order numbers are available in a region, the installed bill of material, support entitlement, compatible PBX or suitability for a particular access and life-safety design.
| Specification | Documented value |
|---|---|
| Main-unit and module boundary | Camera and audio-only main units are listed, with a catalogue of display, button, keypad, Bluetooth, RFID, fingerprint and I/O modules; capabilities depend on the exact ordered assembly Source ↗ |
| Power and network | IEEE 802.3af PoE up to 12.95 W or 12 V DC, with one 10/100BASE-TX Ethernet interface Source ↗ |
| SIP signaling and audio | SIP over UDP, TCP or TLS is listed; audio uses RTP or SRTP with G.711, G.729, G.722 and L16/16 kHz codecs Source ↗ |
| Camera and video | Camera main unit publishes infrared, WDR, RTP, RTSP, RTCP, HTTP and ONVIF Profile S plus MJPEG, H.264, H.265 and Axis Zipstream; an audio-only main unit is a separate order Source ↗ |
| Door I/O | Main-unit specifications list one passive NO/NC switch, one active output and one passive or active input; extension modules can change the installed control architecture Source ↗ |
| Access modules | Bluetooth, RFID, secured RFID, keypad, fingerprint and other modules are separately ordered; card type, credential technology and reader behavior depend on the exact module Source ↗ |
| Environment | The main product page publishes -40 to 60 °C, IP54 and IK08; module, frame, mounting and local exposure still require exact installation review Source ↗ |
| Firmware evidence at review | 2N listed OS 3.3.1 dated August 31, 2026; capture the installed version, track, release notes, integrity data and supported upgrade path before change Source ↗ |
Unlisted fields remain unverified. Platform compatibility and remaining support life require confirmation for the exact ordered model.
Freeze the complete bill of material before final selection
Record the camera or audio-only main-unit order number, finish, every access or I/O module, bus relationship, frame, mounting box, blanking piece and power supply. The product page advertises a broad module catalogue, but no deployment inherits all of those capabilities automatically.
Match every required button, display, credential type, camera, switch, input and environmental boundary to the exact order. Recheck dimensions, module limits and mounting instructions before cutting a wall or ordering door hardware.
Prove SIP signaling and media per installed path
The specifications list SIP over UDP, TCP or TLS and audio over RTP or SRTP. Capture the selected transport, account, registration state if used, called destinations, certificate behavior, offered codecs and negotiated audio. Treat TLS and SRTP as separate configured legs, not a product-wide encryption guarantee.
For a camera main unit, prove the intended video path, viewer and retention separately. The audio-only main unit cannot gain a camera because another Verso 2.0 order supports one.
Keep credential technology and authorization separate
RFID, secured RFID, NFC, Bluetooth, keypad and fingerprint options depend on the installed module and management design. Record the reader order, credential format, issuer, key ownership, user lifecycle, time profile, anti-passback or other rule owner and revocation process.
A recognized card, mobile token or biometric sample does not prove authorization, and an authorized decision does not prove the final door state. Avoid carrying compatibility or security claims from one reader variant to another.
Place door switching at the intended security boundary
The main unit publishes switch and input interfaces, and I/O modules may add other control choices. Decide whether release occurs at the exposed intercom, a protected controller or another access panel. Apply exact terminal ratings and keep lock power, request-to-exit, door sensor, tamper, fire release and emergency egress independently supervised.
Test authorized and rejected credentials, remote unlock, door held or forced, controller or network loss and restoration. A relay click or API success is not proof of safe, logged physical access.
Apply environment and privacy limits to the assembled station
The main product page publishes IP54 and IK08, while module faces, frames, mounting, sealing, condensation and exposure still belong to the exact assembly and installation manual. Inspect the completed cable entries, drainage, gasket, surface, sun and impact environment rather than accepting a headline rating as a site result.
Govern video, audio, credential, biometric and access-event data by purpose, retention and role. Disable unused streams and services, isolate management, validate certificates and keep a controlled recovery path for administrators and users.
Recommission modules and physical control after firmware change
2N listed OS 3.3.1 at review and documented automatic-update and long-term-support track controls in the 3.3 line. Capture the installed build and track, configuration backup, module inventory, release notes and rollback or replacement plan before an authorized change. Recheck SIP, audio, video, every reader, input, output, automation rule, log and outage path.
No IP Verso 2.0 main unit, module, frame, firmware image, SIP account, PBX, camera, stream, credential, reader, mobile service, relay, lock, input, PoE path, availability, compatibility, price, door or emergency release was inspected or tested for this reference.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- 2N IP Verso 2.0 product and technical specifications ↗
- 2N IP Verso 2.0 support and firmware releases ↗
- 2N IP Verso 2.0 installation manual 3.3 ↗
- 2N IP intercom configuration manual 3.3 ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.