However, Alexa does require a TLS secured connection with valid certificates (which is not part of the RTSP protocol specification); however I’m not sure if that alone meets the RTSPS specification compliance requirements. I don’t have any cameras that support RTSPS currently. I should probably try to get a Unifi camera and start testing it out. Would you be able to make a RTSPS steam temporarily available to me for testing? If so, you can PM me the details.
@krh1009 If your cameras are all inside your private Network the no port 443 does not need to be public facing. I do not expose port 443 to the Internet in my personal setup. Monocle Gateway does need to host its services on port 443 but this can be on an internal private network address. The only catch is that Monocle must sent a valid public DNS host name to your Alexa devices when you request a camera stream. When using Monocle Gateway with an internal private IP address we create a custom DNS host name that points to your private IP address. Some routers will not resolve public DNS records to internal private IP addresses by default. Search for DNS REBIND and your router model to see if/how you need to configure it to allow these DNS host names to resolve properly.
INITIALIZE RTSP STREAM: camera da rua
NAME : camera da rua
LABEL : PRIMARY
URL : rtsp://192.168.0.153:554/cam/realmonitor?channel=1&subtype=0
UUID : STREAM:2dfbdabd-003d-48fc-8ca7-4e32e6052440
SESS : dd30da45-478b-4b46-af0d-098ab62f0cb7
MODIF : Mon Feb 14 2022 12:12:19 GMT-0300 (Hora oficial do Brasil)
TAGS : @fakefmtp,@proxy
RTSP STREAM MODIFIED: camera da rua
Any existing RTSP steams will be shut down
and a new stream instance will be registered.
There is something else running on your system that is already using port 443. Or you have two instances of Monocle Gateway attempting to run at the same time. If you installed the gateway on Windows, it may be running as a system service in the background?