Jigasi failing to dial

Hi @damencho
Thank you for responding so fast.

I’m using Letsencrypt Certificat

I tested the SIP config you advised me. After applying it the SIP link between Jitsi server and my FreePBX was not coming up. I had to add the following to bring the link up

net.java.sip.communicator.impl.protocol.sip.acc1403273890647.SERVER_PORT=5160
net.java.sip.communicator.impl.protocol.sip.acc1403273890647.PROXY_ADDRESS=voice.my.domain.com
net.java.sip.communicator.impl.protocol.sip.acc1403273890647.PROXY_PORT=5160
net.java.sip.communicator.impl.protocol.sip.acc1403273890647.PROXY_ADDRESS_VALIDATED=true
net.java.sip.communicator.impl.protocol.sip.acc1403273890647.PROXY_AUTO_CONFIG=false
net.java.sip.communicator.impl.protocol.sip.acc1403273890647.PREFERRED_TRANSPORT=udp

After that when I dialout any number there is no message in jicofo and jigasi log. But on browser console I see the following error

I’m attaching also the SIP Propreties and the Jigasi log during systemctl restat jigasi.
sip-communicator.txt (14.8 KB)
Registration_Ok_With_FreePBX.txt (44.9 KB)

Kindly can you help?
Thank you

Service unavailable means that jicofo does not see any jigasi, any errors in the logs for problems joining the muc control(brewery) room?

When I tail -f below the output ,
tail -f /var/log/jitsi/jicofo.log
Jicofo 2021-01-19 11:44:02.846 INFO: [76] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Joining the room: hamadou@conference.meet.my.domain.com
Jicofo 2021-01-19 11:44:03.575 INFO: [78] org.jitsi.jicofo.xmpp.IqHandler.log() Logout IQ received:
Jicofo 2021-01-19 11:44:03.576 INFO: [78] org.jitsi.jicofo.xmpp.ConferenceIqHandler.log() Focus request for room: hamadou@conference.meet.my.domain.com
Jicofo 2021-01-19 11:44:03.576 INFO: [78] org.jitsi.jicofo.auth.AbstractAuthAuthority.log() Authenticated jid: q_hmbxthdunqgoos@guest.meet.my.domain.com/1oinlqHf with session: AuthSession[ID=nexttel@meet.my.domain.com, JID=q_hmbxthdunqgoos@guest.meet.my.domain.com/1oinlqHf, SID=17d7b737-683c-4ab4-baf7-649d0c6c5df6, MUID=ea9afb8e9aef8e4e4c382c781a5e7d99, LIFE_TM_SEC=0, R=hamadou@conference.meet.my.domain.com]@2010175365
Jicofo 2021-01-19 11:44:03.577 INFO: [78] org.jitsi.jicofo.auth.AbstractAuthAuthority.log() Jid q_hmbxthdunqgoos@guest.meet.my.domain.com/1oinlqHf authenticated as: nexttel@meet.my.domain.com
Jicofo 2021-01-19 11:44:03.813 INFO: [31] org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Chat room event ChatRoomMemberPresenceChangeEvent[type=MemberJoined sourceRoom=org.jitsi.impl.protocol.xmpp.ChatRoomImpl@5faabcea member=ChatMember[hamadou@conference.meet.my.domain.com/e1d340cd, jid: null]@1156508215]
Jicofo 2021-01-19 11:44:03.814 WARNING: [31] org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2021-01-19 11:44:03.820 INFO: [31] org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Obtained focus role: OWNER
Jicofo 2021-01-19 11:44:03.827 INFO: [31] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Member hamadou@conference.meet.my.domain.com/e1d340cd joined.
Jicofo 2021-01-19 11:45:05.143 INFO: [18] org.jitsi.jicofo.auth.AbstractAuthAuthority.log() Expiring session:AuthSession[ID=nexttel@meet.my.domain.com, JID=q_hmbxthdunqgoos@guest.meet.my.domain.com/1oinlqHf, SID=17d7b737-683c-4ab4-baf7-649d0c6c5df6, MUID=ea9afb8e9aef8e4e4c382c781a5e7d99, LIFE_TM_SEC=61, R=hamadou@conference.meet.my.domain.com]@2010175365

But when I try to dial out, there no message in jicofo.log

You need to check jigasi logs on startup when it tries to connect to the brewery room

Thank you for your reply. I attach the log after doing systemctl restart jigasi.
Is it that log you were refering to?
jigasi_restart.txt (44.9 KB)

Best Regards

It looks like wrong password for the user in the xmpp config part of jigasi. Is it added as base64?

Sorry it’s my error
In the config you advised I didn’t modify these lines

If you want jigasi to perform authenticated login instead of anonymous login

to the XMPP server, you can set the following properties.

org.jitsi.jigasi.xmpp.acc.USER_ID=SOME_USER@SOME_DOMAIN

org.jitsi.jigasi.xmpp.acc.PASS=SOME_PASS

org.jitsi.jigasi.xmpp.acc.ANONYMOUS_AUTH=false

Let me do that and come back
Thanks again

Not that password.

This one is wrong: jigasi/sip-communicator.properties at b7423fad61beccab18728e05358b4e7a69702eff · jitsi/jigasi · GitHub

Ok
There i put the Password that I created Jigasi user with command

sudo prosodyctl register user meet.mydomain password
then I converted the password online to bas64 using this link: https://www.base64encode.org/

Still same problem.
Which password should I put there? is it the one created by

sudo prosodyctl register user meet.mydomain password ?

Thanks

If you have created the user the command would be:

prosodyctl adduser jigasi@auth.meet.mydomain

Thank you @damencho

I have a good progress now, I changed the password with one on sip propritues backup I save and now I don’t have anymore error on start

Now when I place a call there is output on jigasi log with below errors

2021-01-19 16:20:13.947 SEVERE: [107] org.jitsi.jigasi.JvbConference.registrationStateChanged().688 [ctx=1611091213865845496454] XMPP Connection failed.
2021-01-19 16:20:13.947 WARNING: [107] org.jitsi.jigasi.JvbConference.leaveConferenceRoom().1115 [ctx=1611091213865845496454] MUC room is null
2021-01-19 16:20:18.872 SEVERE: [103] org.jitsi.jigasi.xmpp.CallControlMucActivator.processIQ().589 Error processing RayoIq

Please can you help?
Thanks

Now the other xmpp account cannot connect for some reason which is not obvious from these particial logs.

Let me delete all the account and uninstall and install jigasi, then apply the sip propreties you advised earlier. then I will keep the password on the generated sip properties during installation.

Thanks again

Hi @damencho
I did a fresh installation of Jigasi, the SIP link is UP but when I call it’s failed.
Any idea?
I put the log in attach. what ever the SIP properties I used the result is the same
Best Regards

Have you configured secure domain?

Yes I did. Should deactivate it?

Have you configured auth and for jigasi? jigasi/sip-communicator.properties at b7423fad61beccab18728e05358b4e7a69702eff · jitsi/jigasi · GitHub

I didn’t activate before you message. Now I activate it and reload jigasi, jvb and jicofo but still given me some error in attach
Thanks
after_activation_jigasi_user.txt (4.4 KB)

What is the co fig you added … Seems wrong …