When i try to do a video call, prosody issues a warning
bosha67b1ca4-cf64-40f7-aba8-de4974004a82 warn No available SASL mechanisms, verify that the configured authentication module is working
Also, i dont see a call being made to the UVS running on 192.168.50.19.
Any idea what could be the issue?
Here is the full log
Jun 26 23:53:18 startup info Hello and welcome to Prosody version 0.11.9
Jun 26 23:53:18 startup info Prosody is using the select backend for connection handling
Jun 26 23:53:18 general info Starting speakerstats for conference.meet.myserver.com
Jun 26 23:53:18 speakerstats.meet.myserver.com:speakerstats_component info No muc component found, will listen for it: conference.meet.myserver.com
Jun 26 23:53:18 speakerstats.meet.myserver.com:tls info Certificates loaded
Jun 26 23:53:18 portmanager info Activated service 's2s' on [*]:5269, [::]:5269
Jun 26 23:53:18 focus.meet.myserver.com:tls info Certificates loaded
Jun 26 23:53:18 portmanager info Activated service 'c2s' on [*]:5222, [::]:5222
Jun 26 23:53:18 portmanager info Activated service 'legacy_ssl' on no ports
Jun 26 23:53:18 auth.meet.myserver.com:tls info Certificates loaded
Jun 26 23:53:18 localhost:tls info Certificates loaded
Jun 26 23:53:18 meet.myserver.com:auth_matrix_user_verification info uvs_base_url = http://192.168.50.19:3000
Jun 26 23:53:18 meet.myserver.com:auth_matrix_user_verification info No uvs_auth_token supplied, not sending authentication headers
Jun 26 23:53:18 meet.myserver.com:auth_matrix_user_verification info uvsSyncPowerLevels = false
Jun 26 23:53:18 portmanager info Activated service 'http' on [*]:5280, [::]:5280
Jun 26 23:53:18 portmanager info Activated service 'https' on no ports
Jun 26 23:53:18 meet.myserver.com:tls info Certificates loaded
Jun 26 23:53:18 internal.auth.meet.myserver.com:tls info Certificates loaded
Jun 26 23:53:18 conference.meet.myserver.com:tls info Certificates loaded
Jun 26 23:53:18 conference.meet.myserver.com:token_verification error 'app_secret' or 'asap_key_server' must be specified
Jun 26 23:53:18 conference.meet.myserver.com:muc_domain_mapper info Loading mod_muc_domain_mapper for host auth.meet.myserver.com!
Jun 26 23:53:18 conference.meet.myserver.com:muc_domain_mapper info Loading mod_muc_domain_mapper for host localhost!
Jun 26 23:53:18 conference.meet.myserver.com:muc_domain_mapper info Loading mod_muc_domain_mapper for host speakerstats.meet.myserver.com!
Jun 26 23:53:18 conference.meet.myserver.com:muc_domain_mapper info Loading mod_muc_domain_mapper for host internal.auth.meet.myserver.com!
Jun 26 23:53:18 conference.meet.myserver.com:muc_domain_mapper info Loading mod_muc_domain_mapper for host conference.meet.myserver.com!
Jun 26 23:53:18 conference.meet.myserver.com:muc_domain_mapper info Loading mod_muc_domain_mapper for host focus.meet.myserver.com!
Jun 26 23:53:18 conference.meet.myserver.com:muc_domain_mapper info Loading mod_muc_domain_mapper for host meet.myserver.com!
Jun 26 23:53:18 speakerstats.meet.myserver.com:speakerstats_component info Hook to muc events on conference.meet.myserver.com
Jun 26 23:53:18 general info Starting conference duration timer for conference.meet.myserver.com
Jun 26 23:53:18 conferenceduration.meet.myserver.com:conference_duration_component info Hook to muc events on conference.meet.myserver.com
Jun 26 23:53:18 conferenceduration.meet.myserver.com:tls info Certificates loaded
Jun 26 23:53:18 conference.meet.myserver.com:muc_domain_mapper info Loading mod_muc_domain_mapper for host conferenceduration.meet.myserver.com!
Jun 26 23:53:18 guest.meet.myserver.com:auth_token error 'app_id' must not be empty
Jun 26 23:53:18 guest.meet.myserver.com:tls info Certificates loaded
Jun 26 23:53:18 conference.meet.myserver.com:muc_domain_mapper info Loading mod_muc_domain_mapper for host guest.meet.myserver.com!
Jun 26 23:53:21 c2s563765b1ddc0 info Client connected
Jun 26 23:53:21 c2s563765b1ddc0 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
Jun 26 23:53:21 c2s563765b1ddc0 info Authenticated as focus@auth.meet.myserver.com
Jun 26 23:53:21 c2s563765b83900 info Client connected
Jun 26 23:53:21 c2s563765b83900 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
Jun 26 23:53:21 c2s563765b83900 info Authenticated as jvb@auth.meet.myserver.com
Jun 26 23:53:33 mod_bosh info New BOSH session, assigned it sid 'dd96ebbc-5f4c-4283-b726-c661168138bf'
Jun 26 23:53:33 boshdd96ebbc-5f4c-4283-b726-c661168138bf warn No available SASL mechanisms, verify that the configured authentication module is working
Hello,
I have setup the prosody config to be like so,
When i try to do a video call, prosody issues a warning
bosha67b1ca4-cf64-40f7-aba8-de4974004a82 warn No available SASL mechanisms, verify that the configured authentication module is working
Also, i dont see a call being made to the UVS running on 192.168.50.19.
Any idea what could be the issue?
Here is the full log