Here is an extract from the FMS client side action script documentation
about the NetConnection object. It explains the fall back mechanism of the
nc.connect method:
If Flash Player fails to connect to the server over an RTMP connection on
the default port, it
will automatically try to establish a connection using a predetermined
sequence of ports and
protocols. For example, if an application tries and fails to connect using
my_nc.connect("rtmp:/myserver/myapp"), Flash Player will automatically try
the
following sequence of connections, until successful:
my_nc.connect("rtmp://myserver:443/myapp");
my_nc.connect("rtmp://myserver:80/myapp");
my_nc.connect("rtmpt://myserver:80/myapp");
This connection sequence can enable connections to succeed that otherwise
would not.
However, during this connection sequence users may wait several seconds for
multiple
connection attempts to time out.
--
Naicu Octavian,
Project Manager for AVChat
http://www.avchat.net
On 23/08/07, Ruben Waitz <[EMAIL PROTECTED]> wrote:
>
> For a while I'm also struggling with the port issues Nauman describes.
>
>
>
> At the following page (
> http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_16631&sliceId=2)
> Adobe says:
>
> "By default, the Macromedia Flash Player communicates with the Flash
> Communication Server using RTMP protocol over port 1935. If that fails, it
> will try again over ports 443 and 80 in an attempt to workaround firewall
> settings within a company, which prevents TCP/IP connections over
> non-standard ports. The above approach allows approximately 96% of all users
> to access publicly accessible Flash Communication servers.
>
> To support closer to 100% of the users we need the Macromedia *Flash*Player to
> *negotiate* connection to the external Flash Communication server though a
> proxy server (if there is one), or use HTTP protocol to transmit RTMP
> packets (HTTP tunneling) if there is a firewall (which allows only HTTP
> content to be sent out to public servers)."
>
> If I understand it correctly one need to program the Flash player to
> choose port 443 and 80 as an alternative (keeping in mind the reserved
> 0-1023 portrange makes life harder for non-root tomcat users). But if those
> ports are already in use for normal the http protocol (e.g. serving
> webpages) the RTMP packets needs to be wrapped in the http protocol
> resulting in RTMPT.
>
>
>
> But the "*if that fails, it will try again over ports 443 and 80........*"
> confuses me.
>
>
>
> Does this make any sense or am I missing something?
>
>
>
> ruben
>
>
>
>
>
>
>
> > -----Oorspronkelijk bericht-----
>
> > Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens
>
> > Luke Scott
>
> > Verzonden: donderdag 23 augustus 2007 16:33
>
> > Aan: [email protected]
>
> > Onderwerp: Re: [Red5] When I add the port number to the connection
> string
>
> > theconnection fails
>
> >
>
> > RTMPT not RTMP.
>
> >
>
> > I'm not sure if you can change it to 80.
>
> >
>
> > First, are you running Red5 as root or another user? If another user,
>
> > check Red5's console as only the root user can bind to ports 0 -
>
> > 1023. Ports above 1023 can be bound by other users.
>
> >
>
> > Second, which port does flash use for RTMPT by default? I'm not quite
>
> > sure, but is it 80?
>
> >
>
> > -Luke
>
> >
>
> > On Aug 23, 2007, at 12:44 AM, Nauman Nasir wrote:
>
> >
>
> > > no i think that rtmp port is 1935 by default
>
> > >
>
> > > On 8/23/07, Steven Gong <[EMAIL PROTECTED]> wrote:
>
> > >> Just curious. Why you add the redundant '80' to the url?
>
> > >>
>
> > >> On 8/23/07, Naicu Octavian <[EMAIL PROTECTED]> wrote:
>
> > >>>
>
> > >>> I have a Red5 server set up on Fedora Core with port 80 set up
>
> > >>> for rtmpt
>
> > >>> in red5.properties .
>
> > >>>
>
> > >>> My issue comes from trying to connect over rtmpt
>
> > >>>
>
> > >>> Whenever I use rtmpt://subdomain.server.com/myapp the connection
>
> > >>> succeeds
>
> > >>> aand my chat app works just fine
>
> > >>> Whenever I use rtmpt://subdomain.server.com:80/myapp the
>
> > >>> connection fails
>
> > >>> with the below onStatus message:
>
> > >>>
>
> > >>> description:No scope "chatapp/avcdr" on this server.
>
> > >>> code:NetConnection.Connect.InvalidApp
>
> > >>> level:error
>
> > >>>
>
> > >>>
>
> > >>> The default port for rtmpt is 80 so I do not see why I get the
>
> > >>> isssue
>
> > >>> above!
>
> > >>>
>
> > >>> _______________________________________________
>
> > >>> Red5 mailing list
>
> > >>> [email protected]
>
> > >>> http://osflash.org/mailman/listinfo/red5_osflash.org
>
> > >>>
>
> > >>>
>
> > >>
>
> > >>
>
> > >> --
>
> > >> Best Regards
>
> > >> Steven Gong
>
> > >>
>
> > >> InfraRed5 Red5 Consultant: http://www.infrared5.com,
>
> > >> [EMAIL PROTECTED]
>
> > >>
>
> > >> Red5 Developer: http://osflash.org/red5,
>
> > >> http://jira.red5.org/confluence/display/~steven/Home<http://jira.red5.org/confluence/display/%7Esteven/Home>
>
> > >>
>
> > >> Modesty is an overrated quality in men of no great
>
> > >> accomplishment. -- Ricky
>
> > >> Jay
>
> > >>
>
> > >
>
> > >
>
> > > --
>
> > > *************************************************
>
> > > The life is too short to Love.
>
> > > I donot know how people manage to hate
>
> > > *************************************************
>
> > > Ch. Nauman Bin Nasir
>
> > >
>
> > > _______________________________________________
>
> > > Red5 mailing list
>
> > > [email protected]
>
> > > http://osflash.org/mailman/listinfo/red5_osflash.org
>
> >
>
> >
>
> > _______________________________________________
>
> > Red5 mailing list
>
> > [email protected]
>
> > http://osflash.org/mailman/listinfo/red5_osflash.org
>
> _______________________________________________
> Red5 mailing list
> [email protected]
> http://osflash.org/mailman/listinfo/red5_osflash.org
>
>
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org
