After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 613591 - rtspsrc doesn't parse negative port numbers
rtspsrc doesn't parse negative port numbers
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
0.10.x
Other Linux
: Normal normal
: 0.10.29
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-03-22 13:44 UTC by Tibor Kocsis
Modified: 2010-03-24 11:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tibor Kocsis 2010-03-22 13:44:49 UTC
Hi,

we have an Arecont IP camera, and try to watch live view on rtp. But when I trying to connect to the camera, the rtspsrc says:

rtspsrc gstrtspsrc.c:4468:gst_rtspsrc_setup_streams:<rtspsrc0> failed
to parse transport
RTP/AVP;unicast;client_port=-18206--18205;server_port=6970-6971

I think the problematic parts are the negative port numbers, it's maybe incorrect, but with mplayer it works fine and i can view live pictures.

Is it an rtspsrc bug?

Regards
Tibor
Comment 1 Wim Taymans 2010-03-22 14:05:31 UTC
(In reply to comment #0)
> I think the problematic parts are the negative port numbers, it's maybe
> incorrect, but with mplayer it works fine and i can view live pictures.
> 
> Is it an rtspsrc bug?

Probably not a bug but it would be good if rtspsrc  could handle wrong input better.
Comment 2 Wim Taymans 2010-03-24 10:35:18 UTC
Can you attach the output of the following line?

 gst-launch rtspsrc debug=1 location=rtsp://....

I think it is the server that echoes the client_port pair with a signedness error.
Comment 3 Wim Taymans 2010-03-24 11:13:05 UTC
commit 4ff230e71bfb08790aaf49f71e57e1ef1205464b
Author: Wim Taymans <wim.taymans@collabora.co.uk>
Date:   Wed Mar 24 12:10:38 2010 +0100

    rtsptransport: ignore unparsable ranges
    
    Ignore unparsable port ranges instead of erroring out.
    
    Fixes #613591