5.7.5 - April 20, 2023 - Onvif updates
- Thread starter fenderman
- Start date
You may want to pass this along to Ken: unfortunately it isn't so simple with the 5442 series, as whether they work with ONVIF authentication also depends on which firmware version you have loaded (older or the most recent one).
I have two 5442 cameras that have had no problem with the last several versions of BI (5.7.5.x), and those two are still on the slightly older camera firmware from 2022-02-18 (ie: ONVIF authentication works). Here is the info from one of them:
Device TypeIPC-T5442T-ZE
System VersionV2.840.15OG008.0.R, Build Date: 2022-02-18
WEB VersionV3.2.1.1140936
ONVIF Version20.12(V3.1.0.1064635)
Algorithm Version1.0.7
Security Baseline VersionV2.1
I also have two other 5442 cameras (one of which is also a IPC-T5442T-ZE, same as above) that run the more recent firmware from 2022-08-18, and those two won't work with ONVIF authentication turned on:
Device TypeIPC-T5442TM-AS-2.8mm
System VersionV2.840.15OG00D.0.R, Build Date: 2022-08-18
WEB VersionV3.2.1.1261216
ONVIF Version21.12(V3.1.0.1235054)
Algorithm Version1.0.7
Security Baseline VersionV2.1
Note that one of the components that changed was the ONVIF Version number. Hopefully this info may help out Ken, but I haven't been in touch with him on this subject, so please pass it along.
Cheers
EDIT: this is still true in BI 5.7.6.7
Last edited:
biggen
Known around here
- Joined
- May 6, 2018
- Messages
- 2,573
- Reaction score
- 2,858
I just updated BI and all of my 5442 cameras now send IVS to BI properly on BI version 5.7.6.7 with ONVIF authentication turned on. My firmware for all my 5442 cams is: V2.840.15OG00D.0.R, Build Date: 2022-08-18
You may want to send him an email then if it still isn't working for you. Out of curiosity, what does the XML log say in BI for these cameras that aren't working?
Yeah, I haven't had issues with the actual IVS (or SmartMotion) ONVIF events being passed along, it just depends for me on whether I can get away with the previously working (on all prior BI versions that didn't expose the inner workings of ONVIF) authentication. So in a sense, I can deal with this; but it's just odd that some users aren't seeing the same firmware date cutoff date that for me determines whether I can use ONVIF authentication.
Meh; ultimately what this probably means is that in order to properly test this I would have to do the "magic" multi-reset/hard-reset/rain-dance/prayer three times on the camera (after re-loading the latest camera firmware) again, then setting up from scratch. I'm not sure it is worth it just for testing this out. I'm pretty sure I did this previously, but not 100%.
The difference in the XML: (with working "Get Events:OK" shown first)
<?xml version="1.0" encoding="UTF-8"?>
<s:Envelope xmlns:tns1="[URL unfurl="true"]http://www.onvif.org/ver10/topics[/URL]" xmlns:wstop="[URL unfurl="true"]http://docs.oasis-open.org/wsn/t-1[/URL]" xmlns:wsa="[URL unfurl="true"]http://schemas.xmlsoap.org/ws/2004/08/addressing[/URL]" xmlns:wsa5="[URL='http://www.w3.org/2005/08/addressing']WS-Addressing 1.0 Namespace[/URL]" xmlns:tev="[URL unfurl="true"]http://www.onvif.org/ver10/events/wsdl[/URL]" xmlns:wsnt="[URL unfurl="true"]http://docs.oasis-open.org/wsn/b-2[/URL]" xmlns:tt="[URL unfurl="true"]http://www.onvif.org/ver10/schema[/URL]" xmlns:s="[URL unfurl="true"]http://www.w3.org/2003/05/soap-envelope[/URL]" xmlns:sc="[URL unfurl="true"]http://www.w3.org/2003/05/soap-encoding[/URL]">
<s:Header>
<wsa5:Action>[URL unfurl="true"]http://www.onvif.org/ver10/events/wsdl/PullPointSubscription/PullMessagesResponse[/URL]</wsa5:Action>
<wsa5:To>[URL unfurl="true"]http://10.11.12.30/onvif/Subscription?Idx=84[/URL]</wsa5:To>
</s:Header>
<s:Body>
<tev:pullMessagesResponse>
<tev:CurrentTime>2023-05-11T23:22:29Z</tev:CurrentTime>
<tev:TerminationTime>2023-05-11T23:31:58Z</tev:TerminationTime>
</tev:pullMessagesResponse>
</s:Body>
</s:Envelope>
Now the non-working one: (GetEvents error 8000ffff):
?xml version="1.0" encoding="UTF-8"?>
<s:Envelope xmlns:d="[URL='http://schemas.xmlsoap.org/ws/2005/04/discovery']Web Services Dynamic Discovery (WS-Discovery)[/URL]" xmlns:wsrf-bf="[URL unfurl="true"]http://docs.oasis-open.org/wsrf/bf-2[/URL]" xmlns:wsnt="[URL unfurl="true"]http://docs.oasis-open.org/wsn/b-2[/URL]" xmlns:ter="[URL unfurl="true"]http://www.onvif.org/ver10/error[/URL]" xmlns:s="[URL unfurl="true"]http://www.w3.org/2003/05/soap-envelope[/URL]" xmlns:sc="[URL unfurl="true"]http://www.w3.org/2003/05/soap-encoding[/URL]">
<s:Body>
<s:Fault>
<s:Code>
<s:Value>s:Sender</s:Value>
<s:Subcode>
<s:Value>ter:NotAuthorized</s:Value>
</s:Subcode>
</s:Code>
<s:Reason>
<s:Text xml:lang="en">Wsse authorized time check failed.</s:Text>
</s:Reason>
</s:Fault>
</s:Body>
</s:Envelope>
biggen
Known around here
- Joined
- May 6, 2018
- Messages
- 2,573
- Reaction score
- 2,858
That '8000ffff' error was exactly what I was getting until his latest release dropped today and now my Get Events are "OK". Very odd indeed.
When I first updated to: 5.7.6.7
I also got 35 events of the 8000ffff error and then suddenly all was fine and the camera went to 'ok', only the camera with firmware :
V2.840.15OG008.0.R, Build Date: 2022-02-18
had that error
the other with newer firmware did not
I also got 35 events of the 8000ffff error and then suddenly all was fine and the camera went to 'ok', only the camera with firmware :
V2.840.15OG008.0.R, Build Date: 2022-02-18
had that error
the other with newer firmware did not
For anyone following this firmware date vs. ONVIF authentication saga: now I'm not so sure that the firmware date matters, but I'm more convinced than ever that a full factory reset MUST be done after upgrading firmware. Sure enough, by rolling the two 5442 cameras that had the most recent (August 2022) firmware back to the February 2022 firmware, now they all accept the ONVIF authentication without errors. Perhaps the last time I had done full resets was when installing this version, a bit hard to say for sure.
looney2ns
IPCT Contributor
It's usually always best before updating a firmware, that you follow this:
1-Set camera back to FULL factory defaults.
2-Update firmware.
3-Set camera once again back to FULL factory defaults.
4- Configure camera back up from scratch, don't import any exported settings.
1-Set camera back to FULL factory defaults.
2-Update firmware.
3-Set camera once again back to FULL factory defaults.
4- Configure camera back up from scratch, don't import any exported settings.
I have a boobie cam and running into the onvif issue (Tried different versions of the latest BI. Is this supposed to be fixed with the latest BI?
Events: subscription 8000ffff
Device TypeIPC-HDBW5441F-AS-E2-2.8mm
System VersionV2.840.0000000.18.R, Build Date: 2022-06-29
WEB VersionV3.2.1.1261216
ONVIF Version21.12(V3.1.0.1235054)
Events: subscription 8000ffff
Device TypeIPC-HDBW5441F-AS-E2-2.8mm
System VersionV2.840.0000000.18.R, Build Date: 2022-06-29
WEB VersionV3.2.1.1261216
ONVIF Version21.12(V3.1.0.1235054)
Under Network > Access Platform, turning onvif authenticator off in the camera stops that error but still allows the ONVIF triggers. It is an issue where the camera and BI are having "handshake" issues and thinks that there is a problem, when there isn't. It is an annoying issue, but not causing any issues other than we don't like seeing that triangle and that "error" LOL.
Thank You, that worked.
I wasn't getting any onvif events.
ditto worked for me as well - thanks a lot wittaj- the little triangle was driving me nuts for days.
So, I'm not getting any detections on vehicles. Was on an earlier version of BI, not available now, when my detection times started getting into the 1000's AI timing out with no detections. First tried deleting DS and reinstalling (with Mike's general module), same results. Upgraded to latest version of BI, 6/4/23, and my times went back to 100~300ms for people but no vehicle detections. Went into all my cams and checked ONIF/camera events (never had it checked & it worked fine) still no vehicle detection. Followed @wattaj advice with turning onvif authenticator off. Downgraded BI to the latest stable version 5/19/23, still no vehicle detection.
did anyone figure this out ? trying to use the factory AI on the 5442, followed wittaj's instructions, but cant seem to get push alerts,
not sure what else i can send, this is also the ACTIONS - ON ALERT if that helps anything
not sure what else i can send, this is also the ACTIONS - ON ALERT if that helps anything
brunokiwi
n3wb
Does you camera report "GetEvents: ok" as below on the camera setting > general tab?
Have you disabled ONVIF authentication in the camera? Network > Access Platform > ONVIF
yes it states GETEVENTS: OK
as far as disabling ONVIF auth. - i dont think so, i tried finding the network->access platform->onvif tabs