Jigasi unable to reach default room. how to check registering?

Install & Config
#1

Hi,
I’m very pleased with my Authenitcated Jitsi with a functionning Jibri and working for restricted firewall clients or not.

The next step is getting Jigasi working.

So I have a Jitisi/Jicofo/Jibri on an Ubuntu 18.04. everything works very well.
Then I installed Jigasi using debian package installation with this command :
apt install jigasi
Till this there is no issue.

Then I edited /etc/prosody/prosody.cfg.lua and append following lines :

Component "callcontrol.mysite.org"
    component_secret = "vjqvbjdfk"

Not sure it was necessary as I found they were already added in /etc/prosody/conf.avail/mysite.org.cfg.lua but in one line like this :

Component "callcontrol.mysite.org" component_secret = "vjqvbjdfk"

I edited and checked the infos in the following lines :

net.java.sip.communicator.impl.protocol.sip.acc1403273896546=acc1403273896546
net.java.sip.communicator.impl.protocol.sip.acc1403273896546.ACCOUNT_UID=SIP\:5500@3cx-mysite.my3cx.fr
net.java.sip.communicator.impl.protocol.sip.acc1403273896546.PASSWORD=cWiXRDlGM3J6Mq==
net.java.sip.communicator.impl.protocol.sip.acc1403273896546.PROTOCOL_NAME=SIP
net.java.sip.communicator.impl.protocol.sip.acc1403273896546.SERVER_ADDRESS=3cx-mysite.my3cx.fr
net.java.sip.communicator.impl.protocol.sip.acc1403273896546.USER_ID=5500@3cx-mysite.my3cx.fr

and added the following line :

net.java.sip.communicator.impl.protocol.sip.acc1403273896546.AUTHORIZATION_NAME=B5wIdfui

like suggested in the following post as I’m using 3cx : Jigasi with 3CX ipbx

I also uncommented and configured these lines :

org.jitsi.jigasi.xmpp.acc.USER_ID=visiter@mysite.org
org.jitsi.jigasi.xmpp.acc.PASS=visiterdefaultpass
org.jitsi.jigasi.xmpp.acc.ANONYMOUS_AUTH=false

Then I modified the config.js and uncommented this line :

call_control: 'callcontrol.mysite.org',

I checked the following line :

/etc/jitsi/jigasi/sip-communicator.properties:org.jitsi.jigasi.DEFAULT_JVB_ROOM_NAME=siptest

I restarted the server.

In the interface I can now see the “+” to invite people by phone even if regarding the config I have done I’m not yet able to launch the call from jitsi-meet.

in the JS console I see :

2020-04-29T09:24:31.042Z [modules/xmpp/moderator.js] <u.parseConfigOptions>:  Sip gateway enabled:  true

As far as I understand this would mean that everyhting is OK.

But I’m unable to reach the default room : https://mysite.org/siptest by phone.

The Ipbx send me to the messagebox as there were no user registred.

Any Idea of what’s happening? There is nothing in Jagasi log that make reference to : 3cx-mysite.my3cx.fr

I don’t see any connection to this site in tcpdump.

May be I don’t look at the good place to check these kind of things.

Any help would be very appreciated. Many thanks by advance for your help.

#2

Hi,

And this is the kind of error I got in the JS console when I try to invite someone from jitsi :

2020-04-30T07:53:58.950Z [modules/xmpp/strophe.rayo.js] Dial error
<iq xmlns=​"jabber:​client" type=​"error" to=​"51f52155-d506-4a81-9468-f59091e59911@guest.mysite.org/​e0b6bf86-110a-4c61-b9d7-798f2b70b81a" from=​"siptest@conference.mysite.org/​focus" id=​"97d8c996-44fe-4182-8f36-c6e8c4b36ec8:​sendIQ">​
	<error type=​"cancel">​
<service-unavailable xmlns=​"urn:​ietf:​params:​xml:​ns:​xmpp-stanzas">​</service-unavailable>​
</error>​</iq>​
Logger.js:154 
2020-04-30T07:53:58.950Z [features/invite] Error inviting phone number:
<iq xmlns=​"jabber:​client" type=​"error" to=​"51f52155-d506-4a81-9468-f59091e59911@guest.mysite.org/​e0b6bf86-110a-4c61-b9d7-798f2b70b81a" from=​"siptest@conference.mysite.org/​focus" id=​"97d8c996-44fe-4182-8f36-c6e8c4b36ec8:​sendIQ">​…​</iq>​
o @ app.bundle.min.js?v=4025:126
Logger.js:154 2020-04-30T07:53:58.961Z [features/invite] 1 invites failed Object
o @ app.bundle.min.js?v=4025:126

Thanks by advance for any help.

#3

Hi So I made it works. youhou. I don’t know how : bouhhh!

But if I restart the server, I have then to restart jigasi to get the functionality and even like that sometime is does not work.

Any idea of what’s going wrong?

#4

Regarding the Jigasi logs, When server is restarted Jigasi service does not try to register or at least not always. And even restarting the server does not force a registering attempt or it does not appear in /var/log/jitsi/jigasi.log.

Any idea of what could going wrong of how to force the registering attempt?

#5

I have 3 errors in Jigasi log file may be it’s related :

2020-05-01 18:17:41.957 SEVERE: [10] impl.configuration.ConfigurationActivator.log() Error creating c lib instance for fixing file permissions
java.nio.file.FileSystemException: /etc/jitsi/jigasi: Operation not permitted
...
2020-05-01 18:17:42.430 WARNING: [10] impl.sysactivity.SystemActivityNotifications.<clinit>().141 Failed to initialize native counterpart
java.lang.UnsatisfiedLinkError: /tmp/jna--1160142225/jna8093420225095110666.tmp: libgdk-x11-2.0.so.0: cannot open shared object file: No such file or directory
...
2020-05-01 18:17:43.128 SEVERE: [10] org.jitsi.impl.neomedia.device.DeviceConfiguration.log() Failed to register custom Renderer org.jitsi.impl.neomedia.jmfext.media.renderer.audio.PulseAudioRenderer with JMF.

Many thanks by advance for any provided help.