Thanks for the kind words and suggestions 
.
- Increase stability. The jitsivideobridge plugin is quite new. I'm confident that stability will increase with each new version
I can't take credit for jitsi videobridge plugin. That is for Emil Ivov and the jitsi.org project. I am just making their great work is accessible to us here at ignite realtime, ensuring that multi-user video is available to all our projects. As they improve the base software, you will see it in the openfire plugin.
I personally use ofmeet for video meetings and it is for most of the time, stable for me when used from my network at home. A lot depends on your network and the network of all participants in the conference. That is why Google hangouts is still usng a propietary system and not yet webrtc they created.
- Support of other browser like Firefox. On http://mozilla.github.io/webrtc-landing/ it seems as if newer Firefox versions are WebRTC capable, although I don't know any details of implementation.
As far as I know, Firefox does not yet support multiple SSRCs (video streams) in the same peerconnection.
- Support of native Clients like Jitsi. Having a browser capable video conference is great, but of course it would be nice if you could use your already video capable XMPP client as well.
JitMeet is compatible with the the Jitsi client. They both use jingle to signal the conference and should work fine. Try it.
- Configurable video image size/bandwidth limits: currently the standard resolution in config.js is "360". Although this is a reasonable setting there might be cases where want to alter this setting without the need to change this setting to higher (=better quality) or lower (=saves bandwidth) settings per conference or even for every connecting user. This might apply to refresh rates as well.
As far as I know, bandwidth management is not yet implemented in Chrome webrtc implementation. When is is available then we can make use of the video/audio contraints set in the config.js.
- IPv6 support: at the moment config.js says "useIPv6: false, // ipv6 support. use at your own risk". IPv6 is a well established standard today and every application should support it out of the box.
That is all down to the Google Chrome browser. IPv6 support for webrtc is still expermimental and not availble in production release yet.