6/12/2023 0 Comments Port forwarding wizard nvr![]() ![]() ![]() Scenario 3: Unsecure, HTTP and RTSPĭevice RTSP port must be set to forwarded port.įorward same port number as RTSP port on device.įorward any port number to device HTTP port. This is the most robust and secure way of adding devices behind NAT in XProtect.įor more information about HTTPS and Media over HTTPS refer to section HTTPS. Scenario 2: Secure, everything over HTTPSĭevice HTTPS port must be set to forwarded port.įorward same port number as HTTPS port on device. One inconvenience is that the HTTP port on all devices must be changed to a unique value. This will work on all devices that support RTSP over HTTP streaming. Scenario 1A: Unsecure, medium setup, everything over HTTPĭevice HTTP port must be set to forwarded port.įorward same port number as HTTP port on device. Also, this will not work on devices that explicitly state the HTTP port in the URL even if it is the default port 80. This will not work when the HTTP port on the device is different from the default port 80 and the forwarded port is different from it. Port Forwarding Installing SwannView Plus app Changing stream settings Setting up a DDNS or hostname Testing internet connection on the phone Adding the. This will work on most devices and is the easiest to setup. bar and the port you want to open is slotted into the Public Port tab. Scenario 1: Unsecure, easy setup, everything over HTTPįorward any port from outside to port 80 on device. If you do not know your IP Address, go to the computers Run bar and type in CMD. ✓: Currently it is not possible to use UDP streaming with devices behind NAT (RTP/UDP and RTP/UDP multicast). Here are some possible scenarios for setting up the ONVIF driver to work with devices behind NAT. The ONVIF driver will try to connect on port 80 instead of port 8081. When the port is explicitly specified in the URL returned in GetStreamUri response, the ONVIF driver will always use that port.įor example, if the device is added with port 8081, but GetStreamUri response returns the URL as follows: For HTTPS, the port that is specified in the device settings in XProtect will be used. For HTTP this will be the port with which the device was added in XProtect (might be different from 80). If the port is not explicitly specified, the ONVIF driver will use the default port for the protocol. The RTSP, HTTP or HTTPS port returned in GetStreamUri is handled differently. The ONVIF driver ignores the IP address returned in the GetStreamUri response and always uses the IP address with which the device was added in XProtect. When such device is behind a NAT, the IP address and port through which the media stream is accessible from outside may be different. When a device is behind a NAT it usually does not know this so when it is sending the URL for connecting to a media stream, the device sends it with its own IP address and the port on which it is listening. One exception is the GetStreamUri command. Configuration of devices behind NAT and port forwardingįor the ONVIF driver it does not matter if it is connecting directly to a device or through a NAT.
0 Comments
Leave a Reply. |