Paromita, Seth,
Just to deal with dumb firewalls and proxy you can configure your server
with multiple IP addresses/names in the same domain, and split HTTP / RTMP
traffic between 2 different IP addresses - make sure you bind HTTP server to
one of them and RTMP to the other.
Hope this helps
Anatole Tartakovsky
Farata Systems
On Mon, Jun 16, 2008 at 1:40 PM, Seth Hodgson <[EMAIL PROTECTED]> wrote:
> Hi,
>
> RTMP is run on a non-standard (meaning, non-HTTP) port so client-side
> firewalls/proxies/etc. may block traffic out on that port. Accessing your
> server over VPN versus over the public internet must be using different
> port-specific rules.
>
> You'll generally want to define your ChannelSet (or the list of channels in
> your server config), to start with RTMP as the preferred option but then
> fallback to one of the AMF HTTP options (streaming, long-polling, simple
> polling). These fallback channels/endpoints should be configured to use port
> 80 if insecure or 443 is secure to guarantee that their traffic makes it
> through the network without being blocked due to port number.
>
> Seth
>
> From: [email protected] <flexcoders%40yahoogroups.com> [mailto:
> [email protected] <flexcoders%40yahoogroups.com>] On Behalf Of
> paromitadey
> Sent: Monday, June 16, 2008 1:13 AM
> To: [email protected] <flexcoders%40yahoogroups.com>
> Subject: [flexcoders] Connection problem in Flex messaging
>
>
> Hi,
>
> We have used Flex messaging in an Flex/Java based application. The
> messaging works fine in our production/QA server. But when we
> deployed the application to the production server, which can be
> accessed by a public IP, the messaging feature failed. Nevertheless,
> if we connect the production server using a VPN connection and use
> an internal IP to run the application, the messaging is working but
> does not work when the same application is accessed using the public
> IP.
> We have used rtmp channel for messaging and we have opened the port
> used in both the public IP as well as the internal IP.
>
> <channel-definition id="my-rtmp"
> class="mx.messaging.channels.RTMPChannel">
> <endpoint uri="rtmp://{server.name}:2037"
> class="flex.messaging.endpoints.RTMPEndpoint"/>
> <properties>
> <idle-timeout-minutes>20</idle-timeout-minutes>
> </properties>
> </channel-definition>
>
> Still we have the same problem. We are unable to find the reason for
> the dubious behavior.
>
> Could anyone please help us to resolve this problem. What possibly
> could be going wrong?
>
> Thanks and Regards,
> Paromita
>
>
>
