Works like a charm - thanks.
Markus.
From: live-devel-boun...@ns.live555.com
[mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson
Sent: Monday, January 21, 2013 2:22 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] stream descriptor only reach
> Do I have to use a lightweight HTTP client to get the SDP and then side load
> your RTPClient with the string?
However you get the SDP description is up to you. (However, since you already
have it - because you included it in your last email - you shouldn't need to
get it again :-)
Once you
: live-devel-boun...@ns.live555.com
[mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson
Sent: Thursday, January 17, 2013 6:37 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] stream descriptor only reachable by HTTP
I have an RTP source where
> I have an RTP source where it’s stream descriptor is only available via HTTP
> – any advice on how to go about it?
[...]
> Browser output:
>
> v=0
> o=- 8161451 8161451 IN IP4 10.0.70.25
> s=ESP H264 STREAM
> e=NONE
> t=0 0
> m=video 8800 RTP/AVP 96
> c=IN IP4 10.0.71.24
> a=rtpmap:96 H264/900
All,
I have an RTP source where it's stream descriptor is only available via HTTP -
any advice on how to go about it?
Thanks
Markus.
URL: http://10.0.70.25/stream.sdp
Browser output:
v=0
o=- 8161451 8161451 IN IP4 10.0.70.25
s=ESP H264 STREAM
e=NONE
t=0 0
m=video 8800 RTP/AVP 96
c=IN IP4 10