-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SATIP-ERROR: invalid status code 454 #12
Comments
What's the version of your libcurl? |
I have checked the tcpdump. This is the response to the SETUP command RTSP/1.0 200 OK And this is what the plugin sends back in the DESCRIBE command DESCRIBE rtsp://192.168.0.18/stream=1600 RTSP/1.0 You can see the first character is missing in the session id. So it is omitted for some reason. Btw: Thank you |
Your libcurl version contains a session bug. Please, upgrade to libcurl 7.36.0 or newer as stated in README. |
Thank you very much Btw. the DVB-S2 card works fine with VDR (using the same channels) and the SatIP device also works properly (tested some Windows sw and Tvheadend (which does not work well)) I have not done extra setup of the plugin as I didn't undestand if it is required. |
I was able to get it all working. Appears that error message is not fatal and it works fine after. What I am strugging now with is the DVBAPI plugin and Oscam. Can you think of any solution? Thank you again. syslog: OSCam log |
For the re-tuning issue, you could try to add a force lock quirk for your device into server.c:
|
Please, don't use the streamdev plugin for testing as it has known issues with decryption. |
Thank you, I have done the patch to the frontend locking. Regarding the decryption, it still does not work properly.
Not testing with streamdev but vnsiserver. I receive one of these in such situation Thank you for your help |
I know this has probably nothing to do with your great vdr plugin but if you have any advices. Thank you again |
Your decryption problems aren't directly related to satip plugin, so there's no point having such conversation here. However, did the re-tuning patch fix your system? If yes, I'll add it into repo. |
I think so, I haven't seen that error ever since |
Great! Pushed the fix to master and let's close this issue. |
Hello
I am trying to use this VDR plugin but I am having issues.
Please, see the log below:
Sep 16 12:01:10 Media vdr: [30749] SATIP: Adding server '192.168.0.18|DVBS2-4|Schwaiger Sat>IP Server' CI: no Quirks: none
Sep 16 12:01:18 Media vdr: [30736] switching to channel 1 (CT1)
Sep 16 12:01:18 Media vdr: [30736] OSD size changed to 720x480 @ 1
Sep 16 12:01:18 Media vdr: [30736] ERROR: no OSD provider available - using dummy OSD!
Sep 16 12:01:19 Media vdr: [30750] curl_easy_perform() [rtsp.c,255] failed: RTSP session error (86)
Sep 16 12:01:19 Media vdr: [30750] SATIP-ERROR: Detected invalid status code 454: rtsp://192.168.0.18/ [device 0]
Sep 16 12:01:20 Media vdr: [30750] curl_easy_perform() [rtsp.c,255] failed: RTSP session error (86)
Sep 16 12:01:20 Media vdr: [30750] SATIP-ERROR: Detected invalid status code 454: rtsp://192.168.0.18/ [device 0]
Sep 16 12:01:21 Media vdr: [30750] curl_easy_perform() [rtsp.c,255] failed: RTSP session error (86)
Sep 16 12:01:21 Media vdr: [30750] SATIP-ERROR: Detected invalid status code 454: rtsp://192.168.0.18/ [device 0]
Can we please troubleshoot this issue? I have tried with 2.2.2 and 2.3.1 and it is the same
Will you please help me to get this working?
Running on Ubuntu 14.04 and VDR 2.2.0
Thank you,
Jakub
The text was updated successfully, but these errors were encountered: