Foscam C1 and Echo



  • I am using the gateway, and my other cameras are working fine.
    With my Foscam C1 however Echo can not show the camera, I am using the noaudio and tunnel tags. The log from the gateway is copied below. Any ideas please?


    INITIALIZE RTSP STREAM: Door

    • NAME : Door
    • LABEL : PRIMARY
    • URL : rtsp://192.168.2.61:554/videoSub
    • UUID : STREAM:dd462f32-7ab3-4869-9e75-e1ca469e3480
    • SESS : 263314c4-ab4b-4188-bc60-a779200ed481
    • MODIF : Sun Jul 07 2019 23:02:16 GMT+0100 (GMT Summer Time)
    • TAGS : @noaudio,@tunnel

    2019-07-07T22:12:20.015Z [INFO] [192.168.2.29:38325 <BJhHCkgWr>] RTSP CLIENT SOCKET CONNECTED
    2019-07-07T22:12:20.140Z [INFO] [192.168.2.29:38325 <BJhHCkgWr>] RTSP CLIENT ATTACHED TO STREAM: Door (STREAM:dd462f32-7ab3-4869-9e75-e1ca469e3480)
    2019-07-07T22:12:20.140Z [INFO] [192.168.2.29:38325 <BJhHCkgWr>] RTSP ENDPOINT SOCKET CONNECTED {192.168.2.61:554}
    2019-07-07T22:12:20.140Z [DEBUG] [192.168.2.29:38325 <BJhHCkgWr>] [CLIENT REQUEST] --> [DESCRIBE] rtsp://0af5c684-f0ae-494a-b9b6-84ad9b2950c2.mproxy.io:443/STREAM:dd462f32-7ab3-4869-9e75-e1ca469e3480?session=263314c4-ab4b-4188-bc60-a779200ed481
    2019-07-07T22:12:20.140Z [TRACE] [192.168.2.29:38325 <BJhHCkgWr>] [CLIENT REQUEST] --> [HEADERS] {
    “accept”: “application/sdp”,
    “user-agent”: “Fire OS/5.3.6.8 stagefright/1.2 (Linux;Android 5.1.1)”,
    “cseq”: “1”
    }
    2019-07-07T22:12:20.140Z [DEBUG] [192.168.2.29:38325 <BJhHCkgWr>] [ENDPOINT REQUEST] --> [DESCRIBE] rtsp://192.168.2.61:554/videoSub
    2019-07-07T22:12:20.140Z [TRACE] [192.168.2.29:38325 <BJhHCkgWr>] [ENDPOINT REQUEST] --> [HEADERS] {
    “accept”: “application/sdp”,
    “user-agent”: “Fire OS/5.3.6.8 stagefright/1.2 (Linux;Android 5.1.1)”,
    “cseq”: “1”
    }
    2019-07-07T22:12:20.140Z [DEBUG] [192.168.2.29:38325 <BJhHCkgWr>] [ENDPOINT RESPONSE] <-- [401 (Unauthorized)] <cseq=1> (session=undefined)
    2019-07-07T22:12:20.140Z [TRACE] [192.168.2.29:38325 <BJhHCkgWr>] [ENDPOINT RESPONSE] <-- [HEADERS] {
    “server”: “Hisilicon Streaming Media Server/1.0.0(Jul 30 2015)”,
    “cseq”: “1”,
    “www-authenticate”: “Basic realm=“Hisilicon””
    }
    2019-07-07T22:12:20.140Z [INFO] [192.168.2.29:38325 <BJhHCkgWr>] RTSP ENDPOINT REQUIRES AUTHENTICATION: Basic realm=“Hisilicon”
    2019-07-07T22:12:20.140Z [INFO] [192.168.2.29:38325 <BJhHCkgWr>] RTSP ENDPOINT ATTEMPTING AUTHENTICATION: BASIC
    2019-07-07T22:12:20.140Z [DEBUG] [192.168.2.29:38325 <BJhHCkgWr>] [ENDPOINT REQUEST] --> [DESCRIBE] rtsp://192.168.2.61:554/videoSub
    2019-07-07T22:12:20.140Z [TRACE] [192.168.2.29:38325 <BJhHCkgWr>] [ENDPOINT REQUEST] --> [HEADERS] {
    “accept”: “application/sdp”,
    “user-agent”: “Fire OS/5.3.6.8 stagefright/1.2 (Linux;Android 5.1.1)”,
    “cseq”: “1”,
    “authorization”: “Basic Y2hyaXM6Q2F0ZnJvZzE=”
    }
    2019-07-07T22:12:20.155Z [DEBUG] [192.168.2.29:38325 <BJhHCkgWr>] [ENDPOINT RESPONSE] <-- [400 (Bad Request)] <cseq=1> (session=undefined)
    2019-07-07T22:12:20.155Z [TRACE] [192.168.2.29:38325 <BJhHCkgWr>] [ENDPOINT RESPONSE] <-- [HEADERS] {
    “server”: “Hisilicon Streaming Media Server/1.0.0(Jul 30 2015)”,
    “cseq”: “1”
    }
    2019-07-07T22:12:20.155Z [WARN] [192.168.2.29:38325 <BJhHCkgWr>] RTSP ENDPOINT RESPONSE ERROR: [DESCRIBE] = 400 (Bad Request)
    2019-07-07T22:12:20.155Z [DEBUG] [192.168.2.29:38325 <BJhHCkgWr>] [CLIENT RESPONSE] <-- [400 (Bad Request)] <cseq=1> (session=undefined)
    2019-07-07T22:12:20.155Z [TRACE] [192.168.2.29:38325 <BJhHCkgWr>] [CLIENT RESPONSE] <-- [HEADERS] {
    “server”: “Hisilicon Streaming Media Server/1.0.0(Jul 30 2015)”,
    “cseq”: “1”
    }
    2019-07-07T22:12:20.155Z [INFO] [192.168.2.29:38325 <BJhHCkgWr>] RTSP ENDPOINT SOCKET CLOSED [192.168.2.29:38325 <BJhHCkgWr>]
    2019-07-07T22:12:20.155Z [INFO] [192.168.2.29:38325 <BJhHCkgWr>] RTSP CLIENT SOCKET CLOSED
    2019-07-07T22:12:20.155Z [INFO] [192.168.2.29:38325 <BJhHCkgWr>] RTSP CLIENT DETACHED FROM STREAM: Door (STREAM:dd462f32-7ab3-4869-9e75-e1ca469e3480)



  • @cjtrevor

    It looks like you have the Monocle Gateway installed and its working because we can see the RTSP attempts to communicate with the IP camera.

    However, its not getting past the first DESCRIBE request to the IP camera.

    2019-07-07T22:12:20.155Z [DEBUG] [192.168.2.29:38325 <BJhHCkgWr>] [ENDPOINT RESPONSE] <-- [400 (Bad Request)] <cseq=1> (session=undefined)
    

    So the Foscam camera is not accepting the RTSP DESCRIBE request for some reason.
    Is port 554 the correct RTSP port for this camera? My Foscam R4 uses port 88 for both HTTP and RTSP. I know it varies on some Foscam models, but worth checking.

    Thanks, Robert



  • Hi Robert
    Thanks for your reply.
    I have tested using VLC media player which accepts the rtsp address and port so I’m pretty sure this is all correct.
    0f5f060d-cdd2-4f92-8adc-74d2e2387312-image.png

    As it works in VLC, and as the gateway works fine for my other cameras, any ideas what I can try next please?

    Many thanks, Chris



  • @cjtrevor

    Try tags @noaudio,@proxy instead of @noaudio,@tunnel. This will internally (in the Monocle Gateway) use a different RTSP client. Perhaps it can get past this issue.

    Thanks, Robert



  • Hi, tried this and no luck, log copied below.
    Regards, Chris


    INITIALIZE RTSP STREAM: Door

    • NAME : Door
    • LABEL : PRIMARY
    • URL : rtsp://192.168.2.61:554/videoSub
    • UUID : STREAM:dd462f32-7ab3-4869-9e75-e1ca469e3480
    • SESS : 6f9efe27-3710-4133-9600-5d78296f70df
    • MODIF : Mon Jul 08 2019 20:31:13 GMT+0100 (GMT Summer Time)
    • TAGS : @noaudio,@proxy

    2019-07-08T19:34:53.413Z [INFO] [192.168.2.34:58884 <HJH1ifZbS>] RTSP CLIENT SOCKET CONNECTED
    2019-07-08T19:34:53.538Z [INFO] [192.168.2.34:58884 <HJH1ifZbS>] RTSP CLIENT ATTACHED TO STREAM: Door (STREAM:dd462f32-7ab3-4869-9e75-e1ca469e3480)
    2019-07-08T19:34:55.551Z [ERROR] [192.168.2.34:58884 <HJH1ifZbS>] [RTSP ENDPOINT SOCKET ERROR] [192.168.2.34:58884 <HJH1ifZbS>] Error: connect ECONNREFUSED 127.0.0.1:8554
    [ ‘[192.168.2.34:58884 <HJH1ifZbS>]’,
    ‘[RTSP ENDPOINT SOCKET ERROR]’,
    ‘[192.168.2.34:58884 <HJH1ifZbS>]’,
    { Error: connect ECONNREFUSED 127.0.0.1:8554
    at Object._errnoException (util.js:1031:13)
    at _exceptionWithHostPort (util.js:1052:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1195:14)
    errno: ‘ECONNREFUSED’,
    code: ‘ECONNREFUSED’,
    syscall: ‘connect’,
    address: ‘127.0.0.1’,
    port: 8554 } ]
    2019-07-08T19:34:55.552Z [ERROR] PROXY ENDPOINT ERROR; Error: connect ECONNREFUSED 127.0.0.1:8554
    [ ‘PROXY ENDPOINT ERROR;’,
    { Error: connect ECONNREFUSED 127.0.0.1:8554
    at Object._errnoException (util.js:1031:13)
    at _exceptionWithHostPort (util.js:1052:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1195:14)
    errno: ‘ECONNREFUSED’,
    code: ‘ECONNREFUSED’,
    syscall: ‘connect’,
    address: ‘127.0.0.1’,
    port: 8554 } ]
    2019-07-08T19:34:55.552Z [INFO] [192.168.2.34:58884 <HJH1ifZbS>] RTSP ENDPOINT SOCKET CLOSED [192.168.2.34:58884 <HJH1ifZbS>]
    2019-07-08T19:35:23.538Z [WARN] [192.168.2.34:58884 <HJH1ifZbS>] RTSP CLIENT SOCKET TIMEOUT
    2019-07-08T19:35:23.541Z [INFO] [192.168.2.34:58884 <HJH1ifZbS>] RTSP CLIENT SOCKET CLOSED
    2019-07-08T19:35:23.541Z [INFO] [192.168.2.34:58884 <HJH1ifZbS>] RTSP CLIENT DETACHED FROM STREAM: Door (STREAM:dd462f32-7ab3-4869-9e75-e1ca469e3480)



  • @cjtrevor

    In this log, it looks like the “monocle-proxy” is not working. Try restarting monocle gateway and see if you notice any errors on startup. A second process named “monocle-proxy” should be automatically started in the background and listening on port 8554.

    Are you running on Windows or Linux? If Windows, it could be Windows Firewall blocking access to port 8554.

    Thanks, Robert



  • All working! Thank you!
    Reboot, restart service, and magic all now working with the @proxy tag!



  • @cjtrevor

    Glad to hear its working now. My guess is that there is something in the RTSP client that the IP camera does not like. Switching to @proxy uses a different RTSP client.


Log in to reply