You can use the device with the following browsers:
ChromeTM
Firefox®
EdgeTM
Safari®
Windows®
recommended
recommended
✓
macOS®
recommended
recommended
✓
✓
Linux®
recommended
recommended
✓
Other operating systems
✓
✓
✓
✓*
*To use AXIS OS web interface with iOS 15 or iPadOS 15, go to Settings > Safari > Advanced > Experimental Features and disable NSURLSession Websocket.
Open the device's web interface
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 the controls and options in the device’s web interface, see The web interface.
Create an administrator account
The first time you log in to your device, you must create an administrator account.
Axis devices send the initially set password in clear text over the network. To protect your device after the first login, set up a secure and encrypted HTTPS connection and then change the password.
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.
Configure your device
Turn off maintenance mode after installing the siren
CAUTION
To protect the installer from hearing damage and from dazzling by bright light, it’s recommended to have maintenance mode on when installing the device.
When you install the device for the first time, maintenance mode is on by default. When the device is in maintenance mode, the siren makes no sound and the light gives white pulsating light patterns.
Go to Overview > Maintenance to turn off Maintenance mode.
Turn on maintenance mode
To perform service of the device, go to Overview > Maintenance and turn on Maintenance mode. Ordinary light and siren activities are then paused.
Configure a profile
A profile is a collection of set configurations. You can have up to 30 profiles with different priorities and patterns.
To set a new profile:
Go to Profiles and click Create.
Enter a Name and Description.
Select the Light and Siren settings that you want for your profile.
Set the light and siren Priority and click Save.
To edit a profile, click and select Edit.
Import or export a profile
If you want to use a profile with predefined configurations, you can import it:
Go to Profiles and click Import.
Browse to locate the file or drag and drop the file that you want to import.
Click Save.
To copy one or more profiles and save to other devices, you can export them:
Select the profiles.
Click Export.
Browse to locate the .json files.
Set up direct SIP (P2P)
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. To better understand how P2P works, see Peer-to-peer SIP (P2PSIP).
For more information about setting options, see SIP.
Go to System > SIP > SIP settings and select Enable SIP.
To allow the device to receive incoming calls, select Allow incoming calls.
Under Call handling, set the timeout and duration for the call.
Under Ports, enter the port numbers.
SIP port – The network port used for SIP communication. The signaling traffic through this port is non-encrypted. The default port number is 5060. Enter a different port number if required.
TLS port – The network port used for encrypted SIP communication. The signaling traffic through this port is encrypted with Transport Layer Security (TLS). The default port number is 5061. Enter a different port number if required.
RTP start port – Enter the port used for the first RTP media stream in a SIP call. The default start port for media transport is 4000. Some firewalls might block RTP traffic on certain port numbers. A port number must be between 1024 and 65535.
Under 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.
Under Audio, select at least one audio codec with the desired audio quality for SIP calls. Drag-and-drop to change the priority.
Under Additional, select additional options.
UDP-to-TCP switching – Select to allow calls to switch transport protocols from UDP (User Datagram Protocol) to TCP (Transmission Control Protocol) temporarily. The reason for switching is to avoid fragmentation, and the switch can take place if a request is within 200 bytes of the maximum transmission unit (MTU) or larger than 1300 bytes.
Allow via rewrite – Select to send the local IP address instead of the router's public IP address.
Allow contact rewrite – Select to send the local IP address instead of the router's public IP address.
Register with server every – Set how often you want the device to register with the SIP server for the existing SIP accounts.
DTMF payload type – Changes the default payload type for DTMF.
Click Save.
Set up SIP through a server (PBX)
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. To better understand how P2P works, see Private Branch Exchange (PBX).
For more information about setting options, see SIP.
Request the following information from your PBX provider:
User ID
Domain
Password
Authentication ID
Caller ID
Registrar
RTP start port
To add a new account, go to System > SIP > SIP accounts and click + Account.
Enter the details you received from your PBX provider.
Select Registered.
Select a transport mode.
Click Save.
Set up the SIP settings the same way as for peer-to-peer. See Set up direct SIP (P2P) for more information.
Go to System > Events and add a rule. The rule defines when the device will perform certain actions. You can set up rules as scheduled, recurring, or manually triggered.
Enter a Name.
Select the Condition that must be met to trigger the action. If you specify more than one condition for the rule, all of the conditions must be met to trigger the action.
Select which Action the device should perform when the conditions are met.
Note
If you make changes to an active rule, the rule must be turned on again for the changes to take effect.
Start a profile when an alarm is triggered
This example explains how to trigger an alarm when the digital input signal is changed.
Set direction input for the port:
Go to System > Accessories > I/O ports.
Go to Port 1 > Normal position and click Circuit closed.
Create a rule:
Go to System > Events and add a rule.
Type a name for the rule.
In the list of conditions, select I/O > Digital input.
Select Port 1.
In the list of actions, select Run light and siren profile while the rule is active.
Select the profile you want to start.
Click Save.
Start a profile through SIP
This example explains how to trigger an alarm through SIP.
Activate SIP:
Go to System > SIP > SIP settings.
Select Enable SIP and Allow incoming calls.
Click Save.
Create a rule:
Go to System > Events and add a rule.
Type a name for the rule.
In the list of conditions, select Call > State.
In the list of state, select Active.
In the list of actions, select Run light and siren profile while the rule is active.
Select the profile you want to start.
Click Save.
Control more than one profile through SIP extensions
Activate SIP:
Go to System > SIP > SIP settings.
Select Enable SIP and Allow incoming calls.
Click Save.
Create a rule to start a profile:
Go to System > Events and add a rule.
Type a name for the rule.
In the list of conditions, select Call > State change.
In the list of reasons, select Accepted by device.
In Call direction, select Incoming.
In Local SIP URI, type sip:[Ext]@[IP address] where [Ext] is the extension used for the profile and [IP address] is the device address. For example sip:1001@192.168.0.90.
In the list of actions, select Light and Siren > Run light and siren profile.
Select the profile you want to start.
Select the action Start.
Click Save.
Create a rule to stop a profile:
Go to System > Events and add a rule.
Type a name for the rule.
In the list of conditions, select Call > State change.
In the list of reasons, select Terminated.
In Call direction, select Incoming.
In Local SIP URI, type sip:[Ext]@[IP address] where [Ext] is the extension used for the profile and [IP address] is the device address. For example sip:1001@192.168.0.90.
In the list of actions, select Light and Siren > Run light and siren profile.
Select the profile you want to stop.
Select the action Stop.
Click Save.
Repeat the steps to create start and stop rules for each profile you want to control through SIP.
Run two profiles with different priorities
If you run two profiles with different priorities, the profile with a higher priority number will interrupt the profile with a lower priority number.
Note
If you run two profiles with the same priority, the most recent profile will cancel the previous one.
This example explains how to set the device to show one profile with priority 4 over another profile with priority 3 when triggered by the digital I/O port.
Create profiles:
Create a profile with priority 3.
Create another profile with priority 4.
Create a rule:
Go to System > Events and add a rule.
Type a name for the rule.
In the list of conditions, select I/O > Digital input.
Select a port.
In the list of actions, select Run light and siren profile while the rule is active.
Select the profile that has the highest priority number.
Click Save.
Go to Profiles and start the profile with the lowest priority number.
Activate a strobe siren through virtual input when a camera detects motion
This example explains how to connect a camera to the strobe siren, and activate a profile in the strobe siren whenever the application AXIS Motion Guard, installed in the camera, detects motion.
Before you start:
Create a new account with Operator or Administrator privileges in the strobe siren.
Create a profile in the strobe siren.
Set up AXIS Motion Guard in the camera and create a profile called “Camera profile”.
Create two recipients in the camera:
In the camera’s device interface, go to System > Events > Recipients and add a recipient.
Replace <IPaddress> with the address of the strobe siren.
The account and password of the newly created strobe siren account.
Click Test to make sure all data is valid.
Click Save.
Create two rules in the camera:
Go to Rules and add a rule.
Enter the following information:
Name: Activate virtual IO1
Condition: Applications > Motion Guard: Camera profile
Action: Notifications > Send notification through HTTP
Recipient: Activate virtual port
Query string suffix: schemaversion=1&port=1
Click Save.
Add another rule with the following information:
Name: Deactivate virtual IO1
Condition: Applications > Motion Guard: Camera profile
Select Invert this condition.
Action: Notifications > Send notification through HTTP
Recipient: Deactivate virtual port
Query string suffix: schemaversion=1&port=1
Click Save.
Create a rule in the strobe siren:
In the strobe siren’s web interface, go to System > Events and add a rule.
Enter the following information:
Name: Trigger on virtual input 1
Condition: I/O > Virtual input
Port: 1
Action: Light and siren > Run light and siren profile while the rule is active
Profile: select the newly created profile
Click Save.
Activate a strobe siren through HTTP post when a camera detects motion
This example explains how to connect a camera to the strobe siren, and activate a profile in the strobe siren whenever the application AXIS Motion Guard, installed in the camera, detects motion.
Before you start:
Create a new user with the role Operator or Administrator in the strobe siren.
Create a profile in the strobe siren called: “Strobe siren profile”.
Set up AXIS Motion Guard in the camera and create a profile called: “Camera profile”.
Make sure to use AXIS Device Assistant with firmware version 10.8.0 or later.
Create a recipient in the camera:
In the camera’s device interface, go to System > Events > Recipients and add a recipient.
Make sure to enter the same information under ‘"profile" : <>’ as you did when you created the profile in the strobe siren, in this case: “Strobe siren profile”.
Click Save.
Add another rule with the following information:
Name: Deactivate strobe siren with motion
Condition: Applications > Motion Guard: Camera profile
Select Invert this condition.
Action: Notifications > Send notification through HTTP
Recipient: Strobe siren
The information must be the same as you previously entered under Events > Recipients > Name.
Make sure to enter the same information under ‘"profile" : <>’ as you did when you created the profile in the strobe siren, in this case: “Strobe siren profile”.
Click Save.
Activate strobe siren over MQTT when camera detects motion
This example explains how connect a camera to the strobe siren over MQTT, and activate a profile in the strobe siren whenever the application AXIS Motion Guard, installed in the camera, detects motion.
Before you start:
Create a profile in the strobe siren.
Set up an MQTT broker and get the broker’s IP address, username and password.
Set up AXIS Motion Guard in the camera.
Set up the MQTT client in the camera:
In the camera’s device interface, go to System > MQTT > MQTT client > Broker and enter the following information:
Host: Broker IP address
Client ID: For example Camera 1
Protocol: The protocol the broker is set to
Port: The port number used by the broker
The broker Username and Password
Click Save and Connect.
Create two rules in the camera for MQTT publishing:
Go to System > Events > Rules and add a rule.
Enter the following information:
Name: Motion detected
Condition: Applications > Motion alarm
Action: MQTT > Send MQTT publish message
Topic: Motion
Payload: On
QoS: 0, 1 or 2
Click Save.
Add another rule with the following information:
Name: No motion
Condition: Applications > Motion alarm
Select Invert this condition.
Action: MQTT > Send MQTT publish message
Topic: Motion
Payload: Off
QoS: 0, 1 or 2
Click Save.
Set up the MQTT client in the strobe siren:
In the strobe siren’s device interface, go to System > MQTT > MQTT client > Broker and enter the following information:
Host: Broker IP address
Client ID: Siren 1
Protocol: The protocol the broker is set to
Port: The port number used by the broker
Username and Password
Click Save and Connect.
Go to MQTT subscriptions and add a subscription.
Enter the following information:
Subscription filter: Motion
Subscription type: Stateful
QoS: 0, 1 or 2
Click Save.
Create a rule in the strobe siren for MQTT subscriptions:
Go to System > Events > Rules and add a rule.
Enter the following information:
Name: Motion detected
Condition: MQTT > Stateful
Subscription filter: Motion
Payload: On
Action: Light and siren > Run light and siren profile while the rule is active
Profile: Select the profile you want to be active.
Click Save.
Learn more
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>.
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.
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.
The web interface
To reach the device’s web interface, type the device’s IP address in a web browser.
Show or hide the main menu.
Access the release notes.
Access the product help.
Change the language.
Set light theme or dark theme.
The user menu contains:
Information about the user who is logged in.
Change account : Log out from the current account and log in to a new account.
Log out : Log out from the current account.
The context menu contains:
Analytics data: Accept to share non-personal browser data.
Feedback: Share any feedback to help us improve your user experience.
Legal: View information about cookies and licenses.
About: View device information, including AXIS OS version and serial number.
Status
Security
Shows what kind of access to the device that is active, what encryption protocols are in use, and if unsigned apps are allowed. Recommendations to the settings are based on the AXIS OS Hardening Guide.
Hardening guide: Link to AXIS OS Hardening guide where you can learn more about cybersecurity on Axis devices and best practices.
Time sync status
Shows NTP synchronization information, including if the device is in sync with an NTP server and the time remaining until the next sync.
NTP settings: View and update the NTP settings. Takes you to the Time and location page where you can change the NTP settings.
Device info
Shows the device information, including AXIS OS version and serial number.
Upgrade AXIS OS: Upgrade the software on your device. Takes you to the Maintenance page where you can do the upgrade.
Connected clients
Shows the number of connections and connected clients.
View details: View and update the list of connected clients. The list shows IP address, protocol, port, state, and PID/process of each connection.
Overview
Light status
Shows the different light activities that run on the device. You can have up to 10 activities in the light status list at the same time. When two or more activities run at the same time, the activity with the highest priority shows the light status. That row will be highlighted in green in the status list.
Siren status
Shows the different siren activities that run on the device. You can have up to 10 activities in the siren status list at the same time. When two or more activities run at the same time, the activity with the highest priority will run. That row will be highlighted in green in the status list.
Maintenance
Maintenance mode: Turn on to pause the light and siren activities during the device maintenance. When you turn on maintenance mode, the device shows a white pulsating light pattern in a triangle and the siren is silent. It protects the installer from hearing damage and dazzling bright light.
Maintenance has priority 11. Only system specific activities with higher priority can disrupt the maintenance mode.
Maintenance mode survives a reboot. For example, if you set the time to 2 hours, turn off the device and restart it one hour later, the device will be in maintenance mode for another hour.
When you do a default reset, the device returns to maintenance mode.
Duration
Continuous: Select to let the device stay in maintenance mode until you turn it off.
Time: Select to set a time when the maintenance mode will turn off.
Health check
Check: Do a health check of the device to make sure the light and siren work fine. It turns on each light section one after another and plays a test tone to check that the device works fine. If the health check doesn’t pass, go to the system logs for more information.
Profiles
Profiles
A profile is a collection of set configurations. You can have up to 30 profiles with different priorities and patterns. The profiles are listed to give an overview of name, priority, and light and siren settings.
Create: Click to create a profile.
Preview/Stop preview: Start or stop a preview of the profile before you save it.
Note
You can’t have two profiles with the same name.
Name: Enter a name of the profile.
Description: Enter a description of the profile.
Light: Select from the drop-down menu what kind of Pattern, Speed, Intensity, and Color of the light you want.
Siren: Select from the drop-down menu what kind of Pattern and Intensity of the siren you want.
Start or stop a preview of only the light or siren.
Duration: Set the duration of the activities.
Continuous: Once started, it runs until it’s stopped.
Time: Set a specified time for how long the activity will last.
Repetitions: Set how many times the activity should repeat itself.
Priority: Set the priority of an activity to a number between 1 and 10. Activities with priority numbers higher than 10 can’t be removed from the status list. There are three activities with higher priority than 10; Maintenance (11), Identify (12), and Health check (13).
Import: Add one or more profiles with predefined configuration.
Add: Add new profiles.
Delete and add: The old profiles are deleted, and you can upload new profiles.
Overwrite: Updated profiles overwrite the existing profiles.
To copy a profile and save it to other devices, select one or more profiles and click Export. A .json file is exported.
Start a profile. The profile and its activities appear in the status list.
Choose to Edit, Copy, Export, or Delete the profile.
Apps
Add app: Install a new app.
Find more apps: Find more apps to install. You will be taken to an overview page of Axis apps.
Allow unsigned apps: Turn on to allow installation of unsigned apps.
Allow root-privileged apps: Turn on to allow apps with root privileges full access to the device.
View the security updates in AXIS OS and ACAP apps.
Note
The device’s performance might be affected if you run several apps at the same time.
Use the switch next to the app name to start or stop the app.
Open: Access the app’s settings. The available settings depend on the application. Some applications don’t have any settings.
The context menu can contain one or more of the following options:
Open-source license: View information about open-source licenses used in the app.
App log: View a log of the app events. The log is helpful when you contact support.
Activate license with a key: If the app requires a license, you need to activate it. Use this option if your device doesn’t have internet access.
If you don’t have a license key, go to axis.com/products/analytics. You need a license code and the Axis product serial number to generate a license key.
Activate license automatically: If the app requires a license, you need to activate it. Use this option if your device has internet access. You need a license code to activate the license.
Deactivate the license: Deactivate the license to replace it with another license, for example, when you change from a trial license to a full license. If you deactivate the license, you also remove it from the device.
Settings: Configure the parameters.
Delete: Delete the app permanently from the device. If you don’t deactivate the license first, it remains active.
System
Time and location
Date and time
The time format depends on the web browser’s language settings.
Note
We recommend you synchronize the device’s date and time with an NTP server.
Synchronization: Select an option for the device’s date and time synchronization.
Automatic date and time (manual NTS KE servers): Synchronize with the secure NTP key establishment servers connected to the DHCP server.
Manual NTS KE servers: Enter the IP address of one or two NTP servers. When you use two NTP servers, the device synchronizes and adapts its time based on input from both.
Max NTP poll time: Select the maximum amount of time the device should wait before it polls the NTP server to get an updated time.
Min NTP poll time: Select the minimum amount of time the device should wait before it polls the NTP server to get an updated time.
Automatic date and time (NTP servers using DHCP): Synchronize with the NTP servers connected to the DHCP server.
Fallback NTP servers: Enter the IP address of one or two fallback servers.
Max NTP poll time: Select the maximum amount of time the device should wait before it polls the NTP server to get an updated time.
Min NTP poll time: Select the minimum amount of time the device should wait before it polls the NTP server to get an updated time.
Automatic date and time (manual NTP servers): Synchronize with NTP servers of your choice.
Manual NTP servers: Enter the IP address of one or two NTP servers. When you use two NTP servers, the device synchronizes and adapts its time based on input from both.
Max NTP poll time: Select the maximum amount of time the device should wait before it polls the NTP server to get an updated time.
Min NTP poll time: Select the minimum amount of time the device should wait before it polls the NTP server to get an updated time.
Custom date and time: Manually set the date and time. Click Get from system to fetch the date and time settings once from your computer or mobile device.
Time zone: Select which time zone to use. Time will automatically adjust to daylight saving time and standard time.
DHCP: Adopts the time zone of the DHCP server. The device must connected to a DHCP server before you can select this option.
Manual: Select a time zone from the drop-down list.
Note
The system uses the date and time settings in all recordings, logs, and system settings.
Device location
Enter where the device is located. Your video management system can use this information to place the device on a map.
Latitude: Positive values are north of the equator.
Longitude: Positive values are east of the prime meridian.
Heading: Enter the compass direction that the device is facing. 0 is due north.
Label: Enter a descriptive name for the device.
Save: Click to save your device location.
Network
IPv4
Assign IPv4 automatically: Select to let the network router assign an IP address to the device automatically. We recommend automatic IP (DHCP) for most networks.
IP address: Enter a unique IP address for the device. Static IP addresses can be assigned at random within isolated networks, provided that each address is unique. To avoid conflicts, we recommend you contact your network administrator before you assign a static IP address.
Subnet mask: Enter the subnet mask to define what addresses are inside the local area network. Any address outside the local area network goes through the router.
Router: Enter the IP address of the default router (gateway) used to connect devices that are attached to different networks and network segments.
Fallback to static IP address if DHCP isn’t available: Select if you want to add a static IP address to use as fallback if DHCP is unavailable and can’t assign an IP address automatically.
Note
If DHCP isn’t available and the device uses a static address fallback, the static address is configured with a limited scope.
IPv6
Assign IPv6 automatically: Select to turn on IPv6 and to let the network router assign an IP address to the device automatically.
Hostname
Assign hostname automatically: Select to let the network router assign a hostname to the device automatically.
Hostname: Enter the hostname manually to use as an alternative way of accessing the device. The server report and system log use the hostname. Allowed characters are A–Z, a–z, 0–9 and -.
DNS servers
Assign DNS automatically: Select to let the DHCP server assign search domains and DNS server addresses to the device automatically. We recommend automatic DNS (DHCP) for most networks.
Search domains: When you use a hostname that is not fully qualified, click Add search domain and enter a domain in which to search for the hostname the device uses.
DNS servers: Click Add DNS server and enter the IP address of the DNS server. This provides the translation of hostnames to IP addresses on your network.
HTTP and HTTPS
HTTPS is a protocol that provides encryption for page requests from users and for the pages returned by the web server. The encrypted exchange of information is governed by the use of an HTTPS certificate, which guarantees the authenticity of the server.
To use HTTPS on the device, you must install an HTTPS certificate. Go to System > Security to create and install certificates.
Allow access through: Select if a user is allowed to connect to the device through the HTTP, HTTPS, or both HTTP and HTTPS protocols.
Note
If you view encrypted web pages through HTTPS, you might experience a drop in performance, especially when you request a page for the first time.
HTTP port: Enter the HTTP port to use. The device allows port 80 or any port in the range 1024-65535. If you are logged in as an administrator, you can also enter any port in the range 1-1023. If you use a port in this range, you get a warning.
HTTPS port: Enter the HTTPS port to use. The device allows port 443 or any port in the range 1024-65535. If you are logged in as an administrator, you can also enter any port in the range 1-1023. If you use a port in this range, you get a warning.
Certificate: Select a certificate to enable HTTPS for the device.
Network discovery protocols
Bonjour®: Turn on to allow automatic discovery on the network.
Bonjour name: Enter a friendly name to be visible on the network. The default name is the device name and MAC address.
UPnP®: Turn on to allow automatic discovery on the network.
UPnP name: Enter a friendly name to be visible on the network. The default name is the device name and MAC address.
WS-Discovery: Turn on to allow automatic discovery on the network.
LLDP and CDP: Turn on to allow automatic discovery on the network. Turning LLDP and CDP off can impact the PoE power negotiation. To resolve any issues with the PoE power negotiation, configure the PoE switch for hardware PoE power negotiation only.
Global proxies
Http proxy: Specify a global proxy host or IP address according to the allowed format.
Https proxy: Specify a global proxy host or IP address according to the allowed format.
Allowed formats for http and https proxies:
http(s)://host:port
http(s)://user@host:port
http(s)://user:pass@host:port
Note
Restart the device to apply the global proxy settings.
No proxy: Use No proxy to bypass global proxies. Enter one of the options in the list, or enter several separated by a comma:
Leave empty
Specify an IP address
Specify an IP address in CIDR format
Specify a domain name, for example: www.<domain name>.com
Specify all subdomains in a specific domain, for example .<domain name>.com
One-click cloud connection
One-click cloud connection (O3C) together with an O3C service provides easy and secure internet access to live and recorded video from any location. For more information, see axis.com/end-to-end-solutions/hosted-services.
Allow O3C:
One-click: This is the default setting. Press and hold the control button on the device to connect to an O3C service over the internet. You need to register the device with the O3C service within 24 hours after you press the control button. Otherwise, the device disconnects from the O3C service. Once you register the device, Always is enabled and the device stays connected to the O3C service.
Always: The device constantly attempts to connect to an O3C service over the internet. Once you register the device, it stays connected to the O3C service. Use this option if the control button on the device is out of reach.
No: Disables the O3C service.
Proxy settings: If needed, enter the proxy settings to connect to the proxy server.
Host: Enter the proxy server’s address.
Port: Enter the port number used for access.
Login and Password: If needed, enter username and password for the proxy server.
Authentication method:
Basic: This method is the most compatible authentication scheme for HTTP. It’s less secure than the Digest method because it sends the username and password unencrypted to the server.
Digest: This method is more secure because it always transfers the password encrypted across the network.
Auto: This option lets the device select the authentication method depending on the supported methods. It prioritizes the Digest method over the Basic method.
Owner authentication key (OAK): Click Get key to fetch the owner authentication key. This is only possible if the device is connected to the internet without a firewall or proxy.
SNMP
The Simple Network Management Protocol (SNMP) allows remote management of network devices.
SNMP: Select the version of SNMP to use.
v1 and v2c:
Read community: Enter the community name that has read-only access to all supported SNMP objects. The default value is public.
Write community: Enter the community name that has read or write access to all supported SNMP objects (except read-only objects). The default value is write.
Activate traps: Turn on to activate trap reporting. The device uses traps to send messages for important events or status changes to a management system. In the web interface, you can set up traps for SNMP v1 and v2c. Traps are automatically turned off if you change to SNMP v3 or turn off SNMP. If you use SNMP v3, you can set up traps through the SNMP v3 management application.
Trap address: Enter the IP address or host name of the management server.
Trap community: Enter the community to use when the device sends a trap message to the management system.
Traps:
Cold start: Sends a trap message when the device starts.
Warm start: Sends a trap message when you change an SNMP setting.
Link up: Sends a trap message when a link changes from down to up.
Authentication failed: Sends a trap message when an authentication attempt fails.
Note
All Axis Video MIB traps are enabled when you turn on SNMP v1 and v2c traps. For more information, see AXIS OS Portal > SNMP.
v3: SNMP v3 is a more secure version, which provides encryption and secure passwords. To use SNMP v3, we recommend you to activate HTTPS, as the password is then sent through HTTPS. This also prevents unauthorized parties’ access to unencrypted SNMP v1 and v2c traps. If you use SNMP v3, you can set up traps through the SNMP v3 management application.
Password for the account “initial”: Enter the SNMP password for the account named “initial”. Although the password can be sent without activating HTTPS, we don’t recommend it. The SNMP v3 password can only be set once, and preferably only when HTTPS is enabled. Once the password is set, the password field is no longer displayed. To set the password again, you must reset the device to factory default settings.
Security
Certificates
Certificates are used to authenticate devices on a network. The device supports two types of certificates:
Client/server certificates
A client/server certificate validates the device’s identity, and can be self-signed or issued by a Certificate Authority (CA). A self-signed certificate offers limited protection and can be used before a CA-issued certificate has been obtained.
CA certificates
You can use a CA certificate to authenticate a peer certificate, for example to validate the identity of an authentication server when the device connects to a network protected by IEEE 802.1X. The device has several pre-installed CA certificates.
These formats are supported:
Certificate formats: .PEM, .CER, and .PFX
Private key formats: PKCS#1 and PKCS#12
Important
If you reset the device to factory default, all certificates are deleted. Any pre-installed CA certificates are reinstalled.
Add certificate : Click to add a certificate.
More: Show more fields to fill in or select.
Secure keystore: Select to use Secure element or Trusted Platform Module 2.0 to securely store the private key. For more information on which secure keystore to select, go to help.axis.com/en-us/axis-os#cryptographic-support.
Key type: Select the default or a different encryption algorithm from the drop-down list to protect the certificate.
The context menu contains:
Certificate information: View an installed certificate’s properties.
Delete certificate: Delete the certificate.
Create certificate signing request: Create a certificate signing request to send to a registration authority to apply for a digital identity certificate.
Secure keystore:
Secure element (CC EAL6+): Select to use secure element for secure keystore.
Trusted Platform Module 2.0 (CC EAL4+, FIPS 140-2 Level 2): Select to use TPM 2.0 for secure keystore.
Network access control and encryption
IEEE 802.1x
IEEE 802.1x is an IEEE standard for port-based network admission control providing secure authentication of wired and wireless network devices. IEEE 802.1x is based on EAP (Extensible Authentication Protocol).
To access a network protected by IEEE 802.1x, network devices must authenticate themselves. The authentication is performed by an authentication server, typically a RADIUS server (for example, FreeRADIUS and Microsoft Internet Authentication Server).
IEEE 802.1AE MACsec
IEEE 802.1AE MACsec is an IEEE standard for media access control (MAC) security that defines connectionless data confidentiality and integrity for media access independent protocols.
Certificates
When configured without a CA certificate, server certificate validation is disabled and the device tries to authenticate itself regardless of what network it is connected to.
When using a certificate, in Axis' implementation, the device and the authentication server authenticate themselves with digital certificates using EAP-TLS (Extensible Authentication Protocol - Transport Layer Security).
To allow the device to access a network protected through certificates, you must install a signed client certificate on the device.
Authentication method: Select an EAP type used for authentication.
Client certificate: Select a client certificate to use IEEE 802.1x. The authentication server uses the certificate to validate the client’s identity.
CA certificates: Select CA certificates to validate the authentication server’s identity. When no certificate is selected, the device tries to authenticate itself regardless of what network it is connected to.
EAP identity: Enter the user identity associated with the client certificate.
EAPOL version: Select the EAPOL version that is used in the network switch.
Use IEEE 802.1x: Select to use the IEEE 802.1x protocol.
These settings are only available if you use IEEE 802.1x PEAP-MSCHAPv2 as the authentication method:
Password: Enter the password for your user identity.
Peap version: Select the Peap version that is used in the network switch.
Label: Select 1 to use client EAP encryption; select 2 to use client PEAP encryption. Select the Label that the network switch uses when using Peap version 1.
These settings are only available if you use IEEE 802.1ae MACsec (Static CAK/Pre-Shared Key) as the authentication method:
Key agreement connectivity association key name: Enter the connectivity association name (CKN). It must be 2 to 64 (divisible by 2) hexadecimal characters. The CKN must be manually configured in the connectivity association and must match on both ends of the link to initially enable MACsec.
Key agreement connectivity association key: Enter the connectivity association key (CAK). It should be either 32 or 64 hexadecimal characters long. The CAK must be manually configured in the connectivity association and must match on both ends of the link to initially enable MACsec.
Prevent brute-force attacks
Blocking: Turn on to block brute-force attacks. A brute-force attack uses trial-and-error to guess login info or encryption keys.
Blocking period: Enter the number of seconds to block a brute-force attack.
Blocking conditions: Enter the number of authentication failures allowed per second before the block starts. You can set the number of failures allowed both on page level and device level.
Firewall
Activate: Turn on the firewall.
Default Policy: Select the default state for the firewall.
Allow: Allows all connections to the device. This option is set by default.
Deny: Denies all connections to the device.
To make exceptions to the default policy, you can create rules that allows or denies connections to the device from specific addresses, protocols, and ports.
Address: Enter an address in IPv4/IPv6 or CIDR format that you want to allow or deny access to.
Protocol: Select a protocol that you want to allow or deny access to.
Port: Enter a port number that you want to allow or deny access to. You can add a port number between 1 and 65535.
Policy: Select the policy of the rule.
: Click to create another rule.
Add rules: Click to add the rules that you have defined.
Time in seconds: Set a time limit for testing the rules. The default time limit is set to 300 seconds. To activate the rules straight away, set the time to 0 seconds.
Confirm rules: Confirm the rules and their time limit. If you have set a time limit of more than 1 second, the rules will be active during this time. If you have set the time to 0, the rules will be active straight away.
Pending rules: An overview of the latest tested rules that you are yet to confirm.
Note
The rules that have a time limit appear under Active rules until the displayed timer runs out, or until you confirm them. If you don't confirm them, they will appear under Pending rules once the timer runs out, and the firewall will revert to the previously defined settings. If you confirm them, they will replace the current active rules.
Confirm rules: Click to activate the pending rules.
Active rules: An overview of the rules you are currently running on the device.
: Click to delete an active rule.
: Click to delete all rules, both pending and active.
Custom signed AXIS OS certificate
To install test software or other custom software from Axis on the device, you need a custom signed AXIS OS certificate. The certificate verifies that the software is approved by both the device owner and Axis. The software can only run on a specific device which is identified by its unique serial number and chip ID. Only Axis can create custom signed AXIS OS certificates, since Axis holds the key to sign them.
Install: Click to install the certificate. You need to install the certificate before you install the software.
The context menu contains:
Delete certificate: Delete the certificate.
Accounts
Accounts
Add account: Click to add a new account. You can add up to 100 accounts.
Account: Enter a unique account name.
New password: Enter a password for the account. Passwords must be 1 to 64 characters long. Only ASCII printable characters (code 32 to 126) are allowed in the password, for example, letters, numbers, punctuation, and some symbols.
Repeat password: Enter the same password again.
Privileges:
Administrator: Has full access to all settings. Administrators can also add, update, and remove other accounts.
Operator: Has access to all settings except:
All System settings.
The context menu contains:
Update account: Edit the account properties.
Delete account: Delete the account. You can’t delete the root account.
Anonymous access
Allow anonymous viewing: Turn on to allow anyone access the device as a viewer without logging in with an account.
Allow anonymous PTZ operating: Turn on to allow anonymous users to pan, tilt, and zoom the image.
SSH accounts
Add SSH account: Click to add a new SSH account.
Restrict root access: Turn on to restrict functionality that requires root access.
Enable SSH: Turn on to use SSH service.
Account: Enter a unique account name.
New password: Enter a password for the account. Passwords must be 1 to 64 characters long. Only ASCII printable characters (code 32 to 126) are allowed in the password, for example, letters, numbers, punctuation, and some symbols.
Repeat password: Enter the same password again.
Comment: Enter a comment (optional).
The context menu contains:
Update SSH account: Edit the account properties.
Delete SSH account: Delete the account. You can’t delete the root account.
Virtual host
Add virtual host: Click to add a new virtual host.
Enabled: Select to use this virtual host.
Server name: Enter the name of the server. Only use numbers 0-9, letters A-Z, and hyphen (-).
Port: Enter the port the server is connected to.
Type: Select the type of authentication to use. Select between Basic, Digest, and Open ID.
The context menu contains:
Update: Update the virtual host.
Delete: Delete the virtual host.
Disabled: The server is disabled.
OpenID Configuration
Important
If you can't use OpenID to sign in, use the Digest or Basic credentials you used when you configured OpenID to sign in.
Client ID: Enter the OpenID username.
Outgoing Proxy: Enter the proxy address for the OpenID connection to use a proxy server.
Admin claim: Enter a value for the admin role.
Provider URL: Enter the web link for the API endpoint authentication. Format should be https://[insert URL]/.well-known/openid-configuration
Operator claim: Enter a value for the operator role.
Require claim: Enter the data that should be in the token.
Viewer claim: Enter the value for the viewer role.
Remote user: Enter a value to identify remote users. This assists to display the current user in the device’s web interface.
Scopes: Optional scopes that could be part of the token.
Client secret: Enter the OpenID password
Save: Click to save the OpenID values.
Enable OpenID: Turn on to close current connection and allow device authentication from the provider URL.
Events
Rules
A rule defines the conditions that triggers the product to perform an action. The list shows all the currently configured rules in the product.
Note
You can create up to 256 action rules.
Add a rule: Create a rule.
Name: Enter a name for the rule.
Wait between actions: Enter the minimum time (hh:mm:ss) that must pass between rule activations. It is useful if the rule is activated by, for example, day-night mode conditions, to avoid that small light changes during sunrise and sunset activate the rule repeatedly.
Condition: Select a condition from the list. A condition must be met for the device to perform an action. If multiple conditions are defined, all of them must be met to trigger the action. For information about specific conditions, see Get started with rules for events.
Use this condition as a trigger: Select to make this first condition function only as a starting trigger. It means that once the rule is activated, it remains active for as long as all the other conditions are met, no matter the state of the first condition. If you don’t select this option, the rule will simply be active whenever all the conditions are met.
Invert this condition: Select if you want the condition to be the opposite of your selection.
Add a condition: Click to add an additional condition.
Action: Select an action from the list and enter its required information. For information about specific actions, see Get started with rules for events.
Recipients
You can set up your device to notify recipients about events or send files.
Note
If you set up your device to use FTP or SFTP, don’t change or remove the unique sequence number that’s added to the file names. If you do that, only one image per event can be sent.
The list shows all the recipients currently configured in the product, along with information about their configuration.
Note
You can create up to 20 recipients.
Add a recipient: Click to add a recipient.
Name: Enter a name for the recipient.
Type: Select from the list:
FTP
Host: Enter the server's IP address or hostname. If you enter a hostname, make sure that a DNS server is specified under System > Network > IPv4 and IPv6.
Port: Enter the port number used by the FTP server. The default is 21.
Folder: Enter the path to the directory where you want to store files. If this directory doesn’t already exist on the FTP server, you will get an error message when uploading files.
Username: Enter the username for the login.
Password: Enter the password for the login.
Use temporary file name: Select to upload files with temporary, automatically generated filenames. The files get renamed to the desired names when the upload completes. If the upload is aborted/interrupted, you don’t get any corrupt files. However, you probably still get the temporary files. This way you know that all files that have the desired name are correct.
Use passive FTP: Under normal circumstances, the product simply requests the target FTP server to open the data connection. The device actively initiates both the FTP control and data connections to the target server. This is normally needed if there is a firewall between the device and the target FTP server.
HTTP
URL: Enter the network address to the HTTP server and the script that will handle the request. For example, http://192.168.254.10/cgi-bin/notify.cgi.
Username: Enter the username for the login.
Password: Enter the password for the login.
Proxy: Turn on and enter the required information if a proxy server must be passed to connect to the HTTP server.
HTTPS
URL: Enter the network address to the HTTPS server and the script that will handle the request. For example, https://192.168.254.10/cgi-bin/notify.cgi.
Validate server certificate: Select to validate the certificate that was created by HTTPS server.
Username: Enter the username for the login.
Password: Enter the password for the login.
Proxy: Turn on and enter the required information if a proxy server must be passed to connect to the HTTPS server.
Network storage
You can add network storage such as NAS (network-attached storage) and use it as a recipient to store files. The files are stored in the Matroska (MKV) file format.
Host: Enter the IP address or hostname for the network storage.
Share: Enter the name of the share on the host.
Folder: Enter the path to the directory where you want to store files.
Username: Enter the username for the login.
Password: Enter the password for the login.
SFTP
Host: Enter the server's IP address or hostname. If you enter a hostname, make sure that a DNS server is specified under System > Network > IPv4 and IPv6.
Port: Enter the port number used by the SFTP server. The default is 22.
Folder: Enter the path to the directory where you want to store files. If this directory doesn’t already exist on the SFTP server, you will get an error message when uploading files.
Username: Enter the username for the login.
Password: Enter the password for the login.
SSH host public key type (MD5): Enter the fingerprint of the remote host’s public key (a 32-digit hexadecimal string). The SFTP client supports SFTP servers using SSH-2 with RSA, DSA, ECDSA, and ED25519 host key types. RSA is the preferred method during negotiation, followed by ECDSA, ED25519, and DSA. Make sure to enter the right MD5 host key that is used by your SFTP server. While the Axis device supports both MD5 and SHA-256 hash keys, we recommend using SHA-256 due to stronger security over MD5. For more information on how to configure an SFTP server with an Axis device, go to the AXIS OS Portal.
SSH host public key type (SHA256): Enter the fingerprint of the remote host’s public key (a 43-digit Base64 encoded string). The SFTP client supports SFTP servers using SSH-2 with RSA, DSA, ECDSA, and ED25519 host key types. RSA is the preferred method during negotiation, followed by ECDSA, ED25519, and DSA. Make sure to enter the right MD5 host key that is used by your SFTP server. While the Axis device supports both MD5 and SHA-256 hash keys, we recommend using SHA-256 due to stronger security over MD5. For more information on how to configure an SFTP server with an Axis device, go to the AXIS OS Portal.
Use temporary file name: Select to upload files with temporary, automatically generated filenames. The files get renamed to the desired names when the upload completes. If the upload is aborted or interrupted, you don’t get any corrupt files. However, you probably still get the temporary files. This way, you know that all files that have the desired name are correct.
SIP or VMS:
SIP: Select to make a SIP call.
VMS: Select to make a VMS call.
From SIP account: Select from the list.
To SIP address: Enter the SIP address.
Test: Click to test that your call settings works.
Email
Send email to: Enter the email address to send emails to. To enter multiple addresses, use commas to separate them.
Send email from: Enter the email address of the sending server.
Username: Enter the username for the mail server. Leave this field empty if the mail server does not require authentication.
Password: Enter the password for the mail server. Leave this field empty if the mail server does not require authentication.
Email server (SMTP): Enter the name of the SMTP server, for example, smtp.gmail.com, smtp.mail.yahoo.com.
Port: Enter the port number for the SMTP server, using values in the range 0-65535. The default value is 587.
Encryption: To use encryption, select either SSL or TLS.
Validate server certificate: If you use encryption, select to validate the identity of the device. The certificate can be self-signed or issued by a Certificate Authority (CA).
POP authentication: Turn on to enter the name of the POP server, for example, pop.gmail.com.
Note
Some email providers have security filters that prevent users from receiving or viewing large amount of attachments, from receiving scheduled emails and similar. Check the email provider's security policy to avoid your email account being locked or missing out on your expected emails.
TCP
Host: Enter the server's IP address or hostname. If you enter a hostname, make sure that a DNS server is specified under System > Network > IPv4 and IPv6.
Port: Enter the port number used to access the server.
Test: Click to test the setup.
The context menu contains:
View recipient: Click to view all the recipient details.
Copy recipient: Click to copy a recipient. When you copy, you can make changes to the new recipient.
Delete recipient: Click to delete the recipient permanently.
Schedules
Schedules and pulses can be used as conditions in rules. The list shows all the schedules and pulses currently configured in the product, along with information about their configuration.
Add schedule: Click to create a schedule or pulse.
Manual triggers
You can use the manual trigger to manually trigger a rule. The manual trigger can, for example, be used to validate actions during product installation and configuration.
MQTT
MQTT (Message Queuing Telemetry Transport) is a standard messaging protocol for the Internet of Things (IoT). It was designed for simplified IoT integration and is used in a wide variety of industries to connect remote devices with a small code footprint and minimal network bandwidth. The MQTT client in Axis device software can simplify integration of data and events produced in the device to systems which are not video management software (VMS).
Set up the device as an MQTT client. MQTT communication is based on two entities, the clients and the broker. The clients can send and receive messages. The broker is responsible for routing messages between clients.
ALPN is a TLS/SSL extension that allows for the selection of an application protocol during the handshake phase of the connection between the client and server. This is used to enable MQTT traffic over the same port that is used for other protocols, such as HTTP. In some cases, there might not be a dedicated port open for MQTT communication. A solution in such cases is to use ALPN to negotiate the use of MQTT as the application protocol on a standard port, allowed by the firewalls.
MQTT client
Connect: Turn on or off the MQTT client.
Status: Shows the current status of the MQTT client.
Broker
Host: Enter the hostname or IP address of the MQTT server.
Protocol: Select which protocol to use.
Port: Enter the port number.
1883 is the default value for MQTT over TCP
8883 is the default value for MQTT over SSL
80 is the default value for MQTT over WebSocket
443 is the default value for MQTT over WebSocket Secure
ALPN protocol: Enter the ALPN protocol name provided by your MQTT broker provider. This is only applicable with MQTT over SSL and MQTT over WebSocket Secure.
Username: Enter the username that the client will use to access the server.
Password: Enter a password for the username.
Client ID: Enter a client ID. The client identifier is sent to the server when the client connects to it.
Clean session: Controls the behavior at connection and disconnection time. When selected, the state information is discarded at connect and disconnect.
HTTP proxy: A URL with a maximum length of 255 bytes. You can leave the field empty if you don't want to use an HTTP proxy.
HTTPS proxy: A URL with a maximum length of 255 bytes. You can leave the field empty if you don't want to use an HTTPS proxy.
Keep alive interval: Enables the client to detect when the server is no longer available without having to wait for the long TCP/IP timeout.
Timeout: The time interval in seconds to allow a connect to complete. Default value: 60
Device topic prefix: Used in the default values for the topic in the connect message and LWT message on the MQTT client tab, and in the publication conditions on the MQTT publication tab.
Reconnect automatically: Specifies whether the client should reconnect automatically after a disconnect.
Connect message
Specifies if a message should be sent out when a connection is established.
Send message: Turn on to send messages.
Use default: Turn off to enter your own default message.
Topic: Enter the topic for the default message.
Payload: Enter the content for the default message.
Retain: Select to keep the state of client on this Topic
QoS: Change the QoS layer for the packet flow.
Last Will and Testament message
The Last Will Testament (LWT) lets a client provide a testament along with its credentials when connecting to the broker. If the client disconnects ungracefully at some point later (maybe because his power source died), it can let the broker deliver a message to other clients. This LWT message has the same form as an ordinary message and gets routed via the same mechanics.
Send message: Turn on to send messages.
Use default: Turn off to enter your own default message.
Topic: Enter the topic for the default message.
Payload: Enter the content for the default message.
Retain: Select to keep the state of client on this Topic
QoS: Change the QoS layer for the packet flow.
MQTT publication
Use default topic prefix: Select to use the default topic prefix, that is defined in the device topic prefix in the MQTT client tab.
Include topic name: Select to include the topic that describes the condition in the MQTT topic.
Include topic namespaces: Select to include ONVIF topic namespaces in the MQTT topic.
Include serial number: Select to include the device’s serial number in the MQTT payload.
Add condition: Click to add a condition.
Retain: Defines which MQTT messages are sent as retained.
None: Send all messages as non-retained.
Property: Send only stateful messages as retained.
All: Send both stateful and stateless messages as retained.
QoS: Select the desired level for the MQTT publication.
MQTT subscriptions
Add subscription: Click to add a new MQTT subscription.
Subscription filter: Enter the MQTT topic that you want to subscribe to.
Use device topic prefix: Add the subscription filter as prefix to the MQTT topic.
Subscription type:
Stateless: Select to convert MQTT messages into a stateless message.
Stateful: Select to convert MQTT messages into a condition. The payload is used as the state.
QoS: Select the desired level for the MQTT subscription.
MQTT overlays
Note
Connect to an MQTT broker before you add MQTT overlay modifiers.
Add overlay modifier: Click to add a new overlay modifier.
Topic filter: Add the MQTT topic that contains the data you want to show in the overlay.
Data field: Specify the key for the message payload that you want to show in the overlay, assuming the message is in JSON format.
Modifier: Use the resulting modifier when you create the overlay.
Modifiers that start with #XMP show all of the data received from the topic.
Modifiers that start with #XMD show the data specified in the data field.
SIP
Settings
Session Initiation Protocol (SIP) is used for interactive communication sessions between users. The sessions can include audio and video.
SIP setup assistant: Click to set up and configure SIP step by step.
Enable SIP: Check this option to make it possible to initiate and receive SIP calls.
Allow incoming calls: Check this option to allow incoming calls from other SIP devices.
Call handling
Calling timeout: Set the maximum duration of an attempted call if no one answers.
Incoming call duration: Set the maximum time an incoming call can last (max 10 min).
End calls after: Set the maximum time that a call can last (max 60 minutes). Select Infinite call duration if you don’t want to limit the length of a call.
Ports
A port number must be between 1024 and 65535.
SIP port: The network port used for SIP communication. The signaling traffic through this port is non-encrypted. The default port number is 5060. Enter a different port number if required.
TLS port: The network port used for encrypted SIP communication. The signaling traffic through this port is encrypted with Transport Layer Security (TLS). The default port number is 5061. Enter a different port number if required.
RTP start port: The network port used for the first RTP media stream in a SIP call. The default start port number is 4000. Some firewalls block RTP traffic on certain port numbers.
NAT traversal
Use NAT (Network Address Translation) traversal when the device is located on an private network (LAN) and you want to make it available from outside of that network.
Note
For NAT traversal to work, the router must support it. The router must also support 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 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 the TURN server address and the login information.
Audio
Audio codec priority: Select at least one audio codec with the desired audio quality for SIP calls. Drag-and-drop to change the priority.
Note
The selected codecs must match the call recipient codec, since the recipient codec is decisive when a call is made.
Audio direction: Select allowed audio directions.
Additional
UDP-to-TCP switching: Select to allow calls to switch transport protocols from UDP (User Datagram Protocol) to TCP (Transmission Control Protocol) temporarily. The reason for switching is to avoid fragmentation, and the switch can take place if a request is within 200 bytes of the maximum transmission unit (MTU) or larger than 1300 bytes.
Allow via rewrite: Select to send the local IP address instead of the router's public IP address.
Allow contact rewrite: Select to send the local IP address instead of the router's public IP address.
Register with server every: Set how often you want the device to register with the SIP server for the existing SIP accounts.
DTMF payload type: Changes the default payload type for DTMF.
Max retransmissions: Set the maximum number of times the device tries to connect to the SIP server before it stops trying.
Seconds until failback: Set the number of seconds until the device tries to reconnect to the primary SIP server after it has failed over to a secondary SIP server.
Accounts
All current SIP accounts are listed under SIP accounts. For registered accounts, the colored circle lets you know the status.
The account is successfully registered with the SIP server.
There is a problem with the account. Possible reasons can be authorization failure, that the account credentials are wrong, or that the SIP server can’t find the account.
The peer to peer (default) account is an automatically created account. You can delete it if you create at least one other account and set that account as default. The default account is always used when a VAPIX® Application Programming Interface (API) call is made without specifying which SIP account to call from.
Add account: Click to create a new SIP account.
Active: Select to be able to use the account.
Make default: Select to make this the default account. There must be a default account, and there can only be one default account.
Answer automatically: Select to automatically answer an incoming call.
Prioritize IPv6 over IPv4: Select to prioritize IPv6 addresses over IPv4 addresses. This is useful when you connect to peer-to-peer accounts or domain names that resolve in both IPv4 and IPv6 addresses. You can only prioritize IPv6 for domain names that are mapped to IPv6 addresses.
Name: Enter a descriptive name. This can, for example, be a first and last name, a role, or a location. The name is not unique.
User ID: Enter the unique extension or phone number assigned to the device.
Peer-to-peer: Use for direct calls to another SIP device on the local network.
Registered: Use for calls to SIP devices outside the local network, through a SIP server.
Domain: If available, enter the public domain name. It will be shown as part of the SIP address when calling other accounts.
Password: Enter the password associated with the SIP account for authenticating against the SIP server.
Authentication ID: Enter the authentication ID used for authenticating against the SIP server. If it is the same as the user ID, you don’t need to enter the authentication ID.
Caller ID: The name which is presented to the recipient of calls from the device.
Registrar: Enter the IP address for the registrar.
Transport mode: Select the SIP transport mode for the account: UPD, TCP, or TLS.
TLS version (only with transport mode TLS): Select the version of TLS to use. Versions v1.2 and v1.3 are the most secure. Automatic selects the most secure version that the system can handle.
Media encryption (only with transport mode TLS): Select the type of encryption for media (audio and video) in SIP calls.
Certificate (only with transport mode TLS): Select a certificate.
Verify server certificate (only with transport mode TLS): Check to verify the server certificate.
Secondary SIP server: Turn on if you want the device to try to register on a secondary SIP server if registration on the primary SIP server fails.
SIP secure: Select to use Secure Session Initiation Protocol (SIPS). SIPS uses the TLS transport mode to encrypt traffic.
Proxies
Proxy: Click to add a proxy.
Prioritize: If you have added two or more proxies, click to prioritize them.
Server address: Enter the IP address of the SIP proxy server.
Username: If required, enter the username for the SIP proxy server.
Password: If required, enter the password for the SIP proxy server.
Video
View area: Select the view area to use for video calls. If you select none, the native view is used.
Resolution: Select the resolution to use for video calls. The resolution affects the required bandwidth.
Frame rate: Select the number of frames per second for video calls. The frame rate affects the required bandwidth.
H.264 profile: Select the profile to use for video calls.
DTMF
Add sequence: Click to create a new dual-tone multifrequency (DTMF) sequence. To create a rule that is activated by touch-tone, go to Events > Rules.
Sequence: Enter the characters to activate the rule. Allowed characters: 0–9, A-D, #, and *.
Description: Enter a description of the action to be triggered by the sequence.
Accounts: Select the accounts that will use the DTMF sequence. If you choose peer-to-peer, all peer-to-peer accounts will share the same DTMF sequence.
Protocols
Select the protocols to use for each account. All peer-to-peer accounts share the same protocol settings.
Use RTP (RFC2833): Turn on to allow dual-tone multifrequency (DTMF) signaling, other tone signals and telephony events in RTP packets.
Use SIP INFO (RFC2976): Turn to include the INFO method to the SIP protocol. The INFO method adds optional application layer information, generally related to the session.
Test call
SIP account: Select which account to make the test call from.
SIP address: Enter a SIP address and click to make a test call and verify that the account works.
Access list
Use access list: Turn on to restrict who can make calls to the device.
Policy:
Allow: Select to allow incoming calls only from the sources in the access list.
Block: Select to block incoming calls from the sources in the access list.
Add source: Click to create a new entry in the access list.
SIP source: Type the caller ID or SIP server address of the source.
Accessories
I/O ports
Use digital input to connect external devices that can toggle between an open and closed circuit, for example, PIR sensors, door or window contacts, and glass break detectors.
Use digital output to connect external devices such as relays and LEDs. You can activate connected devices through the VAPIX® Application Programming Interface or the web interface.
Port
Name: Edit the text to rename the port.
Direction: indicates that the port is an input port. indicates that it’s an output port. If the port is configurable, you can click the icons to change between input and output.
Normal state: Click for open circuit, and for closed circuit.
Current state: Shows the current state of the port. The input or output is activated when the current state is different from the normal state. An input on the device has an open circuit when it’s disconnected or when there is a voltage above 1 V DC.
Note
During restart, the output circuit is open. When the restart is complete, the circuit goes back to the normal position. If you change any settings on this page, the output circuits go back to their normal positions regardless of any active triggers.
Supervised: Turn on to make it possible to detect and trigger actions if someone tampers with the connection to digital I/O devices. In addition to detecting if an input is open or closed, you can also detect if someone has tampered with it (that is, cut or shorted). To supervise the connection requires additional hardware (end-of-line resistors) in the external I/O loop.
Logs
Reports and logs
Reports
View the device server report: View information about the product status in a pop-up window. The Access Log is automatically included in the Server Report.
Download the device server report: It creates a .zip file that contains a complete server report text file in UTF–8 format, as well as a snapshot of the current live view image. Always include the server report .zip file when you contact support.
Download the crash report: Download an archive with detailed information about the server's status. The crash report contains information that is in the server report as well as detailed debug information. This report might contain sensitive information such as network traces. It can take several minutes to generate the report.
Logs
View the system log: Click to show information about system events such as device startup, warnings, and critical messages.
View the access log: Click to show all failed attempts to access the device, for example, when a wrong login password is used.
Network trace
Important
A network trace file might contain sensitive information, for example certificates or passwords.
A network trace file can help you troubleshoot problems by recording activity on the network.
Trace time: Select the duration of the trace in seconds or minutes, and click Download.
Remote system log
Syslog is a standard for message logging. It allows separation of the software that generates messages, the system that stores them, and the software that reports and analyzes them. Each message is labeled with a facility code, which indicates the software type generating the message, and assigned a severity level.
Server: Click to add a new server.
Host: Enter the hostname or IP address of the server.
Format: Select which syslog message format to use.
Axis
RFC 3164
RFC 5424
Protocol: Select the protocol to use:
UDP (Default port is 514)
TCP (Default port is 601)
TLS (Default port is 6514)
Port: Edit the port number to use a different port.
Severity: Select which messages to send when triggered.
CA certificate set: See the current settings or add a certificate.
Plain config
Plain config is for advanced users with experience of Axis device configuration. Most parameters can be set and edited from this page.
Maintenance
Restart: Restart the device. This does not affect any of the current settings. Running applications restart automatically.
Restore: Return most settings to the factory default values. Afterwards you must reconfigure the device and apps, reinstall any apps that didn’t come preinstalled, and recreate any events and presets.
Important
The only settings saved after restore are:
Boot protocol (DHCP or static)
Static IP address
Default router
Subnet mask
802.1X settings
O3C settings
DNS server IP address
Factory default: Return all settings to the factory default values. Afterwards you must reset the IP address to make the device accessible.
Note
All Axis device software is digitally signed to ensure that you only install verified software on your device. This further increases the overall minimum cybersecurity level of Axis devices. For more information, see the white paper “Axis Edge Vault” at axis.com.
AXIS OS upgrade: Upgrade to a new AXIS OS version. New releases can contain improved functionality, bug fixes, and completely new features. We recommend you to always use the latest AXIS OS release. To download the latest release, go to axis.com/support.
When you upgrade, you can choose between three options:
Standard upgrade: Upgrade to the new AXIS OS version.
Factory default: Upgrade and return all settings to the factory default values. When you choose this option, you can’t revert to the previous AXIS OS version after the upgrade.
Autorollback: Upgrade and confirm the upgrade within the set time. If you don’t confirm, the device reverts to the previous AXIS OS version.
AXIS OS rollback: Revert to the previously installed AXIS OS version.
Specifications
Product overview
Network connector PoE
Status LED indicator
I/O connector
Control button
White LEDs
RGBA (red, blue, green, amber) LEDs
Siren
Light direction A
Light direction B
Light direction C
Light direction D
LED indicators
Status LED
Indication
Green
Shows steady green for 10 seconds for normal operation after startup completed.
Amber
Steady during startup, during reset to factory default or when restoring settings.
Connecting to a one-click cloud connection (O3C) service over the internet. To connect, press and hold the button for about 3 seconds until the status LED flashes green.
Connectors
Network connector
RJ45 Ethernet connector with Power over Ethernet (PoE).
I/O connector
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.
4-pin terminal block
Function
Pin
Notes
Specifications
DC ground
1
0 V DC
DC output
2
Can be used to power auxiliary equipment. Note: This pin can only be used as power out.
12 V DC Max load = 50 mA
Configurable (Input or Output)
3–4
Digital input – Connect to pin 1 to activate, or leave floating (unconnected) to deactivate.
0 to max 30 V DC
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.
Wall mounted at a distance of 1 meter on axis at volume setting 5.
Clean your device
You can clean your device with lukewarm water and mild, nonabrasive soap.
NOTICE
Harsh chemicals can damage the device. Don’t use chemicals such as window cleaner or acetone to clean your device.
Don’t spray detergent directly on the device. Instead, spray detergent on a nonabrasive cloth and use that to clean the device.
Avoid cleaning in direct sunlight or elevated temperatures, since this can cause stains.
Use a can of compressed air to remove dust and loose dirt from the device.
If necessary, clean the device with a soft microfiber cloth dampened with lukewarm water and mild, nonabrasive soap.
To avoid stains, dry the device with a clean, nonabrasive cloth.
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
Preconfigured and customized settings are saved when you upgrade the device software (provided that the features are available in the new AXIS OS) although this is not guaranteed by Axis Communications AB.
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 issues, clues, and solutions
If you can’t find what you’re looking for here, try the troubleshooting section at axis.com/support.
Problems upgrading AXIS OS
AXIS OS upgrade failure
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
The device is located on a different subnet
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 cannot set the IP address. Contact your network administrator to obtain an IP address.
The IP address is being used by another device
Disconnect the Axis device from the network. Run the ping command (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 may 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.
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 may be problems accessing the device.
The device can’t be accessed from a browser
Can’t log in
When HTTPS is enabled, ensure that the correct protocol (HTTP or HTTPS) is used when attempting to log in. You may need to manually type http or https in the browser’s address field.
If the password for the root account is lost, the device must be reset to the factory default settings. See Reset to factory default settings.
The IP address has been changed by DHCP
IP addresses obtained from a DHCP server are dynamic and may 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, a static IP address can be assigned 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.
The device is accessible locally but not externally
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 5: 30-day trial version free of charge, ideal for small to mid-size systems.
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.
Can’t connect over port 8883 with MQTT over SSL
The firewall blocks traffic using port 8883 as it’s deemed insecure.
In some cases the server/broker might not provide a specific port for MQTT communication. It may 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 the sound
The device is not as loud as expected
Check that the device is closed correctly and that there are no obstructions in the horn or on the speaker element.
The device makes no sound
Check if the device is in Maintenance mode. If it’s in maintenance mode, turn it off.
Problems with the light
The device is not as bright as expected
Check that a PoE class 4 power supply is used.
Check the device’s ambient temperature. If the device is installed in a high temperature environment, the lights will dim automatically.
Performance considerations
The following factors are important to consider:
Heavy network utilization due to poor infrastructure affects the bandwidth.
For maximum light output, a PoE Class 4 power source is required.
The light output can be reduced if the device is soiled, or at high ambient temperatures.
In bright environments such as in direct sunlight, consider using the sunshield accessory to improve visibility.
The sound output can be reduced if the siren is blocked or if the device is not correctly closed.
The installation environment can affect the sound output. The sound volume can be higher if the device is installed on a wall or in an enclosed space, and lower if installed on a pole in an open space.
