AXIS Audio Manager Center

AXIS Audio Manager Center is a secure and scalable solution for remote management and monitoring of large and complex audio systems.

• Organize your audio sites — You can organize your AXIS Audio Manager Edge audio sites in a structure that suits your organization.

Example

A location named “France” could contain a location called “Paris”, which in turn contains all the audio sites located in Paris.

Example

A location named “Sales region South” could contain all the cities belonging to that region, which in turn contains all the audio sites located in those cities.

• Monitor your system — The Dashboard and Audio sites views give an overview of your system. Filtering functionality makes troubleshooting easy.

• Access your sites remotely — Access the user interface of your sites remotely in a secure way from the Audio sites view.

• Manage users — Invite users and add each user to one or several user groups. Each user group is given a certain access right, and assigned to a location in the audio site structure.

Example

A single user can be part of a group with content manager rights for Europe, but also to a group with administrator rights for an audio site in Paris, France.

• Premium features

• • Scheduling — Schedule announcements, advertisements, and music for multiple audio sites.

  • Paging — Send live audio messages or start two-way communication with devices on your audio sites using the AXIS Audio Manager mobile app.

  • Audio file distribution — Distribute audio files to your audio sites for local scheduling.

For the new features in each AXIS Audio Manager Center release, go to help.axis.com/whats-new-in-axis-audio-manager-center.

• You need to have set up and configured at least one AXIS Audio Manager Edge audio site. For more information, visit the AXIS Audio Manager Edge User Manual.

• To enable communication between AXIS Audio Manager Edge and AXIS Audio Manager Center, the network where the leader device (the main device in your AXIS Audio Manager Edge audio site) is located:

• DNS	Port	Information
  dispatchse1-st.axis.com ​dispatchse2-st.axis.com ​dispatcher-st.axis.com ​dispatchus1-st.axis.com dispatchjp1-st.axis.com	443, 80 Outbound, TCP	Proprietary device communication channel. One of these ports is required. Port 80 is only used if port 443 is not available.
  *.devices.audiomanager.axis.com	443 Outbound, TCP	Proprietary device communication channel.
  a1ecdk2dyb75d7-ats.iot.eu-west-1.amazonaws.com	8883 Outbound, TCP	MQTT channel used for sending and receiving data from a device to the cloud service.
  content.audiomanager.axis.com	443 Outbound, TCP	Necessary for content distribution in scheduling.

1. Go to audiomanager.axis.com in your web browser.

2. Sign in using the credentials for your My Axis account. If you don’t have a My Axis account, you can create one from the login window.

3. When you sign in for the first time, you will be prompted to create your organization.

When you are invited to an organization, you will receive an email with an invitation link from AXIS Audio Manager Center with the subject "User invitation to an organization".

1. To accept the invitation, click the included link or paste it in your browser.

2. Sign in with your My Axis account. If you do not have a My Axis account, you can create one from the sign-in page.

3. You will automatically be routed to the organization you were invited to.

Organize your audio sites in a structure that makes it easy to find a site or group of sites in your organization. You can assign groups of users to single audio sites or groups of audio sites by selecting locations in the structure. For more information, see Manage users.

1. Go to Audio sites.

2. To create a location:

3. 1. Select where in the structure to add the new location.

   2. Click + Create.

   3. Name the location and click Create.

Example

A location can't be moved after it has been created. Plan your structure before creating locations.

Audio sites are organized in the structure you created under locations. Each audio site belongs to one location, so make sure you have selected the correct location before proceeding.

Enable AXIS Audio Manager Center integration in the audio sites you want to add:

1. Log in locally to your AXIS Audio Manager Edge audio site.

2. Go to System settings > Connectivity.

3. Select the checkbox for AXIS Audio Manager Center integration.

4. If needed, select AXIS Audio Manager Center O3C proxy and enter your organization’s proxy details for the network where the audio site is located.

5. Click Save.

Add an audio site to a location:

1. In AXIS Audio Manager Center, go to Audio sites.

2. Select location in the structure.

3. Click + Add audio site.

4. Under Name, enter the site name.

5. Under Serial number (S/N), enter the serial number of the device used as leader in the audio site.

   Format example: S/N: XXXXXXXXXXXX (12 digit hexadecimal)

6. Under Owner authentication key (OAK), enter the OAK key (Owner Authentication Key) of the device used as leader in the audio site.

   Format example: OAK: XXXXXXXXXXXX (12 digit hexadecimal)

   To find the OAK key:

7. 1. Log in locally to your AXIS Audio Manager Edge audio site.

   2. Go to System settings > Leader device settings.

   3. Click Go to device settings.

   4. Go to System > Network.

   5. Under One-click cloud connection and Owner authentication key (OAK), click Get key.

   6. Note

      You find both the S/N (MAC address) and the OAK key (Owner Authentication Key) on a note that came with the product that is used as leader in the audio system.

      Contact Axis in case you lose your note. Proof of ownership is required for receiving a new key.

8. Set the geographic location of the audio site:

9. 1. Select Place audio site on map.

   2. Write an address in the search to zoom in on that location.

   3. Click on the map to add the location.

10. To change or remove the location later on, go to Audio sites, click the row of the audio site to show its details, and then scroll down to the map.

1. Go to Audio sites.

2. Click the row of an audio site to see its details.

   You can also click the audio site on the map.

3. View and edit the audio site details:

4. • Under :

   • • Rename the audio site.

     • Download a server report file for troubleshooting.

     • Open the web interface of the leader device.

     • Remove the audio site.

   • On the Overview tab:

   • • Find information about the leader device, such as AXIS OS version, serial number and product name.

     • Edit or remove the geographical location on the map.

     • Add notes to the audio site for internal reference.

     • Assign labels to make audio sites easier to find and filter.

   • On the Scheduling tab:

   • • View or change the opening hours of the audio site.

     • See which schedules apply to the audio site.

     • View source tag mappings (source tags are managed on AXIS Audio Manager Edge).

When you create a new organization, you become its owner and thereby assigned the highest access level as part of the Organization administrators group. Users belonging to this group will have full read-and-write access to the configurations in the organization, including all locations and sites. To transfer ownership, you have to elevate a user to the owner role. There must be at least one owner of an organization.

In order to use AXIS Audio Manager Center you have to be registered as a user in an organization. There are three pre-defined user roles:

• Administrator – Administrators have read/write access to the locations and audio sites that are assigned to their user group. If they are assigned a location in the audio sites structure, they can add new locations and audio sites below that location.

• Content manager – Content managers have access to upload and schedule content (music, advertisements and announcements) in all audio sites assigned to their user group. If they are assigned a location in the audio sites structure, they have access to all audio sites below this location. Content managers can also set the opening hours and set music volumes for their assigned audio sites.

• Playback operator – Playback operators have access to setting the music volumes in all audio sites assigned to their user group. If they are assigned a location in the audio sites structure, they have access to all audio sites below this location.

If your organization has a premium license, a fourth role is also available:

• Paging operator(premium) — Paging operators can send live audio messages to their assigned audio sites using the AXIS Audio Manager mobile app. This role is available when your organization has a premium license.

The total access rights for users are decided by what user groups they are members of. Each user group has a defined user role and audio sites assigned to the group. A user can be a member of several user groups and the highest access rights for a particular audio site takes precedence for that user.

Example

Imagine a user that belongs to both of the following groups:

• Group: Content managers France

• • User role: Content manager

  • Location: France

• Group: Administrators Paris

• • User role: Administrator

  • Location: Paris (sub-location to France)

The user will have content management rights for all the audio sites in France, except for those in Paris, for which the user will have administrator rights. This is because the administrator rights are of a higher level than content management rights. When a user belongs to several groups, it is possible that multiple user roles apply to the same location. When this happens, only the user role with the highest level of access rights will be applied to the location.

1. Invite a user to your organization:

2. Go to User management.

3. Note

   Only available for owners and organization-level administrators.

4. Create a user group and assign it a user role and audio site access:

5. 1. Click Create user group.

   2. Enter the user group name.

   3. Click Next.

   4. Under User role, select a role for the user group.

   5. Under Location, click Add.

   6. Under Members, click Add.

   7. Click Create.

1. Invite a new user:

2. Go to User management > Users.

3. Click Invite user.

4. Enter the email address to the user you wish to invite.

5. Select the user group.

6. Write a message that will be included in the invitation mail.

7. Click Invite.

Invited users will receive an email with a link to your organization. When they follow the link, they will be prompted to sign in, after which they will be automatically routed to the correct organization. A user can be part of several organizations.

1. Add existing users to a user group:

2. Go to User management.

3. Select the user group which the user should be added to.

4. Click Add next to Members.

5. Locate the user in the list and click Add.

The dashboard gives you an overview of your system. It shows the status of each audio site — for example, whether it's online, offline, or degraded — along with license information and user and device counts. With premium features enabled, additional cards such as paging recipient status are also shown.

1. Go to Dashboard.

2. Check the state of your audio sites and schedules.

3. Investigate your audio sites:

4. 1. Go to Audio sites.

   2. Click the filter icon above the audio site list and select the issues you want to investigate.

      For information about each type of issue, see Troubleshooting.

   3. To investigate an audio site, click > Open AXIS Audio Manager Edge.

5. Investigate your schedules:

6. 1. Go to Scheduling.

   2. Click the filter icon above the schedules list and select the issues you want to investigate.

      For information about each type of issue, see Troubleshooting.

   3. To investigate a schedule, click the row in the list.

AXIS Audio Manager Center can send email and webhook notifications for different types of events that occur on your audio sites. To set up email notifications, you need to be an organization administrator since they apply to the entire organization. To set up webhook notifications, you need to be an administrator on the locations you want to monitor..

To set up an email notification, you need to be an organization administrator, since email notifications apply to the entire organization. To set up a webhook notification, you need to be an administrator on the locations you want to monitor.

You must be an organization-level administrator to set up email notifications.

To avoid sending too many emails, we will not send an email every time an event occurs. Instead, we wait until an event occurs, and then register events during the selected amount of time before sending the notification. The notification email will contain a list of up to ten events that occurred during the time period, and a link to the event log where you can see all the events. If you want real-time notifications, we suggest you set up a webhook instead.

1. Go to Notifications.

2. Click + Create.

3. Name your notification.

4. Select Email.

5. Click Next.

6. Enter the email for the recipient.

7. Select a notification trigger.

8. Click Create.

9. The recipient will receive en email with a confirmation request. After clicking Confirm in the email, the recipient will start receiving notifications.

10. Refresh your browser to check that the status of the notification has changed from Pending to OK, which indicates that the recipient has confirmed the notification.

For more information about webhook notification, see Webhook integration.

1. Go to Notifications.

2. Click + Create.

3. Name your notification.

4. Select Webhook.

5. Click Next.

6. Enter the details for the recipient.

7. Select one or more triggers from the available event types.

8. To select locations, click + Select.

9. Click Create.

AXIS Audio Manager Center provides secure remote access to added audio sites. This enables remote audio site configuration of the local AXIS Audio Manager Edge system. When accessing an audio site, the rights of your user role or user group will decide what you will be able to do remotely. Administrators have full access to all settings on the audio site, while content managers and playback operators have limited access.

1. To open AXIS Audio Manager Edge:

2. Go to Audio sites and find your audio site.

3. Click > Open AXIS Audio Manager Edge.

When you’ve set up AXIS Audio Manager Center and assigned users as well as permissions to your users, then the users will also have access to the audio system through the AXIS Audio Manager mobile app for iOS and Android.

By selecting Connect remotely in the mobile app, your users can log in to AXIS Audio Manager Center and select an audio site to control.

The event log contains events that have occurred in the part of the organization where you are administrator.

1. Go to Event log.

2. Click Data selection.

3. Select a time frame.

4. • Relative: Select how far back in time from the present that you want to retrieve data.

   • Absolute: Select a time interval that you want to retrieve data from.

5. To add a filter, click + Filter and select conditions.

6. Under Order, select how to present the retrieved data.

7. Click Retrieve data to load the matching events.

8. To export the retrieved data to a CSV file, click Export.

AXIS Audio Manager Center has features that are only available if your organization is licensed. These features are typically advanced features that perform operations on several audio sites at once, such as content distribution or batch scheduling of music.

AXIS Audio Manager Center supports distribution of content files to your audio sites for local scheduling. For each audio site, the content will be stored on the leader device and added to the library of the corresponding content type. The files will not be added automatically to any schedule.

Supported file formats: mp3, mpeg, ogg, opus, wave

Maximum allowed file size: 20 MB

1. Go to Distribute audio files and select a content type (Announcement, Advertisement or Music).

2. Click + Add next to Files.

3. Select the files to distribute and click Open.

4. Click + Add next to Audio sites.

5. Select locations in the audio sites structure.

   The content will be distributed to all the audio sites in the location, including audio sites in sub-locations.

6. Click Distribute audio files.

With AXIS Audio Manager Center you can schedule announcements, advertisements and music to multiple audio sites at once. When you create a schedule, you choose which audio sites to include by adding specific audio sites to the schedule.

You can edit a schedule while it's enabled. Before your changes are applied, you'll see a summary of which audio sites will be added to or removed from the schedule.

When you enable a schedule, it is automatically applied to the audio sites included in the schedule, as long as the audio site is connected. If an audio site is not connected, then the schedule will be applied as soon as it becomes connected.

Each audio site can have one enabled schedule per type: music, announcements, or advertisements. Announcements take priority over advertisements, which take priority over music.

AXIS Audio Manager Center also distributes the media content necessary for executing a schedule, to all targeted audio sites. The exception is music schedules that were created with a local library or source tag.

When you schedule relative to opening hours, there is a risk that the event is set to play outside the day (0–24). This audio will not play. For instance, if you schedule an announcement to play 5 hours after closing time, and the closing time is 9pm, the event will be scheduled for 2am the next day, and hence will not play.

• Learn more:

• Source tags

• Before you create a schedule, make sure the following are in place:

• Set the opening hours on each audio site you want to target (on the audio site's Scheduling tab or in AXIS Audio Manager Edge).

• Assign labels to audio sites to make them easier to find when you select audio sites for a schedule (go to Labels to create and manage labels).

• Before you create a music schedule, also make sure the following are in place:

• Create music sources if you're using a web stream (go to Music sources).

• Configure source tags in AXIS Audio Manager Edge if you want to control which local source plays on which zone.

1. Create a schedule:

2. 1. Go to Scheduling.

   2. Click + Create schedule.

   3. Name the schedule.

   4. Under Type of schedule, select Announcement.

   5. Click Create.

3. To upload audio files and create playlists, go to Content.

4. Add audio sites to the schedule:

5. 1. Go to the Audio sites tab.

   2. Click Select audio sites.

   3. Select the audio sites you want to include, and click Confirm.

6. Configure the schedule:

7. 1. Go to Schedule.

   2. Click + Event and select Single event or Interval event.

   3. Fill in the details and click Add.

   4. To save the schedule without enabling it, click Save.

8. Preview the schedule:

9. 1. Under Preview opening hours, select example opening hours or an audio site.

      The event will become gray if it will not be played at all during the selected opening hours.

10. Enable the schedule:

11. 1. Click Save.

    2. Click Enable schedule.

    3. Review the summary of affected audio sites and confirm.

12. To save the changes you made to the schedule, click Save.

1. Create a schedule:

2. 1. Go to Scheduling.

   2. Click + Create schedule.

   3. Name the schedule.

   4. Under Type of schedule, select Advertisement.

   5. Click Create.

3. To upload audio files and create playlists, go to Content.

4. Add audio sites to the schedule:

5. 1. Go to Audio sites.

   2. Click Select audio sites.

   3. Select the audio sites you want to include, and click Confirm.

6. To see the audio sites included in the schedule, go to Audio sites.

7. Configure the schedule:

8. 1. Go to Schedule.

   2. Click + Event and select Single event or Interval event.

   3. Fill in the details and click Add.

   4. To save the schedule without enabling it, click Save.

9. Preview the schedule:

10. 1. Under Preview opening hours, select example opening hours or an audio site.

       The event will become gray if it will not be played at all during the selected opening hours.

11. Enable the schedule:

12. 1. Click Save.

    2. Click Enable schedule.

    3. Review the summary of affected audio sites, then confirm.

13. To save the changes you made to the schedule, click Save.

You can create background music schedules that start and end with an offset relative to the opening hours of an audio site.

For more information, see Opening and closing offset.

• Supported music sources:

• The local library of each audio site.

• A web stream distributed from AXIS Audio Manager Center.

  For more information, see Audio Manager Center Source.

• A source tag that targets local audio site sources, such as line-in and on-board applications.

  For more information, see Source tags.

• Prerequisites:

• The music schedule is applied relative to the opening hours at the local audio site.

  To set the opening hours for a local audio site, see Set the opening hours in the AXIS Audio Manager Edge user manual.

1. To use a web stream source:

2. 1. Go to Music sources and click + Create music source.

   2. Name the source.

   3. The type is currently limited to web stream, which is pre-selected.

   4. Enter the URL for the web stream.

   5. If the URL requires authentication, activate Use authentication and enter username and password.

   6. Click Create.

3. Create a schedule:

4. 1. Go to Scheduling and click + Create schedule.

   2. Name the schedule.

   3. Under Type of schedule, select Music.

   4. Click Create.

5. Add audio sites to the schedule:

6. 1. Go to Audio sites.

   2. Click Select audio sites.

   3. Select the audio sites you want to include, and click Confirm.

7. Configure the schedule:

8. 1. On the Schedule tab, click + Event.

   2. To require someone at the audio site to start playback manually, select Require manual playback start on audio sites.

      Otherwise, music starts automatically when the event begins.

   3. Set the offset relative to the opening and closing hours.

   4. Add music sources:

   5. 1. Click + Select to add a music source.

      2. Select a source: Local music library, an Audio Manager Center source, or a source tag.

      3. Click Add.

   6. Click Save.

9. Note

   You can add multiple sources to a music schedule. Users can switch sources locally from the dashboard in AXIS Audio Manager Edge if they are using a host device with AXIS OS 11.6 or later. For earlier AXIS OS versions, only the first source in the list will be played.

10. Save the schedule:

11. 1. To save without enabling, click Save.

       The schedule appears in your schedules list but is not enabled.

    2. To enable the schedule, click Save > Enable schedule and confirm.

       The schedule is distributed to all included audio sites.

12. Note

    Note that this overrides any local music schedules.

By using AXIS Audio Manager mobile app, you can page remotely from a smartphone to one or more devices on an audio site.

To use the mobile app for remote paging, you first need to create a paging recipient and a user group with paging operator rights in AXIS Audio Manager Center.

• Two types of SIP paging can be configured from AXIS Audio Manager Center:

• One-way paging: for sending, but not receiving, audio messages to one or more devices on an audio site. One-way paging recipients will appear on the Callout tab in the mobile app. You can send both live and pre-recorded audio messages.

• Two-way paging: for live two-way communication through a single device on an audio site. Two-way paging will appear on the Call tab in the mobile app.

1. Create a paging recipient:

2. 1. Go to Paging recipients.

   2. Under Location, select the audio site on which you want to create the paging recipient.

   3. Click + Create.

   4. Name your recipient.

   5. Under Type, select One-way or Two-way.

   6. Note

      We recommend that you create your two-way recipients first, before you create your one-way recipients.

   7. Click Create.

   8. For one-way paging, add the physical zones and devices you want to target.

      For two-way paging, select the device you want to communicate through.

   9. Click Create.

   10. Wait until it says OK under Status.

       If you receive Error instead, click under Actions in the paging recipient list and select Verify configuration to check the setup.

   11. Click > Ports to verify the SIP ports.

   12. Click > Volume to check that the volume level is normalized.

3. Give paging rights to users:

4. 1. Go to User management.

   2. Click + Create user group.

   3. Name the user group.

   4. Under User role, select Paging operator.

   5. Click Create.

   6. Add locations and members.

   7. Click Close.

A location is a node in the audio sites structure. For more information, see Create a structure for your audio sites.

Labels are used to add an identifier to an audio site that can be filtered on or searched for in AXIS Audio Manager Center.

• You can filter and search on a label in the Audio sites view to easier find sites.

The schedules are created relative to each local audio site's opening hours. This solves the problem when audio sites that are targeted by a batch schedule configuration have different opening hours. The opening offset determines when the music starts playing and the closing offset when the music stops playing.

Audio Manager Center Source is a source created under Music sources > Sources. It is automatically distributed to all audio sites in the organization. The source is managed centrally through AXIS Audio Manager Center. Currently, only web stream sources are supported.

If you plan to use sources local to your AXIS Audio Manager Edge audio sites in your AXIS Audio Manager Center schedules, then you will have to assign a source tag to these sources in each of your AXIS Audio Manager Edge audio sites. Source tags are created under Music sources > Source tags, and are distributed to all connected audio sites in the organization. To configure a source in a local audio site with a source tag, go to AXIS Audio Manager Edge > Music, select a source or playlist and assign a source tag. This source can then be used in a schedule distributed by AXIS Audio Manager Center.

• Examples of sources that must be defined locally:

• Line-in

• Playlist

• ACAP

• Unique web stream URLs (i.e. where the URL is unique to each audio site)

Example: An organization has bought an online streaming music service that uses an installed ACAP to deliver the service. They create a source tag "ACAP streaming" in Axis Audio Manager Center. Each audio site that has the ACAP music source must then assign it the source tag "ACAP streaming" to allow this source to be scheduled from Axis Audio Manager Center. When creating the schedule, they add the audio sites they want to target, then they set the wanted opening/closing offset and finally select the music source "Source tag" with the tag "ACAP streaming". The targeted audio sites now have a music schedule playing music via the streaming music service.

You can receive system events via webhook from AXIS Audio Manager Center. Events are delivered as HTTP POST requests.

A validation handshake must be completed before events can be sent to a consumer. When a webhook is configured, the sender issues a preflight request to validate the target endpoint. If the consumer does not respond appropriately to this request, the subscription will not be established.

To accept all issuers of webhook events, respond to the OPTIONS request with a 200 OK status and include the header: Webhook-Allowed-Origin: '*'

To accept only us as the issuer, respond with a 200 OK and include the exact origin from the Webhook-Request-Origin header.

To comply with the CloudEvents specification, webhook receivers must respond with a successful HTTP status such as 200 OK, 201 Created, 202 Accepted, or 204 No Content. Redirect responses (3xx) are not allowed and will not be followed.

If the receiver is temporarily overloaded, it should return 429 Too Many Requests. If the endpoint has been permanently retired, it should return 410 Gone, which disables the subscription and stops event delivery.

All webhook events follow this structure:

{
  "specversion": "1.0",
  "id": "<event-id>",
  "source": "com.axis.audiomanager",
  "type": "<event-type>",
  "time": "<timestamp>",
  "eventversion": "1",
  "eventcorrelationid": "<correlation-id>",
  "datacontenttype": "application/json",
  "dataschema": "com/axis/one/notification-service/webhook/@v/1.0.0",
  "data": {
    "data": { <event-specific data> },
    "datacontenttype": "application/json",
    "dataschema": "<event-specific schema>"
  }
}

1. There are three types of webhook events:

2. Audio site events — Changes in audio site status.

3. • Type: com.axis.audiomanager.status.site

   • Schema: com/axis/audiomanager/status/site/@v/1.0.0

   • Fields in data.data:

   • • siteName – The name of the audio site.

     • siteId – The id of the audio site.

     • siteLocationNames – The location path of the audio site.

     • statusSeverity – High level audio site status.

     • statusType – Audio site status subcategory.

     • organizationName – The name of the organization.

     • organizationId – id of the organization.

     • aamcUrl – Link to the event log in AXIS Audio Manager Center.

4. Scheduled events — Status changes for schedules in the organization.

5. • Type: com.axis.audiomanager.status.schedule

   • Schema: com/axis/audiomanager/status/schedule/@v/1.0.0

   • Fields in data.data:

   • • scheduleName – The name of the schedule.

     • scheduleId – The id of the schedule.

     • statusSeverity – High level schedule status.

     • statusType – Schedule status subcategory.

     • siteName – The name of the site which triggered the event.

     • siteId – The id of the audio site.

     • siteLocationNames – The location path for the audio site.

     • organizationName – the name of the organization.

     • organizationId – id of the organization.

     • aamcUrl – Link to the event log in AXIS Audio Manager Center.

6. Paging recipient events — Status updates for individual paging recipients on audio sites.

7. • Type: com.axis.audiomanager.status.paging

   • Schema: com/axis/audiomanager/status/paging/@v/1.0.0

   • Fields in data.data:

   • • pagingRecipientName – Name of the paging recipient.

     • pagingRecipientId – id of the paging recipient.

     • statusSeverity – High level paging recipient status.

     • statusType – Paging recipient subcategory

     • siteName – Name of the site where the paging recipient is located.

     • siteId – id of the site where the paging recipient is located.

     • siteLocationNames – Location path to the audio site.

     • organizationName – Name of the organization.

     • organizationId – id of the organization.

     • aamcUrl – Link to the event log in AXIS Audio Manager Center.

When configuring a webhook, you can enter a webhook secret together with the destination URL. This secret is used to verify that incoming webhook requests are genuine and untampered.

1. How it works:

2. The sender creates an HMAC-SHA256 signature of the event payload using your configured secret signing key.

3. The signature is included in the webhook-signature-sha256 header of the request.

4. On the server, recompute the HMAC using the received payload and your secret signing key.

5. Compare it to the signature provided.

6. If they match, the request is verified.

Requirements for the webhook secret signing key:

• The secret signing key must be entered when you configure the webhook URL in AXIS Audio Manager Center.

• The secret signing key must be a hexadecimal string with up to 1024 characters.

• The secret signing key must have an even number of characters.

• The same secret must be used on your server to verify incoming requests.

• A regular expression for a valid secret signing key: ^([0-9a-fA-F]{2}){0,512}$

This example demonstrates the basic principles of webhook receiver implementation and is for educational purposes only. Production implementations must include proper security hardening, validation, and error handling.

1. Create a new AWS Lambda function:

2. 1. Runtime: Node.js 22 or greater

   2. Architecture: X86_64

   3. Function URL: Enabled (auth type NONE)

3. Insert and deploy the code.

4. Setup a new webhook in AXIS Audio Manager Center:

5. 1. With your public lambda function URL.

   2. With your secret signing key (from example code: 4d79207365637265742070617373706872617365).

   3. Select which trigger to use (e.g. audio site events) and a location (e.g. organization level).

6. Trigger a test event (e.g., restart an audio site leader to generate a disconnect event).

7. Check your lambda logs.

import { createHmac, timingSafeEqual } from "crypto";

const passphrase = "My secret passphrase";
// Resulting secret signing key (hex): 4d79207365637265742070617373706872617365
const secretSigningKey = Buffer.from(passphrase, "utf-8").toString("hex");

const verifySignature = (event) => {
  try {
    const signature = event.headers["webhook-signature-sha256"];
    const signatureBuffer = Buffer.from(signature, "hex");
    const signingKeyBuffer = Buffer.from(secretSigningKey, "hex");
    const bodyBuffer = Buffer.from(event.body, "utf-8");
    const hmacDigest = createHmac("sha256", signingKeyBuffer).update(bodyBuffer).digest();

    return timingSafeEqual(hmacDigest, signatureBuffer);
  } catch (error) {
    console.error("Failed to verify signature:", error);
    return false;
  }
};

const innerHandler = (event) => {
  // Handle the preflight request (required to verify receiver existence during setup)
  if (event.requestContext.http.method === "OPTIONS") {
    return {
      statusCode: 200,
      headers: { "Webhook-Allowed-Origin": event.headers["webhook-request-origin"] }
    };
  }

  if (!verifySignature(event)) {
    return { statusCode: 401, body: "Invalid signature" };
  }

  // Do business logic, e.g., store the event, send it to another service, etc.

  return { statusCode: 200, body: "Success" };
};

export const handler = async (event) => {
  console.log("Event:", event);
  const response = innerHandler(event);
  console.log("Response:", response);

  return response;
};

If you need more help, go to axis.com/support.

Cybersecurity supports a successful product lifecycle with minimized risks. You can find in-depth information and documentation about our cybersecurity approach at axis.com/about-axis/cybersecurity. Follow the cybersecurity guidelines below to receive product security notifications from Axis and to configure your product for a secure lifecycle and decommissioning.

At Axis Trust Center, you can find information about how Axis implements security compliance, transparency, data protection, and privacy.

Axis is a Common Vulnerability and Exposures (CVE) Numbering Authority (CNA). To minimize your risk of exposure, we follow industry standards when identifying and resolving vulnerabilities in our devices, software, and services. Refer to axis.com/vulnerability-management for information about our vulnerability management policy or to report a vulnerability.

Subscribe to Axis security notification emails at axis.com/security-notification-service. We will send you information about vulnerabilities, corresponding security advisories, and other security-related matters for your Axis product.

Axis minimizes risks throughout the lifetime of our products through secure lifecycle management. Use our hardening guides at help.axis.com to more securely configure and operate your Axis products and to find information about:

Secure first-use

Axis products are pre-configured with high default protection to allow for secure initialization and encrypted communication from the very start.

Intended use and common configuration mistakes

Our guides provide information about the intended usage of Axis products, including common security-relevant misuse and configuration mistakes that should be avoided.

Managing vulnerabilities and supply chain transparency

A Software Bill of Material (SBOM) is published with every software release on axis.com to disclose vulnerabilities and improve supply chain transparency.

Decommissioning and the secure erasure of data

To securely decommission a product when it reaches the end of its lifecycle, reset it to factory default settings. This erases your configurations, stored data, and sensitive information.