Hikvision DS-2CD2142FWD-IS with Show 8

ijhammo

If I try it with Proxy I get this:

-------------------------------------------------
RTSP STREAM MODIFIED:  Driveway
  Any existing RTSP steams will be shut down     
  and a new stream instance will be registered.  
-------------------------------------------------

2019-12-19T23:38:58.590Z [DEBUG] <RTSP-PROXY> [REQUEST]  --> [DEREGISTER] rtsp://192.168.16.16:554/Streaming/Channels/101/
2019-12-19T23:38:58.590Z [TRACE] <RTSP-PROXY> [REQUEST]  --> [HEADERS] {
  "cseq": "1",
  "transport": "reuse_connection=0;preferred_delivery_protocol=udp;proxy_url_suffix=STREAM:0c92eb62-d3bd-441c-8a12-21805a41a235"
}
2019-12-19T23:38:58.591Z [DEBUG] <RTSP-PROXY> [RESPONSE] <-- [451 (Invalid parameter)] <cseq=1> (session=undefined)
2019-12-19T23:38:58.591Z [TRACE] <RTSP-PROXY> [RESPONSE] <-- [HEADERS] {
  "cseq": "1",
  "date": "Thu, Dec 19 2019 23:38:58 GMT"
}

-------------------------------------------------
INITIALIZE RTSP STREAM:  Driveway
-------------------------------------------------
 - NAME  : Driveway
 - LABEL : PRIMARY
 - URL   : rtsp://192.168.16.16:554/Streaming/Channels/101/
 - UUID  : STREAM:0c92eb62-d3bd-441c-8a12-21805a41a235
 - SESS  : 4191e24e-8ec3-41fb-81eb-539fbf7418b7
 - MODIF : Thu Dec 19 2019 23:38:46 GMT+0000 (GMT)
 - TAGS  : @proxy,@tunnel
-------------------------------------------------


-------------------------------------------------
INITIALIZE RTSP STREAM:  Driveway
-------------------------------------------------
 - NAME  : Driveway
 - LABEL : PRIMARY
 - URL   : rtsp://192.168.16.16:554/Streaming/Channels/101/
 - UUID  : STREAM:0c92eb62-d3bd-441c-8a12-21805a41a235
 - SESS  : ee5c3123-272d-4ee9-89ee-cb8754b50b1f
 - MODIF : Thu Dec 19 2019 23:38:46 GMT+0000 (GMT)
 - TAGS  : @proxy,@tunnel
-------------------------------------------------


-------------------------------------------------
INITIALIZE RTSP STREAM:  Driveway
-------------------------------------------------
 - NAME  : Driveway
 - LABEL : PRIMARY
 - URL   : rtsp://192.168.16.16:554/Streaming/Channels/101/
 - UUID  : STREAM:0c92eb62-d3bd-441c-8a12-21805a41a235
 - SESS  : 5ab58460-ee9c-4058-a21d-41180bc878ae
 - MODIF : Thu Dec 19 2019 23:40:11 GMT+0000 (GMT)
 - TAGS  : @proxy-tcp,@tunnel
-------------------------------------------------

ijhammo

Are there any other log files I can look at for more clues?

ijhammo

I have tried running the gateway on a different laptop and get the same result. When making the request I get three copies of the “INITIALIZE RTSP STREAM:” message in the gateway log but nothing else.

Are there any switches for more verbose logging?

mattbradley109

Yep this is exactly the same issue that I’m having

ijhammo

I dont think this is a camera issue but a gateway<->Show 8 issue @Monocle ?

mattbradley109

@ijhammo Did you get anywhere at all with this ? just picking this up again after the Christmas madness ive not managed any progress at all

Upsman

Had similar issue. Gateway with @tunnel tag, substream 2, Digest, DNS setting (Fritzbox), simple password, fixing port 443 worked for me with Hikvision and Trendnet cameras.
Do you use Fritzbox? Did you consider the DNS seeting (allow "mproxy.io”.)
Try substream 2 .
Any issue with port 443 blocked by other application?

ijhammo

Hi, I have a Mikrotik router and dont have any other problems with 443 (that I am aware of) Is that DNS setting specific to Fritzbox?

I tried substream 2 and still get nothing :-(

I am at the point now where I am looking at getting rid of the Hikvision cameras for ones that work natively (like the imou ones)

Monocle

@ijhammo said in Hikvision DS-2CD2142FWD-IS with Show 8:

Fritzbox

By default Fritz-box does block something called DNS REBINDING. This will prevent devices on your local network from resolving the unique DNS hostname that is assigned to your monocle gateway instance. Other routers such as PFSense/DDWRT/etc also can implement this protection as well. It’s trying to prevent DNS hostnames from resolving to local/private IP address inside your network. However in the case of Monocle, we are trying to allow the Alexa devices to resolve to your running instance of Monocle Gateway running inside your network to allow you to keep all your audio/video streaming data entirely inside your network.

More details here:
https://monoclecam.com/monocle-gateway/troubleshooting/dns-rebinding

Thanks, Robert

Monocle

@ijhammo

Based on the log snippets you posted, it does look like the Alexa devices are not able to connect to the Monocle Gateway instance. We should see additional lines of log data showing TCP connections and RTSP negotiations between the Alexa devices and the Monocle Gateway and then out to the IP cameras.

So the typical problems for these symptoms are :

DNS REBINDING - the network is not allowing the unique hostname (FQDN) to be resolved to your local/private IP address running the gateway instance
Alexa device and Monocle Gateway are not on the same network or one is on a Guest network or isolated VLAN.
Something is already using port 443 or port 443 is getting blocked by a firewall on the machine running the Monocle Gateway software.

Thanks, Robert