# Match Axis intercom PIN length and idle timeout to the controller > Match the intercom’s PIN length and no-PIN idle timeout with the access-control unit. Keep a disabled PIN setting distinct from an ordinary length or a timing adjustment. - Canonical URL: https://update.dsesecurity.com/updates/match-axis-intercom-pin-length-and-idle-timeout-to-the-controller/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-10-30T06:05:07+00:00 - Modified: 2026-10-30T06:05:13+00:00 - Last reviewed by DSE: 2026-10-30 - Resource type: Guide - DSE priority: Advisory - Topics: Access Control, Video Surveillance - Reading time: 3 minutes ## What you need to know Match the intercom’s PIN length and no-PIN idle timeout with the access-control unit. Keep a disabled PIN setting distinct from an ordinary length or a timing adjustment. ## Potentially affected Axis intercom integrations exposing the documented PinConfiguration fields; actual intercom, controller and reader-protocol support require confirmation. ## DSE recommendation DSE recommends one shared PIN configuration record for the intercom and access-control unit before either side is changed. ## Article Bottom line: Review PIN length and the no-PIN idle timeout at both ends of the integration. Do not change the intercom’s keypad settings without the access-controller owner’s matching configuration. ## Source fact: documented behavior The [Intercom service](https://developer.axis.com/vapix/intercom/intercom-service/) says the intercom PIN configuration should match the access-control unit’s configuration. Its pinLength field specifies the digit count, with zero disabling PIN use, a maximum of 32 and a documented default of four. The pinTimeout field is the no-PIN interval before returning to idle, measured in seconds, with documented bounds of one to 60 and a default of ten. ## What the source does not establish This article reviews two documented configuration fields. It does not establish a universal PIN policy, successful controller authorization, resistance to guessing or the correct behavior of an unnamed reader protocol. Choose the actual permitted values with the access owner rather than treating documentation defaults as requirements. ## Applicability questions - Which intercom and access-control unit form the actual path? - What PIN length is approved at both ends? - What no-PIN idle interval is intended? - Is a zero length deliberate, or an unintended disabling choice? ## DSE recommendation: controlled next steps The following steps are DSE recommendations based on the cited source. DSE recommends one shared PIN configuration record for the intercom and access-control unit before either side is changed. - Ask the controller owner to identify the approved PIN length and intended idle interval. Obtain the actual current configuration from the intercom and the corresponding controller settings through supported interfaces. Record the selected reader protocol separately. Keep real PIN values out of screenshots, exported examples and the handoff worksheet. - Review the two fields independently. Use a proposed desk case in which a length change is requested but the timeout should remain unchanged. Require the operator to identify only the intended field. Include a separate case with length zero and ask whether disabling PIN use is actually authorized. Do not copy the sample values merely because a demonstration request contains them. - Plan the approved change with an isolated test identity and an attended entry point. Preserve the starting values at both ends and agree how to restore them. Apply only the necessary supported configuration update, retrieve the resulting settings and reconcile them with the controller record before judging the complete access workflow. ## Verification and evidence Proposed verification: use a temporary nonproduction PIN of the approved length without storing its digits in evidence. Observe the agreed access workflow with the controller owner. Separately perform an authorized no-PIN waiting case and record the actual return-to-idle observation against the chosen interval. Stop if the configuration readback or device behavior differs from the approved record. Have another reviewer distinguish a configuration mismatch from an authorization denial. Keep those observations separate so a working display does not close a controller-side issue. Retain sanitized field values and the actual timing observations, then remove the temporary test identity. No PIN entry, timing measurement or live access test was performed for this article. ## Official references - [Intercom service](https://developer.axis.com/vapix/intercom/intercom-service/) — Axis Communications; official VAPIX documentation. Source review completed October 30, 2026. Recheck the official source and deployment-specific applicability before changing production settings. ## Primary reference - Name: Axis Communications — Intercom service - Authority: Axis Communications - URL: https://developer.axis.com/vapix/intercom/intercom-service/ - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Match Axis intercom PIN length and idle timeout to the controller,” DSE Security, https://update.dsesecurity.com/updates/match-axis-intercom-pin-length-and-idle-timeout-to-the-controller/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.