There could be various reasons why sending two consecutive requests with GB28181 protocol is not successful. Here are some possible explanations:
Network issues: It’s possible that there are network connectivity problems or packet loss occurring, which might result in the failure of the second request. You can check for any error messages related to the network or try sending the requests from a different network to see if it resolves the issue.
Server-side limitations: It’s possible that the server you’re sending the requests to has some limitations on the number of requests it can handle in a certain period. You can check the server logs to see if there are any errors or contact the server admin to know more about the limitations.
Protocol-specific issues: GB28181 protocol has some specific requirements related to message sequence, SSRC, and other parameters. Make sure that your requests conform to these requirements, and you’re not violating any rules. You can refer to the protocol documentation or seek help from the community to ensure that your requests are valid.
Application-level issues: It’s possible that there’s something wrong with the application code that is preventing the second request from being sent successfully. You can use debugging tools to check for any errors or log messages related to the application code and fix them accordingly.
Overall, determining the exact cause of the issue would require further investigation and analysis of the relevant factors.
