my escenario is posible using FMS (flash media server)?
this behavior is only with red5?
if i change all my server code, change to WOWZA in place of red5 the exit in all protocols is transparent?
Exist other way to reach my objetive?
I been trying to re-stream from Red5 via Wowza and stream manager (works fine from FMS) but it does not work -I got it work when I pull from FMS 3.57 but if I change to pull from Red5 serveer (1.0) it fails and I see the follow error in console
INFO application app-start _definst_ live/_definst_
INFO stream create - -
INFO server comment - LiveMediaStreamReceiver.connect: SSL:false url:rtmp://192.168.1.11:1935/live/_definst_/livestream
INFO server comment - HTTPStreamManager.onHTTPRequest: Publish stream successfully started [live/_definst_]: flv:rtmp.stream
ERROR server comment - handleResult: can't find resultObj: 0 in
WARN server comment - LiveMediaStreamReceiver.doWatchdog: streamTimeout[live/_definst_/livestream][1391201118701:1391201106675:12000]: Resetting connection: rtmp://192.168.1.11:1935/live/_definst_/livestream
Again the only thing I change is pulling from FMS (which works) to Red5 (which does not). Not sure what Red5 problem has been fixed in Wowza (I am thinking it is a Red5 issue).
I will have to check on this. I'm not sure what I was referring to above. There may have been a report from a customer that had got this to work at that time. However, generally this has not worked, and is not supported at present, in that we have not had success and therefore no guidance to document.
The answer to this this issue is that Red5 Server does not use a default instance name unless you include it in the publishing url. So while FMS/AMS and Wowza will use _definst_ Red5 will not and Wowza will not find the stream to pull in. Once I put in the _definst_ in the stream being published to Red5, Wowza was able to pull streams from Red5 server. So I got this to work.