![]() I cannot fully test the Openfire implementation with the newer code as IĪt home. I have bodged that and just ignored the third parameter for Version and two parameters in the jitsi source (the Configuration manager Slightly different from a source perspective to that which is available At this stage I don't know if I have broken the videobridge orĪwry in the bridge itself and the way it links to JSON/REST. Github which enables it to work with javascript AJAX functions) to work The question then is what to use as the XMPP client for a video conference.Īs part of trying to get the Videobridge to work with REST I have decided OpenFire on windows, but not as a plugin. Is there anything current that I can make the Videobridge work using XMPP onĪlternatively if there is a way of making the current videobridge work with Problem exchanging iqs or something through the muc there, but I think Tried it personally but I think it should work. And I think jitsi-meet should work with that, I haven't You can connect videobridge and jicofo to openfire as externalĬomponents. The question then is what to use as the XMPP client for a video conference. Is there anything current that I can make the Videobridge work using XMPP on Windows?ĪIUI Prosody does not really work with Windows.Īlternatively if there is a way of making the current videobridge work with OpenFire on windows, but not as a plugin. Where could I find the code for videobridge that is compatible with theĭev mailing instructions and other list options: What this tells me is that there is more incompatible source which is out of However, when I run OfMeet it now does load the plugin (previously thatįailed), but gives an error message which a null pointer in the focus ![]() I will, therefore, be able to test this on Monday from my The children are currently playing Minecraft and I will take them I cannot fully test the Openfire implementation with the newer code as I amĪt home. ![]() I have bodged that and just ignored the third parameter for now. Version and two parameters in the jitsi source (the Configuration manager is PluginImpl.initializePlugin in the OpenFire In particular there is a three parameter method in Slightly different from a source perspective to that which is available via I have discovered that the version available from the OpenFire website is That has a goodly few hours work so I am leaving itįor now if I can find a way of getting things to work first. Working on a java link to the bridge because that should work with theīinaries from jitsi. Is my JSON or SDP that are wrong or indeed if there is something slightlyĪwry in the bridge itself and the way it links to JSON/REST. At this stage I don't know if I have broken the videobridge or it Github which enables it to work with javascript AJAX functions) to work with Try to get the version I am working on (with the amendment I have put on Latest source which can be easily updated with latest versions.Īs part of trying to get the Videobridge to work with REST I have decided to There is currently on going work for new jitsi-meet plugin unsing Which version is that and the bridge significantly changed since then. Years old videobridge, it was a fork back in late 2014, I'm not sure If you are talking about the videobridge in ofmeet, this is almost 3 Where could I find the code for videobridge that is compatible with the current plugin version of OpenFire? What this tells me is that there is more incompatible source which is out of phase. However, when I run OfMeet it now does load the plugin (previously that failed), but gives an error message which a null pointer in the focus message and the focus goes wrong. ![]() I will, therefore, be able to test this on Monday from my office. The children are currently playing Minecraft and I will take them to the park soon. I cannot fully test the Openfire implementation with the newer code as I am at home. In particular there is a three parameter method in .PluginImpl.initializePlugin in the OpenFire version and two parameters in the jitsi source (the Configuration manager is missing). I have discovered that the version available from the OpenFire website is slightly different from a source perspective to that which is available via jitsi. That has a goodly few hours work so I am leaving it for now if I can find a way of getting things to work first. I may start working on a java link to the bridge because that should work with the binaries from jitsi. At this stage I don't know if I have broken the videobridge or it is my JSON or SDP that are wrong or indeed if there is something slightly awry in the bridge itself and the way it links to JSON/REST. As part of trying to get the Videobridge to work with REST I have decided to try to get the version I am working on (with the amendment I have put on Github which enables it to work with javascript AJAX functions) to work with OpenFire.
0 Comments
Leave a Reply. |