• Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Help connecting to camera on other LAN

    Support
    2
    5
    232
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      socalgman last edited by

      Camera: AXIS P3364
      NVR: Blue Iris Win10
      Alexa: Echo Show 5

      Hello,

      I have an echo show 5 connected to a LAN with a 192 IP address. My Blue Iris NVR is on a different LAN with a 77 IP address connected to the camera via Ethernet. The NVR touches my home network (192) through a WiFi adapter, hence is is on both the 77 and the 192 networks). I sign on to the NVR bus remote desktop connection. I can ping both the 77 and 192 networks (including the camera) from either machine.

      I am running the monicle gateway, and am tagged @tunnel. I have also tried @proxy. The Monocle skill is enabled on Alexa and it has been discovered. However Alexa won’t pick up the camera feed.

      Any suggestions?

      Monocle 1 Reply Last reply Reply Quote 0
      • Monocle
        Monocle @socalgman last edited by

        @socalgman

        OK, if you can, please provide a copy of the log output from your Monocle Gateway from startup to the point you ask for a camera feed.

        As long as your router can resolve the camera addresses, it should work. For tags, make sure to use either @tunnel or @proxy-tcp. These make make sure to use only TCP for communication with your cameras or NVR. @proxy will attempt to use UDP for the stream and that may fail in a situation where there are multiple VLANs.

        Thanks, Robert

        Monocle: https://monoclecam.com
        Getting Started | Troubleshooting Guide | FAQ | Contact Support

        S 1 Reply Last reply Reply Quote 0
        • S
          socalgman last edited by Monocle

          Hello, Robert- Please see the log cut/paste below. I did try @tunnel and @proxy-tcp and neither worked. Still getting “Hmmm, camera not found”. I also tried some other tags I saw in the forum such as @noaudio, @ntpnow, and @fakentp. The rtsp address did work in VLC for me on the NVP server (77), but not on the LAN (192) where gateway is running. As I mentioned, I can ping back and forth though, and can ping the camera from the LAN PC.

          -------------------------------------------------
MONOCLE RUNTIME ENVIRONMENT
-------------------------------------------------
VERSION   = 0.0.4
OS/ARCH   = win32\x64
PROCESS   = monocle-gateway (PID=33212)
TIMESTAMP = 2019-09-14T08:44:41.337Z

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

-------------------------------------------------
MONOCLE RTSP SERVICE - INITIALIZED
-------------------------------------------------
FQDN = e6cd8c21-da3a-43d8-893b-f1ae390228ed.mproxy.io
HOST = 192.168.1.23
PORT = 443
-------------------------------------------------

-------------------------------------------------
INITIALIZE RTSP STREAM:  1236
-------------------------------------------------
 - NAME  : 1236
 - LABEL : PRIMARY
 - URL   : rtsp://77.1.1.2:554/axis-media/media.amp
 - UUID  : STREAM:39933ad5-0783-4e50-b05d-15445111d263
 - SESS  : 3834404b-92d2-4d53-b72e-d89d600d9d4c
 - MODIF : Sat Sep 14 2019 01:38:19 GMT-0700 (Pacific Daylight Time)
 - TAGS  : @tunnel
-------------------------------------------------

2019-09-14T08:45:36.784Z [INFO]  [192.168.1.41:35444 <rkK3_mqIB>] RTSP CLIENT SOCKET CONNECTED
2019-09-14T08:45:36.910Z [INFO]  [192.168.1.41:35444 <rkK3_mqIB>] RTSP CLIENT ATTACHED TO STREAM: 1236 (STREAM:39933ad5-0783-4e50-b05d-15445111d263)
2019-09-14T08:45:36.923Z [INFO]  [192.168.1.41:35444 <rkK3_mqIB>] RTSP ENDPOINT SOCKET CONNECTED {77.1.1.2:554}
2019-09-14T08:45:36.925Z [DEBUG] [192.168.1.41:35444 <rkK3_mqIB>] [CLIENT REQUEST]  --> [DESCRIBE] rtsp://e6cd8c21-da3a-43d8-893b-f1ae390228ed.mproxy.io:443/STREAM:39933ad5-0783-4e50-b05d-15445111d263?session=3834404b-92d2-4d53-b72e-d89d600d9d4c
2019-09-14T08:45:36.925Z [TRACE] [192.168.1.41:35444 <rkK3_mqIB>] [CLIENT REQUEST]  --> [HEADERS] {
  "accept": "application/sdp",
  "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
  "cseq": "1"
}
2019-09-14T08:45:36.926Z [INFO]  [192.168.1.41:35444 <rkK3_mqIB>] RTSP ENDPOINT ATTEMPTING AUTHENTICATION: BASIC
2019-09-14T08:45:36.927Z [DEBUG] [192.168.1.41:35444 <rkK3_mqIB>] [ENDPOINT REQUEST]  --> [DESCRIBE] rtsp://77.1.1.2:554/axis-media/media.amp
2019-09-14T08:45:36.927Z [TRACE] [192.168.1.41:35444 <rkK3_mqIB>] [ENDPOINT REQUEST]  --> [HEADERS] {
  "accept": "application/sdp",
  "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
  "cseq": "1",
  "authorization": "Basic YWRtaW46YWRtaW4="
}
2019-09-14T08:45:37.124Z [INFO]  [192.168.1.41:35444 <rkK3_mqIB>] RTSP ENDPOINT SOCKET CLOSED [192.168.1.41:35444 <rkK3_mqIB>]
2019-09-14T08:46:06.912Z [WARN]  [192.168.1.41:35444 <rkK3_mqIB>] RTSP CLIENT SOCKET TIMEOUT
2019-09-14T08:46:06.923Z [INFO]  [192.168.1.41:35444 <rkK3_mqIB>] RTSP CLIENT SOCKET CLOSED
2019-09-14T08:46:06.924Z [INFO]  [192.168.1.41:35444 <rkK3_mqIB>] RTSP CLIENT DETACHED FROM STREAM: 1236 (STREAM:39933ad5-0783-4e50-b05d-15445111d263)

-------------------------------------------------
INITIALIZE RTSP STREAM:  1236
-------------------------------------------------
 - NAME  : 1236
 - LABEL : PRIMARY
 - URL   : rtsp://77.1.1.2:554/axis-media/media.amp
 - UUID  : STREAM:39933ad5-0783-4e50-b05d-15445111d263
 - SESS  : a66f766f-4779-4ac8-918d-ea367d95d53d
 - MODIF : Sat Sep 14 2019 01:38:19 GMT-0700 (Pacific Daylight Time)
 - TAGS  : @tunnel
-------------------------------------------------

2019-09-14T08:46:07.887Z [INFO]  [192.168.1.41:35456 <S1uROm98S>] RTSP CLIENT SOCKET CONNECTED
2019-09-14T08:46:08.024Z [INFO]  [192.168.1.41:35456 <S1uROm98S>] RTSP CLIENT ATTACHED TO STREAM: 1236 (STREAM:39933ad5-0783-4e50-b05d-15445111d263)
2019-09-14T08:46:08.035Z [INFO]  [192.168.1.41:35456 <S1uROm98S>] RTSP ENDPOINT SOCKET CONNECTED {77.1.1.2:554}
2019-09-14T08:46:08.035Z [DEBUG] [192.168.1.41:35456 <S1uROm98S>] [CLIENT REQUEST]  --> [DESCRIBE] rtsp://e6cd8c21-da3a-43d8-893b-f1ae390228ed.mproxy.io:443/STREAM:39933ad5-0783-4e50-b05d-15445111d263?session=a66f766f-4779-4ac8-918d-ea367d95d53d
2019-09-14T08:46:08.036Z [TRACE] [192.168.1.41:35456 <S1uROm98S>] [CLIENT REQUEST]  --> [HEADERS] {
  "accept": "application/sdp",
  "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
  "cseq": "1"
}
2019-09-14T08:46:08.037Z [INFO]  [192.168.1.41:35456 <S1uROm98S>] RTSP ENDPOINT ATTEMPTING AUTHENTICATION: BASIC
2019-09-14T08:46:08.038Z [DEBUG] [192.168.1.41:35456 <S1uROm98S>] [ENDPOINT REQUEST]  --> [DESCRIBE] rtsp://77.1.1.2:554/axis-media/media.amp
2019-09-14T08:46:08.038Z [TRACE] [192.168.1.41:35456 <S1uROm98S>] [ENDPOINT REQUEST]  --> [HEADERS] {
  "accept": "application/sdp",
  "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
  "cseq": "1",
  "authorization": "Basic YWRtaW46YWRtaW4="
}
2019-09-14T08:46:08.239Z [INFO]  [192.168.1.41:35456 <S1uROm98S>] RTSP ENDPOINT SOCKET CLOSED [192.168.1.41:35456 <S1uROm98S>]
2019-09-14T08:46:38.025Z [WARN]  [192.168.1.41:35456 <S1uROm98S>] RTSP CLIENT SOCKET TIMEOUT
2019-09-14T08:46:38.035Z [INFO]  [192.168.1.41:35456 <S1uROm98S>] RTSP CLIENT SOCKET CLOSED
2019-09-14T08:46:38.036Z [INFO]  [192.168.1.41:35456 <S1uROm98S>] RTSP CLIENT DETACHED FROM STREAM: 1236 (STREAM:39933ad5-0783-4e50-b05d-15445111d263)

-------------------------------------------------
INITIALIZE RTSP STREAM:  1236
-------------------------------------------------
 - NAME  : 1236
 - LABEL : PRIMARY
 - URL   : rtsp://77.1.1.2:554/axis-media/media.amp
 - UUID  : STREAM:39933ad5-0783-4e50-b05d-15445111d263
 - SESS  : a80934bb-8f4e-40a4-b3a6-f2f9dfc13093
 - MODIF : Sat Sep 14 2019 01:38:19 GMT-0700 (Pacific Daylight Time)
 - TAGS  : @tunnel
-------------------------------------------------

2019-09-14T08:46:38.933Z [INFO]  [192.168.1.41:35458 <ryweYm5IB>] RTSP CLIENT SOCKET CONNECTED
2019-09-14T08:46:39.061Z [INFO]  [192.168.1.41:35458 <ryweYm5IB>] RTSP CLIENT ATTACHED TO STREAM: 1236 (STREAM:39933ad5-0783-4e50-b05d-15445111d263)
2019-09-14T08:46:39.065Z [INFO]  [192.168.1.41:35458 <ryweYm5IB>] RTSP ENDPOINT SOCKET CONNECTED {77.1.1.2:554}
2019-09-14T08:46:39.066Z [DEBUG] [192.168.1.41:35458 <ryweYm5IB>] [CLIENT REQUEST]  --> [DESCRIBE] rtsp://e6cd8c21-da3a-43d8-893b-f1ae390228ed.mproxy.io:443/STREAM:39933ad5-0783-4e50-b05d-15445111d263?session=a80934bb-8f4e-40a4-b3a6-f2f9dfc13093
2019-09-14T08:46:39.066Z [TRACE] [192.168.1.41:35458 <ryweYm5IB>] [CLIENT REQUEST]  --> [HEADERS] {
  "accept": "application/sdp",
  "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
  "cseq": "1"
}
2019-09-14T08:46:39.066Z [INFO]  [192.168.1.41:35458 <ryweYm5IB>] RTSP ENDPOINT ATTEMPTING AUTHENTICATION: BASIC
2019-09-14T08:46:39.067Z [DEBUG] [192.168.1.41:35458 <ryweYm5IB>] [ENDPOINT REQUEST]  --> [DESCRIBE] rtsp://77.1.1.2:554/axis-media/media.amp
2019-09-14T08:46:39.068Z [TRACE] [192.168.1.41:35458 <ryweYm5IB>] [ENDPOINT REQUEST]  --> [HEADERS] {
  "accept": "application/sdp",
  "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
  "cseq": "1",
  "authorization": "Basic YWRtaW46YWRtaW4="
}
2019-09-14T08:46:39.263Z [INFO]  [192.168.1.41:35458 <ryweYm5IB>] RTSP ENDPOINT SOCKET CLOSED [192.168.1.41:35458 <ryweYm5IB>]
2019-09-14T08:47:09.062Z [WARN]  [192.168.1.41:35458 <ryweYm5IB>] RTSP CLIENT SOCKET TIMEOUT
2019-09-14T08:47:09.066Z [INFO]  [192.168.1.41:35458 <ryweYm5IB>] RTSP CLIENT SOCKET CLOSED
2019-09-14T08:47:09.067Z [INFO]  [192.168.1.41:35458 <ryweYm5IB>] RTSP CLIENT DETACHED FROM STREAM: 1236 (STREAM:39933ad5-0783-4e50-b05d-15445111d263)
          1 Reply Last reply Reply Quote 0
          • S
            socalgman @Monocle last edited by

            @Monocle Hello, were you able to see anything in the log suggestive of the issue?

            Monocle 1 Reply Last reply Reply Quote 0
            • Monocle
              Monocle @socalgman last edited by

              @socalgman

              Sorry for the delay, I have been away for a couple of weeks.

              In all cases in the log, the gateway attempts to use BASIC authentication to access the RTSP stream on the camera and perform a DESCRIBE request. In all cases the camera immediately terminates the TCP/RTSP connection from the gateway. So there is something the camera does not like about the request. It should at least return an error code for invalid requests or invalid authentication attempts, but it’s just terminating the TCP socket with no response. Very odd.

              If this is a camera stream that you can temporarily make available to me over the Internet for testing, I can perform some additional tests to see if there is any workaround. You can PM me the connection details and a temporary view-only access credentials.

              Thanks, Robert

              Monocle: https://monoclecam.com
              Getting Started | Troubleshooting Guide | FAQ | Contact Support

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Privacy Policy  |  Terms & Conditions

              © 2018 shadeBlue, LLC.