Unknowed brand IPcam
-
I have opened the port for my iPcam and I have send you a Email with the working URL for VLC.
Hope it works also from you
-
Some progress but not fully working.
Using some additional tools I was able to connect to the camera and start a RTSP negotiation.
However, the camera seems to stop communicating after the RTSP layer request to SETUP the camera stream using TCP interleaved streaming.Basically here is the request its failing on:
Jul 27 13:22:18 rpi4b-2g monocle-gateway[6611]: 2019-07-27T17:22:18.336Z [DEBUG] [10.1.2.232:54615 <By-Iu-cMH>] [ENDPOINT REQUEST] --> [SETUP] rtsp://-!!-REDACTED-!!- Jul 27 13:22:18 rpi4b-2g monocle-gateway[6611]: 2019-07-27T17:22:18.336Z [TRACE] [10.1.2.232:54615 <By-Iu-cMH>] [ENDPOINT REQUEST] --> [HEADERS] { Jul 27 13:22:18 rpi4b-2g monocle-gateway[6611]: "transport": "RTP/AVP/TCP;interleaved=0-1", Jul 27 13:22:18 rpi4b-2g monocle-gateway[6611]: "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)", Jul 27 13:22:18 rpi4b-2g monocle-gateway[6611]: "cseq": "2" Jul 27 13:22:18 rpi4b-2g monocle-gateway[6611]: }
What is odd is that instead of the camera sending back and error response or failure of some kind, it just stalls and locks up. So Alexa after 30 seconds will see no further communication and will forcefully disconnect the socket.
I used some other RTSP tools to further test and I was able to get further, in fact the RTSP negotiation completed but only when I request the camera transport the video/audio using UDP streaming. So … this seems like the camera does support UDP streaming but maybe not TCP interleaved. Unfortunately Alexa requires TCP interleaved streaming. So the Monocle Gateway does include the support to proxy the camera stream and convert from a UDP stream to a TCP interleaved stream, but that does not work across the Internet – only on a local network.
So what have we learned — well … the camera may only support UDP streaming which means that you must use a local Monocle Gateway instance running inside your network and the camera must have the
@proxy
tag instead of the@tunnel
tag to proxy the UDP to TCP for Alexa.I was not able to confirm if the camera is working with Alexa yet because it will only work via UDP on the local network. Thus as far as remote testing, I’m stuck.
So the only option moving forward is to get your local instance of Monocle Gateway working and then test the
@proxy
stream inside your network.In our previous testing, we still did not see any incoming connections to the Monocle Gateway from the Alexa devices. This still suggests some networking related issue, most likely a DNS issue, a Firewall, a Virtual Network or isolated (Guest) network.
Do you run a local DNS server or does your router have the ability to override DNS hostnames via a DNS resolver?
Thanks, Robert
-
Hope I have made it correctly
Jul 27 20:59:55 FhemServer monocle-gateway[24599]: ------------------------------------------------- Jul 27 20:59:55 FhemServer monocle-gateway[24599]: INITIALIZE RTSP STREAM: Garten Jul 27 20:59:55 FhemServer monocle-gateway[24599]: ------------------------------------------------- Jul 27 20:59:55 FhemServer monocle-gateway[24599]: - NAME : Garten Jul 27 20:59:55 FhemServer monocle-gateway[24599]: - LABEL : PRIMARY Jul 27 20:59:55 FhemServer monocle-gateway[24599]: - URL : rtsp://192.168.2.102:554/user=admin&password=xxxxx &channel=1&stream=1.sdp Jul 27 20:59:55 FhemServer monocle-gateway[24599]: - UUID : STREAM:df443cff-97a9-45ac-a21d-9768d4674f63 Jul 27 20:59:55 FhemServer monocle-gateway[24599]: - SESS : 3d70b93e-5326-4d46-a947-f90dfa16e176 Jul 27 20:59:55 FhemServer monocle-gateway[24599]: - MODIF : Sat Jul 27 2019 20:59:02 GMT+0200 (GMT+02:00) Jul 27 20:59:55 FhemServer monocle-gateway[24599]: - TAGS : @proxy Jul 27 20:59:55 FhemServer monocle-gateway[24599]: ------------------------------------------------- Jul 27 20:59:55 FhemServer monocle-gateway[24599]: RTSP STREAM MODIFIED: Garten Jul 27 20:59:55 FhemServer monocle-gateway[24599]: Any existing RTSP steams will be shut down Jul 27 20:59:55 FhemServer monocle-gateway[24599]: and a new stream instance will be registered. Jul 27 20:59:55 FhemServer monocle-gateway[24599]: ------------------------------------------------- Jul 27 20:59:55 FhemServer monocle-gateway[24599]: 2019-07-27T18:59:55.217Z [DEBUG] <RTSP-PROXY> [REQUEST] --> [DEREGISTER] rtsp://192.168.2.102:554/user=admin&password=xxxc&channel=1&stream=1.sdp Jul 27 20:59:55 FhemServer monocle-gateway[24599]: 2019-07-27T18:59:55.218Z [TRACE] <RTSP-PROXY> [REQUEST] --> [HEADERS] { Jul 27 20:59:55 FhemServer monocle-gateway[24599]: "cseq": "1", Jul 27 20:59:55 FhemServer monocle-gateway[24599]: "transport": "reuse_connection=0;preferred_delivery_protocol=udp;proxy_url_suffix=STREAM:df443cff-97a9-45ac-a21d-9768d4674f63" Jul 27 20:59:55 FhemServer monocle-gateway[24599]: } Jul 27 20:59:55 FhemServer monocle-gateway[24599]: 2019-07-27T18:59:55.222Z [DEBUG] <RTSP-PROXY> [RESPONSE] <-- [451 (Invalid parameter)] <cseq=1> (session=undefined) Jul 27 20:59:55 FhemServer monocle-gateway[24599]: 2019-07-27T18:59:55.222Z [TRACE] <RTSP-PROXY> [RESPONSE] <-- [HEADERS] { Jul 27 20:59:55 FhemServer monocle-gateway[24599]: "cseq": "1", Jul 27 20:59:55 FhemServer monocle-gateway[24599]: "date": "Sat, Jul 27 2019 18:59:55 GMT" Jul 27 20:59:55 FhemServer monocle-gateway[24599]: } Jul 27 20:59:55 FhemServer monocle-gateway[24599]: 2019-07-27T18:59:55.225Z [INFO] [RTSP PROXY] REGISTERING STREAM [Garten/PRIMARY]; (STREAM:df443cff-97a9-45ac-a21d-9768d4674f63) Jul 27 20:59:55 FhemServer monocle-gateway[24599]: 2019-07-27T18:59:55.237Z [DEBUG] <RTSP-PROXY> [REQUEST] --> [REGISTER] rtsp://192.168.2.102:554/user=admin&password=xxxxxx&channel=1&stream=1.sdp Jul 27 20:59:55 FhemServer monocle-gateway[24599]: 2019-07-27T18:59:55.238Z [TRACE] <RTSP-PROXY> [REQUEST] --> [HEADERS] { Jul 27 20:59:55 FhemServer monocle-gateway[24599]: "cseq": "1", Jul 27 20:59:55 FhemServer monocle-gateway[24599]: "transport": "reuse_connection=0;preferred_delivery_protocol=udp;proxy_url_suffix=STREAM:df443cff-97a9-45ac-a21d-9768d4674f63" Jul 27 20:59:55 FhemServer monocle-gateway[24599]: } Jul 27 20:59:55 FhemServer monocle-gateway[24599]: 2019-07-27T18:59:55.241Z [DEBUG] <RTSP-PROXY> [RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined) Jul 27 20:59:55 FhemServer monocle-gateway[24599]: 2019-07-27T18:59:55.242Z [TRACE] <RTSP-PROXY> [RESPONSE] <-- [HEADERS] { Jul 27 20:59:55 FhemServer monocle-gateway[24599]: "cseq": "1", Jul 27 20:59:55 FhemServer monocle-gateway[24599]: "date": "Sat, Jul 27 2019 18:59:55 GMT" Jul 27 20:59:55 FhemServer monocle-gateway[24599]: } Jul 27 20:59:58 FhemServer monocle-gateway[24599]: ------------------------------------------------- Jul 27 20:59:58 FhemServer monocle-gateway[24599]: INITIALIZE RTSP STREAM: Garten Jul 27 20:59:58 FhemServer monocle-gateway[24599]: ------------------------------------------------- Jul 27 20:59:58 FhemServer monocle-gateway[24599]: - NAME : Garten Jul 27 20:59:58 FhemServer monocle-gateway[24599]: - LABEL : PRIMARY Jul 27 20:59:58 FhemServer monocle-gateway[24599]: - URL : rtsp://192.168.2.102:554/user=admin&password=xxxxxcc&channel=1&stream=1.sdp Jul 27 20:59:58 FhemServer monocle-gateway[24599]: - UUID : STREAM:df443cff-97a9-45ac-a21d-9768d4674f63 Jul 27 20:59:58 FhemServer monocle-gateway[24599]: - SESS : 5364f750-0536-461b-80e7-c1fd4f3e1c05 Jul 27 20:59:58 FhemServer monocle-gateway[24599]: - MODIF : Sat Jul 27 2019 20:59:02 GMT+0200 (GMT+02:00) Jul 27 20:59:58 FhemServer monocle-gateway[24599]: - TAGS : @proxy Jul 27 20:59:58 FhemServer monocle-gateway[24599]: ------------------------------------------------- Jul 27 20:59:58 FhemServer monocle-gateway[24599]: ------------------------------------------------- Jul 27 20:59:58 FhemServer monocle-gateway[24599]: INITIALIZE RTSP STREAM: Garten Jul 27 20:59:58 FhemServer monocle-gateway[24599]: ------------------------------------------------- Jul 27 20:59:58 FhemServer monocle-gateway[24599]: - NAME : Garten Jul 27 20:59:58 FhemServer monocle-gateway[24599]: - LABEL : PRIMARY Jul 27 20:59:58 FhemServer monocle-gateway[24599]: - URL : rtsp://192.168.2.102:554/user=admin&password=xxxxx&channel=1&stream=1.sdp Jul 27 20:59:58 FhemServer monocle-gateway[24599]: - UUID : STREAM:df443cff-97a9-45ac-a21d-9768d4674f63 Jul 27 20:59:58 FhemServer monocle-gateway[24599]: - SESS : f0dfc23f-9fc2-412d-bd24-1908c3abf498 Jul 27 20:59:58 FhemServer monocle-gateway[24599]: - MODIF : Sat Jul 27 2019 20:59:02 GMT+0200 (GMT+02:00) Jul 27 20:59:58 FhemServer monocle-gateway[24599]: - TAGS : @proxy Jul 27 20:59:58 FhemServer monocle-gateway[24599]: ------------------------------------------------- Jul 27 21:00:01 FhemServer monocle-gateway[24599]: 2019-07-27T19:00:01.229Z [INFO] [RTSP PROXY] STREAM [Garten/PRIMARY] WILL BE DE-REGISTERED IN 4 MINUTES
-
Yes, but the log confirms the same issue as before the Alexa devices are not connecting.
You mentioned that the Alexa devices are behind a different Fritzbox. Is it possible to put a laptop or computer on the same network/router as the Alexa devices and test the DNS hostname (FQDN)? It could be that that specific Fritzbox is blocking the DNS requests to the Alexa devices.
I will also go ahead and remove the cloud gateway instance, it has served its purpose for now and we need to get your local one working before we are able to test this specific camera stream.
Thanks, Robert
-
The Alexa device is connected the my 1. FritzBox via WLAN and also the Raspberry on this is running the gateway service. The camera is connected via WLAN to the 2. FritzBox and this is connected to the 1. FritzBox via Cable.
All Device at in the same Network 192.168.2.x 255.255.255.0
So what can I do for testing if DNS is Working?
-
OK, so both the gateway and Alexa devices are on the same router. Good.
I think we need to look into the Fritzbox settings and add a provision for the DNS hostname.
This is pretty common on Fritzbox routers.You will need to allow DNS hostname
9dd28fe1-40f2-4459-805d-daa62fdc6ff5.mproxy.io
(unless it has changed in our testing efforts, look at the startup messages in the monocle gateway log) Or allow anything with “mproxy.io”.I know we tested the DNS resolution in the past – thinking it was fine, but something is just not right. The Alexa devices should be able to resolve the hostname to the gateway’s local IP address and then connect. We have demonstrates that they will connect to a public IP when we ran a gateway in the cloud. So its not likely to be a problem with the Alexa devices.
Thanks, Robert
-
Okay I have white the address in the FritzBox, in the DNS Rebind protection.
It theems a little bit better
But the cam is not showing
INITIALIZE RTSP STREAM: Garten ------------------------------------------------- - NAME : Garten - LABEL : PRIMARY - URL : rtsp://192.168.2.102:554/user=admin&password=xxxxxx&channel=1&stream=1.sdp - UUID : STREAM:df443cff-97a9-45ac-a21d-9768d4674f63 - SESS : e336adda-557d-47c9-ae78-3b76f60a26a7 - MODIF : Mon Jul 29 2019 16:21:39 GMT+0200 (GMT+02:00) - TAGS : @tunnel ------------------------------------------------- 2019-07-30T07:22:38.024Z [INFO] [192.168.2.50:34792 <rJLHluTzB>] RTSP CLIENT SOCKET CONNECTED 2019-07-30T07:22:38.139Z [INFO] [192.168.2.50:34792 <rJLHluTzB>] RTSP CLIENT ATTACHED TO STREAM: Garten (STREAM:df443cff-97a9-45ac-a21d-9768d4674f63) 2019-07-30T07:22:38.259Z [INFO] [192.168.2.50:34792 <rJLHluTzB>] RTSP ENDPOINT SOCKET CONNECTED {192.168.2.102:554} 2019-07-30T07:22:38.268Z [DEBUG] [192.168.2.50:34792 <rJLHluTzB>] [CLIENT REQUEST] --> [DESCRIBE] rtsp://9dd28fe1-40f2-4459-805d-daa62fdc6ff5.mproxy.io:443/STREAM:df443cff-97a9-45ac-a21d-9768d4674f63?session=e336adda-557d-47c9-ae78-3b76f60a26a7 2019-07-30T07:22:38.268Z [TRACE] [192.168.2.50:34792 <rJLHluTzB>] [CLIENT REQUEST] --> [HEADERS] { "accept": "application/sdp", "user-agent": "stagefright/1.2 (Linux;Android 5.1.1)", "cseq": "1" } 2019-07-30T07:22:38.278Z [DEBUG] [192.168.2.50:34792 <rJLHluTzB>] [ENDPOINT REQUEST] --> [DESCRIBE] rtsp://192.168.2.102:554/user=admin&password=xxxccccc&channel=1&stream=1.sdp 2019-07-30T07:22:38.278Z [TRACE] [192.168.2.50:34792 <rJLHluTzB>] [ENDPOINT REQUEST] --> [HEADERS] { "accept": "application/sdp", "user-agent": "stagefright/1.2 (Linux;Android 5.1.1)", "cseq": "1" } 2019-07-30T07:23:08.136Z [WARN] [192.168.2.50:34792 <rJLHluTzB>] RTSP CLIENT SOCKET TIMEOUT 2019-07-30T07:23:08.147Z [INFO] [192.168.2.50:34792 <rJLHluTzB>] RTSP CLIENT SOCKET CLOSED 2019-07-30T07:23:08.148Z [INFO] [192.168.2.50:34792 <rJLHluTzB>] RTSP CLIENT DETACHED FROM STREAM: Garten (STREAM:df443cff-97a9-45ac-a21d-9768d4674f63) 2019-07-30T07:23:08.150Z [INFO] [192.168.2.50:34792 <rJLHluTzB>] RTSP ENDPOINT SOCKET CLOSED [192.168.2.50:34792 <rJLHluTzB>]
-
Yes definitely looks better. At least we are getting past the DNS issue and the Alexa devices are now able to connect to the gateway and start a RTSP stream.
So what the log is now showing is that the gateway is attempting to communicate with the IP camera at address:
rtsp://192.168.2.102:554/user=admin&password=xxxccccc&channel=1&stream=1.sdp
; however, it’s not able to for some reason.If this the same result on all your cameras? You can also try
@proxy-tcp
instead of@tunnel
, but if this is a networking issue, that won’t help. You mentioned that the IP cameras are on a separate router — can other devices/computers on the gateway/Alexa network talk to the IP cameras?Thanks, Robert
-
I can connect the camera with all other device in my network from all Acesspoints, with the Smartphone with the Laptop and with Kodi on the Raspberry Pi.
Only Alexa will not show the Stream.
I have only one more iP cams but they don’t have a h264 stream -
OK, then try using
@proxy
or@proxy-tcp
instead of@tunnel
. In some rare cases, some camera’s don’t like our default RTSP client and these alternate tags will attempt to use another RTSP client implementation.Thanks, Robert
-
So some old news, I have seen my Cam on Alexa, but,
I must start the Gateway with this command
monocle-gateway
If I start it like
monocle-gateway --start
Alexa can not connect
Also if monocle-gateway --enable after reboot the Raspberry, Alexa can not connect.
Also if I have startet the gateway with
monocle-gateway
Alexa can connect one time and show the live stream for CA 30 second then comes buffering and the connection close after this I must stop the gateway and start again with monocle-gateway.I must use the tag @proxy-tcp
I hope this informations helps
-
We can probably sort of the daemon issue and get it running as a background server. However, I think the more pressing issue is to get it running stable first while just running the executable directly from the shell/command line.
Since you are using one of the
@proxy*
tags, you can also add@hangup
in conjunction with@proxy-tcp
. This has helped a few users with similar symptoms – cameras that would not reconnect after the first stream. The@hangup
tag will make sure to fully shutdown the stream each time the network connection is closed. The default behavior for the proxy implementation is to try and hang on to the stream for a few minutes just in case of a subsequent request is made.Some cameras, like Reolink, don’t like it when you request the stream again immediately after the previous stream is terminated. These cameras will stream again if you wait about 5 minutes before requesting it again. I’m sure its some Alexa incompatibility issue, but it does come up with the Reolink cameras.
As far as the initial stream timing out after 30 seconds, well – solving that may be more difficult. First, make sure to include the
@noaudio
tag just in case there is an audio channel in the stream. Some audio channels really cause issues with Alexa’s player. Next, you may have to play with your camera’s streaming video codec settings to see if you can find a combination that Alexa likes better. For example, try changing H.264 profiles (High, Standard, Baseline), try enabling/disabling H.264+ (if you camera support that), try lowering the resolution, bitrate, etc.Thanks, Robert
-
-
So the problem with buffering after 30 seconds is away also that I can not reconnect without restart the gateway. So the tag @hangup is okay.
Yet I have only the problem that I must start the server with
monocle-gateway
But if I close the Console the gateway stopps
The Autostart or with
monocle-gateway --start
Alexa can not connect the cameraSo I thing we have 80% for my happyness
-
OK, lets try these command to try to UNINSTALL then REINSTALL the daemon config with systemd on Raspbian:
sudo monocle-gateway --uninstall sudo monocle-gateway --install sudo monocle-gateway --restart
Are you using the latest Raspbian Buster distribution?
-
No on this server is not running buster on this one is running the last Jessy version
-
Well, Jesse should have
systemd
, so it “should” work. Wheezy however, may not.
Try the commands posted to reinstall the service/daemon and see what we get.Thanks, Robert
-
Okay I have done but I can test it in nearly one hour. I am just not at home.
-
okay i am at home,
after a reebot from the Raspberry a monocle-gateway --status shows this…
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Fri Aug 2 18:18:35 2019 from 192.168.2.87 root@FhemServer:~# monocle-gateway --status ****************************************************************** * __ __ ___ _ _ ___ ___ _ ___ * * | \/ |/ _ \| \| |/ _ \ / __| | | __| * * | |\/| | (_) | .` | (_) | (__| |__| _| * * |_| |_|\___/|_|\_|\___/ \___|____|___| * * * ****************************************************************** GETTING <<STATUS>> FOR THE [MONOCLE-GATEWAY] SERVICE ● monocle-gateway.service - Monocle Gateway Service Loaded: loaded (/etc/systemd/system/monocle-gateway.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2019-08-02 18:26:46 CEST; 2min 35s ago Main PID: 412 (monocle-gateway) CGroup: /system.slice/monocle-gateway.service ├─412 /usr/local/bin/monocle-gateway └─660 /usr/local/bin/monocle-proxy -p 8554 Aug 02 18:27:03 FhemServer monocle-gateway[412]: [Monocle Connecting] Aug 02 18:27:04 FhemServer monocle-gateway[412]: [Monocle Connected] Aug 02 18:27:04 FhemServer monocle-gateway[412]: [RTSP Server Registered] Aug 02 18:27:04 FhemServer monocle-gateway[412]: ------------------------------------------------- Aug 02 18:27:04 FhemServer monocle-gateway[412]: MONOCLE RTSP SERVICE - INITIALIZED Aug 02 18:27:04 FhemServer monocle-gateway[412]: ------------------------------------------------- Aug 02 18:27:04 FhemServer monocle-gateway[412]: FQDN = 9dd28fe1-40f2-4459-805d-daa62fdc6ff5.mproxy.io Aug 02 18:27:04 FhemServer monocle-gateway[412]: HOST = 192.168.2.172 Aug 02 18:27:04 FhemServer monocle-gateway[412]: PORT = 443 Aug 02 18:27:04 FhemServer monocle-gateway[412]: ------------------------------------------------- root@FhemServer:~#
bus if i say to Alexa show me Garden, she talk to me the Camera is not respons.
then i start gateway like monocle-gateway and Alexa can connect and show me the livestream
root@FhemServer:~# monocle-gateway ****************************************************************** * __ __ ___ _ _ ___ ___ _ ___ * * | \/ |/ _ \| \| |/ _ \ / __| | | __| * * | |\/| | (_) | .` | (_) | (__| |__| _| * * |_| |_|\___/|_|\_|\___/ \___|____|___| * * * ****************************************************************** ------------------------------------------------- MONOCLE RUNTIME ENVIRONMENT ------------------------------------------------- VERSION = 0.0.4-1 OS/ARCH = linux/arm PROCESS = monocle-gateway (PID=1473) TIMESTAMP = 2019-08-02T16:33:08.865Z ------------------------------------------------- MONOCLE GATEWAY SERVICE (Version: 0.0.4-1) ------------------------------------------------- [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=1482) [RTSP Server Listening] 0.0.0.0:8554 (PROXY) [RTSP Server Started] [Monocle Connected] [RTSP Server Registered] ------------------------------------------------- MONOCLE RTSP SERVICE - INITIALIZED ------------------------------------------------- FQDN = 9dd28fe1-40f2-4459-805d-daa62fdc6ff5.mproxy.io HOST = 192.168.2.172 PORT = 443 ------------------------------------------------- ------------------------------------------------- INITIALIZE RTSP STREAM: Garten ------------------------------------------------- - NAME : Garten - LABEL : PRIMARY - URL : rtsp://192.168.2.102:554/user=admin&password=xxxxxxxx&channel=1&stream=1.sdp - UUID : STREAM:df443cff-97a9-45ac-a21d-9768d4674f63 - SESS : fccfd68e-4f40-491d-9a1f-562fe6e01043 - MODIF : Fri Aug 02 2019 15:46:47 GMT+0200 (GMT+02:00) - TAGS : @hangup,@proxy-tcp ------------------------------------------------- 2019-08-02T16:33:18.238Z [INFO] [RTSP PROXY] REGISTERING STREAM [Garten/PRIMARY]; (STREAM:df443cff-97a9-45ac-a21d-9768d4674f63) 2019-08-02T16:33:18.281Z [DEBUG] <RTSP-PROXY> [REQUEST] --> [REGISTER] rtsp://192.168.2.102:554/user=admin&password=xxxxxxxx&channel=1&stream=1.sdp 2019-08-02T16:33:18.282Z [TRACE] <RTSP-PROXY> [REQUEST] --> [HEADERS] { "cseq": "1", "transport": "reuse_connection=0;preferred_delivery_protocol=interleaved;proxy_url_suffix=STREAM:df443cff-97a9-45ac-a21d-9768d4674f63" } 2019-08-02T16:33:18.289Z [DEBUG] <RTSP-PROXY> [RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined) 2019-08-02T16:33:18.291Z [TRACE] <RTSP-PROXY> [RESPONSE] <-- [HEADERS] { "cseq": "1", "date": "Fri, Aug 02 2019 16:33:18 GMT" } 2019-08-02T16:33:19.711Z [INFO] [192.168.2.50:36324 <B1OArkzXB>] RTSP CLIENT SOCKET CONNECTED 2019-08-02T16:33:19.833Z [INFO] [192.168.2.50:36324 <B1OArkzXB>] RTSP CLIENT ATTACHED TO STREAM: Garten (STREAM:df443cff-97a9-45ac-a21d-9768d4674f63) 2019-08-02T16:33:19.844Z [INFO] [192.168.2.50:36324 <B1OArkzXB>] RTSP ENDPOINT SOCKET CONNECTED {127.0.0.1:8554} 2019-08-02T16:33:19.848Z [DEBUG] [192.168.2.50:36324 <B1OArkzXB>] [CLIENT REQUEST] --> [DESCRIBE] rtsp://9dd28fe1-40f2-4459-805d-daa62fdc6ff5.mproxy.io:443/STREAM:df443cff-97a9-45ac-a21d-9768d4674f63?session=fccfd68e-4f40-491d-9a1f-562fe6e01043 2019-08-02T16:33:19.848Z [TRACE] [192.168.2.50:36324 <B1OArkzXB>] [CLIENT REQUEST] --> [HEADERS] { "accept": "application/sdp", "user-agent": "stagefright/1.2 (Linux;Android 5.1.1)", "cseq": "1" } 2019-08-02T16:33:19.856Z [DEBUG] [192.168.2.50:36324 <B1OArkzXB>] [ENDPOINT REQUEST] --> [DESCRIBE] rtsp://9dd28fe1-40f2-4459-805d-daa62fdc6ff5.mproxy.io:443/STREAM:df443cff-97a9-45ac-a21d-9768d4674f63 2019-08-02T16:33:19.856Z [TRACE] [192.168.2.50:36324 <B1OArkzXB>] [ENDPOINT REQUEST] --> [HEADERS] { "accept": "application/sdp", "user-agent": "stagefright/1.2 (Linux;Android 5.1.1)", "cseq": "1" } 2019-08-02T16:33:19.866Z [DEBUG] [192.168.2.50:36324 <B1OArkzXB>] [ENDPOINT RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined) 2019-08-02T16:33:19.867Z [TRACE] [192.168.2.50:36324 <B1OArkzXB>] [ENDPOINT RESPONSE] <-- [HEADERS] { "cseq": "1", "date": "Fri, Aug 02 2019 16:33:19 GMT", "content-base": "rtsp://127.0.0.1:8554/STREAM:df443cff-97a9-45ac-a21d-9768d4674f63/", "content-type": "application/sdp", "content-length": "632" } 2019-08-02T16:33:19.869Z [TRACE] [192.168.2.50:36324 <B1OArkzXB>] [ENDPOINT RESPONSE] <-- [BODY] v=0 o=- 1564763598275594 1 IN IP4 192.168.2.172 s=LIVE555 Streaming Media v2018.04.25 i=LIVE555 Streaming Media v2018.04.25 t=0 0 a=tool:LIVE555 Streaming Media v2018.04.25 a=type:broadcast a=control:* a=range:npt=0- a=x-qt-text-nam:LIVE555 Streaming Media v2018.04.25 a=x-qt-text-inf:LIVE555 Streaming Media v2018.04.25 m=video 0 RTP/AVP 96 c=IN IP4 0.0.0.0 b=AS:50 a=rtpmap:96 H264/90000 a=fmtp:96 packetization-mode=1;profile-level-id=4D001F;sprop-parameter-sets=J00AH41qCgL/lhAAAAMAEAAAAwHoQA==,KO4JyA== a=control:track1 m=audio 0 RTP/AVP 97 c=IN IP4 0.0.0.0 b=AS:50 a=rtpmap:97 PCMA/8000 a=control:track2 2019-08-02T16:33:19.870Z [INFO] [192.168.2.50:36324 <B1OArkzXB>] RTSP ENDPOINT AUTHENTICATION SUCCESSFUL: NONE 2019-08-02T16:33:19.899Z [DEBUG] [192.168.2.50:36324 <B1OArkzXB>] [CLIENT RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined) 2019-08-02T16:33:19.900Z [TRACE] [192.168.2.50:36324 <B1OArkzXB>] [CLIENT RESPONSE] <-- [HEADERS] { "cseq": "1", "date": "Fri, Aug 02 2019 16:33:19 GMT", "content-base": "rtsp://127.0.0.1:8554/STREAM:df443cff-97a9-45ac-a21d-9768d4674f63/", "content-type": "application/sdp", "content-length": "632" } 2019-08-02T16:33:19.904Z [TRACE] [192.168.2.50:36324 <B1OArkzXB>] [CLIENT RESPONSE] <-- [BODY] v=0 o=- 1564763598275594 1 IN IP4 192.168.2.172 s=LIVE555 Streaming Media v2018.04.25 i=LIVE555 Streaming Media v2018.04.25 t=0 0 a=control:* a=tool:LIVE555 Streaming Media v2018.04.25 a=type:broadcast a=range:npt=0- a=x-qt-text-nam:LIVE555 Streaming Media v2018.04.25 a=x-qt-text-inf:LIVE555 Streaming Media v2018.04.25 m=video 0 RTP/AVP 96 c=IN IP4 0.0.0.0 b=AS:50 a=rtpmap:96 H264/90000 a=fmtp:96 packetization-mode=1;profile-level-id=4D001F;sprop-parameter-sets=J00AH41qCgL/lhAAAAMAEAAAAwHoQA==,KO4JyA== a=control:track1 m=audio 0 RTP/AVP 97 c=IN IP4 0.0.0.0 b=AS:50 a=rtpmap:97 PCMA/8000 a=control:track2 2019-08-02T16:33:19.951Z [DEBUG] [192.168.2.50:36324 <B1OArkzXB>] [CLIENT REQUEST] --> [SETUP] rtsp://127.0.0.1:8554/STREAM:df443cff-97a9-45ac-a21d-9768d4674f63/track1 2019-08-02T16:33:19.952Z [TRACE] [192.168.2.50:36324 <B1OArkzXB>] [CLIENT REQUEST] --> [HEADERS] { "transport": "RTP/AVP/TCP;interleaved=0-1", "user-agent": "stagefright/1.2 (Linux;Android 5.1.1)", "cseq": "2" } 2019-08-02T16:33:19.955Z [DEBUG] [192.168.2.50:36324 <B1OArkzXB>] [ENDPOINT REQUEST] --> [SETUP] rtsp://127.0.0.1:8554/STREAM:df443cff-97a9-45ac-a21d-9768d4674f63/track1 2019-08-02T16:33:19.956Z [TRACE] [192.168.2.50:36324 <B1OArkzXB>] [ENDPOINT REQUEST] --> [HEADERS] { "transport": "RTP/AVP/TCP;interleaved=0-1", "user-agent": "stagefright/1.2 (Linux;Android 5.1.1)", "cseq": "2" } 2019-08-02T16:33:19.999Z [DEBUG] [192.168.2.50:36324 <B1OArkzXB>] [ENDPOINT RESPONSE] <-- [200 (OK)] <cseq=2> (session=50BDBEEF;timeout=65) 2019-08-02T16:33:19.999Z [TRACE] [192.168.2.50:36324 <B1OArkzXB>] [ENDPOINT RESPONSE] <-- [HEADERS] { "cseq": "2", "date": "Fri, Aug 02 2019 16:33:19 GMT", "transport": "RTP/AVP/TCP;unicast;destination=127.0.0.1;source=127.0.0.1;interleaved=0-1", "session": "50BDBEEF;timeout=65" } 2019-08-02T16:33:20.003Z [DEBUG] [192.168.2.50:36324 <B1OArkzXB>] [CLIENT RESPONSE] <-- [200 (OK)] <cseq=2> (session=50BDBEEF;timeout=65) 2019-08-02T16:33:20.004Z [TRACE] [192.168.2.50:36324 <B1OArkzXB>] [CLIENT RESPONSE] <-- [HEADERS] { "cseq": "2", "date": "Fri, Aug 02 2019 16:33:19 GMT", "transport": "RTP/AVP/TCP;unicast;destination=127.0.0.1;source=127.0.0.1;interleaved=0-1", "session": "50BDBEEF;timeout=65" } 2019-08-02T16:33:20.016Z [DEBUG] [192.168.2.50:36324 <B1OArkzXB>] [CLIENT REQUEST] --> [SETUP] rtsp://127.0.0.1:8554/STREAM:df443cff-97a9-45ac-a21d-9768d4674f63/track2 2019-08-02T16:33:20.017Z [TRACE] [192.168.2.50:36324 <B1OArkzXB>] [CLIENT REQUEST] --> [HEADERS] { "transport": "RTP/AVP/TCP;interleaved=2-3", "session": "50BDBEEF", "user-agent": "stagefright/1.2 (Linux;Android 5.1.1)", "cseq": "3" } 2019-08-02T16:33:20.021Z [DEBUG] [192.168.2.50:36324 <B1OArkzXB>] [ENDPOINT REQUEST] --> [SETUP] rtsp://127.0.0.1:8554/STREAM:df443cff-97a9-45ac-a21d-9768d4674f63/track2 2019-08-02T16:33:20.022Z [TRACE] [192.168.2.50:36324 <B1OArkzXB>] [ENDPOINT REQUEST] --> [HEADERS] { "transport": "RTP/AVP/TCP;interleaved=2-3", "session": "50BDBEEF", "user-agent": "stagefright/1.2 (Linux;Android 5.1.1)", "cseq": "3" } 2019-08-02T16:33:20.069Z [DEBUG] [192.168.2.50:36324 <B1OArkzXB>] [ENDPOINT RESPONSE] <-- [200 (OK)] <cseq=3> (session=50BDBEEF;timeout=65) 2019-08-02T16:33:20.069Z [TRACE] [192.168.2.50:36324 <B1OArkzXB>] [ENDPOINT RESPONSE] <-- [HEADERS] { "cseq": "3", "date": "Fri, Aug 02 2019 16:33:20 GMT", "transport": "RTP/AVP/TCP;unicast;destination=127.0.0.1;source=127.0.0.1;interleaved=2-3", "session": "50BDBEEF;timeout=65" } 2019-08-02T16:33:20.072Z [DEBUG] [192.168.2.50:36324 <B1OArkzXB>] [CLIENT RESPONSE] <-- [200 (OK)] <cseq=3> (session=50BDBEEF;timeout=65) 2019-08-02T16:33:20.073Z [TRACE] [192.168.2.50:36324 <B1OArkzXB>] [CLIENT RESPONSE] <-- [HEADERS] { "cseq": "3", "date": "Fri, Aug 02 2019 16:33:20 GMT", "transport": "RTP/AVP/TCP;unicast;destination=127.0.0.1;source=127.0.0.1;interleaved=2-3", "session": "50BDBEEF;timeout=65" } 2019-08-02T16:33:20.119Z [DEBUG] [192.168.2.50:36324 <B1OArkzXB>] [CLIENT REQUEST] --> [PLAY] rtsp://127.0.0.1:8554/STREAM:df443cff-97a9-45ac-a21d-9768d4674f63/ 2019-08-02T16:33:20.119Z [TRACE] [192.168.2.50:36324 <B1OArkzXB>] [CLIENT REQUEST] --> [HEADERS] { "session": "50BDBEEF", "user-agent": "stagefright/1.2 (Linux;Android 5.1.1)", "cseq": "4" } 2019-08-02T16:33:20.122Z [DEBUG] [192.168.2.50:36324 <B1OArkzXB>] [ENDPOINT REQUEST] --> [PLAY] rtsp://127.0.0.1:8554/STREAM:df443cff-97a9-45ac-a21d-9768d4674f63/ 2019-08-02T16:33:20.123Z [TRACE] [192.168.2.50:36324 <B1OArkzXB>] [ENDPOINT REQUEST] --> [HEADERS] { "session": "50BDBEEF", "user-agent": "stagefright/1.2 (Linux;Android 5.1.1)", "cseq": "4" } 2019-08-02T16:33:20.169Z [DEBUG] [192.168.2.50:36324 <B1OArkzXB>] [ENDPOINT RESPONSE] <-- [200 (OK)] <cseq=4> (session=50BDBEEF) 2019-08-02T16:33:20.169Z [TRACE] [192.168.2.50:36324 <B1OArkzXB>] [ENDPOINT RESPONSE] <-- [HEADERS] { "cseq": "4", "date": "Fri, Aug 02 2019 16:33:20 GMT", "range": "npt=0.000-", "session": "50BDBEEF", "rtp-info": "url=rtsp://127.0.0.1:8554/STREAM:df443cff-97a9-45ac-a21d-9768d4674f63/track1;seq=44074;rtptime=2658973960,url=rtsp://127.0.0.1:8554/STREAM:df443cff-97a9-45ac-a21d-9768d4674f63/track2;seq=60311;rtptime=3256570573" } 2019-08-02T16:33:20.173Z [DEBUG] [192.168.2.50:36324 <B1OArkzXB>] [CLIENT RESPONSE] <-- [200 (OK)] <cseq=4> (session=50BDBEEF) 2019-08-02T16:33:20.173Z [TRACE] [192.168.2.50:36324 <B1OArkzXB>] [CLIENT RESPONSE] <-- [HEADERS] { "cseq": "4", "date": "Fri, Aug 02 2019 16:33:20 GMT", "range": "npt=0.000-", "session": "50BDBEEF", "rtp-info": "url=rtsp://127.0.0.1:8554/STREAM:df443cff-97a9-45ac-a21d-9768d4674f63/track1;seq=44074;rtptime=2658973960,url=rtsp://127.0.0.1:8554/STREAM:df443cff-97a9-45ac-a21d-9768d4674f63/track2;seq=60311;rtptime=3256570573" } 2019-08-02T16:33:20.175Z [INFO] [192.168.2.50:36324 <B1OArkzXB>] RTSP ENDPOINT PLAYING MEDIA STREAM: Garten (STREAM:df443cff-97a9-45ac-a21d-9768d4674f63) 2019-08-02T16:33:20.176Z [INFO] [192.168.2.50:36324 <B1OArkzXB>] RTSP CLIENT PLAYING MEDIA STREAM: Garten (STREAM:df443cff-97a9-45ac-a21d-9768d4674f63) ^C2019-08-02T16:34:16.450Z [INFO] [192.168.2.50:36324 <B1OArkzXB>] RTSP ENDPOINT SOCKET CLOSED [192.168.2.50:36324 <B1OArkzXB>] [RTSP Server Stopping] [RTSP Server Stopped] [Monocle Stopping] [Monocle Stopped] [RTSP Proxy Stopped] CODE=0; SIGNAL=SIGINT 2019-08-02T16:34:16.472Z [INFO] [192.168.2.50:36324 <B1OArkzXB>] RTSP CLIENT SOCKET CLOSED 2019-08-02T16:34:16.473Z [INFO] [192.168.2.50:36324 <B1OArkzXB>] RTSP CLIENT DETACHED FROM STREAM: Garten (STREAM:df443cff-97a9-45ac-a21d-9768d4674f63) 2019-08-02T16:34:16.474Z [INFO] [RTSP PROXY] DE-REGISTERING STREAM [Garten/PRIMARY]; NO LONGER IN USE 2019-08-02T16:34:16.481Z [ERROR] Uncaught Exception connect ECONNREFUSED 127.0.0.1:8554 [ 'Uncaught Exception', 'connect ECONNREFUSED 127.0.0.1:8554' ] 2019-08-02T16:34:16.489Z [ERROR] Error: connect ECONNREFUSED 127.0.0.1:8554 [ { Error: connect ECONNREFUSED 127.0.0.1:8554 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1158:14) errno: 'ECONNREFUSED', code: 'ECONNREFUSED', syscall: 'connect', address: '127.0.0.1', port: 8554 } ]
-
@Tueftler said in Unknowed brand IPcam:
monocle-gateway --status
OK, we are no seeing enough data in the “–status” example. Lets do this:
stop your independent instance of “monocle-gateway”.
Lets restart the service/daemon:
monocle-gateway --restart
Now start tailing the log file so you can watch all new log records that come in:
monocle-gateway --tail
Now, ask Alexa to show you the camera stream.
Finally, post the output from the log file from the point where the service was restarted to the end of the camera streaming request/failure.
I want to see the startup part for the daemon/service just in case something is failing immediately on startup.Thanks, Robert