VAPIX Service Access Denied

[StatusAuto]

To whomever can help...

We are attempting to access the GetEventInstances call from /vapix/services, but upon making the request, we receive a 401 Unauthorized error.

We can access other services (ws-data-stream and apidiscovery) successfully. We have tried Basic and Digest authentication.

At this point we are stuck.

The one thing of note is the device (an A1610, running the latest firmware as of last week), shows an unusual message in its system logs at the time:
"API cert is in beta state, expected beta to be provided in the url"

Does anyone know why this message is occurring, or why we can access some APIs but not others on the device?

Thanks.

Edit I should add, this is being done using C#.

[github-actions[bot]]

This automatically generated reply acts as a friendly reminder.

Answers to your questions will most often come from the community, from developers like yourself. You will, from time to time, find that Axis employees answers some of the questions, but this is not a guarantee. Think of the discussion forum as a complement to other support channels, not a replacement to any of them.

If your question remains unanswered for a period of time, please revisit it to see whether it can be improved by following the guidelines listed in Axis support guidelines.

[vivekatoffice]

Hi @StatusAuto ,

Please try using Axis OS(Version 10.12.236.1 - LTS 2022 (VAPIX)) instead. It seems you are currently using Axis OS Version 11.8.75.6 (AXIS CAMERA STATION SECURE ENTRY), which is not compatible with VAPIX integration.

[StatusAuto]

This seems like a promising answer, but unfortunately it refuses the VAPIX firmware (it says it can't upgrade).
The device originally came with 11.3.5.1, and we upgraded to 11.8.75.6.
Is there some way to get it to accept the firmware?
Thanks.

[vivekatoffice]

Hi @StatusAuto ,

1. Upgrade the controller to the latest secure entry firmware, for example, 11.8. Factory default is the preferred option.
2. Upgrade the controller to VAPIX firmware. The factory default option has to be selected.

 

[StatusAuto]

Thanks @vivekatoffice. That solved the firmware problem. Now onto the second stage...

[StatusAuto]

So I have now been able to pull the event instances.
The follow-up problem is that the Event Data Streaming (via web socket) doesn't seem to return events for the topics listed there.
(or the topic filter is mal-formed, but not generating an error).

Currently I am trying to use the tns1:AccessControl topic filter.
I have also tried things like tns1:AccessControl/Denied/Credential or tns1:AccessControl/Denied/CredentialNotFound.

The ws-data-stream responds initially with a accepted message response (connection upgraded to websocket), but the events are never received.
(as a note, I can get some other events such as system reboot or firmware upgrade when specifying a content filter such as a source).
(also the events are occurring, I can see them in the Axis Camera Manager).

Is there something wrong with my topic filter?
Alternatively, is there a way to specify a filter that has wildcards or "all events"?
(at least for testing purposes)

Thanks.

[vivekatoffice]

Hi @StatusAuto ,
I don't think the VAPIX Axis OS supports "Event Data Streaming (via web socket)". Please pass me the link to the document/guide you are following.

You can try the RTSP metadata stream for the same.

You can use Axis Metadata Monitor to get the correct filter : Axis Metadata Monitor