Also KSV or somebody else not sure if you have a cable TV subscription or not to test:
http://www.cnn.com/video and test their "Live TV" section.
But I have noticed that the rtmpdump code must have changed sometime after 2011-07-11 because like I said before if I use KSV or normal versions since then it constantly results in "Invalid AMF Data" with rtmpsrv from RTMPDumpHelper.
From what I can tell, they (edgecfs) are simply changing the connection data on every play request and using weird characters like the Spanish upside down exclamation point.
Not sure why but the older rtmpdumps can simply flow with these odd connection data but the newer cannot and just error out, so I was wondering if this could be fixed via a patch.
Here is a sample of what I mean:
rtmpdump -r "rtmpe://cp99921.live.edgefcs.net:1935/live" -a "live?auth=daEdabcbS
bfdrdlcNa.dudNbld5cebQaKan-brBoEc-hca-lxy_GFs&aifp=v001&slist=tvehln104_1_low@s8
9305" -f "WIN 11,7,700,169" -W "http://z.cdn.turner.com/xslo/cvp/plugins/akamai/
streaming/osmf1.6/2.11.3/AkamaiAdvancedStreamingPlugin.swf" -p "http://www.cnn.c
om/video/#/video/cvptve/cvpstream2" --live -C Θ: -y "tvehln104_1_low@s89305?auth
=daEdabcbSbfdrdlcNa.dudNbld5cebQaKan-brBoEc-hca-lxy_GFs&aifp=v001&slist=tvehln10
4_1_low@s89305" -o "tvehln104_1_low@s89305.flv"
ERROR: Invalid AMF parameter: Θ:
It's as if the command would easily work with zero issues if it was not for the strange ASCII characters.
Though not sure if this would be something the actual RTMPDump would need to code.