Ok got it working…

my Notepad log as below, which while long may help others with my step by step process on BASIC v DIGEST, VMWare ports, use of Gateway etc… the answer for me was FIREWALL - kaspersky blocking something so just need to figure out - i suspect 443

"running gateway
when starting it identifies gateway as (not sure about the RTSP Server listening set as 0.0.0.0:8555 etc (assuming broadcast listening?) :

"VERSION = 0.0.4
OS/ARCH = win32\x64
PROCESS = monocle-gateway (PID=15164)
TIMESTAMP = 2019-12-15T10:20:36.394Z

MONOCLE GATEWAY SERVICE (Version: 0.0.4)

[Monocle Starting]
[Monocle Connecting]
[Monocle Started]
[RTSP Server Starting]
[RTSP Server Listening] 0.0.0.0:8555 (RTSP)
[RTSP Server Listening] 0.0.0.0:443 (RTSP-TLS)
[RTSP Proxy Started] (PID=18916)
[RTSP Server Listening] 0.0.0.0:8554 (PROXY)
[RTSP Server Started]
[Monocle Connected]
[RTSP Server Registered]

MONOCLE RTSP SERVICE - INITIALIZED

FQDN = 8bba3f78-c3b7-4534-b1d6-fafcdc03e7f1.mproxy.io
HOST = 192.168.0.14
PORT = 443"

ping the FQDN translates to the IP correctly - originally showed IP for a Virtual Ethernet… so disabled virtual ports on laptop
ipconfig /flushdns
ipconfg and restarted gateway
this now showed the laptops correct IP of x.x.x.14 as above

on DS-2CD2532F-IS Camera

the video configuration on the physical camera is set as :
main stream only for video (not video and audi)
substrem only for video (not video and audio)

substream set to :352x288, variable, highest quality, h.264
mainstream same but higher res.

on Monocole web config

have configured multiple configs
@noaudio, @tunnel/@no proxy, @proxy-tcp and trying all variants on ALEXA Show and monocole - still same - “not responding”

strings as below with settings which I have attempted - using varity of BASIC vs DIGEST, proxy TCP in lieu of UDP and also stream channels - password is long but simple using alpha and numerics:

MAIN channel ok on VLC - not working on SHOW8
rtsp://192.168.0.32:555/video.h264
BASICH264NONE192*192@noaudio@tunnel

MAIN channel ok on VLC - not working on SHOW8
rtsp://192.168.0.32:555/Streaming/Channels/101
BASICH264NONE192*192@noaudio@proxy-tcp

Sub channel ok on VLC - not working on SHOW8
rtsp://192.168.0.32:555/Streaming/channels/102
BASICH264NONE192*192@noaudio@proxy

Sub channel with DIGEST - not working anywhere.
rtsp://192.168.0.32:555/Streaming/channels/102
DIGESTH264NONE192*192@noaudio@proxy-tcp

lost for ideas…
disabled kaspersky also and Thought id try the other cameras - (UK ones not the grey cam)
which was configured as:

SideCam
Manufacturer:HikvisionModel:DS-2CD2142-FWD-i
rtsp://192.168.0.34:557/Streaming/channels/102)
BASICH264NONE192*192@noaudio@tunnel

this wasnt working before… it started showing up on the SHOW8!! (takes a few seconds to start)

Issue therefore isnt the frmware or grey v UK
you NEED the gateway
you NEED to disable firewall (will figure out if 443 or the cam ports n a bit)

I now have cams working ok as:

Manufacturer:HikvisionModel:DS-2CD2532F-IS
rtsp://192.168.0.32:555/Streaming/channels/102
BASICH264NONE192*192@noaudio@tunnel

Manufacturer:HikvisionModel:DS-2CD2532F-IS
rtsp://192.168.0.33:556/Streaming/channels/102
BASICH264NONE192*192@noaudio@tunnel

Manufacturer:HikvisionModel:DS-2CD2142-FWD-i
rtsp://192.168.0.34:557/Streaming/channels/102
BASICH264NONE192*192@noaudio@tunnel

will try to up the sub stream resolution as main stream displays black (prob cos resolution too high)
re-enabled the VM network cards and fushed DNS -the cams still work…

therefore all along it was firewall… sigh!
now to try and get my DANMINI doorbell to work… see if ti generates a RTSP stream to capture…

Hope this helps someone!"

@Dayhunter, @wolfe4656

This change is now in place. You can edit your camera feed in the web portal and remove port 554 and save the camera entry. It should no longer force the default port in the URL if it is omitted in the string.

However, there is one caveat … the existing version of Monocle Gateway does not play nice with the RTSP URL string with no defined port number. So we have made additional changes to force the default RTSP port number back into the URL string if sending this URL to a Monocle Gateway instance. Please note, the camera entry is not altered, but the URL will be updated at runtime when sending to an existing version of the gateway. We have also thus made updates to the gateway software to handle this case where a default RTSP port may not be defined. So new versions of the gateway will handle this condition and the server will send the un-altered RTSP URL to new versions of Monocle Gateway. If you are using Monocle Gateway to test this change, you will need an updated version. I can provide an experimental version upon request, just let me know what platform you are running it on.

Thanks, Robert