Thanks Jack. So found this in the logs:
2011-09-28 20:22:29.634103 [CRIT] rtmp_tcp.c:355 Socket error. Couldn't listen on 0.0.0.0:1935

And turns out i was running red5 on same server, hence the port conflict. I temporarily stopped red5 and can connect now...will sort out the conflict later.
Regards.


On Wed, Sep 28, 2011 at 8:58 PM, Jack <jack@livecall.com> wrote:
David,
I have mod_rtmp installed in a Win2003 environment this is my return when I do rtmp status:
default tcp:0.0.0.0:1935        profile

Make sure you include mod_rtmp in your build, it is not included by default. 

Jack


On 9/27/2011 1:22 PM, David Wafula wrote:
Am finally trying out flex client with mod_rtmp and i just realize how little i know of this module. I have installed mod_rtmp  and loaded it (or so i think). On the server, this is what i get:

 freeswitch@internal>rtmp status
-ERR no reply

This doesn't look right for starters..what do i expect for a valid reply?


To the client.
It looks like the basic config on the flex client is to  update
var flashvars = { xxxxxxxx} to point to my freeswitch server, no ?

So, first i try:
var flashvars = { 
};

And it does connect.

Say my freeswitch server is running at 1.2.3.4

So, naturally i end up with

var flashvars = { 
rtmp_url: 'rtmp://1.2.3.4'
};

Is that the way to do it? Because this gives me:

netStatus: NetConnection.Connect.InvalidApp
netStatus: NetConnection.Connect.Closed

Any pointers will be appreciated.


Thank you
-- 


David Wafula


FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org


FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org




--
David Wafula