>>> AAF Board Info<<<



neu Titan stable 1.87

Hinweis zur DM900 TitanNit Edition

Boardaktion Dreambox unter 100€ mit Titan Lizenz

Bundesligatippspiel Saison 2017/18 und Glückwünsche





Seite 2 von 2 ErsteErste 12
Ergebnis 11 bis 17 von 17

Thema: E2 webif api?

  1. #11
    Betatester
    Registriert seit
    04.05.2010
    Ort
    New Zealand
    Beiträge
    1.578
    Box 1:   Ultraplus F-9000 TitanNit




    I have played with the server via command line and the plugin e2webif replys to a get service command and puts the incorrect port number in the m3u file it sends to the client it uses the titan port and not the e2 port.

    So you get a e2 response in the form of a playlist as expected with the titan wefif port in the response.

    This is a bug in e2webif plugin.

    Code:
    http://192.168.1.20:8080/web/service.m3u

    Code:
    # e2 web port
    port=8080
    # e2 data port
    dataPort=8001
    # titan web port
    titanPort=80
    # titan data port
    titanDataPort=22222
    returned playlist.m3u8 file contents:

    Code:
    #EXTM3U
    #EXTVLCOPT--http-reconnect=true
    http://192.168.1.20:22222/
    proper response (what m3u should contain) :

    Code:
    #EXTM3U
     #EXTVLCOPT--http-reconnect=true
     http://192.168.1.20:8001/

    http://sbnc.dyndns.tv/trac/ticket/537
    Geändert von professor_jonny (06.09.2017 um 21:34 Uhr)

  2. #12
    Betatester
    Registriert seit
    15.12.2010
    Beiträge
    417





    Hi,

    the streamport 22222 with titan service ref is the correct one in m3u.
    ago123 wroted in his thread, that an stream request to port 8001 with E2-Service-ref will return an redirect link to the real titan dataport 22222 with titan-Service-ref.
    The client-app must then use the redirect-URL for the stream.

    A stream request for E2 service 1:0:1:40b:16:2f:6400000:0:0:0:
    http://192.168.1.20:8001/1:0:1:40b:16:2f:6400000:0:0:0:

    return the redirect url to the real streamlink with port 22222 and Titan service 1035%2c3080214
    http://192.168.1.20:22222/1035%2c3080214

    It is not possible to uses a E2-Service-ref direkt with titan port 22222
    The port 8001 is only used on E2webServer to get the redirect link to the real titan stream-url.
    If you request the service.m3u on port 8080, then you get the m3u to the real titan stream-url(22222 with titan service-ref).

  3. #13
    Betatester
    Registriert seit
    04.05.2010
    Ort
    New Zealand
    Beiträge
    1.578
    Box 1:   Ultraplus F-9000 TitanNit




    Zitat Zitat von Wonderdoc Beitrag anzeigen
    Hi,

    the streamport 22222 with titan service ref is the correct one in m3u.
    ago123 wroted in his thread, that an stream request to port 8001 with E2-Service-ref will return an redirect link to the real titan dataport 22222 with titan-Service-ref.
    The client-app must then use the redirect-URL for the stream.

    A stream request for E2 service 1:0:1:40b:16:2f:6400000:0:0:0:
    http://192.168.1.20:8001/1:0:1:40b:16:2f:6400000:0:0:0:

    return the redirect url to the real streamlink with port 22222 and Titan service 1035%2c3080214
    http://192.168.1.20:22222/1035%2c3080214

    It is not possible to uses a E2-Service-ref direkt with titan port 22222
    The port 8001 is only used on E2webServer to get the redirect link to the real titan stream-url.
    If you request the service.m3u on port 8080, then you get the m3u to the real titan stream-url(22222 with titan service-ref).
    yes that is correct redirection works with an e2 request directly via a web command but when downloading a stream link via m3u it does not put the same url embedded in the m3u file....

    When I make a request to download a stream via m3u it is returning incorrect data, basically I get the titan data port mixed with the e2 service request in the url.

    below is what it replys within the m3u the titan port with the e2 web format so redirection does not work as it is invalid link the port should be 8001 so redirection works or use the correct titan service reference right from the bat in the m3u.

    http://192.168.1.20:22222/1:0:1:40b:...6400000:0:0:0:

    The plugin is returning an incorrect e2 url for redirection within the m3u file sent via the e2 server or it is putting the incorrect service reference field format into the m3u file.

    This depends on the server if it asks for an m3u file to stream or if it sends the web if string directly so it will work with some e2 web if clients and it wont with others depending on how they ask to stream the service.
    Geändert von professor_jonny (13.09.2017 um 02:25 Uhr)

  4. #14
    Betatester
    Registriert seit
    15.12.2010
    Beiträge
    417





    Hi,

    I have Test it on my sh4 ufs922 Receiver.
    If i send a request
    http://192.168.31.100:8001/1:0:1:40b...6400000:0:0:0:
    I get a redirect url to
    http://192.168.31.100:22222/1035%2c3080214
    That is correct.

    If i send a request
    http://192.168.31.100:8080/web/strea...6400000:0:0:0:
    I get a Playlist.m3u8 file.

    If i take a look into the file, i can Not see any Problems.
    #EXTM3U
    #EXTVLCOPT--http-reconnect=true
    http://192.168.31.100:22222/1035,3080214

    If i send a request
    http://192.168.31.100:8080/web/strea...:&name=nothing
    I get a playlist.m3u8 File, too.

    If i Open it, it seems all ok.
    #EXTM3U
    #EXTVLCOPT--http-reconnect=true
    http://192.168.31.100:22222/1035,3080214

  5. #15
    Betatester
    Registriert seit
    15.12.2010
    Beiträge
    417





    Please take a Look in the /tmp/e2webserv.log file.

    http://192.168.31.100:8001/1:0:1:40b...6400000:0:0:0:
    Code:
    13.09 07:16:26 [2af604c0] DBG SRV -- new request
    13.09 07:16:26 [2af604c0] INF SRV -- GET /1:0:1:40b:16:2f:6400000:0:0:0:
    13.09 07:16:26 [2af604c0] DBG CLI -- GET: /queryraw?getaktservice
    13.09 07:16:26 [2af604c0] DBG CLI -- OK, len=100
    13.09 07:16:26 [2af604c0] DBG CLI -- GET: /queryraw?switch&1035&3080214
    13.09 07:16:26 [2af604c0] DBG CLI -- OK, len=100
    13.09 07:16:26 [2af604c0] INF SRV -- 302 Moved Temporarily, loc=http://192.168.31.100:22222/1035%2c3080214
    13.09 07:16:26 [2af604c0] DBG SRV -- request handled
    E2webserver is Version 1.1.14.
    You can see it in the Logfile
    Code:
    13.09 06:08:55 [29760000] INF SRV -- start server: GsE2TitanBridge/1.1.14
    On github you can find an newer bin Version 1.1.15 for sh4/mipsel.

  6. #16
    Betatester
    Registriert seit
    04.05.2010
    Ort
    New Zealand
    Beiträge
    1.578
    Box 1:   Ultraplus F-9000 TitanNit




    Zitat Zitat von Wonderdoc Beitrag anzeigen

    E2webserver is Version 1.1.14.
    You can see it in the Logfile
    Code:
    13.09 06:08:55 [29760000] INF SRV -- start server: GsE2TitanBridge/1.1.14
    On github you can find an newer bin Version 1.1.15 for sh4/mipsel.
    Mine is older than 1.1.14 I updated and the returned string seems to be good now.
    I had to manually update via ftp and telnet.

    this is the correct git ?
    https://github.com/gswiatek/e2api4titan

    Code:
    Version 1.1.13 (28.09.2014)
    -------------
    - Fix for standby status in /web/powerstate request (FHEM should work now)
    - Dummy implementation for /ipkg request (required for TVBrowser support)
    - New requests /web/currenttime, /web/stream.m3u and /web/streamcurrent.m3u implemented
    - Workaround for wrong URL encoding in TVBrowser capture plug-in

  7. #17
    Betatester
    Registriert seit
    15.12.2010
    Beiträge
    417





    Yes, This is the correct git .
    ReleaseNots is not up to date.
    If you take a Look into Version.h, then you can See that source is 1.1.15.
    You can Test the bin from sh4/mips directory.

Seite 2 von 2 ErsteErste 12

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •