Jitsi CallIn via Jigasi and Asterisk not working anymore after update of Jigasi

Hi everyone,

some weeks ago I updated Jigasi to the newest version. After that it was impossible to call in via phone to the Jitsi calls. After reading the logfiles I tried out to change the extension on Asterisk for Jitsi from SIP to PJSIP. And now Jigasi is registering again and is available. But I still have a problem with calling in. The call is answered via Asterisk but not redirected to Jitsi:

[2022-07-01 08:55:10] WARNING[26106][C-00000195] app_dial.c: Unable to create channel of type 'SIP' (cause 20 - Subscriber absent)
[2022-07-01 08:55:10] VERBOSE[26106][C-00000195] app_dial.c: Everyone is busy/congested at this time (1:0/0/1)
[2022-07-01 08:55:10] VERBOSE[26106][C-00000195] pbx.c: Executing [s@Jitsi-Conference-Entry:22] Verbose("PJSIP/Telekom-SIP-Trunk", "0, Contacting 6338... Status is CHANUNAVAIL ") in new stack
[2022-07-01 08:55:10] VERBOSE[26106][C-00000195] app_verbose.c:  Contacting 6338... Status is CHANUNAVAIL

I think the problem is in our extensions_custom.conf where the Jitsi conference mapping is happening. Maybe because this script is too old and only working with SIP and not PJSIP. Has anyone more informations ore a running script?

[Jitsi-Conference-Entry]
exten => s,1,Answer()
;Set the extension used for Jitsi
exten => s,2,Set(Jitsi=6338)
;set variable to prevent looping
exten => s,3,Set(Attempts=0)
exten => s,4,Set(Attempts=${MATH(${Attempts}+1,i)})
;Test for invalid entries. On 4th attempt go to error sub
exten => s,5,ExecIf($["${Attempts}" = "4"]?Gosub(Attempts-Error,s,1))
exten => s,6(begin),NooP()
;system listens for DTMF and sets variable "confid"
;10=MAX DIGITS, 10=timeout
exten => s,n,Read(confid,conf-getpin,10,,,10)
;If blank value, start over
exten => s,n,ExecIf($["${confid}"=""]?goto(Jitsi-Conference-Entry,s,4))
;systems plays back the number entered
; tobi exten => s,n,Playback(you-entered)
; tobi exten => s,n,SayDigits(${confid})
;system asks to press 1 to accept or 2 to retry
; tobi exten => s,n,Read(digi,if-this-is-correct-press&digits/1&otherwise-press&digits/2,1,,1,10)
;If blank value, start over
; tobi exten => s,n,ExecIf($["${digi}"=""]?goto(Jitsi-Conference-Entry,s,4))
;if user presses 1 to confirm, system moves onto to check for passcode, if applicable
; tobi exten => s,n,ExecIf($["${digi}"="1"]?goto(passcode))
;if callers presses any other digit, system will re-ask them to enter in their number
; tobi exten => s,n,goto(Jitsi-Conference-Entry,s,begin)
;CURL Jitsi API with meeting pin & retrieve meeting name as the result
exten => s,n,goto(passcode)
;exten => s,n(passcode),Set(CURL_RESULT=${SHELL(curl --silent https://jitsi.DOMAIN.TLD/conferenceMapper?id=${confid} | sed -e 's/.*"conference":"\(.*\)@.*/\1/')})
exten => s,n(passcode),Set(CURL_RESULT=${SHELL(curl --silent https://jitsi.DOMAIN.TLD/static/conferencemapper.php?id=${confid} | sed -e 's/.*"conference":"\(.*\)@.*/\1/')})
exten => s,n,Verbose(0, ${CURL_RESULT});
;speeding this up for the password, but you could mirror the process above if you want the extra readout and verification...
;system listens for DTMF and sets variable "confpin"
;6=MAX DIGITS, 10=timeout
exten => s,n,Read(confpin,pls-enter-conf-password&vm-then-pound&vm-tocancel,6,,,10)
;pls-enter-conf-password
;User will be sent onto the conference whether confpin is blank or not
exten => s,n,goto(enterconf)
;Add SIP Headers based on caller's entries & CURL result
exten => s,n(enterconf),SIPAddHeader(Jitsi-Conference-Room:${CURL_RESULT})
exten => s,n,Set(HASH(__SIPHEADERS,Jitsi-Conference-Room)=${JITSI})
;Sets CDR "userfield" with the Conference ID
;CDR can now be used to track number of calls and durations associated to the Conference ID
exten => s,n,Set(CDR(userfield)=Jitsi:${CURL_RESULT})
;Record Caller's Name
exten => s,n,Set(__rnum=${RAND()})
exten => s,n,Playback(vm-rec-name)
exten => s,n,Record(/tmp/name-${rnum}.gsm,3,10)
;set spygroup to be used for injecting whisper
exten => s,n,Set(SPYGROUP=1000)
;Dial Jitsi extension and play recorded name to the jitisi conference channel
;3 = seconds to ring , m = play music on hold , A = announcement for dialed channel, M = Macro after call connects
exten => s,n,Dial(SIP/${Jitsi},3,m(silence)A(/tmp/name-${rnum})M(Jitsi-join))
exten => s,n,Verbose(0, Contacting ${Jitsi}... Status is ${DIALSTATUS} );
;Take actions based on dialstatus
exten => s,n,GotoIf($["${DIALSTATUS}" = "BUSY"]?unknown)
;Set the extension used for Jitsi
exten => s,2,Set(Jitsi=6338)
;set variable to prevent looping
exten => s,3,Set(Attempts=0)
exten => s,4,Set(Attempts=${MATH(${Attempts}+1,i)})
;Test for invalid entries. On 4th attempt go to error sub
exten => s,5,ExecIf($["${Attempts}" = "4"]?Gosub(Attempts-Error,s,1))
exten => s,6(begin),NooP()
;system listens for DTMF and sets variable "confid"
;10=MAX DIGITS, 10=timeout
exten => s,n,Read(confid,conf-getpin,10,,,10)
;If blank value, start over
exten => s,n,ExecIf($["${confid}"=""]?goto(Jitsi-Conference-Entry,s,4))
;systems plays back the number entered
; tobi exten => s,n,Playback(you-entered)
; tobi exten => s,n,SayDigits(${confid})
;system asks to press 1 to accept or 2 to retry
; tobi exten => s,n,Read(digi,if-this-is-correct-press&digits/1&otherwise-press&digits/2,1,,1,10)
;If blank value, start over
; tobi exten => s,n,ExecIf($["${digi}"=""]?goto(Jitsi-Conference-Entry,s,4))
;if user presses 1 to confirm, system moves onto to check for passcode, if applicable
; tobi exten => s,n,ExecIf($["${digi}"="1"]?goto(passcode))
;if callers presses any other digit, system will re-ask them to enter in their number
; tobi exten => s,n,goto(Jitsi-Conference-Entry,s,begin)
;CURL Jitsi API with meeting pin & retrieve meeting name as the result
exten => s,n,goto(passcode)
;exten => s,n(passcode),Set(CURL_RESULT=${SHELL(curl --silent https://jitsi.DOMAIN.TLD/conferenceMapper?id=${confid} | sed -e 's/.*"conference":"\(.*\)@.*/\1/')})
exten => s,n(passcode),Set(CURL_RESULT=${SHELL(curl --silent https://jitsi.DOMAIN.TLD/static/conferencemapper.php?id=${confid} | sed -e 's/.*"conference":"\(.*\)@.*/\1/')})
exten => s,n,Verbose(0, ${CURL_RESULT});
;speeding this up for the password, but you could mirror the process above if you want the extra readout and verification...
;system listens for DTMF and sets variable "confpin"
;6=MAX DIGITS, 10=timeout
exten => s,n,Read(confpin,pls-enter-conf-password&vm-then-pound&vm-tocancel,6,,,10)
;pls-enter-conf-password
;User will be sent onto the conference whether confpin is blank or not
exten => s,n,goto(enterconf)
extensions_custom.conf
[Jitsi-Conference-Entry]
exten => s,1,Answer()
;Set the extension used for Jitsi
exten => s,2,Set(Jitsi=6338)
;set variable to prevent looping
exten => s,3,Set(Attempts=0)
exten => s,4,Set(Attempts=${MATH(${Attempts}+1,i)})
;Test for invalid entries. On 4th attempt go to error sub
exten => s,5,ExecIf($["${Attempts}" = "4"]?Gosub(Attempts-Error,s,1))
exten => s,6(begin),NooP()
;system listens for DTMF and sets variable "confid"
;10=MAX DIGITS, 10=timeout
exten => s,n,Read(confid,conf-getpin,10,,,10)
;If blank value, start over
exten => s,n,ExecIf($["${confid}"=""]?goto(Jitsi-Conference-Entry,s,4))
;systems plays back the number entered
; tobi exten => s,n,Playback(you-entered)
; tobi exten => s,n,SayDigits(${confid})
;system asks to press 1 to accept or 2 to retry
; tobi exten => s,n,Read(digi,if-this-is-correct-press&digits/1&otherwise-press&digits/2,1,,1,10)
;If blank value, start over
; tobi exten => s,n,ExecIf($["${digi}"=""]?goto(Jitsi-Conference-Entry,s,4))
;if user presses 1 to confirm, system moves onto to check for passcode, if applicable
; tobi exten => s,n,ExecIf($["${digi}"="1"]?goto(passcode))
;if callers presses any other digit, system will re-ask them to enter in their number
; tobi exten => s,n,goto(Jitsi-Conference-Entry,s,begin)
;CURL Jitsi API with meeting pin & retrieve meeting name as the result
exten => s,n,goto(passcode)
;exten => s,n(passcode),Set(CURL_RESULT=${SHELL(curl --silent https://jitsi.DOMAIN.TLD/conferenceMapper?id=${confid} | sed -e 's/.*"conference":"\(.*\)@.*/\1/')})
exten => s,n(passcode),Set(CURL_RESULT=${SHELL(curl --silent https://jitsi.DOMAIN.TLD/static/conferencemapper.php?id=${confid} | sed -e 's/.*"conference":"\(.*\)@.*/\1/')})
exten => s,n,Verbose(0, ${CURL_RESULT});
;speeding this up for the password, but you could mirror the process above if you want the extra readout and verification...
;system listens for DTMF and sets variable "confpin"
;6=MAX DIGITS, 10=timeout
exten => s,n,Read(confpin,pls-enter-conf-password&vm-then-pound&vm-tocancel,6,,,10)
;pls-enter-conf-password
:...skipping...
exten => s,n,GotoIf($["${DIALSTATUS}" = "NOANSWER"]?conf-busy)
exten => s,n,GotoIf($["${DIALSTATUS}" = "CANCEL"]?unknown)
exten => s,n,GotoIf($["${DIALSTATUS}" = "CONGESTION"]?unknown)
exten => s,n,GotoIf($["${DIALSTATUS}" = "CHANUNAVAIL"]?unknown)
exten => s,n,GotoIf($["${DIALSTATUS}" = "DONTCALL"]?unknown)
exten => s,n,GotoIf($["${DIALSTATUS}" = "TORTURE"]?unknown)
exten => s,n,GotoIf($["${DIALSTATUS}" = "INVALIDARGS"]?unknown)
;Hangup if condition is not matched (in the event a new dialstatus is added with an update
exten => s,n,Hangup()
;Jitsi is not reachable, play error message
;This is also a good place to send an SMS to your lead system admins
exten => s,n(unknown),playback(please-contact-tech-supt&vm-goodbye)
exten => s,n,Hangup()
;Initial attempt was ok, but Jitsi didn't pickup the call.
;It's likely that the host hasn't yet authenticated / started the meeting
;Indicate that we're waiting for the leader to join and keep trying
exten => s,n(conf-busy),Playback(conf-waitforleader)
;120 = seconds to ring , m = play music on hold , A = announcement for dialed channel, M = Macro after call connects
exten => s,n,Dial(SIP/${Jitsi},120,m(default)A(/tmp/name-${rnum})M(Jitsi-join))
exten => s,n,Hangup()

[Attempts-Error]
;system plays message and hangs up
exten => s,1,playback(sorry-youre-having-problems)
exten => s,n,playback(tt-monkeys)
;exten => s,n,playback(hangup-try-again)
exten => s,n,Hangup()

[macro-Jitsi-join]
exten => s,1,Originate(Local/999@JitsiWhisper,app,Playback,confbridge-join)

[JitsiWhisper]
exten => _X.,1,NoCDR
exten => _X.,n,Answer()
exten => _X.,n,ChanSpy(,g(1000),qw)
exten => _X.,n,Hangup()
[root@freepbx asterisk]# cat extensions_custom.conf ^C
[root@freepbx asterisk]# less extensions_custom.conf
[root@freepbx asterisk]# cat extensions_custom.conf
[Jitsi-Conference-Entry]
exten => s,1,Answer()
;Set the extension used for Jitsi
exten => s,2,Set(Jitsi=6338)
;set variable to prevent looping
exten => s,3,Set(Attempts=0)
exten => s,4,Set(Attempts=${MATH(${Attempts}+1,i)})
;Test for invalid entries. On 4th attempt go to error sub
exten => s,5,ExecIf($["${Attempts}" = "4"]?Gosub(Attempts-Error,s,1))
exten => s,6(begin),NooP()
;system listens for DTMF and sets variable "confid"
;10=MAX DIGITS, 10=timeout
exten => s,n,Read(confid,conf-getpin,10,,,10)
;If blank value, start over
exten => s,n,ExecIf($["${confid}"=""]?goto(Jitsi-Conference-Entry,s,4))
;systems plays back the number entered
; tobi exten => s,n,Playback(you-entered)
; tobi exten => s,n,SayDigits(${confid})
;system asks to press 1 to accept or 2 to retry
; tobi exten => s,n,Read(digi,if-this-is-correct-press&digits/1&otherwise-press&digits/2,1,,1,10)
;If blank value, start over
; tobi exten => s,n,ExecIf($["${digi}"=""]?goto(Jitsi-Conference-Entry,s,4))
;if user presses 1 to confirm, system moves onto to check for passcode, if applicable
; tobi exten => s,n,ExecIf($["${digi}"="1"]?goto(passcode))
;if callers presses any other digit, system will re-ask them to enter in their number
; tobi exten => s,n,goto(Jitsi-Conference-Entry,s,begin)
;CURL Jitsi API with meeting pin & retrieve meeting name as the result
exten => s,n,goto(passcode)
;exten => s,n(passcode),Set(CURL_RESULT=${SHELL(curl --silent https://jitsi.DOMAIN.TLD/conferenceMapper?id=${confid} | sed -e 's/.*"conference":"\(.*\)@.*/\1/')})
exten => s,n(passcode),Set(CURL_RESULT=${SHELL(curl --silent https://jitsi.DOMAIN.TLD/static/conferencemapper.php?id=${confid} | sed -e 's/.*"conference":"\(.*\)@.*/\1/')})
exten => s,n,Verbose(0, ${CURL_RESULT});
;speeding this up for the password, but you could mirror the process above if you want the extra readout and verification...
;system listens for DTMF and sets variable "confpin"
;6=MAX DIGITS, 10=timeout
exten => s,n,Read(confpin,pls-enter-conf-password&vm-then-pound&vm-tocancel,6,,,10)
;pls-enter-conf-password
;User will be sent onto the conference whether confpin is blank or not
exten => s,n,goto(enterconf)
;Add SIP Headers based on caller's entries & CURL result
exten => s,n(enterconf),SIPAddHeader(Jitsi-Conference-Room:${CURL_RESULT})
exten => s,n,Set(HASH(__SIPHEADERS,Jitsi-Conference-Room)=${JITSI})
;Sets CDR "userfield" with the Conference ID
;CDR can now be used to track number of calls and durations associated to the Conference ID
exten => s,n,Set(CDR(userfield)=Jitsi:${CURL_RESULT})
;Record Caller's Name
exten => s,n,Set(__rnum=${RAND()})
exten => s,n,Playback(vm-rec-name)
exten => s,n,Record(/tmp/name-${rnum}.gsm,3,10)
;set spygroup to be used for injecting whisper
exten => s,n,Set(SPYGROUP=1000)
;Dial Jitsi extension and play recorded name to the jitisi conference channel
;3 = seconds to ring , m = play music on hold , A = announcement for dialed channel, M = Macro after call connects
exten => s,n,Dial(SIP/${Jitsi},3,m(silence)A(/tmp/name-${rnum})M(Jitsi-join))
exten => s,n,Verbose(0, Contacting ${Jitsi}... Status is ${DIALSTATUS} );
;Take actions based on dialstatus
exten => s,n,GotoIf($["${DIALSTATUS}" = "BUSY"]?unknown)
exten => s,n,GotoIf($["${DIALSTATUS}" = "NOANSWER"]?conf-busy)
exten => s,n,GotoIf($["${DIALSTATUS}" = "CANCEL"]?unknown)
exten => s,n,GotoIf($["${DIALSTATUS}" = "CONGESTION"]?unknown)
exten => s,n,GotoIf($["${DIALSTATUS}" = "CHANUNAVAIL"]?unknown)
exten => s,n,GotoIf($["${DIALSTATUS}" = "DONTCALL"]?unknown)
exten => s,n,GotoIf($["${DIALSTATUS}" = "TORTURE"]?unknown)
exten => s,n,GotoIf($["${DIALSTATUS}" = "INVALIDARGS"]?unknown)
;Hangup if condition is not matched (in the event a new dialstatus is added with an update
exten => s,n,Hangup()
;Jitsi is not reachable, play error message
;This is also a good place to send an SMS to your lead system admins
exten => s,n(unknown),playback(please-contact-tech-supt&vm-goodbye)
exten => s,n,Hangup()
;Initial attempt was ok, but Jitsi didn't pickup the call.
;It's likely that the host hasn't yet authenticated / started the meeting
;Indicate that we're waiting for the leader to join and keep trying
exten => s,n(conf-busy),Playback(conf-waitforleader)
;120 = seconds to ring , m = play music on hold , A = announcement for dialed channel, M = Macro after call connects
exten => s,n,Dial(SIP/${Jitsi},120,m(default)A(/tmp/name-${rnum})M(Jitsi-join))
exten => s,n,Hangup()

[Attempts-Error]
;system plays message and hangs up
exten => s,1,playback(sorry-youre-having-problems)
exten => s,n,playback(tt-monkeys)
;exten => s,n,playback(hangup-try-again)
exten => s,n,Hangup()

[macro-Jitsi-join]
exten => s,1,Originate(Local/999@JitsiWhisper,app,Playback,confbridge-join)

[JitsiWhisper]
exten => _X.,1,NoCDR
exten => _X.,n,Answer()
exten => _X.,n,ChanSpy(,g(1000),qw)
exten => _X.,n,Hangup()

Sounds like jigasi is not registered to sip, checkout jigasi logs.

Asterisk says jigasi is registered. And the logfiles too:

2022-07-01 08:29:23.984 INFO: [34] SipGateway.registrationStateChanged#120: REG STATE CHANGE ProtocolProviderServiceSipImpl(SIP:6338@asterisk.domain.tld) -> RegistrationStateChangeEvent[ oldState=Unregistered; newState=RegistrationState=Registering; userRequest=false; reasonCode=-1; reason=null]
2022-07-01 08:29:24.146 INFO: [50] SipGateway.registrationStateChanged#120: REG STATE CHANGE ProtocolProviderServiceSipImpl(SIP:6338@asterisk.domain.tld) -> RegistrationStateChangeEvent[ oldState=Registering; newState=RegistrationState=Registered; userRequest=false; reasonCode=-1; reason=null]
2022-07-01 08:29:39.255 INFO: [36] SipGateway.registrationStateChanged#120: REG STATE CHANGE ProtocolProviderServiceSipImpl(SIP:6338@asterisk.domain.tld) -> RegistrationStateChangeEvent[ oldState=Unregistered; newState=RegistrationState=Registering; userRequest=false; reasonCode=-1; reason=null]
2022-07-01 08:29:39.376 INFO: [52] SipGateway.registrationStateChanged#120: REG STATE CHANGE ProtocolProviderServiceSipImpl(SIP:6338@asterisk.domain.tld) -> RegistrationStateChangeEvent[ oldState=Registering; newState=RegistrationState=Registered; userRequest=false; reasonCode=-1; reason=null]

If I search deeper in the forum I can found that the problem could be that we use SIP commands in the script and not PJSIP commands and that

exten => s,n(enterconf),SIPAddHeader(Jitsi-Conference-Room:${CURL_RESULT})

is deprecated and not used in PJSIP anymore. But currently now I was not able to rewrite the whole script to PJSIP that it is working. Maybe someone has a working script?

Here is the whole jigasi.log after the restart of jigasi. For me there is no error regarding jigasi and SIP. Or does I overview something?

2022-07-01 10:09:54.197 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator org.jitsi.service.libjitsi.LibJitsiActivator in file:/usr/share/jigasi/lib/libjitsi-1.1-16-g6a8b9363.jar
2022-07-01 10:09:54.228 INFO: [16] LibJitsi.start#213: Successfully started LibJitsi using as implementation: org.jitsi.impl.libjitsi.LibJitsiOSGiImpl
2022-07-01 10:09:54.238 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator net.java.sip.communicator.impl.configuration.ConfigurationActivator in file:/usr/share/jigasi/lib/jitsi-configuration-2.14.8fd5f3861.jar
2022-07-01 10:09:54.262 INFO: [16] net.java.sip.communicator.util.osgi.DependentActivator.start: Starting, setting up service tracker for 1  dependencies
2022-07-01 10:09:54.300 INFO: [16] net.java.sip.communicator.impl.configuration.ConfigurationActivator.startWithServices: Using properties file configuration store.
2022-07-01 10:09:54.308 INFO: [16] ConfigurationServiceImpl.debugPrintSystemProperties#1380: awt.toolkit=sun.awt.X11.XToolkit
2022-07-01 10:09:54.309 INFO: [16] ConfigurationServiceImpl.loadDefaultProperties#1570: Normal classloader
2022-07-01 10:09:54.311 INFO: [16] ConfigurationServiceImpl.loadDefaultProperties#1576: failed to find jitsi-defaults.properties with class loader, will continue without it.
2022-07-01 10:09:54.312 INFO: [16] ConfigurationServiceImpl.loadDefaultProperties#1570: Normal classloader
2022-07-01 10:09:54.313 INFO: [16] ConfigurationServiceImpl.loadDefaultProperties#1576: failed to find jitsi-default-overrides.properties with class loader, will continue without it.
2022-07-01 10:09:54.361 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator net.java.sip.communicator.util.UtilActivator in file:/usr/share/jigasi/lib/jitsi-util-2.14.8fd5f3861.jar
2022-07-01 10:09:54.363 INFO: [16] net.java.sip.communicator.util.osgi.DependentActivator.start: Starting, setting up service tracker for 1  dependencies
2022-07-01 10:09:54.364 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator net.java.sip.communicator.plugin.defaultresourcepack.DefaultResourcePackActivator in file:/usr/share/jigasi/lib/jitsi-defaultresourcepack-2.14.8fd5f3861.jar
2022-07-01 10:09:54.422 INFO: [16] net.java.sip.communicator.plugin.defaultresourcepack.DefaultResourcePackActivator.start: Default resources ... [REGISTERED]
2022-07-01 10:09:54.422 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator net.java.sip.communicator.impl.resources.ResourceManagementActivator in file:/usr/share/jigasi/lib/service-resourcemanager-2.14.8fd5f3861.jar
2022-07-01 10:09:54.423 INFO: [16] net.java.sip.communicator.util.osgi.DependentActivator.start: Starting, setting up service tracker for 6  dependencies
2022-07-01 10:09:54.440 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator net.java.sip.communicator.service.notification.NotificationServiceActivator in file:/usr/share/jigasi/lib/service-notification-service-2.14.8fd5f3861.jar
2022-07-01 10:09:54.441 INFO: [16] net.java.sip.communicator.util.osgi.DependentActivator.start: Starting, setting up service tracker for 1  dependencies
2022-07-01 10:09:54.441 INFO: [16] net.java.sip.communicator.service.notification.NotificationServiceActivator.startWithServices: Notification Service...[  STARTED ]
2022-07-01 10:09:54.447 INFO: [16] net.java.sip.communicator.service.notification.NotificationServiceActivator.startWithServices: Notification Service ...[REGISTERED]
2022-07-01 10:09:54.447 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator net.java.sip.communicator.impl.dns.DnsUtilActivator in file:/usr/share/jigasi/lib/jitsi-dns-2.14.8fd5f3861.jar
2022-07-01 10:09:54.451 INFO: [16] net.java.sip.communicator.util.osgi.DependentActivator.start: Starting, setting up service tracker for 4  dependencies
2022-07-01 10:09:54.452 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator net.java.sip.communicator.impl.credentialsstorage.CredentialsStorageActivator in file:/usr/share/jigasi/lib/service-credentialsstorage-2.14.8fd5f3861.jar
2022-07-01 10:09:54.453 INFO: [16] net.java.sip.communicator.util.osgi.DependentActivator.start: Starting, setting up service tracker for 2  dependencies
2022-07-01 10:09:54.454 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator net.java.sip.communicator.impl.netaddr.NetaddrActivator in file:/usr/share/jigasi/lib/service-netaddr-2.14.8fd5f3861.jar
2022-07-01 10:09:54.456 INFO: [16] net.java.sip.communicator.util.osgi.DependentActivator.start: Starting, setting up service tracker for 2  dependencies
2022-07-01 10:09:54.456 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator net.java.sip.communicator.impl.packetlogging.PacketLoggingActivator in file:/usr/share/jigasi/lib/jitsi-packetlogging-2.14.8fd5f3861.jar
2022-07-01 10:09:54.457 INFO: [16] net.java.sip.communicator.util.osgi.DependentActivator.start: Starting, setting up service tracker for 2  dependencies
2022-07-01 10:09:54.474 INFO: [16] net.java.sip.communicator.impl.packetlogging.PacketLoggingActivator.startWithServices: Packet Logging Service ...[REGISTERED]
2022-07-01 10:09:54.475 INFO: [15] net.java.sip.communicator.impl.dns.DnsUtilActivator.startWithServices: DNS service ... [STARTING]
2022-07-01 10:09:54.476 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator net.java.sip.communicator.service.gui.internal.GuiServiceActivator in file:/usr/share/jigasi/lib/service-ui-service-2.14.8fd5f3861.jar
2022-07-01 10:09:54.482 INFO: [16] net.java.sip.communicator.util.osgi.DependentActivator.start: Starting, setting up service tracker for 1  dependencies
2022-07-01 10:09:54.483 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator net.java.sip.communicator.service.protocol.media.ProtocolMediaActivator in file:/usr/share/jigasi/lib/service-protocol-media-2.14.8fd5f3861.jar
2022-07-01 10:09:54.486 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator net.java.sip.communicator.impl.neomedia.NeomediaActivator in file:/usr/share/jigasi/lib/jitsi-neomedia-2.14.8fd5f3861.jar
2022-07-01 10:09:54.488 INFO: [16] net.java.sip.communicator.util.osgi.DependentActivator.start: Starting, setting up service tracker for 6  dependencies
2022-07-01 10:09:54.585 INFO: [15] net.java.sip.communicator.util.NetworkUtils.<clinit>: java.net.preferIPv6Addresses=null
2022-07-01 10:09:54.585 INFO: [15] net.java.sip.communicator.util.NetworkUtils.<clinit>: java.net.preferIPv4Stack=null
2022-07-01 10:09:54.591 INFO: [15] net.java.sip.communicator.impl.dns.DnsUtilActivator.startWithServices: ParallelResolver ... [REGISTERED]
2022-07-01 10:09:54.592 INFO: [15] net.java.sip.communicator.impl.dns.DnsUtilActivator.startWithServices: DNS service ... [STARTED]
2022-07-01 10:09:54.615 INFO: [15] net.java.sip.communicator.impl.netaddr.NetaddrActivator.startWithServices: Network Address Manager         ...[  STARTED ]
2022-07-01 10:09:54.623 INFO: [19] net.java.sip.communicator.impl.netaddr.NetworkConfigurationWatcher.checkNetworkInterfaces: Currently Active ens18:[/1.2.3.4]
2022-07-01 10:09:54.625 INFO: [19] net.java.sip.communicator.impl.dns.DnsUtilActivator.logDNSServers: Loading or Reloading resolver config, default DNS servers are: /1.2.3.4:53, /172.17.7.210:53,
2022-07-01 10:09:54.942 INFO: [15] JitsiConfig.<clinit>#47: Initialized newConfig: merge of system properties,reference.conf @ jar:file:/usr/share/jigasi/jigasi.jar!/reference.conf: 1,reference.conf @ jar:file:/usr/share/jigasi/lib/ice4j-3.0-59-g71e244d.jar!/reference.conf: 1
2022-07-01 10:09:54.947 INFO: [15] ReadOnlyConfigurationService.reloadConfiguration#51: loading config file at path /etc/jitsi/jigasi/sip-communicator.properties
2022-07-01 10:09:54.951 INFO: [15] JitsiConfig.<clinit>#68: Initialized legacyConfig: sip communicator props (no description provided)
2022-07-01 10:09:54.952 INFO: [15] JitsiConfig$Companion.useDebugNewConfig#74: Replacing newConfig with merge of system properties,reference.conf @ jar:file:/usr/share/jigasi/jigasi.jar!/reference.conf: 1,reference.conf @ jar:file:/usr/share/jigasi/lib/ice4j-3.0-59-g71e244d.jar!/reference.conf: 1
2022-07-01 10:09:54.953 INFO: [15] net.java.sip.communicator.impl.netaddr.NetaddrActivator.startWithServices: Network Address Manager Service ...[REGISTERED]
2022-07-01 10:09:55.006 SEVERE: [16] DeviceConfiguration.registerCustomRenderers#1056: Failed to register custom Renderer org.jitsi.impl.neomedia.jmfext.media.renderer.audio.PulseAudioRenderer with JMF.
2022-07-01 10:09:55.023 INFO: [16] net.java.sip.communicator.impl.neomedia.NeomediaActivator.startWithServices: Media Service ... [REGISTERED]
2022-07-01 10:09:55.026 INFO: [16] net.java.sip.communicator.impl.neomedia.NeomediaActivator.startWithServices: Media Configuration ... [REGISTERED]
2022-07-01 10:09:55.034 INFO: [16] net.java.sip.communicator.impl.neomedia.NeomediaActivator.startWithServices: Audio Notifier Service ...[REGISTERED]
2022-07-01 10:09:55.043 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator net.java.sip.communicator.impl.certificate.CertificateVerificationActivator in file:/usr/share/jigasi/lib/service-certificate-2.14.8fd5f3861.jar
2022-07-01 10:09:55.044 INFO: [16] net.java.sip.communicator.util.osgi.DependentActivator.start: Starting, setting up service tracker for 3  dependencies
2022-07-01 10:09:55.044 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator org.jitsi.jigasi.version.VersionActivator in file:/usr/share/jigasi/jigasi.jar
2022-07-01 10:09:55.048 INFO: [16] AbstractVersionActivator.start#91: VersionService registered: Jigasi 1.1.259-g25c51d6
2022-07-01 10:09:55.048 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator org.jitsi.jigasi.osgi.EmptyHidServiceActivator in file:/usr/share/jigasi/jigasi.jar
2022-07-01 10:09:55.049 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator org.jitsi.jigasi.osgi.EmptyUiServiceActivator in file:/usr/share/jigasi/jigasi.jar
2022-07-01 10:09:55.051 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator org.jitsi.jigasi.osgi.EmptyMasterPasswordInputServiceActivator in file:/usr/share/jigasi/jigasi.jar
2022-07-01 10:09:55.052 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator org.jitsi.jigasi.JigasiBundleActivator in file:/usr/share/jigasi/jigasi.jar
2022-07-01 10:09:55.054 INFO: [16] net.java.sip.communicator.util.osgi.DependentActivator.start: Starting, setting up service tracker for 1  dependencies
2022-07-01 10:09:55.056 INFO: [16] JigasiBundleActivator.startWithServices#212: initialized SipGateway
2022-07-01 10:09:55.060 INFO: [16] JigasiBundleActivator.startWithServices#250: skipped initialization of TranscriptionGateway
2022-07-01 10:09:55.065 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator org.jitsi.jigasi.rest.RESTBundleActivator in file:/usr/share/jigasi/jigasi.jar
2022-07-01 10:09:55.441 INFO: [16] net.java.sip.communicator.util.osgi.DependentActivator.start: Starting, setting up service tracker for 1  dependencies
2022-07-01 10:09:55.653 INFO: [16] org.eclipse.jetty.server.Server.doStart: jetty-11.0.9; built: 2022-03-30T17:44:47.085Z; git: 243a48a658a183130a8c8de353178d154ca04f04; jvm 11.0.15+10-post-Debian-1deb10u1
2022-07-01 10:09:55.732 INFO: [16] org.eclipse.jetty.server.AbstractConnector.doStart: Started ServerConnector@61109058{HTTP/1.1, (http/1.1)}{0.0.0.0:8788}
2022-07-01 10:09:55.759 INFO: [16] org.eclipse.jetty.server.Server.doStart: Started Server@4a5731dd{STARTING}[11.0.9,sto=0] @2873ms
2022-07-01 10:09:55.760 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator org.jitsi.jigasi.rest.TranscriptServerBundleActivator in file:/usr/share/jigasi/jigasi.jar
2022-07-01 10:09:55.761 INFO: [16] net.java.sip.communicator.util.osgi.DependentActivator.start: Starting, setting up service tracker for 1  dependencies
2022-07-01 10:09:55.775 INFO: [16] AbstractJettyBundleActivator.startWithServices#447: Not starting the Jetty service for org.jitsi.jigasi.rest.TranscriptServerBundleActivator(port=0)
2022-07-01 10:09:55.776 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator org.jitsi.jigasi.xmpp.CallControlMucActivator in file:/usr/share/jigasi/jigasi.jar
2022-07-01 10:09:55.779 INFO: [16] net.java.sip.communicator.util.osgi.DependentActivator.start: Starting, setting up service tracker for 1  dependencies
2022-07-01 10:09:55.784 WARNING: [16] CallControl.<init>#122: Always trust in remote TLS certificates mode is enabled
2022-07-01 10:09:55.804 INFO: [16] CallControl.<init>#141: JID allowed to make outgoing calls: jigasibrewery@internal.auth.jitsi.domain.tld
2022-07-01 10:09:55.804 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator org.jitsi.jigasi.ddclient.DdClientActivator in file:/usr/share/jigasi/jigasi.jar
2022-07-01 10:09:55.806 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator net.java.sip.communicator.service.protocol.ProtocolProviderActivator in file:/usr/share/jigasi/lib/service-protocol-2.14.8fd5f3861.jar
2022-07-01 10:09:55.807 INFO: [16] net.java.sip.communicator.util.osgi.DependentActivator.start: Starting, setting up service tracker for 3  dependencies
2022-07-01 10:09:55.812 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator net.java.sip.communicator.impl.globaldisplaydetails.GlobalDisplayDetailsActivator in file:/usr/share/jigasi/lib/service-globaldisplaydetails-2.14.8fd5f3861.jar
2022-07-01 10:09:55.814 INFO: [16] net.java.sip.communicator.util.osgi.DependentActivator.start: Starting, setting up service tracker for 3  dependencies
2022-07-01 10:09:55.823 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator net.java.sip.communicator.plugin.reconnectplugin.ReconnectPluginActivator in file:/usr/share/jigasi/lib/jitsi-reconnect-2.14.8fd5f3861.jar
2022-07-01 10:09:55.825 INFO: [16] net.java.sip.communicator.util.osgi.DependentActivator.start: Starting, setting up service tracker for 5  dependencies
2022-07-01 10:09:55.827 FINE: [16] net.java.sip.communicator.util.osgi.DependentActivator.addingService: Got service ResourceManagementServiceImpl, starting now
2022-07-01 10:09:55.835 FINE: [16] net.java.sip.communicator.plugin.reconnectplugin.ReconnectPluginActivator.startWithServices: Found 0 already installed providers.
2022-07-01 10:09:55.836 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator net.java.sip.communicator.impl.phonenumbers.PhoneNumberServiceActivator in file:/usr/share/jigasi/lib/jitsi-phonenumbers-2.14.8fd5f3861.jar
2022-07-01 10:09:55.837 INFO: [16] net.java.sip.communicator.util.osgi.DependentActivator.start: Starting, setting up service tracker for 1  dependencies
2022-07-01 10:09:55.841 INFO: [16] net.java.sip.communicator.impl.phonenumbers.PhoneNumberServiceActivator.startWithServices: Packet Logging Service ...[REGISTERED]
2022-07-01 10:09:55.841 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator net.java.sip.communicator.impl.protocol.sip.SipActivator in file:/usr/share/jigasi/lib/jitsi-protocol-sip-2.14.8fd5f3861.jar
2022-07-01 10:09:55.852 INFO: [16] org.jitsi.impl.osgi.framework.BundleImpl.start: Starting activator net.java.sip.communicator.impl.protocol.jabber.JabberActivator in file:/usr/share/jigasi/lib/jitsi-protocol-jabber-2.14.8fd5f3861.jar
2022-07-01 10:09:55.855 INFO: [16] net.java.sip.communicator.util.osgi.DependentActivator.start: Starting, setting up service tracker for 11  dependencies
2022-07-01 10:09:56.341 WARNING: [35] net.java.sip.communicator.impl.resources.ResourceManagementServiceImpl.getSettingsInt: Missing resource for key: net.java.sip.communicator.SIP_PREFERRED_CLEAR_PORT
2022-07-01 10:09:56.371 WARNING: [35] net.java.sip.communicator.impl.resources.ResourceManagementServiceImpl.getSettingsInt: Missing resource for key: net.java.sip.communicator.SIP_PREFERRED_SECURE_PORT
2022-07-01 10:09:56.726 INFO: [35] SipGateway.registrationStateChanged#120: REG STATE CHANGE ProtocolProviderServiceSipImpl(SIP:6338@asterisk.domain.tld) -> RegistrationStateChangeEvent[ oldState=Unregistered; newState=RegistrationState=Registering; userRequest=false; reasonCode=-1; reason=null]
2022-07-01 10:09:56.905 INFO: [51] SipGateway.registrationStateChanged#120: REG STATE CHANGE ProtocolProviderServiceSipImpl(SIP:6338@asterisk.domain.tld) -> RegistrationStateChangeEvent[ oldState=Registering; newState=RegistrationState=Registered; userRequest=false; reasonCode=-1; reason=null]
2022-07-01 10:09:56.910 WARNING: [51] SipHealthPeriodicChecker.create#169: No health check started, no HEALTH_CHECK_SIP_URI prop.
2022-07-01 10:09:57.043 INFO: [45] net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl$JabberConnectionListener.authenticated: Authenticated: false
2022-07-01 10:09:57.049 INFO: [45] CallControlMucActivator.joinCommonRoom#283: Joining call control room: JigasiBrewery@internal.auth.jitsi.domain.tld pps:ProtocolProviderServiceJabberImpl(Jabber:jigasi@auth.jitsi.domain.tld), id:acc-xmpp-1
2022-07-01 10:09:57.122 INFO: [60] net.java.sip.communicator.impl.protocol.jabber.ChatRoomJabberImpl$MemberListener.joined: jigasibrewery@internal.auth.jitsi.domain.tld/focus has joined the jigasibrewery@internal.auth.jitsi.domain.tld chat room.
2022-07-01 10:09:57.130 INFO: [60] net.java.sip.communicator.impl.protocol.jabber.ChatRoomJabberImpl$MemberListener.joined: jigasibrewery@internal.auth.jitsi.domain.tld/jitsi-1mqf89n has joined the jigasibrewery@internal.auth.jitsi.domain.tld chat room.
2022-07-01 10:09:57.145 INFO: [45] CallControlMucActivator.joinCommonRoom#321: Joined call control room: JigasiBrewery@internal.auth.jitsi.domain.tld pps:ProtocolProviderServiceJabberImpl(Jabber:jigasi@auth.jitsi.domain.tld), id:acc-xmpp-1 nickname:jitsi-1mqf89n sessionId:null

You are calling this:

where your jigasi is registered to an account named 6338. You need to call SIP/6338

Hmm… after changing

exten => s,n,Dial(SIP/${Jitsi},3,m(silence)A(/tmp/name-${rnum})M(Jitsi-join))

in the extensions_custom.conf file to

exten => s,n,Dial(PJSIP/${Jitsi},3,m(silence)A(/tmp/name-${rnum})M(Jitsi-join))

the call is redirected to jigasi. But it has some problems with the header. So I think the

;Add SIP Headers based on caller's entries & CURL result
exten => s,n(enterconf),SIPAddHeader(Jitsi-Conference-Room:${CURL_RESULT})
exten => s,n,Set(HASH(__SIPHEADERS,Jitsi-Conference-Room)=${JITSI})

is still wrong for PJSIP:

2022-07-01 10:16:05.719 INFO: [103] SipGateway$SipCallListener.incomingCallReceived#216: [ctx=1656663365709215972819] Incoming call received...
2022-07-01 10:16:06.734 WARNING: [105] SipGatewaySession$WaitForJvbRoomNameThread.run#1591: [ctx=1656663365709215972819] No JVB room name provided in INVITE header
2022-07-01 10:16:06.746 INFO: [107] SipGatewaySession$SipCallStateListener.handleCallState#1440: [ctx=1656663365709215972819] SIP call ended: CallPeerChangeEvent: type=CallPeerStatusChange oldV=net.java.sip.communicator.service.protocol.CallPeerState:Incoming Call newV=net.java.sip.communicator.service.protocol.CallPeerState:Failed for peer=+4912345 <+4912345@ASTERISK_IP>;status=Failed
2022-07-01 10:16:06.751 INFO: [107] SipGatewaySession.sipCallEnded#694: [ctx=1656663365709215972819] Sip call ended: Call: id=16566633656001913285930 peers=0
2022-07-01 10:16:06.753 SEVERE: [107] AbstractGateway.notifyCallEnded#121: [ctx=1656663365709215972819] Call resource not exists for session.
2022-07-01 10:16:06.755 INFO: [107] SipGatewaySession$CallPeerListener.peerStateChanged#1501: null SIP peer state: Failed