Display posts from previous
Sort by

Re: SAT>IP Protocol support

#17 by evarost
Prog wrote:udp://@:1234 - is not mutlicast. Try restream to unicast or to multicast.
Hi,

First SUCCESS!

FFMPEG Command:

$ ffmpeg.exe -i rtsp://192.168.1.212:554/programID=5266433 -copyts -codec copy -f mpegts "udp://224.0.0.1:1234"

Channel list file (m3u):

#EXTM3U
#EXTINF:0,restreaming
udp://@224.0.0.1:1234

Then I can "scan" and one channel found!

After this trials, I'll try to create your logs of RTSP. Have you reviewed the PDF?

Thank you!
Last edited by evarost on Thu May 29, 2014 7:06 am, edited 1 time in total.

Re: SAT>IP Protocol support

#18 by evarost
Hi Prog,

At time, I'm testing this Linux tool: http://www.live555.com/openRTSP/
I feel that you can be inspired by the source code of this tool to add RTSP support to the IPTV module.

Nevertheless, I'll provide soon the LOGs you request about the calls of the procotol between a client and my STB. I found the debug of the VLC the most verbose and useful to create them (without using a network sniffer, like wireshark).

Regards!

Re: SAT>IP Protocol support

#23 by evarost
Hi Prog,

I have do it already (the vlc log). The relevant data:

Code: Select all

Opening connection to 192.168.111.212, port 554...
...remote connection opened
Sending request: OPTIONS rtsp://192.168.111.212:554/programID=5266433 RTSP/1.0
CSeq: 2
User-Agent: LibVLC/2.1.3 (LIVE555 Streaming Media v2014.01.21)


Received 115 new bytes of response data.
Received a complete OPTIONS response:
RTSP/1.0 200 OK
CSeq: 2
Date: Thu, May 29 2014 13:43:06 GMT
Public: OPTIONS, DESCRIBE, SETUP, TEARDOWN, PLAY


Sending request: DESCRIBE rtsp://192.168.111.212:554/programID=5266433 RTSP/1.0
CSeq: 3
User-Agent: LibVLC/2.1.3 (LIVE555 Streaming Media v2014.01.21)
Accept: application/sdp


Received 378 new bytes of response data.
Received a complete DESCRIBE response:
RTSP/1.0 200 OK
CSeq: 3
Date: Thu, May 29 2014 13:43:06 GMT
Content-Base: rtsp://192.168.111.212/
Content-Type: application/sdp
Content-Length: 222

v=0
o=- 1401370232067000 1 IN IP4 192.168.111.212
s=SatIPServer:1 1
t=0 0
a=control:rtsp://192.168.111.212/programID=5266433
m=video 0 RTP/AVP 33
c=IN IP4 0.0.0.0
a=control:rtsp://192.168.111.212/programID=5266433

Sending request: SETUP rtsp://192.168.111.212/programID=5266433 RTSP/1.0
CSeq: 4
User-Agent: LibVLC/2.1.3 (LIVE555 Streaming Media v2014.01.21)
Transport: RTP/AVP;unicast;client_port=53820-53821


Received 220 new bytes of response data.
Received a complete SETUP response:
RTSP/1.0 200 OK
CSeq: 4
Date: Thu, May 29 2014 13:43:06 GMT
Transport: RTP/AVP;unicast;destination=192.168.111.102;source=192.168.111.212;client_port=53820-53821;server_port=6970-6971
Session: 0F5511ED;timeout=60


Sending request: PLAY rtsp://192.168.111.212/programID=5266433 RTSP/1.0
CSeq: 5
User-Agent: LibVLC/2.1.3 (LIVE555 Streaming Media v2014.01.21)
Session: 0F5511ED
Range: npt=0.000-


Received 140 new bytes of response data.
Received a complete PLAY response:
RTSP/1.0 200 OK
CSeq: 5
Date: Thu, May 29 2014 13:43:06 GMT
Session: 0F5511ED
RTP-Info: url=rtsp://192.168.111.212/programID=5266433
Client: 192.168.111.102
Sat>IP server: 192.168.111.212

It's good for you? :wink:
Last edited by evarost on Sun Jun 08, 2014 8:35 am, edited 1 time in total.

Re: SAT>IP Protocol support

#24 by evarost
Hi,

Good news! Using "manual" commands I can view some channels using ProgDVB from my SAT>IP tuner.

In a Linux machine I use openRTSP and socat to send a multicast stream with the Transport Stream filtered for the channel. An example of the command:

openRTSP -v rtsp://192.168.1.212:554/programID=5272581 | socat - udp:224.0.0.1:5000

In the IPTV Module, you can import a m3u file with udp://@224.0.0.1:5000 and execute the scan (parsing SDT).

This isn't a final solution, pure manual commands, but is a good start.

For Prog: If you like to obtain more RTSP logs, the best option is use "openRTSP". It's using the same LIB as VLC, and with identical log outputs. And is more easy to use! :shock:

If you need more logs, please contact with me.

Re: SAT>IP Protocol support

#26 by evarost
Prog wrote:RTSP is not ease and not quick. I must spend some time for that in future. Your log is good but testing for the device can be demanded. Is it vpn possible?
I can provide to you more logs, captures (raw TS from the SAT>IP server), and I can do more tests as you request. VPN isn't available (I don't have a permanent upload link, sorry).

Perhaps you like to buy a device (50 Euros only!): http://www.amazon.de/Smart-Satelliten-R ... 196&sr=1-3

In reference to the RTSP implementation:

- From my point of view, the best solution is an architecture of 2 processes: the "selector" and the "sink". The "sink" process is very similar to an RTP UDP unicast receiver. And the "selector" process is a separate task that asynchronously is generating the calls of the RTSP control protocol. With parallel execution of both tasks and the decoupling of them, the implementation will be more simple.

Regards.