Nice, how did you capture the packets? Using Wireshark or?
Sebastian 2012/5/23 German Grekhov <[email protected]> > Dear community. > > If somebody has never seen the content of an RTPMT packet, please, let me > show you an example of it: > > POST /send/40/247 HTTP/1.1 > Content-Type: application/x-fcs > User-Agent: Shockwave Flash > Host: 192.168.56.101:8088 > Content-Length: 132 > Connection: Keep-Alive > Cache-Control: no-cache > > R`U5&c3dYhb:hRJe<U'*S%cU63NY(~)/Rh)9 m;nf&HGLcbhg~R~^f$F2\%?S > > > POST /send/40/248 HTTP/1.1 > Content-Type: application/x-fcs > User-Agent: Shockwave Flash > Host: 192.168.56.101:8088 > Content-Length: 66 > Connection: Keep-Alive > Cache-Control: no-cache > > RXyCp TMQBSRi`Q\`erEQiO > > > We can see that RTMPT makes POST requests to the generated "/send/.../..." > address on your server (for sending audio or video). As I understand those > digits (e.g. /40/248) are the identifiers of the stream and the packet in > the stream. > > Also, RTMPT requests could be made on the following addresses: > /open, /idle, /close, /fcs > > German. > -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.openmeetings.de http://www.webbase-design.de http://www.wagner-sebastian.com [email protected]
