no luck with the gateway



  • Trying to get my lorex cameras to work with alexa. I can connect with VLC to my rtsp urls. But the gate way doesn’t seem to be able to.

    here is the log

    INITIALIZE RTSP STREAM:  Front Porch
    -------------------------------------------------
     - NAME  : Front Porch
     - LABEL : PRIMARY
     - URL   : rtsp://192.168.1.78:554/ch01/0
     - UUID  : STREAM:48daafa0-9081-4cd2-a876-bfd97e0df325
     - SESS  : a500f47c-37bb-4ec6-bd93-49510f649f1d
     - MODIF : Sat Mar 09 2019 00:37:07 GMT-0700 (Mountain Standard Time)
     - TAGS  : @noaudio,@tunnel
    -------------------------------------------------
    
    2019-03-09T07:38:21.504Z [INFO]  [192.168.1.8:47220 <SkBO6JbvV>] RTSP CLIENT SOCKET CONNECTED
    2019-03-09T07:38:21.627Z [INFO]  [192.168.1.8:47220 <SkBO6JbvV>] RTSP CLIENT ATTACHED TO STREAM: Front Porch (STREAM:48daafa0-9081-4cd2-a876-bfd97e0df325)
    2019-03-09T07:38:21.633Z [INFO]  [192.168.1.8:47220 <SkBO6JbvV>] RTSP ENDPOINT SOCKET CONNECTED {192.168.1.78:554}
    2019-03-09T07:38:21.634Z [DEBUG] [192.168.1.8:47220 <SkBO6JbvV>] [CLIENT REQUEST]  --> [DESCRIBE] rtsp://2936db6f-e49d-4ac9-8d70-d90e1623db84.mproxy.io:443/STREAM:48daafa0-9081-4cd2-a876-bfd97e0df325?session=a500f47c-37bb-4ec6-bd93-49510f649f1d
    2019-03-09T07:38:21.635Z [TRACE] [192.168.1.8:47220 <SkBO6JbvV>] [CLIENT REQUEST]  --> [HEADERS] {
      "accept": "application/sdp",
      "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
      "cseq": "1"
    }
    2019-03-09T07:38:21.636Z [DEBUG] [192.168.1.8:47220 <SkBO6JbvV>] [ENDPOINT REQUEST]  --> [DESCRIBE] rtsp://192.168.1.78:554/ch01/0
    2019-03-09T07:38:21.637Z [TRACE] [192.168.1.8:47220 <SkBO6JbvV>] [ENDPOINT REQUEST]  --> [HEADERS] {
      "accept": "application/sdp",
      "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
      "cseq": "1"
    }
    2019-03-09T07:38:21.639Z [DEBUG] [192.168.1.8:47220 <SkBO6JbvV>] [ENDPOINT RESPONSE] <-- [401 (Unauthorized)] <cseq=0> (session=undefined)
    2019-03-09T07:38:21.640Z [TRACE] [192.168.1.8:47220 <SkBO6JbvV>] [ENDPOINT RESPONSE] <-- [HEADERS] {
      "cseq": "0",
      "server": "Rtsp Server",
      "www-authenticate": "Digest realm=\"Surveillance Server\", nonce=\"96632035\""
    }
    2019-03-09T07:38:21.640Z [INFO]  [192.168.1.8:47220 <SkBO6JbvV>] RTSP ENDPOINT REQUIRES AUTHENTICATION: Digest realm="Surveillance Server", nonce="96632035"
    2019-03-09T07:38:21.641Z [INFO]  [192.168.1.8:47220 <SkBO6JbvV>] RTSP ENDPOINT ATTEMPTING AUTHENTICATION: DIGEST
    2019-03-09T07:38:21.642Z [DEBUG] [192.168.1.8:47220 <SkBO6JbvV>] [ENDPOINT REQUEST]  --> [DESCRIBE] rtsp://192.168.1.78:554/ch01/0
    2019-03-09T07:38:21.643Z [TRACE] [192.168.1.8:47220 <SkBO6JbvV>] [ENDPOINT REQUEST]  --> [HEADERS] {
      "accept": "application/sdp",
      "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
      "cseq": "1",
      "authorization": "Digest username=\"admin\", realm=\"Surveillance Server\", nonce=\"96632035\", uri=\"rtsp://192.168.1.78:554/ch01/0\", response=\"343b96ea91339a6af26f6f8530800a2f\""
    }
    2019-03-09T07:38:21.645Z [INFO]  [192.168.1.8:47220 <SkBO6JbvV>] RTSP ENDPOINT SOCKET CLOSED [192.168.1.8:47220 <SkBO6JbvV>]
    2019-03-09T07:38:51.627Z [WARN]  [192.168.1.8:47220 <SkBO6JbvV>] RTSP CLIENT SOCKET TIMEOUT
    2019-03-09T07:38:51.652Z [INFO]  [192.168.1.8:47220 <SkBO6JbvV>] RTSP CLIENT SOCKET CLOSED
    2019-03-09T07:38:51.656Z [INFO]  [192.168.1.8:47220 <SkBO6JbvV>] RTSP CLIENT DETACHED FROM STREAM: Front Porch (STREAM:48daafa0-9081-4cd2-a876-bfd97e0df325)
    

    I have tested with authentication before. But presently I have authentication disabled in my camera PVR rtsp server. It is a Lorex LHA4108. Auth is also disabled in my monocle portal.

    I have tried the proxy tags, no audio tags, tunnel tags.

    I have tried different resolutions. I have verified H264 codec. I can adjust the bitrate, its currently 4096. But I’m not sure where to set it.

    It is a 3rd gen firetv stick.

    Hopefully that is enough information maybe someone has some idea’s.

    Thanks.



  • ran another connection test just to post the log. with digest auth enabled. oh, and i have verified the DNS as well.

    -------------------------------------------------
    INITIALIZE RTSP STREAM:  Driveway
    -------------------------------------------------
     - NAME  : Driveway
     - LABEL : PRIMARY
     - URL   : rtsp://192.168.1.78:554/ch02/0
     - UUID  : STREAM:5b8bb56c-3c2e-4eb0-9e2b-7a9d092be127
     - SESS  : ca3e487d-c8fc-4276-9c7c-1df52fa5706b
     - MODIF : Sat Mar 09 2019 01:12:56 GMT-0700 (Mountain Standard Time)
     - TAGS  : @noaudio,@tunnel
    -------------------------------------------------
    
    2019-03-09T08:14:18.604Z [INFO]  [192.168.1.8:47432 <HkmJLxbv4>] RTSP CLIENT SOCKET CONNECTED
    2019-03-09T08:14:18.720Z [INFO]  [192.168.1.8:47432 <HkmJLxbv4>] RTSP CLIENT ATTACHED TO STREAM: Driveway (STREAM:5b8bb56c-3c2e-4eb0-9e2b-7a9d092be127)
    2019-03-09T08:14:18.724Z [INFO]  [192.168.1.8:47432 <HkmJLxbv4>] RTSP ENDPOINT SOCKET CONNECTED {192.168.1.78:554}
    2019-03-09T08:14:18.725Z [DEBUG] [192.168.1.8:47432 <HkmJLxbv4>] [CLIENT REQUEST]  --> [DESCRIBE] rtsp://2936db6f-e49d-4ac9-8d70-d90e1623db84.mproxy.io:443/STREAM:5b8bb56c-3c2e-4eb0-9e2b-7a9d092be127?session=ca3e487d-c8fc-4276-9c7c-1df52fa5706b
    2019-03-09T08:14:18.726Z [TRACE] [192.168.1.8:47432 <HkmJLxbv4>] [CLIENT REQUEST]  --> [HEADERS] {
      "accept": "application/sdp",
      "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
      "cseq": "1"
    }
    2019-03-09T08:14:18.727Z [DEBUG] [192.168.1.8:47432 <HkmJLxbv4>] [ENDPOINT REQUEST]  --> [DESCRIBE] rtsp://192.168.1.78:554/ch02/0
    2019-03-09T08:14:18.728Z [TRACE] [192.168.1.8:47432 <HkmJLxbv4>] [ENDPOINT REQUEST]  --> [HEADERS] {
      "accept": "application/sdp",
      "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
      "cseq": "1"
    }
    2019-03-09T08:14:18.731Z [DEBUG] [192.168.1.8:47432 <HkmJLxbv4>] [ENDPOINT RESPONSE] <-- [401 (Unauthorized)] <cseq=0> (session=undefined)
    2019-03-09T08:14:18.733Z [TRACE] [192.168.1.8:47432 <HkmJLxbv4>] [ENDPOINT RESPONSE] <-- [HEADERS] {
      "cseq": "0",
      "server": "Rtsp Server",
      "www-authenticate": "Digest realm=\"Surveillance Server\", nonce=\"63906401\""
    }
    2019-03-09T08:14:18.733Z [INFO]  [192.168.1.8:47432 <HkmJLxbv4>] RTSP ENDPOINT REQUIRES AUTHENTICATION: Digest realm="Surveillance Server", nonce="63906401"
    2019-03-09T08:14:18.734Z [INFO]  [192.168.1.8:47432 <HkmJLxbv4>] RTSP ENDPOINT ATTEMPTING AUTHENTICATION: DIGEST
    2019-03-09T08:14:18.735Z [DEBUG] [192.168.1.8:47432 <HkmJLxbv4>] [ENDPOINT REQUEST]  --> [DESCRIBE] rtsp://192.168.1.78:554/ch02/0
    2019-03-09T08:14:18.736Z [TRACE] [192.168.1.8:47432 <HkmJLxbv4>] [ENDPOINT REQUEST]  --> [HEADERS] {
      "accept": "application/sdp",
      "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
      "cseq": "1",
      "authorization": "Digest username=\"admin\", realm=\"Surveillance Server\", nonce=\"63906401\", uri=\"rtsp://192.168.1.78:554/ch02/0\", response=\"5055098e00edae52794645d49d53968f\""
    }
    2019-03-09T08:14:18.737Z [INFO]  [192.168.1.8:47432 <HkmJLxbv4>] RTSP ENDPOINT SOCKET CLOSED [192.168.1.8:47432 <HkmJLxbv4>]
    2019-03-09T08:14:48.720Z [WARN]  [192.168.1.8:47432 <HkmJLxbv4>] RTSP CLIENT SOCKET TIMEOUT
    2019-03-09T08:14:48.801Z [INFO]  [192.168.1.8:47432 <HkmJLxbv4>] RTSP CLIENT SOCKET CLOSED
    2019-03-09T08:14:48.802Z [INFO]  [192.168.1.8:47432 <HkmJLxbv4>] RTSP CLIENT DETACHED FROM STREAM: Driveway (STREAM:5b8bb56c-3c2e-4eb0-9e2b-7a9d092be127)
    


  • @cferguson

    Based on the log information, the first attempt to ask the camera for it to DESCRIBE its streams fails and the camera responds with an error code 401 saying the requestor is not authenticated. In the response headers the camera also returns:

     "www-authenticate": "Digest realm=\"Surveillance Server\", nonce=\"63906401\""
    

    this is telling us that the camera wants to use DIGEST authentication.

    (All this so far is very normal for a typical RTSP negotiation.)

    The next thing that happens is that the Monocle Gateway re-attempts to ask the camera for its streaming info via the DESCRIBE request but this time including the DIGEST authentication information:

    2019-03-09T07:38:21.642Z [DEBUG] [192.168.1.8:47220 <SkBO6JbvV>] [ENDPOINT REQUEST]  --> [DESCRIBE] rtsp://192.168.1.78:554/ch01/0
    2019-03-09T07:38:21.643Z [TRACE] [192.168.1.8:47220 <SkBO6JbvV>] [ENDPOINT REQUEST]  --> [HEADERS] {
      "accept": "application/sdp",
      "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
      "cseq": "1",
      "authorization": "Digest username=\"admin\", realm=\"Surveillance Server\", nonce=\"96632035\", uri=\"rtsp://192.168.1.78:554/ch01/0\", response=\"343b96ea91339a6af26f6f8530800a2f\""
    }
    

    Immediately after receiving this request the camera terminates the connection:

    2019-03-09T07:38:21.645Z [INFO]  [192.168.1.8:47220 <SkBO6JbvV>] RTSP ENDPOINT SOCKET CLOSED [192.168.1.8:47220 <SkBO6JbvV>]
    

    I’m not sure why the camera is terminating the connection instead of responding with either a (200) success response or error response.

    Base on the log info, I don’t think the bitrate, codec, audio or any stream specific configuration is causing the problem. It’s something going wrong in the RTSP authentication negotiation.



  • I’m kinda lost at this point then. lol.

    So I tried setting up another account in my pvr server. the log in credentials work on vlc. but not on monocle, same error.

    When i click on the camera settings in monocle though it doesn’t seem to have a stored password. it is a series of aterisks that aren’t real. just let setting up a new camera it “seems” blank. Would that possibly be the cause? no stored password?



  • @cferguson

    When i click on the camera settings in monocle though it doesn’t seem to have a stored password. it is a series of aterisks that aren’t real. just let setting up a new camera it “seems” blank. Would that possibly be the cause? no stored password?

    This is just a security/obfuscation technique. You password is stored and used at runtime, but we don’t reveal any details about it when viewing it on subsequent visits to the camera page.

    If you have not already done so, can you open a support ticket? I think the next step would be for us to try accessing your camera stream from here and determine if we can get it working.

    Thanks, Robert


Log in to reply