Stun server settings in ofmeet plugins
ClaudeStabile opened this issue · 7 comments
Jitsi Meet does not use that parameter any more. It now supports XEP 0215
I must remember to remove it. You have to use the the External Service Discovery plugin for Openfire instead
I have also created a TURN server plugin for Openfire using the Pion Project
Dele,
Thanks i manage to make it work and use my local Stun/return server setting it this way.
I use one external stun server for all my instances, that's fine seem to be all OKI.
For more information
For more details see https://jitsi.github.io/handbook/docs/devops-guide/turn
Closed in error.
Hi @deleolajide
I have also created a TURN server plugin for Openfire using the Pion Project
Great! I was interested and tried this. Would you please tell me how to verify it?
(* We want to use this in an environment where external access is restricted, such as stun: stun.l.google.com.)
Setup is complete as follows. This following log is output, Is there a way to check if the jitsi-meet client is using Pion STUN?
2020.05.28 02:35:50 INFO [Thread-17]: org.ifsoft.turn.openfire.PionTurn - PionTurn onOutputLine Inbound STUN: Binding request l=24 attrs=2 id=6WE0V3IB/hGH6t1j
2020.05.28 02:35:50 INFO [Thread-17]: org.ifsoft.turn.openfire.PionTurn - PionTurn onOutputLine Outbound STUN: Binding success response l=20 attrs=2 id=6WE0V3IB/hGH6t1j
Would you please tell me how to verify it?
See my comments above about using the openfire external services discovery plugin for openfire that implements xep 0215. Jitsi-Meet uses xep 0215
For more details, see https://jitsi.github.io/handbook/docs/devops-guide/turn