In the live555 mediaserver, RTSP-over-HTTP has been implemented, but it is not enabled by default. To implement this function, call rtspserver: setuptunnelingoverhttp () to specify the port used for RTSP-over-http. This port must be different from the normal RTSP-over-TCP port.
In my current version of mediaserver/live555mediaserver. cpp, there is such a program that has been commented out, it is not hard to see that it is the initialization of RTSP-over-http:
[CPP]View plaincopy
- # If 0 // RTSP-over-HTTP tunneling is not yet working
- // Also, attempt to create a HTTP server for RTSP-over-HTTP tunneling.
- // Try first with the default http port (80), and then with the alternative HTTP
- // Port number (8000 ).
- Rtspoverhttpserver * rtspoverhttpserver;
- Portnumbits httpserverportnum = 80;
- Rtspoverhttpserver = rtspoverhttpserver: createnew (* ENV, httpserverportnum, rtspserverportnum );
- If (rtspoverhttpserver = NULL ){
- Httpserverportnum= 8000;
- Rtspoverhttpserver = rtspoverhttpserver: createnew (* ENV, httpserverportnum, rtspserverportnum );
- }
- If (rtspoverhttpserver = NULL ){
- * Env <"(No server for RTSP-over-HTTP tunneling was created.) \ n ";
- } Else {
- * Env <"(we use port"
- }
- # Endif
Therefore, similar code can be transplanted to implement RTSP-over-HTTP in Wis-streamer. However, when oppro live starts a Wis-streamer for each code stream, a total of five Wis-streamer instances are started. If all five processes have RTSP-over-HTTP, isn't it a mess?
We look forward to your message!
Http://blog.csdn.net/lxhjjz/article/details/8052465
Http://www.dajudeng.com/d201208100980c90277375a417866f8f41.html
Http://www.ebaina.com/bbs/thread-1734-1-1.html
Http://blog.csdn.net/niu_gao/article/details/6911130 live55 details
WIS-stream in multimedia development