5.3.1 - July 16, 2020 Your Blue Iris web server now is also an RTSP server.

Is there a limit on how many can be accessing the RTSP feed at once? Wondering if I can put up a live feed of a came on our reader board and numerous people can be watching it at once?

And is there a way to have it not ask for login?
 
Hello,

I heard of that RTSP output stream out of blueiris. CHecked with vlc and it works fine.

my problem is my GIRA doorring only accepts stream with the profile RTSP BASELINE and max 640x480. My DOorcamera doesnt support that profile. Is it possible to use that output stream with special profile settings?

and if yes, can you tell me what I have to do?
 
Hi guys!
I installed an nvidia Jetson Nano as a client viewer for BlueIris, connecting 8 rtsp streams directly from BlueIris. Everything has been working very well for several months, but I have noticed that when I turn on the Jetson Nano, the i7 cpu of my BlueIris goes from 18% to 70%. I have checked and each camera is set to "Intel" and therefore uses QuickSync very well.

How come for the stream rtsp does not use the GPU, but uses the CPU? some idea? thank you!!
 
Gosh I feel like such a noob. I had this working long ago albeit only half my cameras worked on the echo show because I connected them directly so I lost the appetite to continue using this but I am back at it again. However, I am unable to get any method described here to work. My echo show realizes there is a camera, tries to connect to it and then silently goes back to the home screen.

The URL I am using in MONOCLE from BI is: rtsp:/BI-IP:BI-PORT/CAMERA SHORT NAME

I have tried basic / Digest / None authentication with no luck.

Are there any settings in BI that I need to change?
I am running BI version 5.3.1.6 x64

Any suggestions?
 
BrewFixer said:
Gosh I feel like such a noob. I had this working long ago albeit only half my cameras worked on the echo show because I connected them directly so I lost the appetite to continue using this but I am back at it again. However, I am unable to get any method described here to work. My echo show realizes there is a camera, tries to connect to it and then silently goes back to the home screen.

The URL I am using in MONOCLE from BI is: rtsp:/BI-IP:BI-PORT/CAMERA SHORT NAME

I have tried basic / Digest / None authentication with no luck.

Are there any settings in BI that I need to change?
I am running BI version 5.3.1.6 x64

Any suggestions?
Click to expand...

Yeah, the BI > Monocle > Alexa > Show can be a challenge. Lots of things in play.

First, test your connection string in VLC or something similar. Unless you can get the stream there, then you won't get anything beyond to work. The string convention that you're using works fine for mine. Should for yours too.

Set up the device on the Monocle site as you'd access the cam using the same string and credentials. I use Digest for mine. Try adding @noaudio, @tunnel to tags. Wait a few minutes for things to flow through after adding/changing.

Do discovery on the Alexa app or the Show. Make sure that it finds the device. It should report that it's found a new device and show it in the device list.

IF everything is right, it should work then when you say "Alexa, show [cam name]."

If not, check the log file that's in the same folder as Monocle. Look for any errors there. If it's long, maybe delete it, then try again to call the cam so you're not dealing with so much there. Post here if you want and I'll take a look.

Also note that the Show 5 is limited to only 1080 streams. Anything larger and it will do as you describe. I don't recall making any changes in BI. Generally, I just pull directly from the cams. I did test a few tonight to make sure that it worked from BI.
 
Last edited:
Mike A. said:
Yeah, the BI > Monocle > Alexa > Show can be a challenge. Lots of things in play.

First, test your connection string in VLC or something similar. Unless you can get the stream there, then you won't get anything beyond to work. The string convention that you're using works fine for mine. Should for yours too.

Set up the device on the Monocle site as you'd access the cam using the same string and credentials. I use Digest for mine. Try adding @noaudio, @tunnel to tags. Wait a few minutes for things to flow through after adding/changing.

Do discovery on the Alexa app or the Show. Make sure that it finds the device. It should report that it's found a new device and show it in the device list.

IF everything is right, it should work then when you say "Alexa, show [cam name]."

If not, check the log file that's in the same folder as Monocle. Look for any errors there. If it's long, maybe delete it, then try again to call the cam so you're not dealing with so much there. Post here if you want and I'll take a look.

Also note that the Show 5 is limited to only 1080 streams. Anything larger and it will do as you describe. I don't recall making any changes in BI. Generally, I just pull directly from the cams. I did test a few tonight to make sure that it worked from BI.
Click to expand...
Thanks Mike,
So everything flows through just fine in VLC. I switched to Digest and tried the couple of tags you suggested. If I use @noaudio, I get the same behavior as before I.E. Show will acknowledge it is trying to connect the camera in this case my Driveway cam and shows a message "Waiting for Driveway" with the 3 progress dots above but then it will silently go back to the home screen.
If I use the tag @tunnel, then it just tells me it can not find the device.

Just curious if my BI needs to be updated.. There have been a few updates since I installed about a year ago but I let my support run out and I am a few versions behind.

By the way... I can not find the log file you mentioned. Would these be on my PC, SERVER, Etc.. Or is it on the Monocle site? Also curious if I need to run the MONOCLE GATEWAY service on my server? It said technically it is for Foscam, ReoLink, D-Link or Sricam camera but, none of mine are any of these.

Thanks again
 
Last edited:
Ahhh... Yes, you do need to run the gateway now after some security changes on Amazon's side a while back. That may be why it was working and doesn't now. Also why you don't see the log file. That should be in the same folder where the gateway is installed on the server.

Try that first.
 
  • Like
Reactions: looney2ns
Mike A. said:
Ahhh... Yes, you do need to run the gateway now after some security changes on Amazon's side a while back. That may be why it was working and doesn't now. Also why you don't see the log file. That should be in the same folder where the gateway is installed on the server.

Try that first.
Click to expand...
Yes this can drive me to drink... Installed and started Monocle gateway service, forward TCP port 443 on local server and GATEWAY Firewall. Still not finding a log when I attempt to show a camera. Used several different tags and now the only one that does not throw the Device not found on the echo show is the @noaudio.

Based on the service below, do I also need to open tcp port 8555?

-------------------------------------------------
VERSION = 0.0.4
OS/ARCH = win32\x64
PROCESS = monocle-gateway (PID=8492)
TIMESTAMP = 2022-02-18T02:02:50.864Z

-------------------------------------------------
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=8584)
[RTSP Server Listening] 0.0.0.0:8554 (PROXY)
[RTSP Server Started]
[RTSP Proxy Stopped] CODE=3221225781; SIGNAL=null
[Monocle Connected]
[RTSP Server Registered]

-------------------------------------------------
MONOCLE RTSP SERVICE - INITIALIZED
-------------------------------------------------
FQDN = 76ab94fa-7f14-4019-bc25-78dbac59669b.mproxy.io
HOST = 192.168.1.5
PORT = 443
-------------------------------------------------
 
All of that looks good. I don't recall ever having to do anything with port 8555 but not sure how you're set up there. Try it.

The log should be there. Same folder as Monocle as monocle.log.
 
Mike A. said:
All of that looks good. I don't recall ever having to do anything with port 8555 but not sure how you're set up there. Try it.

The log should be there. Same folder as Monocle as monocle.log.
Click to expand...
Yeah I looked again tonight and no log. However, on the Monocle website, there is this info which I can see the 3 attempts I tried to connect to the camera
[
{
"timestamp": "2022-02-19T03:17:18.695Z",
"request": "InitializeCameraStreams",
"response": [
{
"uri": "rtsp:/%USER%:%PWD%@192.168.1.5/DRVWY",
"proxy": "rtsp:/proxy.monoclecam.com:443/98c51c0e-d5bf-4b49-8342-7597859a788c",
"resolution": {
"width": "1920",
"height": "1080"
},
"authorizationType": "DIGEST",
"videoCodec": "H264",
"audioCodec": "AAC",
"protocol": "RTSP"
}
]
},
{
"timestamp": "2022-02-19T03:15:38.942Z",
"request": "InitializeCameraStreams",
"response": [
{
"uri": "rtsp:/%USER%:%PWD%@192.168.1.5/DRVWY",
"proxy": "rtsp:/proxy.monoclecam.com:443/8b291c5d-c43a-4c59-bd79-efc08ae5a3c8",
"resolution": {
"width": "1920",
"height": "1080"
},
"authorizationType": "DIGEST",
"videoCodec": "H264",
"audioCodec": "AAC",
"protocol": "RTSP"
}
]
},
{
"timestamp": "2022-02-19T03:14:08.914Z",
"request": "InitializeCameraStreams",
"response": [
{
"uri": "rtsp:/%USER%:%PWD%@192.168.1.5/DRVWY",
"proxy": "rtsp:/proxy.monoclecam.com:443/0205666c-5fc5-446b-9c91-b10054c6c4b4",
"resolution": {
"width": "1920",
"height": "1080"
},
"authorizationType": "DIGEST",
"videoCodec": "H264",
"audioCodec": "AAC",
"protocol": "RTSP"
}
]
}
]


1645237208576.png
 
Last edited:
That's odd. I've helped a bunch of people with Monocle and never seen one that didn't have the log. Usually there are several with .log extensions. That's unfortunate since it shows all of the steps connecting and any errors and that's the best way to see what's happening. The above from Monocle's side doesn't show the results of the calls and all the rest.

In that folder under View, check that you have hidden items and extensions checked to show. Also, normally it's in a Monocle Gateway folder vs Monocle. Check that your don't have another folder. Maybe delete that one and reinstall.

This is what the log file looks like making a successful connection to a cam and Show;

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


-------------------------------------------------
MONOCLE RUNTIME ENVIRONMENT
-------------------------------------------------
VERSION = 0.0.4
OS/ARCH = win32\x64
PROCESS = monocle-gateway (PID=10016)
TIMESTAMP = 2022-02-09T04:32:48.078Z

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

-------------------------------------------------
MONOCLE RTSP SERVICE - INITIALIZED
-------------------------------------------------
FQDN = 0e8222e2-ad54-4d29-8992-a96fxxxxxx.mproxy.io
HOST = 192.168.2.4
PORT = 443
-------------------------------------------------

-------------------------------------------------
INITIALIZE RTSP STREAM: Front Door
-------------------------------------------------
  • NAME : Front Door
  • LABEL : PRIMARY
  • URL : rtsp:/192.168.2.18:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif
  • UUID : STREAM:92687794-aa5c-4430-af83-8a25cxxxxx
  • SESS : 9dbe6f9f-d9f8-47ae-a001-e5a2f5x3xxxx
  • MODIF : Fri Nov 26 2021 01:25:56 GMT-0500 (Eastern Standard Time)
  • TAGS : @tunnel
-------------------------------------------------

2022-02-09T15:46:46.458Z [INFO] [192.168.2.98:35964 <r1CJfDb1c>] RTSP CLIENT SOCKET CONNECTED
2022-02-09T15:46:46.588Z [INFO] [192.168.2.98:35964 <r1CJfDb1c>] RTSP CLIENT ATTACHED TO STREAM: Front Door (STREAM:92687794-aa5c-4430-af83-8a25c96f867c)
2022-02-09T15:46:46.590Z [INFO] [192.168.2.98:35964 <r1CJfDb1c>] RTSP ENDPOINT SOCKET CONNECTED {192.168.2.18:554}
2022-02-09T15:46:46.592Z [DEBUG] [192.168.2.98:35964 <r1CJfDb1c>] [CLIENT REQUEST] --> [DESCRIBE] rtsp:/0e8222e2-ad54-4d29-8992-a96fdxxxxx5.mproxy.io:443/STREAM:92687794-aa5c-4430-af83-8a25c9xxxxc?session=9dbe6f9xxxxx8-47ae-a001-e5a2f5388xxxxxxxx-02-09T15:46:46.593Z [TRACE] [192.168.2.98:35964 <r1CJfDb1c>] [CLIENT REQUEST] --> [HEADERS] {
"accept": "application/sdp",
"user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
"cseq": "1"
}
2022-02-09T15:46:46.595Z [DEBUG] [192.168.2.98:35964 <r1CJfDb1c>] [ENDPOINT REQUEST] --> [DESCRIBE] rtsp:/192.168.2.18:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif
2022-02-09T15:46:46.596Z [TRACE] [192.168.2.98:35964 <r1CJfDb1c>] [ENDPOINT REQUEST] --> [HEADERS] {
"accept": "application/sdp",
"user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
"cseq": "1"
}
2022-02-09T15:46:46.665Z [DEBUG] [192.168.2.98:35964 <r1CJfDb1c>] [ENDPOINT RESPONSE] <-- [401 (Unauthorized)] <cseq=1> (session=undefined)
2022-02-09T15:46:46.665Z [TRACE] [192.168.2.98:35964 <r1CJfDb1c>] [ENDPOINT RESPONSE] <-- [HEADERS] {
"cseq": "1",
"www-authenticate": "Digest realm=\"Login to 7A0109CPAG84BB1\", nonce=\"9fe5c59bc6500c6a6a58e54xxxxxx2a\""
}
2022-02-09T15:46:46.665Z [INFO] [192.168.2.98:35964 <r1CJfDb1c>] RTSP ENDPOINT REQUIRES AUTHENTICATION: Digest realm="Login to 7A0109CPAG84BB1", nonce="9fe5c59bc6500c6a6a58e5xxxxxxx"
2022-02-09T15:46:46.667Z [INFO] [192.168.2.98:35964 <r1CJfDb1c>] RTSP ENDPOINT ATTEMPTING AUTHENTICATION: DIGEST
2022-02-09T15:46:46.667Z [DEBUG] [192.168.2.98:35964 <r1CJfDb1c>] [ENDPOINT REQUEST] --> [DESCRIBE] rtsp:/192.168.2.18:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif
2022-02-09T15:46:46.667Z [TRACE] [192.168.2.98:35964 <r1CJfDb1c>] [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=\"Login to 7A0109CPAxxxxxx\", nonce=\"9fe5c59bc6500c6a6a58e548fxxxxxxx\", uri=\"rtsp:/192.168.2.18:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif\", response=\"b695ac5402df8f0b7d72xxxxxxxxxx\""
}
2022-02-09T15:46:46.722Z [DEBUG] [192.168.2.98:35964 <r1CJfDb1c>] [ENDPOINT RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined)
2022-02-09T15:46:46.722Z [TRACE] [192.168.2.98:35964 <r1CJfDb1c>] [ENDPOINT RESPONSE] <-- [HEADERS] {
"cseq": "1",
"x-accept-dynamic-rate": "1",
"content-base": "rtsp:/192.168.2.18:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif/",
"cache-control": "must-revalidate",
"content-length": "611",
"content-type": "application/sdp"
}
2022-02-09T15:46:46.722Z [TRACE] [192.168.2.98:35964 <r1CJfDb1c>] [ENDPOINT RESPONSE] <-- [BODY]
v=0
o=- 2252360199 2252360199 IN IP4 0.0.0.0
s=Media Server
c=IN IP4 0.0.0.0
t=0 0
a=control:*
a=packetization-supported:DH
a=rtppayload-supported:DH
a=range:npt=now-
m=video 0 RTP/AVP 96
a=control:trackID=0
a=framerate:15.000000
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1;profile-level-id=640028;sprop-parameter-sets=Z2QAKKwbGoB4AiflwFuAgICgAAB9AAAOph0MAH0AAAMC+vBd5caGAD6AAAF9eC7y4UAA,aO44MAA=
a=recvonly
m=audio 0 RTP/AVP 8
a=control:trackID=1
a=rtpmap:8 PCMA/16000
a=recvonly
m=application 0 RTP/AVP 107
a=control:trackID=4
a=rtpmap:107 vnd.onvif.metadata/90000
a=recvonly

2022-02-09T15:46:46.722Z [INFO] [192.168.2.98:35964 <r1CJfDb1c>] RTSP ENDPOINT AUTHENTICATION SUCCESSFUL: DIGEST
2022-02-09T15:46:46.726Z [INFO] [192.168.2.98:35964 <r1CJfDb1c>] RTSP ENDPOINT SDP REMOVED AUDIO CHANNEL: [PORT=0; PROTOCOL=RTP/AVP; PAYLOADS=8]
2022-02-09T15:46:46.730Z [DEBUG] [192.168.2.98:35964 <r1CJfDb1c>] [CLIENT RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined)
2022-02-09T15:46:46.730Z [TRACE] [192.168.2.98:35964 <r1CJfDb1c>] [CLIENT RESPONSE] <-- [HEADERS] {
"cseq": "1",
"x-accept-dynamic-rate": "1",
"content-base": "rtsp:/192.168.2.18:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif/",
"cache-control": "must-revalidate",
"content-length": "534",
"content-type": "application/sdp"
}
2022-02-09T15:46:46.730Z [TRACE] [192.168.2.98:35964 <r1CJfDb1c>] [CLIENT RESPONSE] <-- [BODY]
v=0
o=- 2252360199 2252360199 IN IP4 0.0.0.0
s=Media Server
c=IN IP4 0.0.0.0
t=0 0
a=control:*
a=packetization-supported:DH
a=rtppayload-supported:DH
a=range:npt=now-
m=video 0 RTP/AVP 96
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1;profile-level-id=640028;sprop-parameter-sets=Z2QAKKwbGoB4AiflwFuAgICgAAB9AAAOph0MAH0AAAMC+vBd5caGAD6AAAF9eC7y4UAA,aO44MAA=
a=control:trackID=0
a=recvonly
a=framerate:15.000000
m=application 0 RTP/AVP 107
a=rtpmap:107 vnd.onvif.metadata/90000
a=control:trackID=4
a=recvonly

2022-02-09T15:46:46.762Z [DEBUG] [192.168.2.98:35964 <r1CJfDb1c>] [CLIENT REQUEST] --> [SETUP] rtsp:/192.168.2.18:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif/trackID=0
2022-02-09T15:46:46.762Z [TRACE] [192.168.2.98:35964 <r1CJfDb1c>] [CLIENT REQUEST] --> [HEADERS] {
"transport": "RTP/AVP/TCP;interleaved=0-1",
"user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
"cseq": "2"
}
2022-02-09T15:46:46.763Z [DEBUG] [192.168.2.98:35964 <r1CJfDb1c>] [ENDPOINT REQUEST] --> [SETUP] rtsp:/192.168.2.18:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif/trackID=0
2022-02-09T15:46:46.763Z [TRACE] [192.168.2.98:35964 <r1CJfDb1c>] [ENDPOINT REQUEST] --> [HEADERS] {
"transport": "RTP/AVP/TCP;interleaved=0-1",
"user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
"cseq": "2",
"authorization": "Digest username=\"admin\", realm=\"Login to 7A0109CPAG84BB1\", nonce=\"9fe5c59bc6500c6a6a58e548f8xxxxxxx\", uri=\"rtsp:/192.168.2.18:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif\", response=\"b695ac5402df8f0b7d72xxxxxxxxxx\""
}
2022-02-09T15:46:46.785Z [DEBUG] [192.168.2.98:35964 <r1CJfDb1c>] [ENDPOINT RESPONSE] <-- [200 (OK)] <cseq=2> (session=462584660692;timeout=60)
2022-02-09T15:46:46.786Z [TRACE] [192.168.2.98:35964 <r1CJfDb1c>] [ENDPOINT RESPONSE] <-- [HEADERS] {
"cseq": "2",
"session": "462584660692;timeout=60",
"transport": "RTP/AVP/TCP;unicast;interleaved=0-1;ssrc=2A01D2F0",
"x-dynamic-rate": "1"
}
2022-02-09T15:46:46.786Z [DEBUG] [192.168.2.98:35964 <r1CJfDb1c>] [CLIENT RESPONSE] <-- [200 (OK)] <cseq=2> (session=462584660692;timeout=60)
2022-02-09T15:46:46.786Z [TRACE] [192.168.2.98:35964 <r1CJfDb1c>] [CLIENT RESPONSE] <-- [HEADERS] {
"cseq": "2",
"session": "462584660692;timeout=60",
"transport": "RTP/AVP/TCP;unicast;interleaved=0-1;ssrc=2A01D2F0",
"x-dynamic-rate": "1"
}
2022-02-09T15:46:46.845Z [DEBUG] [192.168.2.98:35964 <r1CJfDb1c>] [CLIENT REQUEST] --> [PLAY] rtsp:/192.168.2.18:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif/
2022-02-09T15:46:46.846Z [TRACE] [192.168.2.98:35964 <r1CJfDb1c>] [CLIENT REQUEST] --> [HEADERS] {
"session": "462584660692",
"user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
"cseq": "3"
}
2022-02-09T15:46:46.846Z [DEBUG] [192.168.2.98:35964 <r1CJfDb1c>] [ENDPOINT REQUEST] --> [PLAY] rtsp:/192.168.2.18:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif/
2022-02-09T15:46:46.846Z [TRACE] [192.168.2.98:35964 <r1CJfDb1c>] [ENDPOINT REQUEST] --> [HEADERS] {
"session": "462584660692",
"user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
"cseq": "3",
"authorization": "Digest username=\"admin\", realm=\"Login to 7A0109CPAG84BB1\", nonce=\"9fe5c59bc6500c6a6a58e5xxxxxx\", uri=\"rtsp:/192.168.2.18:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif\", response=\"b695ac5402df8f0b7d72xxxxxxxxxx\""
}
2022-02-09T15:46:46.970Z [DEBUG] [192.168.2.98:35964 <r1CJfDb1c>] [ENDPOINT RESPONSE] <-- [200 (OK)] <cseq=3> (session=462584660692)
2022-02-09T15:46:46.970Z [TRACE] [192.168.2.98:35964 <r1CJfDb1c>] [ENDPOINT RESPONSE] <-- [HEADERS] {
"cseq": "3",
"session": "462584660692",
"rtp-info": "url=trackID=0;seq=49201;rtptime=3650286600"
}
2022-02-09T15:46:46.971Z [DEBUG] [192.168.2.98:35964 <r1CJfDb1c>] [CLIENT RESPONSE] <-- [200 (OK)] <cseq=3> (session=462584660692)
2022-02-09T15:46:46.971Z [TRACE] [192.168.2.98:35964 <r1CJfDb1c>] [CLIENT RESPONSE] <-- [HEADERS] {
"cseq": "3",
"session": "462584660692",
"rtp-info": "url=trackID=0;seq=49201;rtptime=3650286600"
}
2022-02-09T15:46:46.972Z [INFO] [192.168.2.98:35964 <r1CJfDb1c>] RTSP ENDPOINT PLAYING MEDIA STREAM: Front Door (STREAM:92687794-aa5c-4430-af83-8a2xxxxx)
2022-02-09T15:46:46.972Z [INFO] [192.168.2.98:35964 <r1CJfDb1c>] RTSP CLIENT PLAYING MEDIA STREAM: Front Door (STREAM:92687794-aa5c-4430-af83-8axxxxxxxxx)
Click to expand...
 
Last edited:
I just stumbled upon this. Great hidden feature! I have it working in VLC right now. I may attempt to stream it to YouTube to work around a problem I'm having whereby ffmpeg's composition of 2 streams into a side-by-side 2-up view stopped working for reasons unknown.
 
You must log in or register to reply here.
Top Bottom