Skip navigation
Up to Discussions in Red5
5498 Views 4 Replies Latest reply: Aug 23, 2012 10:35 AM by Dele Olajide RSS
Dele Olajide KeyContributor
Dele Olajide
862 posts since
Apr 10, 2006
Currently Being Moderated

Aug 14, 2012 5:52 AM

Redfire is still alive

A new version of  Redfire (0.0.3.0) has been posted on project site http://code.google.com/p/redfire/

 

It has three major changes

 

  • The Redfire plugin for Spark now uses the multicast DNS protocol to auto-discover the Redfire plugin for Openfire and obtain the server address and port number in order to load the web pages for the audio/video chat. I have not tested it properly, so please report any issues found.

 

  • Support for RTMFP has been added using Cumulus OpenRTMFP server. It is disabled by default as the binary for only Windows is provided. Linux users must download and build the binary from source and point the "cumulus.path" Openfire property at the binary file location. When enabled, all audio/video calls can be peer to peer using UDP instead of TCP and improving performance.

 

  • Red5Phone is now replaced with Redfire-Phono which a modified version of the Phono SDK from Voxeo. It is a Javascript library based on jQuery and Strophe that enables telephone calls to be made from a web browser. Redfire-Phono allows Jingle audio calls using the RTMP transport between any Redfire-Phono users as well as audio calls to any SIP address and external telephone numbers using a configured gateway with the SIP plugin for Openfire.

    Image2.jpg

 

I still do not have a 64-bit Windows PC, so all reported issues with redfire plugin for Spark on 64-bit PCs have not been fixed.

Tags: spark, openfire, plugin, red5, redfire, rtmp, rtmfp
  • black187 Bronze
    black187
    10 posts since
    Jul 4, 2009
    Currently Being Moderated
    Aug 23, 2012 3:46 AM (in response to Dele Olajide)
    Redfire is still alive

    What about RTMPT?

    • Dele Olajide KeyContributor
      Dele Olajide
      862 posts since
      Apr 10, 2006
      Currently Being Moderated
      Aug 23, 2012 4:01 AM (in response to black187)
      Redfire is still alive

      Unfortunately, the root application of the web service under which Red5 runs belongs to the http-bind BOSH service, so RTMPT is not supported out of the box.

       

      If you really need it, then you can manually move Red5 to the root web application. The location is OPENFIRE_HOME\resources\spank.

       

      The alternative is to spawn a new jetty web service on another port like 5080 instead of using the http-bind web service on 7070. That will will require a bit of coding

      • black187 Bronze
        black187
        10 posts since
        Jul 4, 2009
        Currently Being Moderated
        Aug 23, 2012 4:25 AM (in response to Dele Olajide)
        Redfire is still alive

        Hi,

         

        Thanks for the quick answer - so the redfire directory should reside in OPENFIRE_HOME\resources\spank.

         

        I can access it via: http://ip_address:7070/redfire -> how do I configure red5 rtmpt url:

         

        rtmpt://ip_address:7070/sip

         

        ?

        • Dele Olajide KeyContributor
          Dele Olajide
          862 posts since
          Apr 10, 2006
          Currently Being Moderated
          Aug 23, 2012 10:35 AM (in response to black187)
          Redfire is still alive

          It is not as simple as that. You have to edit the web.xml file and put the red5 config files in the correct place in OPENFIRE_HOME\resources\spank.

           

          If you know your way around servlets, then you would know what to do, otherwise, forget Redfire and simply install your own red5 server on your openfire server box.

More Like This

  • Retrieving data ...

Incoming Links

Bookmarked By (0)

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points