[MP1.11 TV Server] Can't scan Fritz! DVB-C Wlan Repeater M3U (1 Viewer)

Status
Not open for further replies.

Nervesagent

Portal Pro
February 26, 2014
150
19
40
Home Country
Denmark Denmark
[SOLVED!] Read the thread or PM if you need help!

Hi I'm having a problem scanning the rtsp channels from my Fritz! dvb-c network tuner.
Tried working around the problem with Vodserver but
I was advised to create a new thread and post logs.. because the streams could be compatible with MP
(here's the old ref:
https://forum.team-mediaportal.com/...ams-as-tv-channels.121732/page-7#post-1136186)

Extra info required? Please ask!
Thank you!
edit: here's the m3u
#EXTM3U
#EXTINF:-1,Regio TV Utrecht
#EXTVLCOPT:network-caching=1000
rtsp://192.168.1.65:554/?freq=162&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,4100,2001,2010,2101
#EXTINF:-1,TV Rijnmond
#EXTVLCOPT:network-caching=1000
rtsp://192.168.1.65:554/?freq=162&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,4400,2301,2310,2401
#EXTINF:-1,Omroep Flevoland
#EXTVLCOPT:network-caching=1000
rtsp://192.168.1.65:554/?freq=162&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,4700,2601,2610,2701
#EXTINF:-1,L1TV
#EXTVLCOPT:network-caching=1000
rtsp://192.168.1.65:554/?freq=162&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,5000,2901,2910,3001
#EXTINF:-1,Omroep Brabant
#EXTVLCOPT:network-caching=1000
rtsp://192.168.1.65:554/?freq=162&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,5300,3201,3210,3301
#EXTINF:-1,TV Gelderland
#EXTVLCOPT:network-caching=1000
rtsp://192.168.1.65:554/?freq=162&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,5600,3501,3510,3601
#EXTINF:-1,AT5
#EXTVLCOPT:network-caching=1000
rtsp://192.168.1.65:554/?freq=162&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,5900,3801,3810,3901
#EXTINF:-1,Regio TV Utrecht
#EXTVLCOPT:network-caching=1000
rtsp://192.168.1.65:554/?freq=162&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,2000,2001,2010,2101
#EXTINF:-1,TV Rijnmond
#EXTVLCOPT:network-caching=1000
rtsp://192.168.1.65:554/?freq=162&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,2300,2301,2310,2401
#EXTINF:-1,Omroep Flevoland
#EXTVLCOPT:network-caching=1000
rtsp://192.168.1.65:554/?freq=162&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,2600,2601,2610,2701
#EXTINF:-1,L1 TV
#EXTVLCOPT:network-caching=1000
rtsp://192.168.1.65:554/?freq=162&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,2900,2901,2910,3001
#EXTINF:-1,Omroep Brabant
#EXTVLCOPT:network-caching=1000
rtsp://192.168.1.65:554/?freq=162&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,3200,3201,3210,3301
#EXTINF:-1,TV Gelderland
#EXTVLCOPT:network-caching=1000
rtsp://192.168.1.65:554/?
 
Last edited:

mm1352000
Country flag

Development Group
  • Team MediaPortal
  • September 1, 2008
    21,546
    8,208
    Home Country
    New Zealand New Zealand
    Thanks (y)

    Sorry for the long response. Lots of things to say; please read carefully and try to answer all questions.

    So, first thing I notice is that the URLs in your m3u file are just a little bit unusual. "KABEL>IP" (SAT>IP for DVB-C/C2) DVB-C URLs should not include the "bw" (bandwidth) parameter. That parameter is required for DVB-C2... but not for DVB-C.
    Where did you get the m3u from? ...and are you 100% sure that the URLs are correct/working?

    The next thing I notice is that TV Server is using the new merged URL-source-splitter/IPTV filter, instead of the standard IPTV filter that is comes with TV Server. I'm more familiar with the "standard" IPTV filter, and I'm not sure how stable/compatible the new "merged" filter is... but I'll do my best to understand what is going on.
    Did you intentionally install the "merged" filter for some reason?


    The filter seems to be loading correctly, and communicating with your network tuner. It successfully sends and receives OPTIONS and DESCRIBE RTSP commands:
    [collapse]
    14-05-2015 11:31:44.783 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlWorker(): RTSP request:
    OPTIONS rtsp://192.168.1.65:554/?freq=162&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,5300,3201,3210,3301 RTSP/1.0
    CSeq: 1


    14-05-2015 11:31:44.783 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlDebug(): CURL message: 'Found bundle for host 192.168.1.65: 0x5acb4f8'
    14-05-2015 11:31:44.783 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlDebug(): CURL message: 'Re-using existing connection! (#52) with host 192.168.1.65'
    14-05-2015 11:31:44.783 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlDebug(): CURL message: 'Connected to 192.168.1.65 (192.168.1.65) port 554 (#52)'
    14-05-2015 11:31:44.783 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlDebug(): CURL message: 'Connection #52 to host 192.168.1.65 left intact'
    14-05-2015 11:31:44.803 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlWorker(): RTSP response:
    RTSP/1.0 200 OK
    Public: OPTIONS, DESCRIBE, SETUP, PLAY, TEARDOWN
    CSeq: 1[/collapse]

    [collapse]
    14-05-2015 11:31:44.824 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlWorker(): RTSP request:
    DESCRIBE rtsp://192.168.1.65:554/?freq=162&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,5300,3201,3210,3301 RTSP/1.0
    Accept: application/sdp
    CSeq: 2


    14-05-2015 11:31:44.824 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlDebug(): CURL message: 'Found bundle for host 192.168.1.65: 0x5acb4f8'
    14-05-2015 11:31:44.824 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlDebug(): CURL message: 'Re-using existing connection! (#52) with host 192.168.1.65'
    14-05-2015 11:31:44.824 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlDebug(): CURL message: 'Connected to 192.168.1.65 (192.168.1.65) port 554 (#52)'
    14-05-2015 11:31:44.824 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlDebug(): CURL message: 'Connection #52 to host 192.168.1.65 left intact'
    14-05-2015 11:31:44.844 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlWorker(): RTSP response:
    RTSP/1.0 200 OK
    Content-Base: rtsp://192.168.1.65:554/?freq=162&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,5300,3201,3210,3301
    Content-Length: 4330
    Content-Type: application/sdp
    CSeq: 2

    v=0
    o=- 148 1 IN IP4 192.168.1.65
    s=SatIPServer:1 2
    t=0 0
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=4
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,330,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,2900,2901,2911,3001
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=6
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,330,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,2900,2901,2911,3001
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=8
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,330,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,2900,2901,2911,3001
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=10
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,330,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,2900,2901,2911,3001
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=12
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,330,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,2900,2901,2911,3001
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=14
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,330,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,2900,2901,2911,3001
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=17
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,330,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,2900,2901,2911,3001
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=19
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,330,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,2900,2901,2911,3001
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=21
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,330,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,2900,2901,2911,3001
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=23
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,330,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,2900,2901,2911,3001
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=25
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,330,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,2900,2901,2911,3001
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=27
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,330,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,2900,2901,2911,3001
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=29
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,330,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,2900,2901,2911,3001
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=31
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,330,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,2900,2901,2911,3001
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=33
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,330,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,2900,2901,2911,3001
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=35
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,330,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,2900,2901,2911,3001
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=37
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,330,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,2900,2901,2911,3001
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=39
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,330,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,2900,2901,2911,3001
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=41
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,330,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,2900,2901,2911,3001
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=43
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,330,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,2900,2901,2911,3001
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=45
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,330,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,2900,2901,2911,3001
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=49
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,162,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,4100,2001,2010,2101
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=51
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,162,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,4100,2001,2010,2101
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=53
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,162,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,4100,2001,2010,2101
    a=inactive
    m=video 0 RTP/AVP 33
    c=In IP4 0.0.0.0
    a=control:stream=55
    a=fmtp:33 ver1.0;src=1;tuner=1,0,1,0,162,,dvbc,256qam,,,6900,0;pids=0,16,17,18,20,4100,2001,2010,2101
    a=inactive[/collapse]

    As you can see from the DESCRIBE response, your tuner currently has a lot (25?) of inactive streams/connections. These are probably from failed tune requests. I would suggest that you reboot the network tuner to clear those.

    Anyhow, still so far so good. :)

    Next, the filter tries to send the tune request by sending an RTSP SETUP command. This is when the problem seems to happen:
    [collapse]
    14-05-2015 11:31:44.904 [1d88] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': Initialize(): trying to negotiate TCP transport on same connection
    14-05-2015 11:31:44.905 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlWorker(): RTSP request:
    SETUP rtsp://192.168.1.65:554/?freq=162&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,5300,3201,3210,3301/stream=4 RTSP/1.0
    Transport: RTP/AVP/TCP;interleaved=0-1
    CSeq: 3


    14-05-2015 11:31:44.905 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlDebug(): CURL message: 'Found bundle for host 192.168.1.65: 0x5acb4f8'
    14-05-2015 11:31:44.905 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlDebug(): CURL message: 'Re-using existing connection! (#52) with host 192.168.1.65'
    14-05-2015 11:31:44.905 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlDebug(): CURL message: 'Connected to 192.168.1.65 (192.168.1.65) port 554 (#52)'
    14-05-2015 11:31:44.905 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlDebug(): CURL message: 'Connection #52 to host 192.168.1.65 left intact'
    14-05-2015 11:31:44.925 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Warning] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlWorker(): RTSP response:
    RTSP/1.0 461 Unkown


    14-05-2015 11:31:44.926 [1d88] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Error] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': Initialize(): error while sending RTSP SETUP: 0x8007000D
    14-05-2015 11:31:44.926 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Error] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlWorker(): not interleaved packet and also not valid RTSP response
    14-05-2015 11:31:44.927 [1d88] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Error] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': Initialize(): error while sending same connection TCP RTSP SETUP: 0x8007000D
    [/collapse]

    As you can see, the RTSP SETUP request fails with code "461 Unkown". According to the SAT>IP specification, that error code means "unsupported transport":
    Status code 461 – Unsupported Transport
    Description The "Transport:" header field of the request did not contain a supported transport specification.
    Returned e.g. when issuing a profile that is different from "RTP/AVP".
    You can also see that the request is sent with transport field "RTP/AVP/TCP;interleaved=0-1"... so the error is valid, and not really surprising.

    Next, the filter tries to send another SETUP request:
    [collapse]14-05-2015 11:31:44.927 [1d88] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': Initialize(): trying to negotiate udp transport
    14-05-2015 11:31:44.946 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlWorker(): RTSP request:
    SETUP rtsp://192.168.1.65:554/?freq=162&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,5300,3201,3210,3301/stream=4 RTSP/1.0
    Transport: RTP/AVP;unicast;client_port=50000-50001
    CSeq: 4


    14-05-2015 11:31:44.946 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlDebug(): CURL message: 'Found bundle for host 192.168.1.65: 0x5acb4f8'
    14-05-2015 11:31:44.946 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlDebug(): CURL message: 'Re-using existing connection! (#52) with host 192.168.1.65'
    14-05-2015 11:31:44.946 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlDebug(): CURL message: 'Connected to 192.168.1.65 (192.168.1.65) port 554 (#52)'
    14-05-2015 11:31:44.946 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlDebug(): CURL message: 'Connection #52 to host 192.168.1.65 left intact'
    14-05-2015 11:31:44.946 [41f8] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Warning] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': CurlWorker(): RTSP response:
    RTSP/1.0 461 Unkown


    14-05-2015 11:31:44.947 [1d88] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Error] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': Initialize(): error while sending RTSP SETUP: 0x8007000D
    14-05-2015 11:31:44.948 [1d88] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Error] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': Initialize(): error while sending UDP RTSP SETUP: 0x8007000D
    14-05-2015 11:31:44.948 [1d88] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Verbose] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': Initialize(): trying to negotiate multicast transport
    14-05-2015 11:31:44.948 [1d88] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Error] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': Initialize(): multicast transport not implemented
    14-05-2015 11:31:44.948 [1d88] [{6CD05074-A14A-4820-962D-8230C8CE998F}] [Error] MPUrlSourceSplitter_Protocol_Rtsp: instance 'Main': Initialize(): can't negotiate any transport
    [/collapse]

    This time the transport field is "RTP/AVP;unicast;client_port=50000-50001". As far as I can tell, the request is valid... but the tuner still returns error code 461.

    This cycle of { OPTIONS -> DESCRIBE -> SETUP -> SETUP -> fail } is repeated over and over again. Eventually (after ~2 seconds) the filter gives up.


    So, the question is: what is the problem.
    I'm not sure why your tuner is returning the error code for the second [valid] SETUP (tune) request, but perhaps it gets confused after the first [incompatible] SETUP request... or maybe it is the unexpected "bw" parameter in the URL. You can easily modify the m3u to test without the "bw" parameter. If that doesn't work: I don't know if it is possible to disable sending of the first [incompatible] SETUP request... but I do know that the standard IPTV filter doesn't send such a request. So, maybe you could try to revert to the standard filter.

    @georgius
    Is there any way to prevent the merged filter from trying to send the RTP/AVP/TCP SETUP request?
    Do you have any other recommendations?
     

    Nervesagent

    Portal Pro
    February 26, 2014
    150
    19
    40
    Home Country
    Denmark Denmark
    Here's a new log with edited m3u file without the bw=8 option and reset the tuner. Same result though.
    The m3u comes from the webinterface on the device as an export. VLC plays them just fine.

    I must have installed the merged filter sometime because I thought that would solve my issue with this. How do I revert this to normal iptv filter? Just uninstall the plugin?
     

    mm1352000
    Country flag

    Development Group
  • Team MediaPortal
  • September 1, 2008
    21,546
    8,208
    Home Country
    New Zealand New Zealand
    Here's a new log with edited m3u file without the bw=8 option and reset the tuner. Same result though.
    Yeah, I confirm. Looks like changing the URL hasn't made any difference.

    The m3u comes from the webinterface on the device as an export. VLC plays them just fine.
    Okay, thanks.

    I must have installed the merged filter sometime because I thought that would solve my issue with this. How do I revert this to normal iptv filter? Just uninstall the plugin?
    Sorry, I'm not sure. georgius would be able to say... but uninstalling the plugin is probably a good guess.
     

    Nervesagent

    Portal Pro
    February 26, 2014
    150
    19
    40
    Home Country
    Denmark Denmark
    I'm guessing disabling the plugin is not eniough..
    Georgius how do i uninstall?
     

    georgius

    Retired Team Member
  • Premium Supporter
  • October 31, 2010
    1,376
    654
    Bratislava
    Home Country
    Slovakia Slovakia
    I must have installed the merged filter sometime because I thought that would solve my issue with this. How do I revert this to normal iptv filter? Just uninstall the plugin?
    Just uninstall merged filter. Stock MP filter should be registered on uninstallation.

    I just saw this in the configuration for RTSP:
    http://attachments.team-mediaportal.com/2014/11/212258_rtsp_settings.png

    What happens if you try to set "connection preference" to "UDP"?
    If UDP will be first, then filter sends "RTP/AVP;unicast;client_port=50000-50001" SETUP request as first, then probably RTP/AVP/TCP SETUP request (same connection) and last one will be multicast (not implemented).

    I don't have any idea, why RTSP is not working, I think that without wireshark log (network dump) with running VLC it will be impossible to find the cause of problem.
     

    Nervesagent

    Portal Pro
    February 26, 2014
    150
    19
    40
    Home Country
    Denmark Denmark
    I just saw this in the configuration for RTSP:
    http://attachments.team-mediaportal.com/2014/11/212258_rtsp_settings.png

    What happens if you try to set "connection preference" to "UDP"?
    Does not change anything.. I did notice that I cannot access the streams from the Fritz device after I do a scan. Like it crashes. So I have to restart it.

    I will try Georgius' suggestion and see if I can snort something if the normal iptv filter has the same problem.[DOUBLEPOST=1431626059][/DOUBLEPOST]edit: updated log
     

    Nervesagent

    Portal Pro
    February 26, 2014
    150
    19
    40
    Home Country
    Denmark Denmark
    ---------------------------
    So I disabled/uninstalled the filter and now it's scanning and finding channels..
    It's taking longer than on my N7 and I see that for every new found channel it updates 13? That's weird, but I'll see what the result is after its done scanning all the channels.
     

    mm1352000
    Country flag

    Development Group
  • Team MediaPortal
  • September 1, 2008
    21,546
    8,208
    Home Country
    New Zealand New Zealand
    I just saw this in the configuration for RTSP:
    http://attachments.team-mediaportal.com/2014/11/212258_rtsp_settings.png

    What happens if you try to set "connection preference" to "UDP"?
    Does not change anything..
    From the log files, it doesn't look like the setting was changed... which would explain why the results didn't change.
    Did you click "apply settings" after making the change? ;)

    So I disabled/uninstalled the filter and now it's scanning and finding channels..
    It's taking longer than on my N7 and I see that for every new found channel it updates 13? That's weird, but I'll see what the result is after its done scanning all the channels.
    Your "Fritz" (or whatever it is called) is receiving all the channels on each frequency. That's why it updates more than 1 channel for each channel that it scans. If you have a gigabit wired network, you could create an M3U with one channel per frequency (and replace pids=0,1,... with pids=all).
     
    Status
    Not open for further replies.

    Users Who Are Viewing This Thread (Users: 0, Guests: 1)

    Top Bottom