The ONVIF Device Manager video is a short 7 min video explaining how to use the software.
The How to Get the RTSP URL from IP Cameras video is great to learn how to get the RTSP URL to pull video from an IP camera.

If a camera supports ONVIF, ODM helps gather valuable information needed to connect the camera to BI. What's nice about ODM is that it will confirm other functionality available on the camera through ONVIF as well, e.g. PTZ.

Once connected to a camera, the application shows the RTSP URLs used to connect to the different video streams. With that information you should be able to input the same information into the BI IP Config Dialog to connect your camera.

For example, below is the RTSP URI of the camera determined by ODM.


Based on the URL information, it is easy to now populate the IP Config Dialog as seen below:

ODM is also a great tool to learn which ONVIF events are supported by the camera. If you have a camera with advanced features such as Person/Vehicle detection and the camera supports ONVIF events, BI may be able to trigger based on the camera's AI.

In the image below, the events tab shows the ONVIF events generated by the camera. BI listens for isMotion:true/false, by default, so this camera would work perfectly with BI.

2745 = Socket error 10053.

WSAECONNABORTED
10053
Software caused connection abort.
An established connection was aborted by the software in your host computer, possibly due to a data transmission time-out or protocol error.

2746 = Socket error 10054.

WSAECONNRESET
10054
Connection reset by peer.
An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.

IP config dialog
Double check your advanced settings.
Maybe turn RTSP keep alives off? On by default.
Confirm RTSP back-channel is unselected.

274C = Socket error 10060.

WSAETIMEDOUT
10060
Connection timed out.
A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond.

Server settings
Double check the IP address and available ports on the camera.

Try toggling the Advanced connector settings on/off (IP Config dialog). Below are the default settings. I highlighted the selections that usually have an effect on connections. Help file has details.


Network
Very possible there is a network issue. See Network tests to rule out hardware issues.

Remote testing
If you want us to test your camera, see Camera issues article for needed information.

274D = Socket error 10061

WSAECONNREFUSED
10061
Connection refused.
No connection could be made because the target computer actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host—that is, one with no server application running.

This error basically means the camera or endpoint you are trying to communicate with does not exist based on your networking settings: IP address / Port / URI stream.

Scenario 1: Power outage: A power outage means the cameras and the router and the BI server restarted. The error implies the cameras were assigned new IP addresses by the router and thus BI can no longer talk to the cameras.

Networking is the responsibility of the user. The Network setup section of the Camera setup article talks a little bit about finding IP addresses for cameras on the network.

You can make the network setup more resilient so the next time this happens the cameras connect automatically.

• Tell the router to assign all your cameras the same IP address.
• Or, tell the cameras to always use the same IP address

Seek guidance from blueirissoftware.com/forum or consult with a networking expert for details.


Scenario 2: The RTSP port was not enabled.

I was able to solve the problem. For some reason, the RTSP port was unchecked.

Scenario 3: Wrong URI suffix.

Thanks for the reply. Turns out I forgot I had to use the URI suffix for the RTSP stream.

Another clue the URI was the issue came from the Find/Inspect dialog.

Opening 192.168.1.233 port 80...
HTTP Get / request...
Failed with HTTP 12029
Opening 192.168.1.233 port 8999...
ONVIF GetSystemDateAndTime
HTTP 12029
Checking for common cameras...
Foscam FI86xx/98xx compatible?
Foscam FI89xx compatible?
Foscam FI9821 V2 compatible?
Foscam FI9821 media port compatible?
Cantonk port 34567?
RTSP port open?
RTSP port detected!
Done

Communication issues related to error 12002 and 12029 are usually related to a network block of some sort. Because the URI was incorrect, the resource being requested does not exist causing the error message.

An RTSP URL for VLC is constructed with three components.

• IP Address
• Port (usually 554)
• URI stream

For example if your camera has the following settings:

• 10.0.0.5
• RTSP port for camera is 554
• URI for camera is /Streaming/channels/701 (convention for Hikvision)

The RTSP stream needed for VLC is rtsp://10.0.0.5:554/Streaming/channels/701. Identifying the correct URI stream can be the most challenging. Know your cameras. Reach out to the vendor/documentation. One user asked the vendor how to connect the camera to VLC. After much prying, the vendor finally gave up the information. Camera vendors would prefer you use their software and lock you in to their ecosystem.

VLC onvif code
POE camera：rtsp://IP address:554/uscast/11
Smart IPC：rtsp://IPaddress:554/video1
Old cameras：rtsp://IP address:554/onvif1

Alternatively, if your camera supports ONVIF, you can use another free software, ONVIF Device Manager, to get the RTSP URL.

• I blocked out the IP address for privacy. I showed the side-by-side BI settings to VLC settings so it would be easy to get VLC working.
• Simply copy the RTSP URL to the VLC window.
• When you hit play, you will be prompted for the username/password to the camera.