-
Notifications
You must be signed in to change notification settings - Fork 185
-
Notifications
You must be signed in to change notification settings - Fork 185
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
Something wrong when parseing package,and it will be timeout #123
Comments
Hello, please try to connect to the cameras with rtsp-simple-server and post a log with the option |
I tried to analyze the dump but i was not able to find the exact problem, so more infos are needed. |
OK, but I don't have debugging conditions these days. I'll upload it when I can test it |
I'm very sorry. I haven't had time to capture packets before. Today, I tested and played two cameras. One can play and the other can't. The packet capturing data is the gortsplib referenced by our service, and the other two log files are printed with RTSP-simple-server |
This is the bag caught by my direct camera. It can't be played. The address is: rtsp://admin:admin123 @10.105.240.92:554/cam/realmonitor? Channel=1&subtype=0 the same address can be played using VLC |
None of the file you provided gives any hint about the issue. Server logs show that you're trying to publish something with FFmpeg (what's the role of ffmpeg in all this?), while test.zip shows a successful connection from the server to the camera.
|
Sorry, I tested it again today. You can use rtsp-simple-server to directly access and pull streams. It should not be the problem of gortsplib, but the problem of my plug-in service. Thank you very much. |
This issue is being locked automatically because it has been closed for more than 6 months. |
Hello, when I use gortsplib to pull streams, I connect to Dahua dss-h8900 platform, and some stream connection times out (VLC and Dahua plug-ins can be used normally). There may be a problem with the parsing package. The relevant logs are as follows:the ip is from 10.105.243.19 to 10.105 240.22
2022-04-27T18.log
data.zip
The text was updated successfully, but these errors were encountered: