Problems with authentication RTSP if the address has an ampersand (&) in address

rtevyncke rtevyncke at gmail.com
Wed Nov 4 05:34:42 UTC 2020


If I run gstreamer with this;

gst-launch-1.0 playbin
uri=rtsp://test:test1@192.168.0.50:554/cam/play=1&subtype=0

or

gst-launch-1.0 rtspsrc
location=rtsp://test:test1@192.168.0.50:554/cam/play=1&subtype=0

It will authenticate ok, but fail as the address sent (monitoring network
with Wireshark) is 

rtsp://test:test1@192.168.0.50:554/cam/play=1

If I run gstreamer with this;

gst-launch-1.0 playbin
uri="rtsp://test:test1@192.168.0.50:554/cam/realmonitor?play=1&subtype=0"

or

gst-launch-1.0 rtspsrc
location="rtsp://test:test1@192.168.0.50:554/cam/realmonitor?play=1&subtype=0"

Then it hangs at the authentication line (Progress: (open) Retrieving server
options) as the rtsp server does not respond.

If run with same rtsp information in ffmpeg, it streams ok. Here is the cli;

ffmpeg -rtsp_transport tcp -i
"rtsp://test:test1@192.168.0.50:554/cam/realmonitor?play=1&subtype=0" -f
image2 -vf fps=fps=1 hello/img%3d.png


Different I see is that at authentication gstreamer sends a lot of
miscellaneous information which may be causing issue because of the
ampersand; Below is the information not found in ffmpeg

User-Agent: RealMedia Player Version 6.0.9.1235
(linux-2.0-libc6-i386-gcc2.95)
ClientChallenge: 9e26d33f2984236010ef6253fb1887f7
CompanyID: sfdgsdfgsfdgsgfsgdf
GUID: 00000000-0000-0000-0000-000000000000
RegionData: 0
PlayerStarttime: [28/03/2003:22:50:23 00:00]
ClientID: Linux_2.4_6.0.9.1235_play32_RN01_EN_586
User-Agent: RealMedia Player Version 6.0.9.1235
(linux-2.0-libc6-i386-gcc2.95)
ClientChallenge: 9e26d33f2984236010ef6253fb1887f7
CompanyID: sfdgsdfgsfdgsgfsgdf
GUID: 00000000-0000-0000-0000-000000000000
RegionData: 0
PlayerStarttime: [28/03/2003:22:50:23 00:00]
ClientID: Linux_2.4_6.0.9.1235_play32_RN01_EN_586


NOTE : If there is no ampersand, then this part works ok in gstreamer.

There is no other difference in Wireshark monitoring between ffmpeg and
gstreamer communications and the OPTIONS, AUTHENTICATION strings are all the
same.

Any help ??



--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/


More information about the gstreamer-devel mailing list