> For the complete documentation index, see [llms.txt](https://help.sipgate.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sipgate.de/trunking/en/wie-registriere-ich-jitsi-meet-mit-sipgate-trunking.md).

# How do I register Jitsi Meet with sipgate trunking?

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](https://github.com/jitsi/jigasi) – 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`

{% stepper %}
{% step %}

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

**➔ hosts.call\_control** must be set to callcontrol.$JITSI\_URL
{% endstep %}

{% step %}

#### 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
```

{% hint style="info" %}
**Note:** Dynamic mapping is not yet supported by sipgate.
{% endhint %}

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

```properties
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
```

{% hint style="info" %}
**Note:** The password must be Base64 encoded and cannot simply be copied here. The identifier in the example "acc1403273890647" may differ.
{% endhint %}
{% endstep %}

{% step %}

#### 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](https://github.com/jitsi/jigasi#call-control-mucs-brewery).
{% endstep %}

{% step %}

#### Configuration file: `/etc/jitsi/jigasi/config`

The SIP data must also be entered in this configuration.

The password must also be Base64 encoded.

```properties
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
```

{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.sipgate.de/trunking/en/wie-registriere-ich-jitsi-meet-mit-sipgate-trunking.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.