How do I register Jitsi Meet with sipgate trunking?

Instructions for configuring Jitsi Meet with sipgate trunking for outgoing calls.

The video conferencing software Jitsi can be configured for outgoing calls with sipgate trunking. Calls are then made from the Jitsi web interface. The resulting costs are billed through your trunking account. Therefore, we recommend protecting your account from misuse by third parties.

Limitations:

• At least one person must be part of the conference via the web so that the caller can invite people into the conference.

• The setup was tested with a sipgate trunking account. All configurations refer to this setup. With other sipgate products, problems may occur due to a bug in Jigasi.

Prerequisite:

A prerequisite for the configuration is access to the configuration files and the ability to install additional packages on the system.

Install the Jigasi package – it is a SIP adapter for Jitsi Meet. After the configuration, Jigasi must be restarted so that the changes take effect. After that, the trunk should also be shown as Online in the sipgate frontend.

The configuration:

Configure the following files with a text editor of your choice.

• /etc/jitsi/jigasi/sip-communicator.properties

• /etc/jitsi/jigasi/config

• /etc/jitsi/meet/$JITSI_URL-config.js

1

Configuration file: /etc/jitsi/meet/$JITSI_URL-config.js

➔ hosts.call_control must be set to callcontrol.$JITSI_URL

2

Configuration file: /etc/jitsi/jigasi/sip-communicator.properties

specify a default room in which the caller can be connected. To do this, adjust the properties as follows:

org.jitsi.jigasi.DEFAULT_JVB_ROOM_NAME

Example:

org.jitsi.jigasi.DEFAULT_JVB_ROOM_NAME=RoomName

Note: Dynamic mapping is not yet supported by sipgate.

In addition, data for the account such as the following example must be stored:

net.java.sip.communicator.impl.protocol.sip.acc1403273890647=acc1403273890647
net.java.sip.communicator.impl.protocol.sip.acc1403273890647.ACCOUNT_UID=sipgate_trunking
net.java.sip.communicator.impl.protocol.sip.acc1403273890647.PASSWORD=Base64 encoded password (echo -n <PW> | base64)
net.java.sip.communicator.impl.protocol.sip.acc1403273890647.PROTOCOL_NAME=SIP
net.java.sip.communicator.impl.protocol.sip.acc1403273890647.SERVER_ADDRESS=sipconnect.sipgate.de
net.java.sip.communicator.impl.protocol.sip.acc1403273890647.USER_ID=<t Textension>
net.java.sip.communicator.impl.protocol.sip.acc1403273890647.KEEP_ALIVE_INTERVAL=25
net.java.sip.communicator.impl.protocol.sip.acc1403273890647.KEEP_ALIVE_METHOD=OPTIONS
net.java.sip.communicator.impl.protocol.sip.acc1403273890647.VOICEMAIL_ENABLED=false
net.java.sip.communicator.impl.protocol.sip.acc1403273890647.Encodings.G722/8000=700
net.java.sip.communicator.impl.protocol.sip.acc1403273890647.Encodings.PCMA/8000=600
net.java.sip.communicator.impl.protocol.sip.acc1403273890647.Encodings.opus/48000=1000
net.java.sip.communicator.impl.protocol.sip.acc1403273890647.Encodings.telephone-event/8000=1
net.java.sip.communicator.impl.protocol.sip.acc1403273890647.OVERRIDE_ENCODINGS=true
net.java.sip.communicator.impl.protocol.sip.acc1403273890647.DEFAULT_ENCRYPTION=false

Note: The password must be Base64 encoded and cannot simply be copied here. The identifier in the example "acc1403273890647" may differ.

3

Configure outgoing calls and XMPP

For outgoing calls, the callcontrol XMPP component must be configured. In addition, an XMPP account is required to authenticate with the XMPP server.

Here you will find an overview, of what the configuration should look like.

4

Configuration file: /etc/jitsi/jigasi/config

The SIP data must also be entered in this configuration.

The password must also be Base64 encoded.

JIGASI_SIPUSER=<T-Extension>@sipconnect.sipgate.de
JIGASI_SIPPWD=Base64 encoded password (echo -n <PW> | base64)
JIGASI_SECRET=Base64 encoded password (echo -n <PW> | base64)
JIGASI_OPTS=""
JIGASI_HOSTNAME=<hostname>
JIGASI_HOST=localhost