JD - not responding



  • Hello, I have the Sercomm IP 1000 Cameras. I can get them to work with the live555stream proxy server workaround to the Echo Show, but not to the Amazon Fire TV Cube. I have tried the monocle-gateway with all the tags and Alexa just says, “Camera is not responding”, after a few minutes. I am not sure what I am doing wrong. Any help…

    Also when trying to put the nssm.exe 64bit version in the monocle folder, my virus protection tags it as a threat. Can you explain that also?

    Also, here is some output from what I am getting…
    C:\Monocle>monocle-gateway.exe


    •         __  __  ___  _  _  ___   ___ _    ___              *
      
    •        |  \/  |/ _ \| \| |/ _ \ / __| |  | __|             *
      
    •        | |\/| | (_) | .` | (_) | (__| |__| _|              *
      
    •        |_|  |_|\___/|_|\_|\___/ \___|____|___|             *
      
    •                                                            *
      


    MONOCLE RUNTIME ENVIRONMENT

    VERSION = 0.0.3
    OS/ARCH = win32\x64
    PROCESS = monocle-gateway (PID=8132)
    TIMESTAMP = 2018-11-28T02:57:33.855Z


    MONOCLE GATEWAY SERVICE (Version: 0.0.3)

    [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=10252)
    [RTSP Server Listening] 0.0.0.0:8554 (PROXY)
    [RTSP Server Started]
    [Monocle Connected]
    [RTSP Server Registered]


    MONOCLE RTSP SERVICE - INITIALIZED

    FQDN = 3eec9e24-9d47-406b-8e66-357ba18901c9.mproxy.io
    HOST = 192.168.30.7
    PORT = 443


    INITIALIZE RTSP STREAM: Front Yard Cam

    • NAME : Front Yard Cam
    • LABEL : PRIMARY
    • URL : rtsp://192.168.30.7:554/proxystream-3
    • UUID : STREAM:f9f54502-5e28-45ec-90e2-174dfe0dab75
    • SESS : b94d9da6-21fa-405b-b4ed-3d424a4bbe51
    • MODIF : Tue Nov 27 2018 21:55:27 GMT-0500 (Eastern Standard Time)
    • TAGS : @proxy

    2018-11-28T02:57:48.518Z [INFO] [RTSP PROXY] REGISTERING STREAM [Front Yard Cam/PRIMARY]; (STREAM:f9f54502-5e28-45ec-90e2-174dfe0dab75)
    2018-11-28T02:57:48.524Z [DEBUG] <RTSP-PROXY> [REQUEST] --> [REGISTER] rtsp://192.168.30.7:554/proxystream-3
    2018-11-28T02:57:48.524Z [TRACE] <RTSP-PROXY> [REQUEST] --> [HEADERS] {
    “cseq”: “1”,
    “transport”: “reuse_connection=0;preferred_delivery_protocol=udp;proxy_url_suffix=STREAM:f9f54502-5e28-45ec-90e2-174dfe0dab75;username=administrator;password=1234”
    }
    2018-11-28T02:57:48.525Z [DEBUG] <RTSP-PROXY> [RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined)
    2018-11-28T02:57:48.526Z [TRACE] <RTSP-PROXY> [RESPONSE] <-- [HEADERS] {
    “cseq”: “1”,
    “date”: “Wed, Nov 28 2018 02:57:48 GMT”
    }
    2018-11-28T02:58:33.852Z [INFO] [RTSP PROXY] STREAM [Front Yard Cam/PRIMARY] WILL BE DE-REGISTERED IN 4 MINUTES



  • @johnanyul

    The Monocle Gateway is required for all FireTV 4K and newer models. Amazon has enforced new restriction policies in these devices that require more sophisticated security, encryption, etc. The Monocle Gateway addresses these requirements.

    Is the log data you provided all that you see after starting the gateway and asking Alexa to show you a camera feed? You should see additional connection attempts in the log from the Alexa devices and then further to the IP cameras. If you are not getting any Alexa connection attempts then something is wrong at the network layer. I would check to see if port 443 is getting blocked by firewall rules on the computer running the Monocle Gateway. Are the Alexa devices on the same network and should be able to access the Monocle Gateway at 192.168.30.7? Is the IP address “192.168.30.7” the correct local IP address that Monocle Gateway should be using to host its services?

    I’m not sure why your antivirus is complaining about “nssm.exe”? You can find the source of that program here: https://nssm.cc/download . NSSM is a tool used to help create/remove/start/stop and mange NT services on Windows. You can also download the latest version directly from their website and see if the antivirus software seems to like it better. I’m guessing some antivirus software has probably used NSSM to install their malicious code as a Windows service and now the antivirus software is flagging NSSM even though it by itself is not the bad actor.