Quote:
Originally Posted by KSV
That's not the problem with rtmpdump. rtmpdump tries to connect with their sever on detected port (1935) and server disconnects the connection. it's also the reason why rtmpsuck doesn't work on this site. after disconnection their flash client switches to another port (probably 80 or 443) which is not redirected to rtmpsrv or rtmpsuck by default (check RTMPDumpHelper options). try after changing the port from 1935 to 80 or 443. it's better to use wireshark in this case to know which protocol (RTMPT ?) and port is being used.
|
A wireshark analysis just seems to show normal HTTP/HTTPS traffic then the minute the stream plays a flow of "RTMP" traffic with a ton of "Unknowns (0x0)" which I always seem to see with RTMPE on port 1935, which is confirmed after reading an XML that was sent before hand.
http://www.cnn.com/video/data/3.0/vi...eam1/index.xml
You can tell it seems to mention rtmpe first and that's the protocol uses in the older version but I do see an rtmpte URL also in that XML but Wireshark claims rtmpte is not in use by default.