Unfortunately, the RTSP server that I am implementing is for an IP
Camera that should support PSIA conformance client. PSIA requires
handling of fully qualified path in URL
You have things backwards. Just because a client is required to
handle such "rtsp://" URLs (with "/" characters in the '
Unfortunately, the RTSP server that I am implementing is for an IP Camera that
should support PSIA conformance client. PSIA requires handling of fully
qualified path in URL. I changed parseRTSPRequestString() in RTSPCommon.cpp to
support the fully qualified path.
To minimize the change, I am c
You shouldn't worry about the server returning "a=control:track1" in
the SDP description, and thus having "/track1" appended to the
control URL that RTSP clients use internally, when sending a RTSP
"SETUP" command. RTSP clients do this automatically, and it doesn't
affect the URL that you give
It seems to me the ParseRTSPRequestString() only handles one specific RTSP URI
format and does not handle the generic allowed format. According to RFC2326
syntax and semantics for RTSP URLs is:
rtsp_URL = ( "rtsp:" | "rtspu:" )
"//" host [ ":" port ] [ abs_path ]
host
