If you don’t have a 2N Media Library account, please fill in the online registration form and apply for access.
Please note, that access to the Media Library is exclusive to authorized representatives of 2N business partners. Therefore your request will be reviewed and approved by 2N.
Whether you’re looking for a catalogue detailing our apartment intercom system solutions or want a data sheet for the 2N IP Style, everything is below. Search, find, download, share!
Added functionality ‘Push to talk’ when Lift8 Fireman station activated (Lift8-1271)
Possibility to select behavior when concurrent alarm call activated on cabin units connected to one central unit, either queuing or connecting to conference according to new parameter 968 (Lift8-1690)
Possibility to mute microphone in cabin unit by DTMF signaling ‘9’ to make possible voice connection to the place with very high level of noise. End of muting again by sending DTMF signal ‘9’ Lift8-1699
Security improvements
New version of Mbed TLS 4.1.0 applicated (Lift8-1691)
New version of LittleFS 2.11.3 applicated (Lift8-1679)
Displaying of SMS with sensitive information in log is no more active (Lift8-1711)
Bugfixes
Unwanted permanent connection between fireman unit and machine room unit when installed in one shaft (Lift8-1472)
Logging time of NTP synchronization uses time after synchronization instead of actual time when synchronization was initiated (Lift8-1656)
Maximal length of service password set using service tool is 15 characters, correct value is 16 characters max. (LIFT8-1655)
Interrupted connection between 4G data and Ethernet port configured as internal data connection, reconnection of Ethernet cable needed (Lift8-1348)
Issue with operational call and checking call with DTMF inband communication (Lift8-1535)
SIP call using TCP direct call can’t be executed, P2P solution using TCP is not available – only UTP works correctly for connection without SIP proxy (Lift8-1661, Lift8-1664)
Time for checking call is changeable +- 10 minutes although NTP service works correctly (Lift8-1662)
Blocked log of central unit followed by restart (Lift8-1665)
Incorrect audio test of cabin unit on HW v.4 (Lift8-57)
When PIN on SIM in LTE module is changed, needed restart of the module is performed after timeout. Correct behavior is immediate restart (Lift8-685)
Repeated use of incorrect PIN for SIM in LTE module can result in SIM blocking. Now only one try of use incorrect PIN performed (Lift8-763)
Sporadic error in measured value of battery voltage (Lift8-821)
When MBN profile in LTE module is changed, restart of module must be performed (Lift8-1705)
Attempt for concurrent connection to central unit by USB and IP result in error of service tool (Lift8-323)
Displaying of ICCID in service tool without last digit fixed (Lift8-1261)
Communication error on serial line to LTE module resulting in occasional loss of character fixed (Lift8-1677)
SMS command for restart L8 RST password doesn’t result in restart of central unit (Lift8-1710)
Installation of service tool on new PC was problematic because of incorrect setting of installation process (Lift8-1718)
Incorrect message in evacuation mode for Italian language (Lift8-1230)
Restart of central unit fails when activated by change parameter 998 from 0 to 1 (Lift8-1714)
Operational call doesn’t work until checking call activated at least once (Lift8-1715)
Lift8 – Password management changed according to RED/CRA (LIFT8-1590)
Lift8 – Change in SMS password, not only numeric, command PWD for keyword change added (LIFT8-1594)
Lift8 – Forced change of service password for service tool, SMS and voice menu setting (LIFT8-1597, 1598)
Lift8 – Default time after switch on is set to first of February 2026 (LIFT8-1606)
Service tool – Added hint describing, that SIP phone number must have prefix ‘sip’ (LIFT8-941)
Service tool – Change in password menu place to menu ‘Device’ (LIFT8-1595)
Service tool – Change in numbering of parameters, setting of service password from 991 to 891 (LIFT8-1596)
Service tool – Added menu for rescue mode configuration - enabling and password (LIFT8-1599)
Service tool – Change of maximal length of strings in configuration according to needed values (LIFT8-1605)
Service tool – SIP registration time limits set to 60 – 3600s to avoid setting of too short values resulting in wrong functionality, setting 0 results in 300s (default value)(LIFT8-1616, 555)
Service tool – format validation of phone numbers for notification events (LIFT8-1622)
Security improvements
Lift8 – scan product for known open source vulnerabilities and address issues according to the Axis Vulnerability Management Policy (LIFT8-1444)
Lift8 – SBOM delivered for every release (LIFT8-1444)
Lift8 – Secure communication with device during configuration (LIFT8-1467)
Lift8 – Change in setting of passwords, demanded change of admin password and service password prior any changes (LIFT8-1515)
Lift8 – After setting wrong password 3 times, the device is blocked for password input for defined time (LIFT8-1581)
Bugfixes
Lift8 - RS232 module – AT command issue resulting in device restart (LIFT8-1485)
Lift8 - Error in planned checking call (LIFT8-1573)
Lift8 - SIP call over TCP protocol can’t be realized (LIFT8-1608)
Lift8 – Date can’t be set using phone call (LIFT8-179)
Lift8 – Issue with combination of wireless data connection and LAN connection (LIFT8-616)
Lift8 – Direct call to IP address doesn’t work when TCP protocol used (LIFT8-1563)
Lift8 – issues with quality of reproduced sound in announcements (LIFT8-1301)
Lift8 – When password for rescue mode end demanded, control of password parameter provided (LIFT8-1493)
Lift8 – Combination of FW upgrade in progress and sending event SMS results in unsuccessful upgrade (LIFT8-1549)
Lift8 - Invalid length of service password sent by SMS results in device reset (LIFT8-1610)
Lift8 – Setting of date to invalid value can result in need to perform firmware upgrade (LIFT8-179)
Lift8 – Sending SMS event without response results in LTE module reset (LIFT8-1620)
Service tool – Event configuration issue when configuration loaded from device, it can’t be loaded back (LIft8-1614)
Service tool – For some new functionalities missing translation to other languages than English, fixed (LIFT8-1430, 1572)
Service tool – issue with blocking tool when invalid date set, added checking of tine in device after setting (LIFT8-1532)
Service tool – When device connected by TCP, change in language od service tool results in device restart (LIFT8-1623)
Version: 3.1.4
Final version: 3.1.4.0.1
Date: 26.11.2025
New features and improvements
Lift8 – TCP signaling for SIP connection added – both TCP and UDP available (LIFT8-1041)
Lift8 – camera functionality is not supported for FW versions 3.x both for new and old version of hardware (LIFT8-1560)
Lift8 – User Agent field filled with actual device or application (LIFT8-1043)
Communicator – signaling of data communication error added (LIFT8-1495)
Lift8 server – repeated question whether configuration files should be deleted to avoid unwanted deleting of application data (LIFT8-1476)
Security improvements
Lift8 – conformity with standard EMN 18031 approved (LIFT8-1091)
Lift8 – conformity with standard EN 303 645 approved (LIFT8-1139)
Bugfixes
Lift8 – unreliable upgrade of LTE module fixed (LIFT8-1415)
Lift8 – identification of used audio unit by SIP call in evacuation mode (LIFT8-1420, LIFT8-1426)
Lift8 – repeated attempt to SIP registration although the data connection is not available (LIFT8-753)
Lift8 – incorrect functionality of machine room unit when invert of Alarm input applicated (LIFT8-1247)
Lift8 – audio unit Compact can be used in cabin only – changed to any position (LIFT8-1502)
Lift8 – audio quality in call improved, disturbance in call and in reproduced sounds fixed (LIFT8-1418, LIFT8-1301)
Lift8 LTE – added MBN profile for Vodafone (LIFT8-1519)
Service tool – user message can’t be deleted during playback, delete function blocked. Improved loading user message (LIFT8-1380, LIFT8-1386)
Version: 3.0.0 – Hardware version 4 support
Final version: 3.0.0.0.8
Date: 15.10.2025
New features and improvements
Lift8 – Reporting of battery capacity for one hour of operation according to EN 81-28 (LIFT8-1275)
Lift8 – forced test alarm set by default to 30s to fulfill demand of EN 81-28 by default (LIFT8-1407)
Lift8 – Ethernet port placed on base board of L8 HW version 4, no additional Ethernet board needed (LIFT8-950)
Lift8 – USB C port supported on base board of L8 HW version 4, instead of previous USB B (LIFT8-988)
Lift8 – Change in battery and power source voltage displaying – two separated values (LIFT8-456)
Lift8 – Improved signalization of data connection status by LED (LIFT8-13290)
Lift8, Communicator – Unification of user agent reporting with other 2N products (LIFT8-1043, LIFT8-1044)
Lift8, Communicator – Possibility to confirm checking call by connecting the call without any additional confirmation (LIFT8-1257)
Lift8 LTE – Possibility to select MBN profile for LTE module, needed for VoLTE support for some operators, profiles added to upgrade packets (LIFT8-1282, LIFT-1284, LIFT8-1285)
Control panel – Reporting extended by possibility to report time and date of last successful call (LIFT8-1258)
Control panel – When the interval for checking call is set to 72 hour (default value – 3 days), the interval 74 hour is accepted, error is reported after this time (LIFT8-904, LIFT8-1385)
Control panel – separated upgrade for LTE module and FW in Lift8 to prevent problems when upgrade is done in one step over wireless connection (LIFT8-1401)
Communicator – Change of map used for localization of installation, instead of BingMaps used OpenStreetMaps because of licensing issue (LIFT8-1288)
Communicator – Improved reporting checking call by adding information about results (LIFT8-1391)
Security improvements
Lift8 - Trust zone supported for HW version 4, secure memory area to save information, which should be kept private (LIFT8-960)
Lift8 – Secure boot supported for HW version 4, verified FW loading protected against use of unauthorized firmware (LIFT8-1019, LIFT8-1116)
Lift8 – Verification of authenticity and integrity of firmware for update (LIFT8-1156, LIFT8-1157)
Lift8 - Cryptography protection of personal data transiting between device and associated services (LIFT8-1187)
Lift8 - Libraries of third party upgraded to latest versions (LittleFS, LWIP, TLS…) (LIFT8-1208, LIFT8-1262, LIFT8-1264, LIFT8-1313)
Lift8 – Tamper added for HW version 4, possibility to report opening of the case (LIFT8-999, LIFT8-989, LIFT8-1029)
Lift8 – Mechanism against unauthorized authentication by repeated access looking for and and keyword by blocking interface (LIFT8-1144)
Lift8 – Protection against unauthorized debug processing (LIFT8-1179)
Lift8 – Protecting user data by replacing after factory reset (LIFT8-1194, LIFT8-1195, LIFT8-1196)
Lift8 LTE - New SDK for LTE module used – RED compliant (Lift8-1346)
Bugfixes
Lift8 – Lost IP connection when static IP address set – fixed (LIFT8-1090)
Lift8 – Incorrect LED signalization when connection in roaming active (LIFT8-816, LIFT8-1078)
Lift8 – Restart activated by SIP service by call is delayed for 2-3 minutes – fixed (LIFT8-1287, LIFT8-1292, LIFT8-1408)
Lift8 – Error in invite by SIP call, missing TAG fixed (LIFT8-1278, LIFT8-1399)
Lift8 – Default value for forced call changed to 30s to allow initialization of forced call according EN 81-28 in default setting (LIFT8-1388)
Lift8 LTE – Upgrade of module failed because of memory shortage – fixed (LIFT8-1333)
Version: 2.9.2 – Bugfix version
Final version: 2.9.2.0.5
Date: 17.3.2025
New features and improvements
Lift8 – Functionality of machine room communicator according EN 81-72, activation of microphone by button demanded (LIFT8-1014)
Lift8 LTE – possibility to set preferred DNS 1 and 2 added (LIFT8-1079)
Bugfixes
Lift8 – reporting identification od calling location in higher detail (LIFT8-449)
Lift8 LTE – long time period for SIM logging for some operators – fixed by longer timeout for critical operations (LIFT8-1081)
Control panel – Notification of license expiration of Lift8 server added, correct message when license expired displayed, login with expired license allowed with limited functionality (LIFT8-576, LIFT8-847, LIFT8-849, LIFT8-568, LIFT8-1232)
Communicator – limits for setting of port numbers replaced (LIFT8-523)
Lift8 server – Expiration of license correctly reported (LIFT8-868, LIFT8-1034)
Version: 2.9.0 – Evacuation scenario support, control center capacity increase
Final version: 2.9.0.0.2
Date: 6.12.2024
New features and improvements
Lift8 – evacuation mode available, up to 64 communication units, driven from connected IP phone – see manual for details (LIFT8-931, LIFT8-932, LIFT8-933, LIFT8-934, LIFT8-946, LIFT8-949, LIFT8-953, LIFT8-1036)
Lift8 – support of two Fireman units in one shaft available (LIFT8-1013)
Lift8 LTE – possibility to set PAP, CHAP authorization for wireless connection added (LIFT8-1052)
Control panel – counter of control and alarm call added (Lift8-776, Lift8-1038)
Lift8 server, communicator, control panel – improvements to increase number of connected devices up to 5000 units with keeping acceptable response for demanded operations (Lift8-350, Lift8-839, Lift8-865, Lift8-908)
Lift8 Control panel, Communicator – listing of information organized by groups in alphabetic order instead of time of recording – better orientation in listings (LIFT8-524)
Bugfixes
Control panel – increased number of control calls and reports to be registered to support traffic for higher number of connected devices (Lift8-882, Lift8-883).
Communicator – global map functionality switched off because of issues with map source and wrong function of displaying for 100+ points in map. Plam to solve this issue in future (LIFT8-843, LIFT8-1032).
Communicator – acceptation of identification number for incoming call with prefix * to be able to accept signaling from some SIP connection providers (LIFT8-708).
Communicator, Lift8 server – high number of registered control calls and alarm calls (about 50 000+) resulted into Lift8 server crash when higher amount of incoming calls occur concurrently (Lift8-883)
Version: 2.8.7 – 100 Mb LAN connection
Final version: 2.8.7.33.33
Date: 24.4.2024
New features and improvements
Lift8 – support for LAN communication board 100 Mb added (LIFT8-595, LIFT8-631)
Lift8 – second DNS server setting available (LIFT8-647, LIFT8-665)
Service tool - configurable space between DTMF tones during configuration to allow setting when issues with DTMF transmitting occur (LIFT8-677)
Service tool – changed provider of map source (LIFT8-734, LIFT8-701)
LiftIP1 – Incoming call by default configuration, ability to switch to voice menu by DTMF 9 (LIFT8-155)
Bugfixes
Lift8 – incorrect message about end of button stuck error when alarm activated – fixed (LIFT8-640, LIFT8-327)
Lift8 – error of wireless module registration fixed (LIFT8-745)
Lift8 LTE – MBN profile activation check after restart – improved reliability of VoLTE calls (LIFT8-676)
Lift8 LTE – upgrade of central unit blocked when SIM with PIN inserted and incorrect PIN set in Lift8 (LIFT8-667)
Lift8 LTE – change of SIP availability according to 2G/4G technology changes (LIFT8-675, LIFT8-753)
LIFT8 LTE – when LTE module inserted, upgrade from older versions which doesn’t support LTE module is not possible - fixed (LIFT8-683)
LIFT8 LTE – module restart after VoLTE activation on SIM – necessary for VoLTE activation (LIFT8-754)
Service tool – configuration blocked during loading to prevent data damage (LIFT8-662)
Service tool – visualization of line speed for LAN corrected after connecting device, no restart of lift8 needed (LIFT8-723)
Service tool – unsuccessful FW upgrade with LTE module thru USB (LIFT8-791)
Service tool – compatibility of different versions of service tool and L8-server allowed (LIFT8-569)
L8-Server – incorrect setting if SIP domain – used parameter from SIP server (LIFT8-795, LIF8-798)
L8-Server – incorrect length of CLIP (less then minimal length 5 digits) results in server restart – fixed (LIFT8-680)
Version: 2.8.5 – LTE support
Final version: 2.8.5.33.28
Date: 27.11.2023
New features and improvements
Lift8 - France language added to voice menu (LIFT8-527)
Lift8 – Support for LTE module integration and communication (LIFT8-110), (LIFT8-111), (LIFT8-112), (LIFT8-116), (LIFT8-121), (LIFT8-130), (LIFT8-137), (LIFT8-138), (LIFT8-140), (LIFT8-374)
Lift8 – SIP call using LTE module and wireless data connection implemented, direction of call defined by prefix (LIFT8-123), (LIFT8-124), (LIFT8-125), (LIFT8-114), (LIFT8-128), (LIFT8-134), (LIFT8-553), (LIFT8-634)
Lift8 – VoLTE call support using LTE module (LIFT8-117)
Lift8 – SMS services added to support LTE module (LIFT8-444)
Lift8 – Data connection support for LTE module (LIFT8-122)
Lift8 – Firmware in LTE module upgrade support (LIFT8-136)
Lift8 – LED functionality changed to support new features connected with LTE module use, description of new functionality in user manual (LIFT8-591)
Lift8 – Compressing of log files configured, block compressed when size 10MB reached (LIFT8-528)
Lift8 – Reporting of LTE module FW version, both the application FW and module FW, adding to log (LIFT8-582), (LIFT8-587)
Lift8 – Restart of LTE module when the malfunction detected, including logging of this situation with details allowing troubleshooting (LIFT8-108)
Service tool – SIP and VoLTE status visualization when LTE module assembled (LIFT8-435), (LIFT8-543)
Service tool – Reset for I/O module added to set default settings (LIFT8-359)
L8-Server – Repeating unsuccessful registration attempt till restart of application fixed (LIFT8-337)
Bugfixes
Lift8 - Change in checking call DTMF timing, unwanted space fixed (LIFT8-445)
Lift8 – Incorrect DTMF signaling during alarm call fixed, timing of signals for call end changed (LIFT8-446)
Lift8 – Watchdog for SIP connection on Ethernet port added, restart of SIP engine when registration failed (LIFT8-424), (LIFT8-309)
Lift8 – Day of week for checking call functionality fixed (LIFT8-251)
Lift8 – Default time setting from programming tool by DTMF fixed (LIFT8-333)
Lift8 – Parameter ‘day of week’ (986) shifted, beginning of week now Monay (LIFT8-325)
Lift8 – Default battery expiration time changed from 3 years to 2 years, according standards (LIFT8-632)
Lift8 – When PIN for SIM is filled with incorrect value, the PIN is after restart repeated till SIM blocked and PUK needed, now blocking of SIM avoided and wrong PIN indicated by LED (LIFT8-635)
Service tool – Beep notification of I/O module, input and output divided (LIFT8-330)
Service tool – Popup notification of I/O module status can result in application crash, fixed (LIFT8-425)
Service tool – Filtering of connection status fixed (LIFT8-464)
Service tool – Connection attempt during device factory reset results in impossibility of later connection, fixed (LIFT8-439)
Communicator – error in compatibility of database resulting to impossibility to save time setting fixed (LIFT8-511)
Communicator – change in PJSIP licensing done because of different mode of use (LIFT8-418)
Communicator - License politics error fixed, real status of license displayed (LIFT8-522)
Control panel – Incorrect export of Operational Calls report – format error fixed (LIFT8-410), (LIFT8-411)
Control panel – Export of alarm call identification file corrected (LIFT8-430)
Control panel – Incorrect way for new group creation by superuser in another group fixed (LIFT8-381)
Control panel – License politics error fixed, group licenses working after expiration (LIFT8-520), (LIFT8-517), (LIFT8-518)
Control panel – Communication with Lift8 during the call may result in application crash, fixed (LIFT8-611)
Graphic of tools – Resolution of application window setting changed (LIFT8-513)
All tools – After replacing from computer some empty directories resists, fixed (LIFT8-536)
Whole system – 2N logo changed (LIFT8-419)
Version: 2.8.4 - Schmitt
Final version: 2.8.4.33.21
Date: 15.5.2023
New features and improvements
Change in licensing – control of connected devices, whether the amount agrees with license, timing of trial time period improved (LIFT8-438), (LIFT-486)
E-mail notification of exceeding number of licenses added (LIFT8-488)
Bugfixes
Fixed errors in German translation for service tool (LIFT8-458)
Lift8 - Voice menu for Latin America (Spain) added (LIFT8-366)
Service tool – Fixed position of parameter groups, independently on languages (LIFT8-375)
L8 server - Support of LiftIP2 on Lift8 server (LIFT8-326)
Communicator - Dual audio output added – different audio output can be set for ringing and for call, improved management of connected audio devices (LIFT8-396)
Control Panel – Increased maximal length of intercom name from 15 to 49 characters
Control Panel – Specific response (Custom) to Lift8 to confirm Checking call, Alarm call and Call to Lift8 added (LIFT8-393, LIFT8-394)
Bugfixes
Fixed translation in tool texts and hints (LIFT8-373, LIFT8-200, LIFT8-372)
Fixed issues in manuals and in references to manual in tools (LIFT8-334, LIFT8-335)
Lift8, LiftIP – Support of SIP proxy registration after change in Netstar (LIFT8-391, LIFT8-405)
Service tool - Wrong functionality of calendar, when month changed, day of weeks stays from last month (LIFT8-328)
LiftIP – Checking call timeout can result to incorrect end of call when registration during the waiting changes (LIFT8-403)
LiftIP – Finding in logs improved, wrong function of help fixed (LIFT8-245)
Service tool - Selection of connection in service tool for LiftIP selects more than one connection (LIFT8-361)
Service tool – Hidden keyword for parameter 1122 – keyword for RTSP connection to camera in service tool (LIFT8-305)
Service tool – Improved search in logs, now is case sensitive (LIFT8-371)
Service tool – Graphical view to configuration fixed (LIFT8-380)
L8 Server – MapQuest API service change supported to keep map functionality unchanged (LIFT8-388)
L8 Server – Setting detail of server fixed (LIFT8-515)
Communicator - During incoming call to Communicator, the map is not visible (LIFT8-347)
Communicator – Wrong position of intercom position on map, when windows size changed, improved accuracy of position (LIFT8-316, LIFT8-329, LIFT8-360)
Communicator – Incorrect setting of audio device for input and output (LIFT8-397)
Communicator – Incorrect displaying of names of audio devices – 32 characters only (LIFT8-398)
Communicator – Adding new Lift8 fails in specific circumstances (LIFT8-401)
Control Panel - List of intercoms in Control panel doesn’t show added intercom before refresh, not full view to all intercoms as admin without selected group of intercom (LIFT8-356)
Control Panel - Configuration of maps available to prevent issues connected with end of service MapQuest (LIFT8-363)
Control Panel - Fixed error in setting of test E-mail (LIFT8-302)
Control Panel – CPC Antenna 2N Extension support bug fixed (LIFT8-315)
Control Panel – Specific response to Lift8 to confirm Checking call, Alarm call and Call to Lift8 fixed (LIFT8-393, LIFT8-394)
Control Panel – ID extraction from CPC Antenna 2N ext. protocol fixed (LIFT8-357)
Control Panel – Export of alarm call has missing information about Agent, when the value is Server (LIFT8-343)
Control Panel – Export of call from intercom detail shows only test call (LIFT8-407)
Version: 2.8.3
Final version: 2.8.3.33.14
Date: 28.6.2022
New features and improvements
Lift8 – Identification of lift shaft in alarm call by voice message. (Lift8-25)
Lift8 – Alarm button self-test added, special type of alarm button needed. (Lift8-27, LIFT8-209)
Lift8 – Italian voice menu added. (LIFT8-31)
Lift8 – Polish voice menu added. (LIFT8-185)
Lift8 - Possibility to set siren output on the machine room communicator when alarm call activated. (LIFT8-33)
Lift8 - Information E-mail from alarm call to Control Panel (additional functionality to E-mail notification about checking call). (LIFT8-12)
LiftIP – Italian voice menu added. (LIFT8-32)
All tools - GUI of Lift8 supports seven languages: CZE, ENG, ESP, GER, FRA, ITA, RU. (LIFT8-6)
Communicator - Plan or map of the area with marked locality of lift is visible during emergency call. (LIFT8-7)
Communicator - Possibility to set keyboard shortcuts for define actions in Communicator to allow use of keyboard emulator. (LIFT8-20)
Communicator – Test of microphone connection added. (Lift8-189)
Bugfixes
Installation - Missing DLL libraries when Lift8 tools installed, mostly connected with Win10. (LIFT8-59, LIFT8-89)
Lift8 - Time overflow error – when Lift8 runs 49,7 days, timer overflow can result into unexpected irregularities in function. (LIFT8-36)
Lift8 – Alarm call with CPC Antena support failed in intercom identification – first number lost. (LIFT8-197)
Lift8 - Time synchronization by SNTP on by default – log with correct timing supported. (LIFT8-56)
LiftIP – issue with Payload Type for DTMF. (LIFT8-159, LIFT8-19)
LiftIP – communication issue with AVAYA – too long packets. (LIFT8-42)
LiftIP – After change of configuration confirmed by password, wrong password reported. (LIFT8-254)
Service tool - doesn’t correctly display all parameters depending on screen resolution. (LIFT8-52, LIFT8-147)
Service tool – incorrect filter, only numbers applied. (LIFT8-257)
Service tool – Device info error when older device connected because of missing hwinfo. (LIFT8-249)
L8 Server - Special characters for example - !@#$% - can’t be used as part of the SIP password. (LIFT8-10)
L8 Server -after change of IP address on connected PC registration failure occur. (LIFT8-90)
L8 Server – Error occur when E-mail report sent to three or more address. (Lift8-344)
L8 Server – Empty E-mail address for notification results into application lock or sending error. (LIFT8-247, LIFT8-301)
Communicator - Deleting of Control panel user, who is registered in Communicator results In lock of the application. (LIFT8-24)
Communicator - crash when display resolution changes. (Lift8-146)
Communicator - direct call user is not correctly signed off after user delete performed. (LIFT8-148)
Communicator - doesn’t allow moving of map by scrollbar. (LIFT8-171)
Communicator – when size of map changed, the change is not permanent. (LIFT8-252)
Communicator - crash when display resolution changes. (Lift8-146)
Communicator - direct call user is not correctly signed off after user delete performed.
Communicator - doesn’t allow moving of map by scrollbar. (LIFT8-171)
Communicator – when size of map changed, the change is not permanent. (LIFT8-252)
Communicator - doesn’t allow moving of map by scrollbar. (LIFT8-171)
Communicator – when size of map changed, the change is not permanent. (LIFT8-252)
Communicator - doesn’t allow moving of map by scrollbar. (LIFT8-171)
Communicator – when size of map changed, the change is not permanent. (LIFT8-252)
Communicator – When filtering by length of call or agent used, application crashes. (LIFT8-313)
Control panel - When Call server is set, correct visualization of all details in graphics is not guaranteed. (LIFT8-47)
Control panel – forced save of storage setting before next step can be performed. (LIFT8-158)
Control panel – When more intercoms on one plan placed, it is not possible to remove any of them. (LIFT8-217)
Control Panel – Test of storge availability, if lost, warning generated. (LIFT8-223)
Control Panel – searching of intercom by address in map failed. (LIFT8-92)
2N Access Commander version 3.6 introduces a faster way to configure devices through device templates, a centralised call log for intercoms, a dedicated Company Admin role for managing organisation-level settings, and several quality-of-life improvements throughout the system.
Bugs fixed in 3.6.1:
Addresses a critical bug that a ects a small number of Access Commander Box installations and My2N app pairing.
New Features:
Device Templates
Admins can now save and edit the configuration file of any 2N OS–based device and apply it to other devices individually or in bulk.
Create templates from an existing device, a configuration file, or a device backup.
Templates can include only selected parts of the configuration, allowing controlled or
limited deployments.
Before a template is applied, Access Commander automatically creates a backup of the
target device.
Templates can be downloaded and uploaded to existing or future Access Commander
installations.
Important:
Templates are an advanced feature. Always review the configuration parameters and
values before applying a template.
Some parameters are automatically excluded (for example, static IP address) to prevent
unwanted duplication.
Certain parameters are highlighted with warnings; verify these carefully before
deployment.
Templates are supported only on 2N OS–based IP devices. They are not supported on 2N
Electronic Locks or 2N Indoor Touch.
Call logs
Call logs provide administrators with a single, unified view of incoming and outgoing calls from all intercoms and elevator communication devices.
One consolidated list: Calls from every managed device appear together.
Door unlock during a call: If a door is opened during a call, the event is recorded in both
the Call log and the Access log, and clearly marked with an icon.
Optional CAM logs: Enable CAM logs to capture images from intercoms when a call
begins.
Please note: If both the caller and receiver are managed by Access Commander, the system
may record two entries for the same call — one outgoing and one incoming. Call logs are
created in Access Commander once a call is terminated.
Company admin role
The new Company Admin role gives designated users control over company-specific settings that previously required full administrator rights. This role can be combined with others such as User Manager or Visitor Manager, depending on requirements. Company Admin rights include:
Viewing system log events related to their company.
Managing company details such as the name, default language, working hours,
holidays, and visitor settings.
Creating and editing email templates.
Managing LDAP user synchronisation.
Initiating lockdown of company devices (intercoms and access units).
Other improvements:
Pairing with the My2N mobile app is now faster and more secure. Users can pair the app via a QR code displayed in Access Commander or from a link or QR code sent by email. (Supported on devices running FW 2.50/3.0 and higher).
Access Commander can now be discovered on the local network using the 2N IP Utility
application, together with 2N OS and Axis devices. (Windows only; the Access
Commander IP address cannot be configured through the tool).
mDNS domain name support added. Access Commander can now be reached on the
local network at https://accesscommander.local
Network discovery features (mDNS domain and 2N IP Utility) can be disabled in
Settings>Configuration.
The linux console welcome message has been updated to include the mDNS domain in
addition to the IP address.
Access Commander now supports MIFARE DESFire cards in use by a third-party. Cards
must support anonymous application creation.
Required Device Firmware Versions for Full Feature Support
2N IP Intercoms: 2.50.x/3.2.x
2N Access Units: 2.50.x/3.2.x
2N Answering Units: 2.50.x/3.2.x
2N Emergency Elevator Communicators: 3.2.x
Note - some older 2N devices cannot support versions higher than 2.50.
Minimum Supported Firmware Versions (Devices running firmware older than these versions will not sync with Access Commander)
2N IP Intercoms: 2.47.x
2N Access Unit: 2.47.x
2N Answering Units 2.47.x
2N Indoor Touch 2.0: 4.3.x (Devices running earlier versions will be disabled in Access
Commander)
2N Indoor Touch 1.0 is not supported in Access Commander
API Changes
2N Access Commander version 3.6 introduces a faster way to configure devices through device templates, a centralised call log for intercoms, a dedicated Company Admin role for managing organisation-level settings, and several quality-of-life improvements throughout the system.
Bugs fixed in 3.6.1:
Addresses a critical bug that a ects a small number of Access Commander Box installations and My2N app pairing.
New Features:
Device Templates
Admins can now save and edit the configuration file of any 2N OS–based device and apply it to other devices individually or in bulk.
Create templates from an existing device, a configuration file, or a device backup.
Templates can include only selected parts of the configuration, allowing controlled or
limited deployments.
Before a template is applied, Access Commander automatically creates a backup of the
target device.
Templates can be downloaded and uploaded to existing or future Access Commander
installations.
Important:
Templates are an advanced feature. Always review the configuration parameters and
values before applying a template.
Some parameters are automatically excluded (for example, static IP address) to prevent
unwanted duplication.
Certain parameters are highlighted with warnings; verify these carefully before
deployment.
Templates are supported only on 2N OS–based IP devices. They are not supported on 2N
Electronic Locks or 2N Indoor Touch.
Call logs
Call logs provide administrators with a single, unified view of incoming and outgoing calls from all intercoms and elevator communication devices.
One consolidated list: Calls from every managed device appear together.
Door unlock during a call: If a door is opened during a call, the event is recorded in both
the Call log and the Access log, and clearly marked with an icon.
Optional CAM logs: Enable CAM logs to capture images from intercoms when a call
begins.
Please note: If both the caller and receiver are managed by Access Commander, the system
may record two entries for the same call — one outgoing and one incoming. Call logs are
created in Access Commander once a call is terminated.
Company admin role
The new Company Admin role gives designated users control over company-specific settings that previously required full administrator rights. This role can be combined with others such as User Manager or Visitor Manager, depending on requirements. Company Admin rights include:
Viewing system log events related to their company.
Managing company details such as the name, default language, working hours,
holidays, and visitor settings.
Creating and editing email templates.
Managing LDAP user synchronisation.
Initiating lockdown of company devices (intercoms and access units).
Other improvements:
Pairing with the My2N mobile app is now faster and more secure. Users can pair the app via a QR code displayed in Access Commander or from a link or QR code sent by email. (Supported on devices running FW 2.50/3.0 and higher).
Access Commander can now be discovered on the local network using the 2N IP Utility
application, together with 2N OS and Axis devices. (Windows only; the Access
Commander IP address cannot be configured through the tool).
mDNS domain name support added. Access Commander can now be reached on the
local network at https://accesscommander.local
Network discovery features (mDNS domain and 2N IP Utility) can be disabled in
Settings>Configuration.
The linux console welcome message has been updated to include the mDNS domain in
addition to the IP address.
Access Commander now supports MIFARE DESFire cards in use by a third-party. Cards
must support anonymous application creation.
Required Device Firmware Versions for Full Feature Support
2N IP Intercoms: 2.50.x/3.2.x
2N Access Units: 2.50.x/3.2.x
2N Answering Units: 2.50.x/3.2.x
2N Emergency Elevator Communicators: 3.2.x
Note - some older 2N devices cannot support versions higher than 2.50.
Minimum Supported Firmware Versions (Devices running firmware older than these versions will not sync with Access Commander)
2N IP Intercoms: 2.47.x
2N Access Unit: 2.47.x
2N Answering Units 2.47.x
2N Indoor Touch 2.0: 4.3.x (Devices running earlier versions will be disabled in Access
Commander)
2N Indoor Touch 1.0 is not supported in Access Commander
API Changes
2N OS version 2.50.1 for 2N Intercoms includes the following changes
Essential Corrections
Fixed an issue with 2N Electronic Locks that limited the device directory to 2000 users.
Fixed an issue where the ProfileStateChanged block in Automation functions caused an error after reboot.
Added support for a new Vbus display revision.
Improved ACS connection stability.
Updated several internal libraries.
Important bug fixes.
2N OS version 2.50.0 for 2N Intercoms includes the following changes
Precautions to be taken during update to FW version 2.50.x
For security reasons, network settings can no longer be modified using 2N Network Scanner.
All 2N OS devices (except those on the original platform: IP Vario, IP Force, IP Safety, IP Solo, IP/LTE Verso, IP Base, IP Uni, IP Audio Kit, IP Video Kit, Access Unit, SIP Speaker) can no longer be downgraded below version 2.47.0 after updating.
Devices no longer accept certificates signed with 1024-bit RSA keys. These certificates are removed during the update and must be replaced with certificates using at least 2048-bit RSA or ECC keys. Services relying on weaker certificates will stop functioning, and a warning will appear next to the certificate selection parameter in the web interface.
In EAP-TLS mode, 802.1x no longer supports RADIUS certificates containing the `id-kp-clientAuth` Extended Key Usage. If such certificates are used, they will be rejected after the update, resulting in the device being unable to authenticate and connect to the network.
Due to essential authentication updates for an improved user experience, you must restart the ACS server to restore connectivity for devices upgraded from a version lower than 2.49.0 to version 2.49.0 or higher.
New Functions and Improvements
Reception of `In-Band (Audio)` DTMF is now disabled by default to improve resilience against malicious attacks.
STUN support has been added and can be configured under `Calling > SIP # > Configuration`.
Added support for the Japanese language in the display UI of Answering Units and IP Style.
Support for 2N Electronic Locks is now included as part of the standard firmware release.
Essential Corrections
Improved compatibility of outgoing H.264 and H.265 video streams.
Private keys are no longer exposed via `GET /api/mobilekey/config`.
Updated several internal libraries.
Web configuration pages for Automation features now load correctly even when the device is offline (without an active internet connection).
Eliminated occasional audio distortions on IP Uni and IP Audio Kit devices.
Fixed an intermittent issue where audio inputs could become swapped on IP Uni and IP Audio Kit devices.
Devices no longer crash when a user with a limited validity period presents their card, provided the associated RFID reader extension module has `Door` set to `Not used`.
Cached DNS entries for SIP registrars now expire immediately and correctly when the registrar IP address changes, preventing registration failures.
Fixed an issue where devices could lose and reacquire their IP address via DHCP twice after a factory reset and subsequent reboots.
Resolved a device crash that could occur when sending emails using specific SMTP server configurations.
The `snmpget` function now works correctly on devices using SNMPv3.
Devices now correctly process `Too Brief` SIP responses during registration and immediately apply the updated expiry period.
Fixed device crashes caused by specific malformed or non-standard ONVIF requests.
Corrected an issue where video resolution could be incorrectly limited when selecting lower bitrate settings for the H.265 codec.
Added a limited-range mode to the WaveKey opening algorithm to prevent unintended door openings from excessive distance.
PEAP MSCHAPv2 authentication is now fully functional and reliable across all supported models.
Eliminated a condition that could cause SIP registration to become permanently stuck in the unregistered state.
2N OS version 2.50.0 for 2N Intercoms includes the following changes
Precautions to be taken during update to FW version 2.50.x
Devices no longer emit audible beeps during boot or network state changes by default. If required, this behavior can be enabled under `Hardware > Audio > Startup and Network States Signalization`.
For security reasons, network settings can no longer be modified using 2N Network Scanner.
All 2N OS devices (except those on the original platform: IP Vario, IP Force, IP Safety, IP Solo, IP/LTE Verso, IP Base, IP Uni, IP Audio Kit, IP Video Kit, Access Unit, SIP Speaker) can no longer be downgraded below version 2.47.0 after updating.
Devices no longer accept certificates signed with 1024-bit RSA keys. These certificates are removed during the update and must be replaced with certificates using at least 2048-bit RSA or ECC keys. Services relying on weaker certificates will stop functioning, and a warning will appear next to the certificate selection parameter in the web interface.
In EAP-TLS mode, 802.1x no longer supports RADIUS certificates containing the `id-kp-clientAuth` Extended Key Usage. If such certificates are used, they will be rejected after the update, resulting in the device being unable to authenticate and connect to the network.
New Functions and Improvements
Reception of `In-Band (Audio)` DTMF is now disabled by default to improve resilience against malicious attacks.
STUN support has been added and can be configured under `Calling > SIP # > Configuration`.
Added support for the Japanese language in the display UI of Answering Units and IP Style.
Support for 2N Electronic Locks is now included as part of the standard firmware release.
Essential Corrections
Improved compatibility of outgoing H.264 and H.265 video streams.
Private keys are no longer exposed via `GET /api/mobilekey/config`.
Updated several internal libraries.
Web configuration pages for Automation features now load correctly even when the device is offline (without an active internet connection).
Eliminated occasional audio distortions on IP Uni and IP Audio Kit devices.
Fixed an intermittent issue where audio inputs could become swapped on IP Uni and IP Audio Kit devices.
Devices no longer crash when a user with a limited validity period presents their card, provided the associated RFID reader extension module has `Door` set to `Not used`.
Cached DNS entries for SIP registrars now expire immediately and correctly when the registrar IP address changes, preventing registration failures.
Fixed an issue where devices could lose and reacquire their IP address via DHCP twice after a factory reset and subsequent reboots.
Resolved a device crash that could occur when sending emails using specific SMTP server configurations.
The `snmpget` function now works correctly on devices using SNMPv3.
Devices now correctly process `Too Brief` SIP responses during registration and immediately apply the updated expiry period.
Fixed device crashes caused by specific malformed or non-standard ONVIF requests.
Corrected an issue where video resolution could be incorrectly limited when selecting lower bitrate settings for the H.265 codec.
Added a limited-range mode to the WaveKey opening algorithm to prevent unintended door openings from excessive distance.
PEAP MSCHAPv2 authentication is now fully functional and reliable across all supported models.
Eliminated a condition that could cause SIP registration to become permanently stuck in the unregistered state.
2N OS version 2.50.1 for 2N Intercoms includes the following changes
Essential Corrections
Fixed an issue with 2N Electronic Locks that limited the device directory to 2000 users.
Fixed an issue where the ProfileStateChanged block in Automation functions caused an error after reboot.
Added support for a new Vbus display revision.
Improved ACS connection stability.
Updated several internal libraries.
Important bug fixes.
2N OS version 2.50.0 for 2N Intercoms includes the following changes
Precautions to be taken during update to FW version 2.50.x
For security reasons, network settings can no longer be modified using 2N Network Scanner.
All 2N OS devices (except those on the original platform: IP Vario, IP Force, IP Safety, IP Solo, IP/LTE Verso, IP Base, IP Uni, IP Audio Kit, IP Video Kit, Access Unit, SIP Speaker) can no longer be downgraded below version 2.47.0 after updating.
Devices no longer accept certificates signed with 1024-bit RSA keys. These certificates are removed during the update and must be replaced with certificates using at least 2048-bit RSA or ECC keys. Services relying on weaker certificates will stop functioning, and a warning will appear next to the certificate selection parameter in the web interface.
In EAP-TLS mode, 802.1x no longer supports RADIUS certificates containing the `id-kp-clientAuth` Extended Key Usage. If such certificates are used, they will be rejected after the update, resulting in the device being unable to authenticate and connect to the network.
Due to essential authentication updates for an improved user experience, you must restart the ACS server to restore connectivity for devices upgraded from a version lower than 2.49.0 to version 2.49.0 or higher.
New Functions and Improvements
Reception of `In-Band (Audio)` DTMF is now disabled by default to improve resilience against malicious attacks.
STUN support has been added and can be configured under `Calling > SIP # > Configuration`.
Added support for the Japanese language in the display UI of Answering Units and IP Style.
Support for 2N Electronic Locks is now included as part of the standard firmware release.
Essential Corrections
Improved compatibility of outgoing H.264 and H.265 video streams.
Private keys are no longer exposed via `GET /api/mobilekey/config`.
Updated several internal libraries.
Web configuration pages for Automation features now load correctly even when the device is offline (without an active internet connection).
Eliminated occasional audio distortions on IP Uni and IP Audio Kit devices.
Fixed an intermittent issue where audio inputs could become swapped on IP Uni and IP Audio Kit devices.
Devices no longer crash when a user with a limited validity period presents their card, provided the associated RFID reader extension module has `Door` set to `Not used`.
Cached DNS entries for SIP registrars now expire immediately and correctly when the registrar IP address changes, preventing registration failures.
Fixed an issue where devices could lose and reacquire their IP address via DHCP twice after a factory reset and subsequent reboots.
Resolved a device crash that could occur when sending emails using specific SMTP server configurations.
The `snmpget` function now works correctly on devices using SNMPv3.
Devices now correctly process `Too Brief` SIP responses during registration and immediately apply the updated expiry period.
Fixed device crashes caused by specific malformed or non-standard ONVIF requests.
Corrected an issue where video resolution could be incorrectly limited when selecting lower bitrate settings for the H.265 codec.
Added a limited-range mode to the WaveKey opening algorithm to prevent unintended door openings from excessive distance.
PEAP MSCHAPv2 authentication is now fully functional and reliable across all supported models.
Eliminated a condition that could cause SIP registration to become permanently stuck in the unregistered state.
2N OS version 2.50.1 for 2N Intercoms includes the following changes
Essential Corrections
Fixed an issue with 2N Electronic Locks that limited the device directory to 2000 users.
Fixed an issue where the ProfileStateChanged block in Automation functions caused an error after reboot.
Added support for a new Vbus display revision.
Improved ACS connection stability.
Updated several internal libraries.
Important bug fixes.
2N OS version 2.50.0 for 2N Intercoms includes the following changes
Precautions to be taken during update to FW version 2.50.x
For security reasons, network settings can no longer be modified using 2N Network Scanner.
All 2N OS devices (except those on the original platform: IP Vario, IP Force, IP Safety, IP Solo, IP/LTE Verso, IP Base, IP Uni, IP Audio Kit, IP Video Kit, Access Unit, SIP Speaker) can no longer be downgraded below version 2.47.0 after updating.
Devices no longer accept certificates signed with 1024-bit RSA keys. These certificates are removed during the update and must be replaced with certificates using at least 2048-bit RSA or ECC keys. Services relying on weaker certificates will stop functioning, and a warning will appear next to the certificate selection parameter in the web interface.
In EAP-TLS mode, 802.1x no longer supports RADIUS certificates containing the `id-kp-clientAuth` Extended Key Usage. If such certificates are used, they will be rejected after the update, resulting in the device being unable to authenticate and connect to the network.
Due to essential authentication updates for an improved user experience, you must restart the ACS server to restore connectivity for devices upgraded from a version lower than 2.49.0 to version 2.49.0 or higher.
New Functions and Improvements
Reception of `In-Band (Audio)` DTMF is now disabled by default to improve resilience against malicious attacks.
STUN support has been added and can be configured under `Calling > SIP # > Configuration`.
Added support for the Japanese language in the display UI of Answering Units and IP Style.
Support for 2N Electronic Locks is now included as part of the standard firmware release.
Essential Corrections
Improved compatibility of outgoing H.264 and H.265 video streams.
Private keys are no longer exposed via `GET /api/mobilekey/config`.
Updated several internal libraries.
Web configuration pages for Automation features now load correctly even when the device is offline (without an active internet connection).
Eliminated occasional audio distortions on IP Uni and IP Audio Kit devices.
Fixed an intermittent issue where audio inputs could become swapped on IP Uni and IP Audio Kit devices.
Devices no longer crash when a user with a limited validity period presents their card, provided the associated RFID reader extension module has `Door` set to `Not used`.
Cached DNS entries for SIP registrars now expire immediately and correctly when the registrar IP address changes, preventing registration failures.
Fixed an issue where devices could lose and reacquire their IP address via DHCP twice after a factory reset and subsequent reboots.
Resolved a device crash that could occur when sending emails using specific SMTP server configurations.
The `snmpget` function now works correctly on devices using SNMPv3.
Devices now correctly process `Too Brief` SIP responses during registration and immediately apply the updated expiry period.
Fixed device crashes caused by specific malformed or non-standard ONVIF requests.
Corrected an issue where video resolution could be incorrectly limited when selecting lower bitrate settings for the H.265 codec.
Added a limited-range mode to the WaveKey opening algorithm to prevent unintended door openings from excessive distance.
PEAP MSCHAPv2 authentication is now fully functional and reliable across all supported models.
Eliminated a condition that could cause SIP registration to become permanently stuck in the unregistered state.
2N OS version 2.50.1 for 2N Intercoms includes the following changes
Essential Corrections
Fixed an issue with 2N Electronic Locks that limited the device directory to 2000 users.
Fixed an issue where the ProfileStateChanged block in Automation functions caused an error after reboot.
Added support for a new Vbus display revision.
Improved ACS connection stability.
Updated several internal libraries.
Important bug fixes.
2N OS version 2.50.0 for 2N Intercoms includes the following changes
Precautions to be taken during update to FW version 2.50.x
For security reasons, network settings can no longer be modified using 2N Network Scanner.
All 2N OS devices (except those on the original platform: IP Vario, IP Force, IP Safety, IP Solo, IP/LTE Verso, IP Base, IP Uni, IP Audio Kit, IP Video Kit, Access Unit, SIP Speaker) can no longer be downgraded below version 2.47.0 after updating.
Devices no longer accept certificates signed with 1024-bit RSA keys. These certificates are removed during the update and must be replaced with certificates using at least 2048-bit RSA or ECC keys. Services relying on weaker certificates will stop functioning, and a warning will appear next to the certificate selection parameter in the web interface.
In EAP-TLS mode, 802.1x no longer supports RADIUS certificates containing the `id-kp-clientAuth` Extended Key Usage. If such certificates are used, they will be rejected after the update, resulting in the device being unable to authenticate and connect to the network.
Due to essential authentication updates for an improved user experience, you must restart the ACS server to restore connectivity for devices upgraded from a version lower than 2.49.0 to version 2.49.0 or higher.
New Functions and Improvements
Reception of `In-Band (Audio)` DTMF is now disabled by default to improve resilience against malicious attacks.
STUN support has been added and can be configured under `Calling > SIP # > Configuration`.
Added support for the Japanese language in the display UI of Answering Units and IP Style.
Support for 2N Electronic Locks is now included as part of the standard firmware release.
Essential Corrections
Improved compatibility of outgoing H.264 and H.265 video streams.
Private keys are no longer exposed via `GET /api/mobilekey/config`.
Updated several internal libraries.
Web configuration pages for Automation features now load correctly even when the device is offline (without an active internet connection).
Eliminated occasional audio distortions on IP Uni and IP Audio Kit devices.
Fixed an intermittent issue where audio inputs could become swapped on IP Uni and IP Audio Kit devices.
Devices no longer crash when a user with a limited validity period presents their card, provided the associated RFID reader extension module has `Door` set to `Not used`.
Cached DNS entries for SIP registrars now expire immediately and correctly when the registrar IP address changes, preventing registration failures.
Fixed an issue where devices could lose and reacquire their IP address via DHCP twice after a factory reset and subsequent reboots.
Resolved a device crash that could occur when sending emails using specific SMTP server configurations.
The `snmpget` function now works correctly on devices using SNMPv3.
Devices now correctly process `Too Brief` SIP responses during registration and immediately apply the updated expiry period.
Fixed device crashes caused by specific malformed or non-standard ONVIF requests.
Corrected an issue where video resolution could be incorrectly limited when selecting lower bitrate settings for the H.265 codec.
Added a limited-range mode to the WaveKey opening algorithm to prevent unintended door openings from excessive distance.
PEAP MSCHAPv2 authentication is now fully functional and reliable across all supported models.
Eliminated a condition that could cause SIP registration to become permanently stuck in the unregistered state.
2N OS version 2.50.1 for 2N Intercoms includes the following changes
Essential Corrections
Fixed an issue with 2N Electronic Locks that limited the device directory to 2000 users.
Fixed an issue where the ProfileStateChanged block in Automation functions caused an error after reboot.
Added support for a new Vbus display revision.
Improved ACS connection stability.
Updated several internal libraries.
Important bug fixes.
2N OS version 2.50.0 for 2N Intercoms includes the following changes
Precautions to be taken during update to FW version 2.50.x
For security reasons, network settings can no longer be modified using 2N Network Scanner.
All 2N OS devices (except those on the original platform: IP Vario, IP Force, IP Safety, IP Solo, IP/LTE Verso, IP Base, IP Uni, IP Audio Kit, IP Video Kit, Access Unit, SIP Speaker) can no longer be downgraded below version 2.47.0 after updating.
Devices no longer accept certificates signed with 1024-bit RSA keys. These certificates are removed during the update and must be replaced with certificates using at least 2048-bit RSA or ECC keys. Services relying on weaker certificates will stop functioning, and a warning will appear next to the certificate selection parameter in the web interface.
In EAP-TLS mode, 802.1x no longer supports RADIUS certificates containing the `id-kp-clientAuth` Extended Key Usage. If such certificates are used, they will be rejected after the update, resulting in the device being unable to authenticate and connect to the network.
Due to essential authentication updates for an improved user experience, you must restart the ACS server to restore connectivity for devices upgraded from a version lower than 2.49.0 to version 2.49.0 or higher.
New Functions and Improvements
Reception of `In-Band (Audio)` DTMF is now disabled by default to improve resilience against malicious attacks.
STUN support has been added and can be configured under `Calling > SIP # > Configuration`.
Added support for the Japanese language in the display UI of Answering Units and IP Style.
Support for 2N Electronic Locks is now included as part of the standard firmware release.
Essential Corrections
Improved compatibility of outgoing H.264 and H.265 video streams.
Private keys are no longer exposed via `GET /api/mobilekey/config`.
Updated several internal libraries.
Web configuration pages for Automation features now load correctly even when the device is offline (without an active internet connection).
Eliminated occasional audio distortions on IP Uni and IP Audio Kit devices.
Fixed an intermittent issue where audio inputs could become swapped on IP Uni and IP Audio Kit devices.
Devices no longer crash when a user with a limited validity period presents their card, provided the associated RFID reader extension module has `Door` set to `Not used`.
Cached DNS entries for SIP registrars now expire immediately and correctly when the registrar IP address changes, preventing registration failures.
Fixed an issue where devices could lose and reacquire their IP address via DHCP twice after a factory reset and subsequent reboots.
Resolved a device crash that could occur when sending emails using specific SMTP server configurations.
The `snmpget` function now works correctly on devices using SNMPv3.
Devices now correctly process `Too Brief` SIP responses during registration and immediately apply the updated expiry period.
Fixed device crashes caused by specific malformed or non-standard ONVIF requests.
Corrected an issue where video resolution could be incorrectly limited when selecting lower bitrate settings for the H.265 codec.
Added a limited-range mode to the WaveKey opening algorithm to prevent unintended door openings from excessive distance.
PEAP MSCHAPv2 authentication is now fully functional and reliable across all supported models.
Eliminated a condition that could cause SIP registration to become permanently stuck in the unregistered state.
2N OS version 2.50.1 for 2N Intercoms includes the following changes
Essential Corrections
Fixed an issue with 2N Electronic Locks that limited the device directory to 2000 users.
Fixed an issue where the ProfileStateChanged block in Automation functions caused an error after reboot.
Added support for a new Vbus display revision.
Improved ACS connection stability.
Updated several internal libraries.
Important bug fixes.
2N OS version 2.50.0 for 2N Intercoms includes the following changes
Precautions to be taken during update to FW version 2.50.x
For security reasons, network settings can no longer be modified using 2N Network Scanner.
All 2N OS devices (except those on the original platform: IP Vario, IP Force, IP Safety, IP Solo, IP/LTE Verso, IP Base, IP Uni, IP Audio Kit, IP Video Kit, Access Unit, SIP Speaker) can no longer be downgraded below version 2.47.0 after updating.
Devices no longer accept certificates signed with 1024-bit RSA keys. These certificates are removed during the update and must be replaced with certificates using at least 2048-bit RSA or ECC keys. Services relying on weaker certificates will stop functioning, and a warning will appear next to the certificate selection parameter in the web interface.
In EAP-TLS mode, 802.1x no longer supports RADIUS certificates containing the `id-kp-clientAuth` Extended Key Usage. If such certificates are used, they will be rejected after the update, resulting in the device being unable to authenticate and connect to the network.
Due to essential authentication updates for an improved user experience, you must restart the ACS server to restore connectivity for devices upgraded from a version lower than 2.49.0 to version 2.49.0 or higher.
New Functions and Improvements
Reception of `In-Band (Audio)` DTMF is now disabled by default to improve resilience against malicious attacks.
STUN support has been added and can be configured under `Calling > SIP # > Configuration`.
Added support for the Japanese language in the display UI of Answering Units and IP Style.
Support for 2N Electronic Locks is now included as part of the standard firmware release.
Essential Corrections
Improved compatibility of outgoing H.264 and H.265 video streams.
Private keys are no longer exposed via `GET /api/mobilekey/config`.
Updated several internal libraries.
Web configuration pages for Automation features now load correctly even when the device is offline (without an active internet connection).
Eliminated occasional audio distortions on IP Uni and IP Audio Kit devices.
Fixed an intermittent issue where audio inputs could become swapped on IP Uni and IP Audio Kit devices.
Devices no longer crash when a user with a limited validity period presents their card, provided the associated RFID reader extension module has `Door` set to `Not used`.
Cached DNS entries for SIP registrars now expire immediately and correctly when the registrar IP address changes, preventing registration failures.
Fixed an issue where devices could lose and reacquire their IP address via DHCP twice after a factory reset and subsequent reboots.
Resolved a device crash that could occur when sending emails using specific SMTP server configurations.
The `snmpget` function now works correctly on devices using SNMPv3.
Devices now correctly process `Too Brief` SIP responses during registration and immediately apply the updated expiry period.
Fixed device crashes caused by specific malformed or non-standard ONVIF requests.
Corrected an issue where video resolution could be incorrectly limited when selecting lower bitrate settings for the H.265 codec.
Added a limited-range mode to the WaveKey opening algorithm to prevent unintended door openings from excessive distance.
PEAP MSCHAPv2 authentication is now fully functional and reliable across all supported models.
Eliminated a condition that could cause SIP registration to become permanently stuck in the unregistered state.
2N OS version 2.50.1 for 2N IP Access Control Systems includes the following changes
Essential Corrections
Fixed an issue with 2N Electronic Locks that limited the device directory to 2000 users.
Fixed an issue where the ProfileStateChanged block in Automation functions caused an error after reboot.
Fixed an issue where Access Unit 1.0 was unable to boot for an extended period after power loss.
Updated several internal libraries.
Important bug fixes.
2N OS version 2.50.0 for 2N IP Access Control Systems includes the following changes
Precautions to be taken during update to FW version 2.50.x
For security reasons, network settings can no longer be modified using 2N Network Scanner.
All 2N OS devices (except those on the original platform: IP Vario, IP Force, IP Safety, IP Solo, IP/LTE Verso, IP Base, IP Uni, IP Audio Kit, IP Video Kit, Access Unit, SIP Speaker) can no longer be downgraded below version 2.47.0 after updating.
Devices no longer accept certificates signed with 1024-bit RSA keys. These certificates are removed during the update and must be replaced with certificates using at least 2048-bit RSA or ECC keys. Services relying on weaker certificates will stop functioning, and a warning will appear next to the certificate selection parameter in the web interface.
In EAP-TLS mode, 802.1x no longer supports RADIUS certificates containing the `id-kp-clientAuth` Extended Key Usage. If such certificates are used, they will be rejected after the update, resulting in the device being unable to authenticate and connect to the network.
New Functions and Improvements
Support for 2N Electronic Locks is now included as part of the standard firmware release.
Essential Corrections
Private keys are no longer exposed via `GET /api/mobilekey/config`.
Updated several internal libraries.
Web configuration pages for Automation features now load correctly even when the device is offline (without an active internet connection).
Devices no longer crash when a user with a limited validity period presents their card, provided the associated RFID reader extension module has `Door` set to `Not used`.
The `snmpget` function now works correctly on devices using SNMPv3.
Fixed device crashes caused by specific malformed or non-standard ONVIF requests.
Corrected an issue where video resolution could be incorrectly limited when selecting lower bitrate settings for the H.265 codec.
Added a limited-range mode to the WaveKey opening algorithm to prevent unintended door openings from excessive distance.