Skip to main content
A
Anonymous
July 8, 2009
Question

Firewall ports

  • July 8, 2009
  • 1 reply
  • 1486 views

I have a few problems with respect to the FMS3.5 server.  When the default server configuration is being installed (with apache):  do I need to open port 8134 in for the firewall or not?  When non-FMS content is served over the default apache server, is the FMS server configuration being in any way used to pass on the content?  The problem for me is that pseudostreaming windows media files and  ram files for rm media does not perform as rapidly and even not at all when using the fms default apache (the connection times out);  while a standalone apache on a different machine does it all fine.

    This topic has been closed for replies.

    1 reply

    A
    Anonymous
    July 8, 2009

    When using Apache with FMS, FMS acts as a proxy, so you shouldn't need to open 8134 to the outside world.

    Given that the FMS process is acting as proxy, I would expect it to perforn a bit slower, but I haven't worked with the HTTP proxy features with it enough to know where the points of failure might be.

    A
    Anonymous
    July 11, 2009

    Thanks.  Appreciate your response.  I suspect that there is something trivial that I miss.  It seems that the FMS tries to  use its own applications to open the mp3 and real media files that it receives from the httpd request.   From the httpd access log I can see that the requests for these file formats from 127.0.0.1  have been successful, but they have not been forwarded back properly to the client.  Is it possible to specify that the FMS does not handle mime types for mp3 and real media and windows media, but simply proxies them back to the client?  And that the FMS uses its process for the mp4 and f4v files?

    More specifically, what if I placed an rm audio file (real media file) into the default apache webroot.  (By the way, I've left all configurations of the servers as default install)  Now when I make an http request for this "audio.rm"  file through a ram file, such as this:   http://localhost/audiofile.ram   it does not deliver the rm file.  (The ram file holds this content:    http://localhost/audio.rm )  The audio rm file, when requested apart from the ram file does deliver.

    Why is that so, and is it possible to configure the FMS to forward it?

    A
    Anonymous
    July 15, 2009

    Additionally, this is most likely an FMS issue, not the apache server issue.  The apache forwards its stuff to the FMS, but the FMS seems to mishandle it.  But another question:  since the FMS at times needs a crossover.xml file - would perhaps this is what has to be used in my scenario.  The real media ram file is the metadata file that references the rm file?

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices