Preview mode is ideal for installers when fine tuning the camera view during the installation. No login is required to access the camera view in preview mode. It is available only in factory defaulted state for a limited time from powering up the device.
This video demonstrates how to use preview mode.
Get started
Find the device on the network
To find Axis devices on the network and assign them IP addresses in Windows®, use AXIS IP Utility or AXIS Device Manager. Both applications are free and can be downloaded from axis.com/support.
You can use the device with the following browsers:
ChromeTM
EdgeTM
Firefox®
Safari®
Windows®
✓
✓
*
*
macOS®
✓
✓
*
*
Linux®
✓
✓
*
*
Other operating systems
*
*
*
*
✓: Recommended *: Supported with limitations
Open the device's web interface
Open a browser and type the IP address or host name of the Axis device.
If you don’t know the IP address, use AXIS IP Utility or AXIS Device Manager to find the device on the network.
Type the username and password. If you access the device for the first time, you must create an administrator account. See Create an administrator account.
For descriptions of all features and settings in the web interface of devices with AXIS OS, see AXIS OS web interface help.
Create an administrator account
The first time you log in to your device, you must create an administrator account.
The device has no default account. If you lose the password for your administrator account, you must reset the device. See Reset to factory default settings.
Secure passwords
Important
Use HTTPS (which is enabled by default) to set your password or other sensitive configurations over the network. HTTPS enables secure and encrypted network connections, thereby protecting sensitive data, such as passwords.
The device password is the primary protection for your data and services. Axis devices do not impose a password policy as they may be used in various types of installations.
To protect your data we strongly recommend that you:
Use a password with at least 8 characters, preferably created by a password generator.
Don’t expose the password.
Change the password at a recurring interval, at least once a year.
Make sure that no one has tampered with the device software
To make sure that the device has its original AXIS OS, or to take full control of the device after a security attack:
After the reset, secure boot guarantees the state of the device.
Configure and install the device.
Configure your device
This section covers all the important configurations that an installer needs to do to get the product up and running after the hardware installation has been completed.
Calibrate and run a remote speaker test
You can run a speaker test to verify from a remote location that a speaker is working as intended. The speaker performs the test by playing a series of test tones that are registered by the built-in microphone. Every time you run the test, the registered values are compared with the values that were registered during the calibration.
Note
The test must be calibrated from its mounted position at the installation site. If the speaker is moved or if its local surroundings change, for instance if a wall is built or removed, the speaker should be re-calibrated
During calibration, it is recommended that someone is physically present at the installation site to listen to the test tones and ensure that the test tones are not muffled or blocked by any unintended obstructions in the speaker’s acoustic path.
Go to the device interface > Audio > Speaker test.
To calibrate the audio device, click Calibrate.
Note
Once the Axis product is calibrated, the speaker test can be run at any time.
To run the speaker test, click Run the test.
Note
It is also possible to run the calibration by pressing the control button on the physical device. See Product overview to identify the control button.
Set up direct SIP (P2P)
VoIP (Voice over IP) is a group of technologies that enables voice and multimedia communication over IP networks. For more information, see Voice over IP (VoIP).
There are two types of setups for SIP. Direct or peer-to-peer (P2P) is one of them. Use peer-to-peer when the communication is between a few user agents within the same IP network and there is no need for extra features that a PBX-server could provide. For information on how to set it up, see Peer-to-peer SIP (P2PSIP).
Go to Communication > SIP > Settings and select Enable SIP.
To allow the device to receive incoming calls, select Allow incoming calls.
NOTICE
When you allow incoming calls, the device accepts calls from any device connected to the network. If the device is accessible from a public network or the internet, we recommend you not to allow incoming calls.
Click Call handling.
In Calling timeout, set the number of seconds that a call will last before it ends if there is no answer.
If you have allowed incoming calls, set the number of seconds before timeout for incoming calls in Incoming call timeout.
Click Ports.
Enter the SIP port number and TLS port number.
Note
SIP port – for SIP sessions. Signalling traffic through this port is non-encrypted. The default port number is 5060.
TLS port – for SIPS and TLS secured SIP sessions. Signalling traffic through this port is encrypted with Transport Layer Security (TLS). The default port number is 5061.
RTP start port – the port used for the first RTP media stream in a SIP call. The default start port is 4000. Some firewalls can block RTP traffic on certain port numbers. The port number must be between 1024 and 65535.
Click NAT traversal.
Select the protocols you want to enable for NAT traversal.
Note
Use NAT traversal when the device is connected to the network from behind a NAT router or a firewall. For more information see NAT traversal.
Click Save.
Set up SIP through a server (PBX)
VoIP (Voice over IP) is a group of technologies that enables voice and multimedia communication over IP networks. For more information, see Voice over IP (VoIP).
There are two types of setups for SIP. A PBX server is one of them. Use a PBX server when the communication should be between an infinite number of user agents within and outside the IP network. Additional features could be added to the setup depending on the PBX provider. For more information, see Private Branch Exchange (PBX).
Request the following information from your PBX provider:
User ID
Domain
Password
Authentication ID
Caller ID
Registrar
RTP start port
Go to Communication > SIP > Accounts and click + Add account.
Enter a Name for the account.
Select Registered.
Select a transport mode.
Add the account information from the PBX provider.
Click Save.
Set up the SIP settings in the same way as for peer-to-peer, see Set up direct SIP (P2P). Use the RTP start port from the PBX provider.
Create a contact
This example explains how to create a new contact in the contact list. Before you start, enable SIP in Communication > SIP.
Availability options are defined in System > Events > Schedules.
Choose the contact’s Availability. If there’s a call when the contact isn’t available, the call gets canceled unless a there’s a fallback contact.
Note
A fallback is a contact, to whom the call gets forwarded if the original contact doesn’t reply or isn’t available.
In Fallback, select None.
Click Save.
Add a call button to the display
This example explains how to configure the display to show a button that visitors can press to call the reception.
Before you start
Create the reception contact. For instructions, see Create a contact.
Go to Display > Pages.
On Default Homepage, click and select Edit.
Click + Add.
In the Type list, select Button.
In the list of contacts, select the reception.
Select a button size.
To save the button, click Save.
To save the default homepage, click Save.
Set up as reader
You can set up your intercom as a reader to allow credential holders to open the door.
By using Entry list, the intercom stores the credentials locally and can function as a standalone reader for up to fifty credential holders.
When connecting the intercom to a door controller, the intercom can still store up to fifty credentials, and if the requested credential is found in the Entry list, the intercom manages the access permissions. If a requested credential is not found in the Entry list and the Use connected door controller option is enabled, the request is forwarded to the door controller, which then manages the access permissions.
Use Entry list to allow credential holders to open the door
With Entry list, you can make it possible for credential holders to use their credentials to trigger actions, such as opening a door. This example explains how to add a credential holder who can use their card to open the door 10 times.
Prerequisites
Make sure the correct chip type is active in Reader > Chip types.
Turn on Entry list and add a credential holder:
Go to Reader > Entry list.
Turn on Use Entry list.
Click + Add credential holder.
Enter the credential holder's first and last name. The first name must be unique.
Select Card.
Swipe the credential holder's card on the device and click Get latest.
Keep the event condition Access granted.
Under Valid to, select Number of times.
In Number of times, enter 10.
Click Save.
Create a rule:
Go to System > Events.
Under Rules, click + Add a rule.
In Name, enter Open door.
In the list of conditions, select Entry list > Access granted.
In the list of actions, select I/O > Toggle I/O once.
In the list of ports, select Door.
Under State, select Active.
Set the duration to 00:00:07.
Click Save.
Set up as card reader using a door controller
Network connection
To use the intercom as a card reader, you can connect it to a door controller. The door controller stores all credentials and keeps track of who is allowed through the door. In this example we connect the devices over the network. We also modify the allowed card types.
Important
The network connection only works with Axis door controllers. To connect to a non-Axis door controller, you need to physically connect the devices with wires. See Wired connection.
Set up the intercom as a card reader
Go to Reader > Connection.
Select the VAPIX reader protocol type.
Select the protocol for communicating with the door controller.
Note
We recommend turning on Verify certificate if you’re using HTTPS.
Enter the IP address for the door controller.
Enter the credentials for the door controller.
Click Connect.
Select the entrance reader for the appropriate door.
Click Save.
Wired connection
To use the door station as a card reader, you can connect it to a door controller. The door controller stores all credentials and keeps track of who is allowed through the door. In this example, we connect the devices with wires, we use the Wiegand protocol, activate the beeper and use one I/O port for the LED. We also modify the allowed card types.
Important
Use I/O ports that are not already in use. If you use I/O ports already in use, any events created for these ports will stop working.
Before you start
Connect the intercom to a door controller.
See the electrical wiring drawings, which you can find in Connect equipment.
Configure the door controller’s hardware, using the Wiegand protocol for the reader. See the door controller’s user manual for instructions.
Set up the intercom as a card reader
Go to Reader > Connection.
Select Wiegand as protocol type.
Turn on Beeper.
Under Input for beeper, select I3.
In Input used for LED control, select 1.
Under Input for LED1, select I1.
Select what colors to use for each state.
Under Keypress format, select FourBit.
Click Save.
Go to Reader > Chip types and activate the chip types you want to use.
Note
You can keep the default set of chip types but we recommend that you modify the list according to your specific needs.
Click Add data set to specify the data sets for the different chip types.
Click Save.
Use protected data on cards to increase security
To increase security in your access control system, you can choose to use secure card data stored on some types of cards. The data is protected by a secret key. To read the card data, you need to store the secret key and other information about the card on the device.
Go to Reader > Chip types.
Under Data sets, select the chip type you want to edit and click Add data set.
Enter information about the card data. What information to enter depends on the card type and how the cards were enrolled.
If you use the OSDP or Wiegand protocols, select Use as UID to send the secure data as the UID/CSN instead of the normal card UID/CSN.
To only allow cards that comply with the specified card data to be sent to the access controller, select Required data. Cards that don't comply are silently ignored by the reader.
Click Save.
Use DTMF to show a map on the display
When a visitor makes a call from the intercom and needs directions, the person who answers can use DTMF (Dual-Tone Multi-Frequency) signaling to show a map on the intercom’s display.
This example explains how to:
Upload a map image to the intercom.
Create a page that contains the map image in the intercom.
Define the DTMF sequence in the intercom.
Set up the intercom to show the map page for 30 seconds as a response to the DTMF sequence.
Drag-and-drop an image that shows a map of the building. The recommended image resolution is 480x800 pixels, and the maximum resolution is 2048x2048 pixels.
Click Save.
Create a map page for the display
Go to Display > Pages.
Click + Add.
Type a name for the page, for example Map page.
Click + Add.
In the list of types, select Image.
Type a name for the image, for example Map image.
In the list of images, select the map image.
Click Save.
Click Save again.
Define the DTMF sequence
Go to Communication > SIP > DTMF.
Click + Add sequence.
In Sequence, type 9.
In Description, type Show map.
Select an account.
Click Save.
Create a rule
Go to System > Events > Rules and add a rule.
Type a name for the rule, for example Use DTMF to show map.
In the list of conditions, select Call > DTMF.
In the list of DTMF event IDs, select Show map.
In the list of actions, select Display > Show page.
In the list of pages, select Map page.
In Duration, enter 00:00:30 to show the map for 30 seconds.
Click Save.
The web interface
To read about all the features and settings available in the web interface of devices with AXIS OS, go to AXIS OS web interface help.
Learn more
Voice over IP (VoIP)
Voice over IP (VoIP) is a group of technologies that enables voice communication and multimedia sessions over IP networks, such as the internet. In traditional phone calls, analog signals are sent through circuit transmissions over the Public Switched Telephone Network (PSTN). In a VoIP call, analog signals are turned into digital signals to make it possible to send them in data packets across local IP networks or the internet.
In the Axis product, VoIP is enabled through the Session Initiation Protocol (SIP) and Dual-Tone Multi-Frequency (DTMF) signaling.
Example
When you press the call button on an Axis intercom, a call is initiated to one or more predefined recipients. When a recipient replies, a call is established. The voice and video is transferred through VoIP technologies.
Session Initiation Protocol (SIP)
The Session Initiation Protocol (SIP) is used to set up, maintain and terminate VoIP calls. You can make calls between two or more parties, called SIP user agents. To make a SIP call you can use, for example, SIP phones, softphones or SIP-enabled Axis devices.
The actual audio or video is exchanged between the SIP user agents with a transport protocol, for example RTP (Real-Time Transport Protocol).
You can make calls on local networks using a peer-to-peer setup, or across networks using a PBX.
Peer-to-peer SIP (P2PSIP)
The most basic type of SIP communication takes place directly between two or more SIP user agents. This is called peer-to-peer SIP (P2PSIP). If it takes place on a local network, all that’s needed are the SIP addresses of the user agents. A typical SIP address in this case would be sip:<local-ip>.
Example
User agent A - intercom. SIP address: sip:192.168.1.101
User agent B - SIP-enabled phone. SIP address: sip:192.168.1.100
You can set up the Axis intercom to call for example a SIP-enabled phone on the same network using a peer-to-peer SIP setup.
Private Branch Exchange (PBX)
When you make SIP calls outside your local IP network, a Private Branch Exchange (PBX) can act as a central hub. The main component of a PBX is a SIP server, which is also referred to as a SIP proxy or a registrar. A PBX works like a traditional switchboard, showing the client's current status and allowing for example call transfers, voicemail, and redirections.
The PBX SIP server can be set up as a local entity or offsite. It can be hosted on an intranet or by a third party provider. When you make SIP calls between networks, calls are routed through a set of PBXs, that query the location of the SIP address to be reached.
Each SIP user agent registers with the PBX, and can then reach the others by dialing the correct extension. A typical SIP address in this case would be sip:<user>@<domain> or sip:<user>@<registrar-ip>. The SIP address is independent of its IP address and the PBX makes the device accessible as long as it is registered to the PBX.
Example
sip:mydoor@company.com
sip:myspeaker@company.com
PBX sip.company.com
sip:office@company.com
When you press the call button on an Axis intercom, the call is forwarded through one or more PBXs to a SIP address either on the local IP network or over the internet.
NAT traversal
Use NAT (Network Address Translation) traversal when the Axis device is located on an private network (LAN) and you want to access it from outside of that network.
Note
The router must support NAT traversal and UPnP®.
Each NAT traversal protocol can be used separately or in different combinations depending on the network environment.
ICE The ICE Interactive Connectivity Establishment) protocol increases the chances of finding the most efficient path to successful communication between peer devices. If you also enable STUN and TURN, you improve the ICE protocol’s chances.
STUN - STUN (Session Traversal Utilities for NAT) is a client-server network protocol that lets the Axis device determine if it is located behind a NAT or firewall, and if so obtain the mapped public IP address and port number allocated for connections to remote hosts. Enter the STUN server address, for example, an IP address.
TURN - TURN (Traversal Using Relays around NAT) is a protocol that lets a device behind a NAT router or firewall receive incoming data from other hosts over TCP or UDP. Enter TURN server address and the login information.
Set up rules for events
You can create rules to make your device perform an action when certain events occur. A rule consists of conditions and actions. The conditions can be used to trigger the actions. For example, the device can start a recording or send an email when it detects motion, or show an overlay text while the device is recording.
With analytics and apps you can get more out of your Axis device. AXIS Camera Application Platform (ACAP) is an open platform that makes it possible for third parties to develop analytics and other apps for Axis devices. Apps can be preinstalled on the device, available for download for free, or for a license fee.
To find the user manuals for Axis analytics and apps, go to help.axis.com.
Axis provides a notification service with information about vulnerability and other security related matters for Axis devices. To receive notifications, you can subscribe at axis.com/security-notification-service.
Vulnerability management
To minimize customers' risk of exposure, Axis, as a Common Vulnerability and Exposures (CVE) numbering authority (CNA), follows industry standards to manage and respond to discovered vulnerabilities in our devices, software, and services. For more information about Axis vulnerability management policy, how to report vulnerabilities, already disclosed vulnerabilities, and corresponding security advisories, see axis.com/vulnerability-management.
Secure operation of Axis devices
Axis devices with factory default settings are pre-configured with secure default protection mechanisms. We recommend using more security configuration when installing the device. To learn more about Axis' approach to cybersecurity, including best practices, resources, and guidelines for securing your devices, go to axis.com/about-axis/cybersecurity.
Specifications
Product overview
Microphone (x2)
T-coil
RFID reader
Speaker
PIR sensor
Camera
Display
Light sensor
Grounding screw
Installation hinges
Power connector
Network connector
Relay connector (x2)
Status LED
I/O connector
Control button
SD card slot (microSD)
Audio connector
Reader connector
LED indicators
Status LED
Indication
Green
Steady green for normal operation.
SD card slot
NOTICE
Risk of damage to SD card. Don’t use sharp tools, metal objects, or excessive force when inserting or removing the SD card. Use your fingers to insert and remove the card.
Risk of data loss and corrupted recordings. Unmount the SD card from the device’s web interface before removing it. Don’t remove the SD card while the product is running.
This device supports microSD/microSDHC/microSDXC cards.
microSD, microSDHC, and microSDXC Logos are trademarks of SD-3C LLC. microSD, microSDHC, microSDXC are trademarks or registered trademarks of SD-3C, LLC in the United States, other countries or both.
RJ45 Ethernet connector with Power over Ethernet Plus (PoE+).
Audio connector
4-pin terminal block for audio input and output.
Function
Pin
Notes
Line in
1
Line in (mono)
GND
2
Audio ground
Line out
3
Line out
GND
4
Audio ground
Relay connector
8-pin terminal block for solid state relays that can be used in the following ways:
As a standard relay that opens and closes auxiliary circuits.
To control a lock directly.
To control a lock through a safety relay. Using a safety relay on the secure side of the door prevents hotwiring.
Function
Pin
Notes
Specifications
NO/NC
1
Normally open/normally closed For connecting relay devices. The two relay pins are galvanically separated from the rest of the circuitry.
Max current 1 A Max voltage 30 V DC
COM
2
Common
24 V DC
3
For powering auxiliary equipment. Note: This pin can only be used as power out.
Output voltage 24 V DC Max current 50 mA(1) Max current 300 mA(2)
DC ground
4
0 V DC
NO/NC
5
Normally open/normally closed For connecting relay devices. The two relay pins are galvanically separated from the rest of the circuitry.
Max current 1 A Max voltage 30 V DC
COM
6
Common
12 V DC
7
For powering auxiliary equipment. Note: This pin can only be used as power out.
Output voltage 12 V DC Max current 100 mA(3) Max current 600 mA(4)
DC ground
8
0 V DC
When powered through Power over Ethernet IEEE 802.3af/802.3at Type 1 Class 3.
When powered through Power over Ethernet Plus (PoE+) IEEE 802.3at Type 2 Class 4 or DC power input.
When powered through Power over Ethernet IEEE 802.3af/802.3at Type 1 Class 3.
When powered through Power over Ethernet Plus (PoE+) IEEE 802.3at Type 2 Class 4 or DC power input.
Reader connector
4–pin terminal block for connecting external reader.
Function
Pin
Notes
Specifications
DC ground
1
0 V DC
12 V DC
2
For powering auxiliary equipment. Note: This pin can only be used as power out.
Output voltage 12 V DC
D0/A+
3
Wiegand: DATA0 output RS485: A+
D1/B-
4
Wiegand: DATA1 output RS485: B-
I/O connector
Use the I/O connector with external devices in combination with, for example, motion detection, event triggering, and alarm notifications. In addition to the 0 VDC reference point and power (12 V DC output), the I/O connector provides the interface to:
Digital input
For connecting devices that can toggle between an open and closed circuit, for example PIR sensors, door/window contacts, and glass break detectors.
Digital output
For connecting external devices such as relays and LEDs. Connected devices can be activated by the VAPIX® Application Programming Interface, through an event or from the device’s web interface.
Function
Pin
Notes
Specifications
DC ground
1
0 VDC
DC output
2
Can be used to power auxiliary equipment. Note: This pin can only be used as power out.
12 VDC Max load = 50 mA
Configurable (Input or Output)
3–6
Digital input – Connect to pin 1 to activate, or leave floating (unconnected) to deactivate.
0 to max 30 VDC
Digital output – Internally connected to pin 1 (DC ground) when active, and floating (unconnected) when inactive. If used with an inductive load, e.g., a relay, connect a diode in parallel with the load, to protect against voltage transients.
0 to max 30 VDC, open drain, 100 mA
Example
DC ground
DC output 12 V, max 50 mA
I/O configured as input
I/O configured as output
Configurable I/O
Configurable I/O
Power connector
2-pin terminal block for DC power input. Use a Safety Extra Low Voltage (SELV) compliant limited power source (LPS) with either a rated output power limited to ≤100 W or a rated output current limited to ≤5 A.
Function
Pin
Notes
Specifications
DC ground
1
0 V DC
DC input
2
For powering controller when not using Power over Ethernet. Note: This pin can only be used as power in.
18–28 V DC, max 22 W Max load on outputs 9 W
Connect equipment
One relay powered by PoE (12V)
To check relay state, go to System > Accessories and find the relay port.
Set Normal state to:
for a fail-secure lock.
for a fail-safe lock.
Two relays powered by PoE (12V)
To check relay state, go to System > Accessories and find the relay port.
Set Normal state to:
for a fail-secure lock.
for a fail-safe lock.
One relay powered by PoE (12V) + one relay powered by external power supply
To check relay state, go to System > Accessories and find the relay port.
Set Normal state to:
for a fail-secure lock.
for a fail-safe lock.
One relay powered by PoE (12V) + one relay potential-free contact
The potential-free contact can be, for example, a door chime.
To check relay state, go to System > Accessories and find the relay port.
Set Normal state to:
for a fail-secure lock.
for a fail-safe lock.
12V fail-secure lock powered by PoE+ from intercom
To check relay state, go to System > Accessories and find the relay port.
Set Normal state to:
for a fail-secure lock.
for a fail-safe lock.
Fail-secure lock powered by external power supply
To check relay state, go to System > Accessories and find the relay port.
Set Normal state to:
for a fail-secure lock.
for a fail-safe lock.
One relay powered by PoE (24V) + one relay potential-free contact
The potential-free contact can be, for example, a door chime.
To check relay state, go to System > Accessories and find the relay port.
Set Normal state to:
for a fail-secure lock.
for a fail-safe lock.
Reader connected to door controller using OSDP
Go to Reader > Connection > Reader protocol.
Set the Reader protocol type to OSDP and click Save.
Reader connected to door controller using Wiegand
Go to Reader > Connection > Reader protocol.
Set the Reader protocol type to Wiegand.
Turn on Beeper.
In Input for beeper, select I3.
In Input used for LED control, select 1.
In Input for LED1, select I1.
Adjust other settings and click Save.
Reader connected to Axis door controller using VAPIX reader
Go to Reader > Connection > Reader protocol.
Set the Reader protocol type to VAPIX reader.
Connect to an Axis door controller.
Troubleshooting
Reset to factory default settings
Important
Reset to factory default should be used with caution. A reset to factory default resets all settings, including the IP address, to the factory default values.
To reset the product to the factory default settings:
Disconnect power from the product.
Press and hold the control button while reconnecting power. See Product overview.
Keep the control button pressed for 15–30 seconds until the status LED indicator flashes amber.
Release the control button. The process is complete when the status LED indicator turns green. If no DHCP server is available on the network, the device IP address will default to one of the following:
Devices with AXIS OS 12.0 and later: Obtained from the link-local address subnet (169.254.0.0/16)
Devices with AXIS OS 11.11 and earlier: 192.168.0.90/24
Use the installation and management software tools to assign an IP address, set the password, and access the device.
The installation and management software tools are available from the support pages on axis.com/support.
You can also reset parameters to factory default through the device’s web interface. Go to Maintenance > Factory default and click Default.
AXIS OS options
Axis offers device software management according to either the active track or the long-term support (LTS) tracks. Being on the active track means continuously getting access to all the latest product features, while the LTS tracks provide a fixed platform with periodic releases focused mainly on bug fixes and security updates.
Using AXIS OS from the active track is recommended if you want to access the newest features, or if you use Axis end-to-end system offerings. The LTS tracks are recommended if you use third-party integrations, which are not continuously validated against the latest active track. With LTS, the products can maintain cybersecurity without introducing any significant functional changes or affecting any existing integrations. For more detailed information about Axis device software strategy, go to axis.com/support/device-software.
Check the current AXIS OS version
AXIS OS determines the functionality of our devices. When you troubleshoot a problem, we recommend that you to start by checking the current AXIS OS version. The latest version might contain a correction that fixes your particular problem.
To check the current AXIS OS version:
Go to the device’s web interface > Status.
Under Device info, see the AXIS OS version.
Upgrade AXIS OS
Important
When you upgrade the device software, your preconfigured and customized settings are saved. Axis Communications AB can't guarantee that the settings are saved, even if the features are available in the new AXIS OS version.
Starting from AXIS OS 12.6, you must install every LTS version between your device’s current version and the target version. For example, if the currently installed device software version is AXIS OS 11.2, you have to install the LTS version AXIS OS 11.11 before you can upgrade the device to AXIS OS 12.6. For more information, see AXIS OS Portal: Upgrade path.
Make sure the device remains connected to the power source throughout the upgrade process.
Note
When you upgrade the device with the latest AXIS OS version in the active track, the product receives the latest functionality available. Always read the upgrade instructions and release notes available with each new release before you upgrade. To find the latest AXIS OS version and the release notes, go to axis.com/support/device-software.
Go to Maintenance > AXIS OS upgrade and click Upgrade.
When the upgrade has finished, the product restarts automatically.
Technical problems and possible solutions
Problems upgrading AXIS OS
AXIS OS upgrade failed
If the upgrade fails, the device reloads the previous version. The most common reason is that the wrong AXIS OS file has been uploaded. Check that the name of the AXIS OS file corresponds to your device and try again.
Problems after AXIS OS upgrade
If you experience problems after the upgrade, roll back to the previously installed version from the Maintenance page.
Problems setting the IP address
Can’t set the IP address
If the IP address intended for the device and the IP address of the computer used to access the device are located on different subnets, you can’t set the IP address. Contact your network administrator to obtain an IP address.
The IP address could be in use by another device. To check:
Disconnect the Axis device from the network.
In a Command/DOS window, type ping and the IP address of the device.
If you receive: Reply from <IP address>: bytes=32; time=10... this means that the IP address might already be in use by another device on the network. Obtain a new IP address from the network administrator and reinstall the device.
If you receive: Request timed out, this means that the IP address is available for use with the Axis device. Check all cabling and reinstall the device.
There could be a possible IP address conflict with another device on the same subnet. The static IP address in the Axis device is used before the DHCP server sets a dynamic address. This means that if the same default static IP address is also used by another device, there could be problems accessing the device.
Problems accessing the device
Can’t log in when accessing the device from a browser
When HTTPS is enabled, make sure that you use the correct protocol (HTTP or HTTPS) when you try to log in. You might need to manually type http or https in the browser’s address field.
If you’ve lost the password for the root account, you must reset the device to the factory default settings. For instructions, see Reset to factory default settings.
The IP address has been changed by DHCP
IP addresses obtained from a DHCP server are dynamic and could change. If the IP address has been changed, use AXIS IP Utility or AXIS Device Manager to locate the device on the network. Identify the device using its model or serial number, or by the DNS name (if the name has been configured).
If required, you can assign a static IP address manually. For instructions, go to axis.com/support.
Certificate error when using IEEE 802.1X
For authentication to work properly, the date and time settings in the Axis device must be synchronized with an NTP server. Go to System > Date and time.
To access the device externally, we recommend you to use one of the following applications for Windows®:
AXIS Camera Station Edge: free of charge, ideal for small systems with basic surveillance needs.
AXIS Camera Station Pro: 90-day trial version free of charge, ideal for small to mid-size systems.
For instructions and download, go to axis.com/vms.
Problems with MQTT
Can’t connect over port 8883 with MQTT over SSL
The firewall blocks traffic that uses port 8883 since it’s regarded insecure.
In some cases the server/broker might not provide a specific port for MQTT communication. It might still be possible to use MQTT over a port normally used for HTTP/HTTPS traffic.
If the server/broker supports WebSocket/WebSocket Secure (WS/WSS), typically on port 443, use this protocol instead. Check with the server/broker provider to see if WS/WSS is supported and which port and basepath to use.
If the server/broker supports ALPN, the use of MQTT can be negotiated over an open port, such as 443. Check with your server/broker provider to see if ALPN is supported and which ALPN protocol and port to use.
Problems with operating the device
Front heater and wiper aren’t working
If the front heater or wiper are not turning on, confirm that the top cover is properly fastened to the bottom of the housing unit.
If you can’t find what you’re looking for here, try the troubleshooting section at axis.com/support.
Performance considerations
When you set up your system, it’s important to consider how different settings and situations affect performance. Some factors affect bandwidth (bitrate), others affect frame rate, and some affect both.
The most important factors to consider:
High image resolution or lower compression levels result in images containing more data which in turn affects the bandwidth.
Access by large numbers of Motion JPEG clients or unicast H.264/H.265/AV1 clients affects the bandwidth.
Simultaneous viewing of different streams (resolution, compression) by different clients affects both frame rate and bandwidth.
Use identical streams wherever possible to maintain a high frame rate. Stream profiles can be used to ensure that streams are identical.
Accessing video streams with different codecs simultaneously affects both frame rate and bandwidth. For optimal performance, use streams with the same codec.
Heavy usage of event settings affects the product’s CPU load which in turn affects the frame rate.
Using HTTPS may reduce frame rate, in particular if streaming Motion JPEG.
Heavy network utilization due to poor infrastructure affects the bandwidth.
Viewing on poorly performing client computers lowers perceived performance and affects frame rate.
Running multiple AXIS Camera Application Platform (ACAP) applications simultaneously may affect the frame rate and the general performance.
microSD, microSDHC, and microSDXC Logos are trademarks of SD-3C LLC. microSD, microSDHC, microSDXC are trademarks or registered trademarks of SD-3C, LLC in the United States, other countries or both.
