Network IP camera configuration - Make/Model settings for EmpireTech IPC-T5442T-ZE/Dahau IPC-HDW5442T-ZE

[EricB]

I have the EmpireTech IPC-T5442T-ZE which is the same as the Dahua IPC-HDW5442T-ZE.

I am wondering what Make and Model I should use since I couldn't find an entry for EmpireTech in the Make dropdown, and when choosing Dahau as the Make, was not one of the models listed in the Model dropdown.

I have attached a screen capture of the "Network IP camera configuration" for this camera.

When I did a "Find/Inspect" with no value in the IP Address textbox and the User and Password values entered, the camera was found in the resulting list as:

IP Address: 192.168.0.230:80,54,1935 (which is the correct IP address, but I don't know if the ports portion is correct).​

When I double clicked the entry to do an "Inspect", the result in the "Inspecting..." window was:

Opening 192.168.0.230 port 80...​

HTTP Get / request...​

OK​

ONVIF GetSystemDateAndTime​

2023-01-17T19:01:51.000Z​

Requesting device information...​

Manufacturer: General​

Model: IPC-T5442T-ZEB​

FirmwareVersion: 2.820.15OG001.0.R, Build Date 2021-07-06​

GetCapabilities...​

Querying services​

Has Imaging services: /onvif/imaging_service​

Has media services: /onvif/media_service​

Has RTP_RTSP_TCP, requesting profiles​

profile token MediaProfile00000​

profile name MediaProfile_Channel1_MainStream​

profile source is 00000​

profile source config is 00000​

profile token MediaProfile00001​

profile name MediaProfile_Channel1_SubStream1​

profile source is 00000​

profile source config is 00000​

profile token MediaProfile00002​

profile name MediaProfile_Channel1_SubStream2​

profile source is 00000​

profile source config is 00000​

requesting URI for profile MediaProfile00000​

RTSP URI: /cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif​

requesting URI for profile MediaProfile00001​

RTSP URI: /cam/realmonitor?channel=1&subtype=1&unicast=true&proto=Onvif​

requesting URI for profile MediaProfile00002​

RTSP URI: /cam/realmonitor?channel=1&subtype=2&unicast=true&proto=Onvif​

Has Event services: /onvif/event_service​

Has WSPullPointSupport​

RelayOutputs: 0​

InputConnectors: 0​

Has Device IO services: /onvif/deviceIO_service​

AudioOutputs: 0​

Has PTZ service: /onvif/ptz_service​

Done​

My question are...

1. Since I could not find it in the Make/Model dropdown for either the EmpireTech or a Dahau IPC-HDW5442T-ZE, is this the correct camera "Make" and "Model" or is there a better one to use for this camera?​

2. Do the settings look correct?​

3. Could the "Network IP camera configuration" settings be the reason that I am seeing multiple "Warning Message" entries in the Status Log with a "Message" of "Events: subscription 00002efd"?​

​

Thanks,


Eric

 

[wittaj]

In most instances it is best to type in IP address and user/pw and hit find/inspect and let BI do it's thing.

Most of the time it will come up generic and that is totally ok.

Most of mine including that model come up as generic and work just fine.

 

[EricB]

In most instances it is best to type in IP address and user/pw and hit find/inspect and let BI do it's thing.

Most of the time it will come up generic and that is totally ok.

Most of mine including that model come up as generic and work just fine.

Thanks.

Do you see a reoccurring status log message "Events: subscription 00002efd" for this camera?

Eric

 

[wittaj]

Yep it is just a thrown "error" to do with the ONVIF. Mine stops after a couple of minutes until another reboot.

 

[EricB]

Ok, I'll see if it ever stops. Looking at the log, it seems that yesterday it was firing about every 5 seconds or so for most of the day.

 

[wittaj]

You probably have a newer ONVIF version than mine.

If it is continuing more than a few minutes, then Under Network > Access Platform, try turning onvif authenticator off in the camera and see if that stops it.

 

[EricB]

Ok, I'll give that a try and see. I realized that a lot of those messages may have been from when I was testing various things yesterday, so I'll check it later today and see if it is still doing the same thing.

Later,

Eric