[ISSUE] Jibri SIP Gateway Setup

Hello, Jitsi Community. I’m trying to use Jibri as a SIP Gateway, and trying to make a call to a Polycom device. I’ve managed to configure the “people search URL”, and am inviting the device through the UI. Upon trying such, nothing happens to the Polycom device. Here are my logs;

Pjsua;

13:04:16.233         sip_endpoint.c  .Module "mod-pjsua-log" registered
13:04:16.233           pjsua_core.c  .Nameserver 8.8.8.8 added
13:04:16.233         sip_endpoint.c  .Module "mod-tsx-layer" registered
13:04:16.233         sip_endpoint.c  .Module "mod-stateful-util" registered
13:04:16.233         sip_endpoint.c  .Module "mod-ua" registered
13:04:16.233         sip_endpoint.c  .Module "mod-100rel" registered
13:04:16.233         sip_endpoint.c  .Module "mod-pjsua" registered
13:04:16.233         sip_endpoint.c  .Module "mod-invite" registered
13:04:16.253             alsa_dev.c  ..ALSA driver found 24 devices
13:04:16.253             alsa_dev.c  ..ALSA initialized
13:04:16.253                  pjlib  ..select() I/O Queue created (0x55d73f2ff2d8)
13:04:16.256            pjsua_vid.c  ..Initializing video subsystem..
13:04:16.256                  vpx.c  ...VPX codec initialized
13:04:16.256             v4l2_dev.c  ...Video4Linux2 has 0 devices
13:04:16.301              sdl_dev.c  ...SDL 2.0 initialized
13:04:16.301         colorbar_dev.c  ...Colorbar video src initialized with 2 device(s):
13:04:16.301         colorbar_dev.c  ... 0: Colorbar generator
13:04:16.301         colorbar_dev.c  ... 1: Colorbar-active
13:04:16.302         sip_endpoint.c  .Module "mod-evsub" registered
13:04:16.302         sip_endpoint.c  .Module "mod-presence" registered
13:04:16.302         sip_endpoint.c  .Module "mod-mwi" registered
13:04:16.302         sip_endpoint.c  .Module "mod-refer" registered
13:04:16.302         sip_endpoint.c  .Module "mod-pjsua-pres" registered
13:04:16.302         sip_endpoint.c  .Module "mod-pjsua-im" registered
13:04:16.302         sip_endpoint.c  .Module "mod-pjsua-options" registered
13:04:16.302           pjsua_core.c  .1 SIP worker threads created
13:04:16.302           pjsua_core.c  .pjsua version 2.10-jitsi3 for Linux-5.10.0.11/x86_64/glibc-2.31 initialized
13:04:16.302           pjsua_core.c  .PJSUA state changed: CREATED --> INIT
13:04:16.302         sip_endpoint.c  Module "mod-default-handler" registered
13:04:16.302           pjsua_core.c  SIP UDP socket reachable at ip.of.my.machine:5060
13:04:16.302      udp0x55d73f2f1d90  SIP UDP transport started, published address is ip.of.my.machine:5060
13:04:16.302            pjsua_acc.c  Adding account: id=<sip:ip.of.my.machine:5060>
13:04:16.302            pjsua_acc.c  .Account <sip:ip.of.my.machine:5060> added with id 0
13:04:16.302            pjsua_acc.c  Modifying account 0
13:04:16.302            pjsua_acc.c  Acc 0: setting online status to 1..
13:04:16.302            pjsua_acc.c  Adding account: id=My ID <sip:jibri@127.0.0.1>
13:04:16.302            pjsua_acc.c  .Account My ID <sip:jibri@127.0.0.1> added with id 1
13:04:16.302            pjsua_acc.c  Acc 1: setting online status to 1..
13:04:16.302           pjsua_pres.c  Adding buddy: sip:the_sip_address@device
13:04:16.302           pjsua_pres.c  .Buddy 0 added.
13:04:16.302           pjsua_pres.c  ..Buddy 0: updating presence..
13:04:16.302           pjsua_core.c  PJSUA state changed: INIT --> STARTING
13:04:16.302         sip_endpoint.c  .Module "mod-unsolicited-mwi" registered
13:04:16.302           pjsua_core.c  .PJSUA state changed: STARTING --> RUNNING
13:04:16.302                 main.c  Ready: Success
13:04:16.302           pjsua_call.c  Making call with acc #1 to sip:the_sip_address@device
13:04:16.302            pjsua_aud.c  .Set sound device: capture=-1, playback=-2
13:04:16.302            pjsua_app.c  ..Turning sound device -1 -2 ON
13:04:16.302            pjsua_aud.c  ..Opening sound device (speaker + mic) PCM@16000/1/20ms
13:04:16.304          pjsua_media.c  .Call 0: initializing media..
13:04:16.304          pjsua_media.c  ..RTP socket reachable at ip.of.my.machine:4000
13:04:16.304          pjsua_media.c  ..RTCP socket reachable at ip.of.my.machine:4001
13:04:16.304          pjsua_media.c  ..RTP socket reachable at ip.of.my.machine:4002
13:04:16.304          pjsua_media.c  ..RTCP socket reachable at ip.of.my.machine:4003
13:04:16.304          pjsua_media.c  ..Media index 0 selected for audio call 0
13:04:16.305             resolver.c  ....Transmitting 40 bytes to NS 0 (8.8.8.8:53): DNS SRV query for _sip._udp.facegate.biz: Success
13:04:16.305            pjsua_app.c  .......Call 0 state changed to CALLING
13:04:16.313             resolver.c !Transmitting 28 bytes to NS 0 (8.8.8.8:53): DNS A query for ygg1.vp.vc: Success
13:04:16.313             resolver.c  Transmitting 28 bytes to NS 0 (8.8.8.8:53): DNS A query for ygg2.vp.vc: Success
13:04:16.324      tsx0x55d73f311848  Temporary failure in sending Request msg INVITE/cseq=16114 (tdta0x55d73f30e8d8), will try next server: Unsupported transport (PJSIP_EUNSUPTRANSPORT)
13:04:16.324      tsx0x55d73f311848  Temporary failure in sending Request msg INVITE/cseq=16114 (tdta0x55d73f30e8d8), will try next server: Unsupported transport (PJSIP_EUNSUPTRANSPORT)
13:04:16.324           pjsua_core.c  TX 1703 bytes Request msg INVITE/cseq=16114 (tdta0x55d73f30e8d8) to UDP ip.i.don't.know:5060:
INVITE sip:the_sip_address@device SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5060;rport;branch=z9hG4bKPj063ad391-4a6a-460f-93f9-b95c7d4ea7b3
Max-Forwards: 70
From: "My ID" <sip:jibri@127.0.0.1>;tag=87a2184d-67d5-4c27-84ea-e470e56495f9
To: sip:the_sip_address@device
Contact: "My ID" <sip:jibri@ip.of.my.machine:5060;ob>
Call-ID: 6cc30578-1deb-442e-af42-7d64ae8428c5
CSeq: 16114 INVITE
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Supported: replaces, 100rel, timer, norefersub
Session-Expires: 1800
Min-SE: 90
User-Agent: PJSUA v2.10-jitsi3 Linux-5.10.0.11/x86_64/glibc-2.31
Content-Type: application/sdp
Content-Length:   994

v=0
o=- 3854606656 3854606656 IN IP4 ip.of.my.machine
s=pjmedia
b=AS:2742
t=0 0
a=X-nat:0
m=audio 4000 RTP/AVP 96 9 97 98 99 8 0 120 121 122 123
c=IN IP4 ip.of.my.machine
b=TIAS:96000
a=rtcp:4001 IN IP4 ip.of.my.machine
a=sendrecv
a=rtpmap:96 opus/48000/2
a=fmtp:96 useinbandfec=1
a=rtpmap:9 G722/8000
a=rtpmap:97 speex/32000
a=rtpmap:98 speex/16000
a=rtpmap:99 speex/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:120 telephone-event/48000
a=fmtp:120 0-16
a=rtpmap:121 telephone-event/8000
a=fmtp:121 0-16
a=rtpmap:122 telephone-event/32000
a=fmtp:122 0-16
a=rtpmap:123 telephone-event/16000
a=fmtp:123 0-16
a=ssrc:229759570 cname:20393946079cd1b9
m=video 4002 RTP/AVP 97 102
c=IN IP4 ip.of.my.machine
b=TIAS:2500000
a=rtcp:4003 IN IP4 ip.of.my.machine
a=sendrecv
a=rtpmap:97 H264/90000
a=fmtp:97 profile-level-id=42801f; packetization-mode=1
a=rtpmap:102 VP8/90000
a=fmtp:102 max-fr=30; max-fs=580
a=ssrc:482127620 cname:20393946079cd1b9
a=rtcp-fb:* nack pli

--end msg--
13:04:16.824           pjsua_core.c  .TX 1703 bytes Request msg INVITE/cseq=16114 (tdta0x55d73f30e8d8) to UDP ip.i.don't.know:5060:
INVITE sip:the_sip_address@device SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5060;rport;branch=z9hG4bKPj063ad391-4a6a-460f-93f9-b95c7d4ea7b3
Max-Forwards: 70
From: "My ID" <sip:jibri@127.0.0.1>;tag=87a2184d-67d5-4c27-84ea-e470e56495f9
To: sip:the_sip_address@device
Contact: "My ID" <sip:jibri@ip.of.my.machine:5060;ob>
Call-ID: 6cc30578-1deb-442e-af42-7d64ae8428c5
CSeq: 16114 INVITE
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Supported: replaces, 100rel, timer, norefersub
Session-Expires: 1800
Min-SE: 90
User-Agent: PJSUA v2.10-jitsi3 Linux-5.10.0.11/x86_64/glibc-2.31
Content-Type: application/sdp
Content-Length:   994

v=0
o=- 3854606656 3854606656 IN IP4 ip.of.my.machine
s=pjmedia
b=AS:2742
t=0 0
a=X-nat:0
m=audio 4000 RTP/AVP 96 9 97 98 99 8 0 120 121 122 123
c=IN IP4 ip.of.my.machine
b=TIAS:96000
a=rtcp:4001 IN IP4 ip.of.my.machine
a=sendrecv
a=rtpmap:96 opus/48000/2
a=fmtp:96 useinbandfec=1
a=rtpmap:9 G722/8000
a=rtpmap:97 speex/32000
a=rtpmap:98 speex/16000
a=rtpmap:99 speex/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:120 telephone-event/48000
a=fmtp:120 0-16
a=rtpmap:121 telephone-event/8000
a=fmtp:121 0-16
a=rtpmap:122 telephone-event/32000
a=fmtp:122 0-16
a=rtpmap:123 telephone-event/16000
a=fmtp:123 0-16
a=ssrc:229759570 cname:20393946079cd1b9
m=video 4002 RTP/AVP 97 102
c=IN IP4 ip.of.my.machine
b=TIAS:2500000
a=rtcp:4003 IN IP4 ip.of.my.machine
a=sendrecv
a=rtpmap:97 H264/90000
a=fmtp:97 profile-level-id=42801f; packetization-mode=1
a=rtpmap:102 VP8/90000
a=fmtp:102 max-fr=30; max-fs=580
a=ssrc:482127620 cname:20393946079cd1b9
a=rtcp-fb:* nack pli

--end msg--
13:04:17.824           pjsua_core.c  .TX 1703 bytes Request msg INVITE/cseq=16114 (tdta0x55d73f30e8d8) to UDP ip.i.don't.know:5060:
INVITE sip:the_sip_address@device SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5060;rport;branch=z9hG4bKPj063ad391-4a6a-460f-93f9-b95c7d4ea7b3
Max-Forwards: 70
From: "My ID" <sip:jibri@127.0.0.1>;tag=87a2184d-67d5-4c27-84ea-e470e56495f9
To: sip:the_sip_address@device
Contact: "My ID" <sip:jibri@ip.of.my.machine:5060;ob>
Call-ID: 6cc30578-1deb-442e-af42-7d64ae8428c5
CSeq: 16114 INVITE
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Supported: replaces, 100rel, timer, norefersub
Session-Expires: 1800
Min-SE: 90
User-Agent: PJSUA v2.10-jitsi3 Linux-5.10.0.11/x86_64/glibc-2.31
Content-Type: application/sdp
Content-Length:   994

v=0
o=- 3854606656 3854606656 IN IP4 ip.of.my.machine
s=pjmedia
b=AS:2742
t=0 0
a=X-nat:0
m=audio 4000 RTP/AVP 96 9 97 98 99 8 0 120 121 122 123
c=IN IP4 ip.of.my.machine
b=TIAS:96000
a=rtcp:4001 IN IP4 ip.of.my.machine
a=sendrecv
a=rtpmap:96 opus/48000/2
a=fmtp:96 useinbandfec=1
a=rtpmap:9 G722/8000
a=rtpmap:97 speex/32000
a=rtpmap:98 speex/16000
a=rtpmap:99 speex/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:120 telephone-event/48000
a=fmtp:120 0-16
a=rtpmap:121 telephone-event/8000
a=fmtp:121 0-16
a=rtpmap:122 telephone-event/32000
a=fmtp:122 0-16
a=rtpmap:123 telephone-event/16000
a=fmtp:123 0-16
a=ssrc:229759570 cname:20393946079cd1b9
m=video 4002 RTP/AVP 97 102
c=IN IP4 ip.of.my.machine
b=TIAS:2500000
a=rtcp:4003 IN IP4 ip.of.my.machine
a=sendrecv
a=rtpmap:97 H264/90000
a=fmtp:97 profile-level-id=42801f; packetization-mode=1
a=rtpmap:102 VP8/90000
a=fmtp:102 max-fr=30; max-fs=580
a=ssrc:482127620 cname:20393946079cd1b9
a=rtcp-fb:* nack pli

--end msg--
13:04:19.824           pjsua_core.c  .TX 1703 bytes Request msg INVITE/cseq=16114 (tdta0x55d73f30e8d8) to UDP ip.i.don't.know:5060:
INVITE sip:the_sip_address@device SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5060;rport;branch=z9hG4bKPj063ad391-4a6a-460f-93f9-b95c7d4ea7b3
Max-Forwards: 70
From: "My ID" <sip:jibri@127.0.0.1>;tag=87a2184d-67d5-4c27-84ea-e470e56495f9
To: sip:the_sip_address@device
Contact: "My ID" <sip:jibri@ip.of.my.machine:5060;ob>
Call-ID: 6cc30578-1deb-442e-af42-7d64ae8428c5
CSeq: 16114 INVITE
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Supported: replaces, 100rel, timer, norefersub
Session-Expires: 1800
Min-SE: 90
User-Agent: PJSUA v2.10-jitsi3 Linux-5.10.0.11/x86_64/glibc-2.31
Content-Type: application/sdp
Content-Length:   994

v=0
o=- 3854606656 3854606656 IN IP4 ip.of.my.machine
s=pjmedia
b=AS:2742
t=0 0
a=X-nat:0
m=audio 4000 RTP/AVP 96 9 97 98 99 8 0 120 121 122 123
c=IN IP4 ip.of.my.machine
b=TIAS:96000
a=rtcp:4001 IN IP4 ip.of.my.machine
a=sendrecv
a=rtpmap:96 opus/48000/2
a=fmtp:96 useinbandfec=1
a=rtpmap:9 G722/8000
a=rtpmap:97 speex/32000
a=rtpmap:98 speex/16000
a=rtpmap:99 speex/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:120 telephone-event/48000
a=fmtp:120 0-16
a=rtpmap:121 telephone-event/8000
a=fmtp:121 0-16
a=rtpmap:122 telephone-event/32000
a=fmtp:122 0-16
a=rtpmap:123 telephone-event/16000
a=fmtp:123 0-16
a=ssrc:229759570 cname:20393946079cd1b9
m=video 4002 RTP/AVP 97 102
c=IN IP4 ip.of.my.machine
b=TIAS:2500000
a=rtcp:4003 IN IP4 ip.of.my.machine
a=sendrecv
a=rtpmap:97 H264/90000
a=fmtp:97 profile-level-id=42801f; packetization-mode=1
a=rtpmap:102 VP8/90000
a=fmtp:102 max-fr=30; max-fs=580
a=ssrc:482127620 cname:20393946079cd1b9
a=rtcp-fb:* nack pli

--end msg--
13:04:23.823           pjsua_core.c  .TX 1703 bytes Request msg INVITE/cseq=16114 (tdta0x55d73f30e8d8) to UDP ip.i.don't.know:5060:
INVITE sip:the_sip_address@device SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5060;rport;branch=z9hG4bKPj063ad391-4a6a-460f-93f9-b95c7d4ea7b3
Max-Forwards: 70
From: "My ID" <sip:jibri@127.0.0.1>;tag=87a2184d-67d5-4c27-84ea-e470e56495f9
To: sip:the_sip_address@device
Contact: "My ID" <sip:jibri@ip.of.my.machine:5060;ob>
Call-ID: 6cc30578-1deb-442e-af42-7d64ae8428c5
CSeq: 16114 INVITE
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Supported: replaces, 100rel, timer, norefersub
Session-Expires: 1800
Min-SE: 90
User-Agent: PJSUA v2.10-jitsi3 Linux-5.10.0.11/x86_64/glibc-2.31
Content-Type: application/sdp
Content-Length:   994

v=0
o=- 3854606656 3854606656 IN IP4 ip.of.my.machine
s=pjmedia
b=AS:2742
t=0 0
a=X-nat:0
m=audio 4000 RTP/AVP 96 9 97 98 99 8 0 120 121 122 123
c=IN IP4 ip.of.my.machine
b=TIAS:96000
a=rtcp:4001 IN IP4 ip.of.my.machine
a=sendrecv
a=rtpmap:96 opus/48000/2
a=fmtp:96 useinbandfec=1
a=rtpmap:9 G722/8000
a=rtpmap:97 speex/32000
a=rtpmap:98 speex/16000
a=rtpmap:99 speex/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:120 telephone-event/48000
a=fmtp:120 0-16
a=rtpmap:121 telephone-event/8000
a=fmtp:121 0-16
a=rtpmap:122 telephone-event/32000
a=fmtp:122 0-16
a=rtpmap:123 telephone-event/16000
a=fmtp:123 0-16
a=ssrc:229759570 cname:20393946079cd1b9
m=video 4002 RTP/AVP 97 102
c=IN IP4 ip.of.my.machine
b=TIAS:2500000
a=rtcp:4003 IN IP4 ip.of.my.machine
a=sendrecv
a=rtpmap:97 H264/90000
a=fmtp:97 profile-level-id=42801f; packetization-mode=1
a=rtpmap:102 VP8/90000
a=fmtp:102 max-fr=30; max-fs=580
a=ssrc:482127620 cname:20393946079cd1b9
a=rtcp-fb:* nack pli

--end msg--
13:04:31.823           pjsua_core.c  .TX 1703 bytes Request msg INVITE/cseq=16114 (tdta0x55d73f30e8d8) to UDP ip.i.don't.know:5060:
INVITE sip:the_sip_address@device SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5060;rport;branch=z9hG4bKPj063ad391-4a6a-460f-93f9-b95c7d4ea7b3
Max-Forwards: 70
From: "My ID" <sip:jibri@127.0.0.1>;tag=87a2184d-67d5-4c27-84ea-e470e56495f9
To: sip:the_sip_address@device
Contact: "My ID" <sip:jibri@ip.of.my.machine:5060;ob>
Call-ID: 6cc30578-1deb-442e-af42-7d64ae8428c5
CSeq: 16114 INVITE
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Supported: replaces, 100rel, timer, norefersub
Session-Expires: 1800
Min-SE: 90
User-Agent: PJSUA v2.10-jitsi3 Linux-5.10.0.11/x86_64/glibc-2.31
Content-Type: application/sdp
Content-Length:   994

v=0
o=- 3854606656 3854606656 IN IP4 ip.of.my.machine
s=pjmedia
b=AS:2742
t=0 0
a=X-nat:0
m=audio 4000 RTP/AVP 96 9 97 98 99 8 0 120 121 122 123
c=IN IP4 ip.of.my.machine
b=TIAS:96000
a=rtcp:4001 IN IP4 ip.of.my.machine
a=sendrecv
a=rtpmap:96 opus/48000/2
a=fmtp:96 useinbandfec=1
a=rtpmap:9 G722/8000
a=rtpmap:97 speex/32000
a=rtpmap:98 speex/16000
a=rtpmap:99 speex/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:120 telephone-event/48000
a=fmtp:120 0-16
a=rtpmap:121 telephone-event/8000
a=fmtp:121 0-16
a=rtpmap:122 telephone-event/32000
a=fmtp:122 0-16
a=rtpmap:123 telephone-event/16000
a=fmtp:123 0-16
a=ssrc:229759570 cname:20393946079cd1b9
m=video 4002 RTP/AVP 97 102
c=IN IP4 ip.of.my.machine
b=TIAS:2500000
a=rtcp:4003 IN IP4 ip.of.my.machine
a=sendrecv
a=rtpmap:97 H264/90000
a=fmtp:97 profile-level-id=42801f; packetization-mode=1
a=rtpmap:102 VP8/90000
a=fmtp:102 max-fr=30; max-fs=580
a=ssrc:482127620 cname:20393946079cd1b9
a=rtcp-fb:* nack pli

--end msg--
13:04:47.824           pjsua_core.c  .TX 1703 bytes Request msg INVITE/cseq=16114 (tdta0x55d73f30e8d8) to UDP ip.i.don't.know:5060:
INVITE sip:the_sip_address@device SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5060;rport;branch=z9hG4bKPj063ad391-4a6a-460f-93f9-b95c7d4ea7b3
Max-Forwards: 70
From: "My ID" <sip:jibri@127.0.0.1>;tag=87a2184d-67d5-4c27-84ea-e470e56495f9
To: sip:the_sip_address@device
Contact: "My ID" <sip:jibri@ip.of.my.machine:5060;ob>
Call-ID: 6cc30578-1deb-442e-af42-7d64ae8428c5
CSeq: 16114 INVITE
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Supported: replaces, 100rel, timer, norefersub
Session-Expires: 1800
Min-SE: 90
User-Agent: PJSUA v2.10-jitsi3 Linux-5.10.0.11/x86_64/glibc-2.31
Content-Type: application/sdp
Content-Length:   994

v=0
o=- 3854606656 3854606656 IN IP4 ip.of.my.machine
s=pjmedia
b=AS:2742
t=0 0
a=X-nat:0
m=audio 4000 RTP/AVP 96 9 97 98 99 8 0 120 121 122 123
c=IN IP4 ip.of.my.machine
b=TIAS:96000
a=rtcp:4001 IN IP4 ip.of.my.machine
a=sendrecv
a=rtpmap:96 opus/48000/2
a=fmtp:96 useinbandfec=1
a=rtpmap:9 G722/8000
a=rtpmap:97 speex/32000
a=rtpmap:98 speex/16000
a=rtpmap:99 speex/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:120 telephone-event/48000
a=fmtp:120 0-16
a=rtpmap:121 telephone-event/8000
a=fmtp:121 0-16
a=rtpmap:122 telephone-event/32000
a=fmtp:122 0-16
a=rtpmap:123 telephone-event/16000
a=fmtp:123 0-16
a=ssrc:229759570 cname:20393946079cd1b9
m=video 4002 RTP/AVP 97 102
c=IN IP4 ip.of.my.machine
b=TIAS:2500000
a=rtcp:4003 IN IP4 ip.of.my.machine
a=sendrecv
a=rtpmap:97 H264/90000
a=fmtp:97 profile-level-id=42801f; packetization-mode=1
a=rtpmap:102 VP8/90000
a=fmtp:102 max-fr=30; max-fs=580
a=ssrc:482127620 cname:20393946079cd1b9
a=rtcp-fb:* nack pli

--end msg--
13:04:48.324            pjsua_app.c  ....Call 0 is DISCONNECTED [reason=408 (Request Timeout)]
13:04:48.325     pjsua_app_common.c  ....
  [DISCONNCTD] To: sip:the_sip_address@device
    Call time: 00h:00m:00s, 1st res in 32020 ms, conn in 0ms

Jibri;

2022-02-23 13:52:23.996 INFO: [77] XmppApi.handleJibriIq#171: Received JibriIq <iq xmlns='jabber:client' to='jibri@auth.my.domain.com/NIup-V1Q' from='thesipbrewery                                                              @conference.my.domain.com/focus' id='amlicmlAYXV0aC52bS1iZ2VyLWppdHNpLTAyLnR1eDQyLmNoL05JdXAtVjFRAEtNN0E0LTY2NAAW+1qwPr7BUDQZ606i6Ls5' type='set'><jibri xmlns='htt                                                              p://jitsi.org/protocol/jibri' action='start' recording_mode='file' room='geneticusescreepdelicately@conference.my.domain.com' displayname='Bger Lausanne' sipaddres                                                              s='my-sip@address' session_id='lfnzujmjqvegjcwl'/></iq> from environment [MucClient id=my.domain.com hostname=my.domain.com]
2022-02-23 13:52:23.997 INFO: [77] XmppApi.handleStartJibriIq#199: Received start request, starting service
2022-02-23 13:52:23.997 INFO: [77] XmppApi.handleStartService#304: Parsed call url info: CallUrlInfo(baseUrl=https://my.domain.com, callName=geneticusescreepdelica                                                              tely, urlParams=[])
2022-02-23 13:52:23.997 INFO: [77] JibriManager.startSipGateway#176: Starting a SIP gateway with params: ServiceParams(usageTimeoutMinutes=0, appData=null) SipGatewayServicePa                                                              rams(callParams=CallParams(callUrlInfo=CallUrlInfo(baseUrl=https://my.domain.com, callName=geneticusescreepdelicately, urlParams=[]), email='', passcode=null, call                                                              StatsUsernameOverride=, displayName=), callLoginParams=XmppCredentials(domain=recorder.my.domain.com, port=null, username=recorder, password=*****), sipClientParam                                                              s=SipClientParams(sipAddress=my-sip@address, displayName=Bger Lausanne, autoAnswer=false, userName=null, password=null))
2022-02-23 13:52:24.774 INFO: [77] org.openqa.selenium.remote.ProtocolHandshake.createSession: Detected dialect: OSS
2022-02-23 13:52:24.785 FINE: [77] JibriStatsDClient.incrementCounter#38: Incrementing statsd counter: start:sip_gateway
2022-02-23 13:52:24.786 INFO: [77] JibriStatusManager$$special$$inlined$observable$1.afterChange#72: Busy status has changed: IDLE -> BUSY
2022-02-23 13:52:24.786 FINE: [77] WebhookClient$updateStatus$1.invokeSuspend#107: Updating 0 subscribers of status
2022-02-23 13:52:24.786 INFO: [77] XmppApi.updatePresence#144: Jibri reports its status is now JibriStatus(busyStatus=BUSY, health=OverallHealth(healthStatus=HEALTHY, details=                                                              {})), publishing presence to connections
2022-02-23 13:52:24.793 INFO: [77] XmppApi.handleStartJibriIq#207: Sending 'pending' response to start IQ
2022-02-23 13:52:24.797 INFO: [88] AbstractPageObject.visit#32: Visiting url https://my.domain.com
2022-02-23 13:52:26.206 INFO: [88] AbstractPageObject.visit#38: Waited 1.41s for driver to load page
2022-02-23 13:52:26.277 INFO: [88] AbstractPageObject.visit#32: Visiting url https://my.domain.com/geneticusescreepdelicately#config.iAmRecorder=true&config.iAmSip                                                              Gateway=true&config.ignoreStartMuted=true&config.analytics.disabled=true&config.enableEmailInStats=false&config.p2p.enabled=false&config.prejoinPageEnabled=false&config.prejoi                                                              nConfig.enabled=false&config.requireDisplayName=false&devices.videoInput="PJSUA"
2022-02-23 13:52:27.168 INFO: [88] AbstractPageObject.visit#38: Waited 891ms for driver to load page
2022-02-23 13:52:27.210 FINE: [88] CallPage$visit$$inlined$measureTimedValue$lambda$1.apply#58: Not joined yet: Cannot read properties of undefined (reading 'isJoined')
2022-02-23 13:52:27.720 FINE: [88] CallPage$visit$$inlined$measureTimedValue$lambda$1.apply#58: Not joined yet: Cannot read properties of undefined (reading 'isJoined')
2022-02-23 13:52:28.746 INFO: [88] CallPage.visit#71: Waited 1.58s to join the conference
2022-02-23 13:52:28.747 INFO: [88] EmptyCallStatusCheck.<init>#26: Starting empty call check with a timeout of PT30M
2022-02-23 13:52:28.747 INFO: [88] LocalParticipantKickedStatusCheck.<init>#14: Starting local participant kicked out call check
2022-02-23 13:52:28.767 INFO: [88] JibriSelenium.onSeleniumStateChange#215: Transitioning from state Starting up to Running
2022-02-23 13:52:28.768 INFO: [88] SipGatewayJibriService$start$2.invoke#139: Selenium joined the call, starting pjsua
2022-02-23 13:52:28.769 INFO: [88] JibriSubprocess.launch#42: Starting pjsua with command /opt/jitsi/jibri/pjsua.sh --id=Bger Lausanne <sip:jibri@127.0.0.1> sip:bger-lausanne@                                                              facegate.biz ([/opt/jitsi/jibri/pjsua.sh, --id=Bger Lausanne <sip:jibri@127.0.0.1>, sip:my-sip@address])
2022-02-23 13:52:29.773 INFO: [94] StatefulJibriService.onServiceStateChange#39: SIP gateway service transitioning from state Starting up to Running
2022-02-23 13:52:29.773 INFO: [94] XmppApi$createServiceStatusHandler$1.invoke#260: Current service started up successfully, sending on iq <iq xmlns='jabber:client' to='thesip                                                              brewery@conference.my.domain.com/focus' id='K8Q1N-119' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' status='on' sipaddress='my-sip@address                                                              '/></iq>
2022-02-23 13:52:33.773 FINE: [17] ProcessStatePublisher$startProcessAliveChecks$1.invoke#86: Process pjsua hasn't written in 2 seconds, publishing periodic update
2022-02-23 13:52:35.773 FINE: [17] ProcessStatePublisher$startProcessAliveChecks$1.invoke#86: Process pjsua hasn't written in 2 seconds, publishing periodic update
2022-02-23 13:52:37.772 FINE: [17] ProcessStatePublisher$startProcessAliveChecks$1.invoke#86: Process pjsua hasn't written in 2 seconds, publishing periodic update
2022-02-23 13:52:39.772 FINE: [17] ProcessStatePublisher$startProcessAliveChecks$1.invoke#86: Process pjsua hasn't written in 2 seconds, publishing periodic update
2022-02-23 13:52:41.772 FINE: [17] ProcessStatePublisher$startProcessAliveChecks$1.invoke#86: Process pjsua hasn't written in 2 seconds, publishing periodic update
2022-02-23 13:52:43.837 INFO: [17] MediaReceivedStatusCheck.run#40: Jibri client receive bitrates: {audio={download=0, upload=0}, download=0, upload=0, video={download=0, uplo                                                              ad=0}}, num participants: 1, numMutedParticipants: 0, numJigasis: 0, all clients muted? false
2022-02-23 13:52:43.846 FINE: [17] ProcessStatePublisher$startProcessAliveChecks$1.invoke#86: Process pjsua hasn't written in 2 seconds, publishing periodic update
2022-02-23 13:52:45.772 FINE: [17] ProcessStatePublisher$startProcessAliveChecks$1.invoke#86: Process pjsua hasn't written in 2 seconds, publishing periodic update
2022-02-23 13:52:47.772 FINE: [17] ProcessStatePublisher$startProcessAliveChecks$1.invoke#86: Process pjsua hasn't written in 2 seconds, publishing periodic update
2022-02-23 13:52:49.772 FINE: [17] ProcessStatePublisher$startProcessAliveChecks$1.invoke#86: Process pjsua hasn't written in 2 seconds, publishing periodic update
2022-02-23 13:52:51.772 FINE: [17] ProcessStatePublisher$startProcessAliveChecks$1.invoke#86: Process pjsua hasn't written in 2 seconds, publishing periodic update
2022-02-23 13:52:53.772 FINE: [17] ProcessStatePublisher$startProcessAliveChecks$1.invoke#86: Process pjsua hasn't written in 2 seconds, publishing periodic update
2022-02-23 13:52:55.772 FINE: [17] ProcessStatePublisher$startProcessAliveChecks$1.invoke#86: Process pjsua hasn't written in 2 seconds, publishing periodic update
2022-02-23 13:52:57.772 FINE: [17] ProcessStatePublisher$startProcessAliveChecks$1.invoke#86: Process pjsua hasn't written in 2 seconds, publishing periodic update
2022-02-23 13:52:58.791 INFO: [17] MediaReceivedStatusCheck.run#40: Jibri client receive bitrates: {audio={download=29, upload=0}, download=221, upload=0, video={download=192,                                                               upload=0}}, num participants: 1, numMutedParticipants: 0, numJigasis: 0, all clients muted? false
2022-02-23 13:52:59.772 FINE: [17] ProcessStatePublisher$startProcessAliveChecks$1.invoke#86: Process pjsua hasn't written in 2 seconds, publishing periodic update
2022-02-23 13:53:01.772 FINE: [17] ProcessStatePublisher$startProcessAliveChecks$1.invoke#86: Process pjsua hasn't written in 2 seconds, publishing periodic update
2022-02-23 13:53:01.773 INFO: [94] StatefulJibriService.onServiceStateChange#39: SIP gateway service transitioning from state Running to Error: RemoteSipClientBusy SESSION Rem                                                              ote side busy
2022-02-23 13:53:01.774 INFO: [94] XmppApi$createServiceStatusHandler$1.invoke#243: Current service had an error Error: RemoteSipClientBusy SESSION Remote side busy, sending e                                                              rror iq <iq xmlns='jabber:client' to='thesipbrewery@conference.my.domain.com/focus' id='K8Q1N-122' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' status                                                              ='off' sipaddress='my-sip@address' failure_reason='error' should_retry='true'/></iq>
2022-02-23 13:53:01.774 FINE: [94] JibriStatsDClient.incrementCounter#38: Incrementing statsd counter: stop:sip_gateway
2022-02-23 13:53:01.775 INFO: [94] JibriManager.stopService#260: Stopping the current service
2022-02-23 13:53:01.775 INFO: [94] JibriSubprocess.stop#75: Stopping pjsua process
2022-02-23 13:53:01.779 INFO: [94] JibriSubprocess.stop#89: pjsua exited with value 2
2022-02-23 13:53:01.779 INFO: [94] JibriSelenium.leaveCallAndQuitBrowser#336: Leaving call and quitting browser
2022-02-23 13:53:01.779 INFO: [94] JibriSelenium.leaveCallAndQuitBrowser#339: Recurring call status checks cancelled
2022-02-23 13:53:01.821 INFO: [94] JibriSelenium.leaveCallAndQuitBrowser#345: Got 15 log entries for type browser
2022-02-23 13:53:01.890 INFO: [94] JibriSelenium.leaveCallAndQuitBrowser#345: Got 762 log entries for type driver
2022-02-23 13:53:02.048 INFO: [94] JibriSelenium.leaveCallAndQuitBrowser#345: Got 0 log entries for type client
2022-02-23 13:53:02.049 INFO: [94] JibriSelenium.leaveCallAndQuitBrowser#354: Leaving web call
2022-02-23 13:53:02.228 INFO: [94] JibriSelenium.leaveCallAndQuitBrowser#361: Quitting chrome driver
2022-02-23 13:53:02.316 INFO: [94] JibriSelenium.leaveCallAndQuitBrowser#363: Chrome driver quit
2022-02-23 13:53:02.317 INFO: [94] JibriServiceFinalizeCommandRunner.doFinalize#44: Finalizing the jibri service operation using command [/opt/jitsi/jibri/finalize_sip.sh]
2022-02-23 13:53:02.322 INFO: [88] LoggingUtils$Companion$OutputLogger$1$1.call#42: Appending pjsua logs from /var/log/jitsi/jibri/pjsua.log, to /var/log/jitsi/jibri/pjsua_all                                                              .log
2022-02-23 13:53:02.323 INFO: [94] JibriServiceFinalizeCommandRunner.doFinalize#60: Finalize script finished with exit value 0
2022-02-23 13:53:02.323 INFO: [94] JibriStatusManager$$special$$inlined$observable$1.afterChange#72: Busy status has changed: BUSY -> IDLE
2022-02-23 13:53:02.324 FINE: [94] WebhookClient$updateStatus$1.invokeSuspend#107: Updating 0 subscribers of status
2022-02-23 13:53:02.325 INFO: [94] XmppApi.updatePresence#144: Jibri reports its status is now JibriStatus(busyStatus=IDLE, health=OverallHealth(healthStatus=HEALTHY, details=                                                              {})), publishing presence to connections
2022-02-23 13:53:13.272 FINE: [17] WebhookClient$updateStatus$1.invokeSuspend#107: Updating 0 subscribers of status

Jicofo;

Jicofo 2022-02-23 13:57:21.264 INFO: [261] JibriSession.startInternal#320: Starting session with Jibri thesipbrewery@conference.my.domain.com/jibri-nickname
Jicofo 2022-02-23 13:57:21.264 INFO: [261] JibriSession.sendJibriStartIq#474: Starting Jibri thesipbrewery@conference.my.domain.com/jibri-nickname for stream ID: null in room: woodenmonitorsendorsebadly@conference.my.domain.com
Jicofo 2022-02-23 13:57:22.005 INFO: [261] JibriSession.processJibriIqFromJibri#435: Updating status from JIBRI: <iq xmlns='jabber:client' to='focus@auth.my.domain.com/focus' from='thesipbrewery@conference.my.domain.com/jibri-nickname' id='KM7A4-806' type='result'><jibri xmlns='http://jitsi.org/protocol/jibri' status='pending' sipaddress='my-sip@address'/></iq> for woodenmonitorsendorsebadly@conference.my.domain.com
Jicofo 2022-02-23 13:57:22.006 INFO: [261] JibriSession.handleJibriStatusUpdate#623: Got Jibri status update: Jibri thesipbrewery@conference.my.domain.com/jibri-nickname has status pending and failure reason null, current Jibri jid is thesipbrewery@conference.my.domain.com/jibri-nickname
Jicofo 2022-02-23 13:57:22.006 INFO: [261] [room=woodenmonitorsendorsebadly@conference.my.domain.com meeting_id=63904d28-064a-4a50-8214-b0c8169724ac] JibriSipGateway.handleStartRequest#91: Started Jibri session
Jicofo 2022-02-23 13:57:25.286 INFO: [261] ConferenceIqHandler.handleConferenceIq#63: Focus request for room: woodenmonitorsendorsebadly@conference.my.domain.com
Jicofo 2022-02-23 13:57:25.454 INFO: [262] [room=woodenmonitorsendorsebadly@conference.my.domain.com meeting_id=63904d28-064a-4a50-8214-b0c8169724ac] JitsiMeetConferenceImpl.onMemberJoined#596: Member joined:6dc6612a
Jicofo 2022-02-23 13:57:25.456 INFO: [261] DiscoveryUtil.discoverParticipantFeatures#154: Doing feature discovery for woodenmonitorsendorsebadly@conference.my.domain.com/6dc6612a
Jicofo 2022-02-23 13:57:25.456 INFO: [261] DiscoveryUtil.discoverParticipantFeatures#194: Successfully discovered features for woodenmonitorsendorsebadly@conference.my.domain.com/6dc6612a in 0
Jicofo 2022-02-23 13:57:25.458 INFO: [261] [room=woodenmonitorsendorsebadly@conference.my.domain.com meeting_id=63904d28-064a-4a50-8214-b0c8169724ac] ColibriV1SessionManager.allocate#145: Added participant id=6dc6612a, bridge=jvbbrewery@internal.auth.my.domain.com/6a99ce57-7d20-4510-8970-45e0c7784390
Jicofo 2022-02-23 13:57:25.458 INFO: [261] [room=woodenmonitorsendorsebadly@conference.my.domain.com meeting_id=63904d28-064a-4a50-8214-b0c8169724ac] ColibriV1SessionManager.allocateChannels#165: Using jvbbrewery@internal.auth.my.domain.com/6a99ce57-7d20-4510-8970-45e0c7784390 to allocate channels for: Participant[woodenmonitorsendorsebadly@conference.my.domain.com/6dc6612a]@1659781290
Jicofo 2022-02-23 13:57:25.504 INFO: [261] [room=woodenmonitorsendorsebadly@conference.my.domain.com meeting_id=63904d28-064a-4a50-8214-b0c8169724ac participant=6dc6612a] ParticipantInviteRunnable.doInviteOrReinvite#411: Sending session-initiate to: woodenmonitorsendorsebadly@conference.my.domain.com/6dc6612a
Jicofo 2022-02-23 13:57:25.883 INFO: [262] [room=woodenmonitorsendorsebadly@conference.my.domain.com meeting_id=63904d28-064a-4a50-8214-b0c8169724ac] JitsiMeetConferenceImpl.onSessionAccept#948: Receive session-accept from woodenmonitorsendorsebadly@conference.my.domain.com/6dc6612a
Jicofo 2022-02-23 13:57:25.884 INFO: [262] [room=woodenmonitorsendorsebadly@conference.my.domain.com meeting_id=63904d28-064a-4a50-8214-b0c8169724ac] JitsiMeetConferenceImpl.onSessionAcceptInternal#1301: Participant[woodenmonitorsendorsebadly@conference.my.domain.com/6dc6612a]@1659781290 did not advertise any SSRCs. Injecting 3986180900
Jicofo 2022-02-23 13:57:25.885 INFO: [262] [room=woodenmonitorsendorsebadly@conference.my.domain.com meeting_id=63904d28-064a-4a50-8214-b0c8169724ac] JitsiMeetConferenceImpl.onSessionAcceptInternal#1315: Accepted initial sources from 6dc6612a: {woodenmonitorsendorsebadly@conference.my.domain.com/6dc6612a=[audio=[3986180900], video=[], groups=[]]}
Jicofo 2022-02-23 13:57:26.960 INFO: [261] JibriSession.processJibriIqFromJibri#435: Updating status from JIBRI: <iq xmlns='jabber:client' to='focus@auth.my.domain.com/focus' from='thesipbrewery@conference.my.domain.com/jibri-nickname' id='Zm9jdXNAYXV0aC52bS1iZ2VyLWppdHNpLTAyLnR1eDQyLmNoL2ZvY3VzAEs4UTFOLTE0OAD70Wqx7HZK+tmXNqP++lyO' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' status='on' sipaddress='my-sip@address'/></iq> for woodenmonitorsendorsebadly@conference.my.domain.com
Jicofo 2022-02-23 13:57:26.960 INFO: [261] JibriSession.handleJibriStatusUpdate#623: Got Jibri status update: Jibri thesipbrewery@conference.my.domain.com/jibri-nickname has status on and failure reason null, current Jibri jid is thesipbrewery@conference.my.domain.com/jibri-nickname
Jicofo 2022-02-23 13:57:26.960 INFO: [261] JibriSession.clearPendingTimeout#575: Jibri is no longer pending, cancelling pending timeout task
Jicofo 2022-02-23 13:57:26.960 INFO: [261] JibriSession.handleJibriStatusUpdate#707: Jibri session started, notifying owner
Jicofo 2022-02-23 13:57:26.960 INFO: [261] [room=woodenmonitorsendorsebadly@conference.my.domain.com meeting_id=63904d28-064a-4a50-8214-b0c8169724ac] JibriSipGateway.publishJibriSipCallState#143: Publishing new state: my-sip@address <jibri-sip-call-state xmlns='http://jitsi.org/protocol/jibri/call_state' state='on' sipaddress='my-sip@address' session_id='yevqrxbnyclfmmac'/>
Jicofo 2022-02-23 13:57:58.962 INFO: [261] JibriSession.processJibriIqFromJibri#435: Updating status from JIBRI: <iq xmlns='jabber:client' to='focus@auth.my.domain.com/focus' from='thesipbrewery@conference.my.domain.com/jibri-nickname' id='Zm9jdXNAYXV0aC52bS1iZ2VyLWppdHNpLTAyLnR1eDQyLmNoL2ZvY3VzAEs4UTFOLTE1MQD70Wqx7HZK+tmXNqP++lyO' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' status='off' sipaddress='my-sip@address' failure_reason='error' should_retry='true'/></iq> for woodenmonitorsendorsebadly@conference.my.domain.com
Jicofo 2022-02-23 13:57:58.963 INFO: [261] JibriSession.handleJibriStatusUpdate#623: Got Jibri status update: Jibri thesipbrewery@conference.my.domain.com/jibri-nickname has status off and failure reason error, current Jibri jid is thesipbrewery@conference.my.domain.com/jibri-nickname
Jicofo 2022-02-23 13:57:58.963 INFO: [261] JibriSession.handleJibriStatusUpdate#662: Jibri failed, trying to fall back to another Jibri
Jicofo 2022-02-23 13:57:58.964 SEVERE: [261] JibriSession.startInternal#308: Unable to find an available Jibri, can't start
Jicofo 2022-02-23 13:57:58.964 WARNING: [261] JibriSession.handleJibriStatusUpdate#673: Failed to fall back to another Jibri, this session has now failed: org.jitsi.jicofo.jibri.JibriSession$StartException$AllBusy: All jibri instances are busy
org.jitsi.jicofo.jibri.JibriSession$StartException$AllBusy: All jibri instances are busy
        at org.jitsi.jicofo.jibri.JibriSession.startInternal(JibriSession.java:312)
        at org.jitsi.jicofo.jibri.JibriSession.start(JibriSession.java:286)
        at org.jitsi.jicofo.jibri.JibriSession.retryRequestWithAnotherJibri(JibriSession.java:599)
        at org.jitsi.jicofo.jibri.JibriSession.handleJibriStatusUpdate(JibriSession.java:666)
        at org.jitsi.jicofo.jibri.JibriSession.processJibriIqFromJibri(JibriSession.java:437)
        at org.jitsi.jicofo.jibri.JibriSession.processJibriIqRequestFromJibri(JibriSession.java:421)
        at org.jitsi.jicofo.jibri.BaseJibri.doHandleIQRequest(BaseJibri.kt:158)
        at org.jitsi.jicofo.jibri.BaseJibri.incomingIqQueue$lambda-0(BaseJibri.kt:56)
        at org.jitsi.utils.queue.PacketQueue$HandlerAdapter.handleItem(PacketQueue.java:381)
        at org.jitsi.utils.queue.AsyncQueueHandler$1.run(AsyncQueueHandler.java:133)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
        at java.base/java.lang.Thread.run(Thread.java:833)
Jicofo 2022-02-23 13:57:58.965 INFO: [261] [room=woodenmonitorsendorsebadly@conference.my.domain.com meeting_id=63904d28-064a-4a50-8214-b0c8169724ac] JibriSipGateway.publishJibriSipCallState#143: Publishing new state: my-sip@address <jibri-sip-call-state xmlns='http://jitsi.org/protocol/jibri/call_state' state='off' failure_reason='error' sipaddress='my-sip@address' session_id='yevqrxbnyclfmmac'/>
Jicofo 2022-02-23 13:57:58.965 INFO: [261] [room=woodenmonitorsendorsebadly@conference.my.domain.com meeting_id=63904d28-064a-4a50-8214-b0c8169724ac] JibriSipGateway.onSessionStateChanged#121: Removing SIP call: my-sip@address
Jicofo 2022-02-23 13:57:58.965 INFO: [261] JibriSession.cleanupSession#390: Cleaning up current JibriSession
Jicofo 2022-02-23 13:57:59.211 INFO: [253] [room=woodenmonitorsendorsebadly@conference.my.domain.com meeting_id=63904d28-064a-4a50-8214-b0c8169724ac] JitsiMeetConferenceImpl.onMemberLeft#782: Member left:6dc6612a
Jicofo 2022-02-23 13:57:59.212 INFO: [253] [room=woodenmonitorsendorsebadly@conference.my.domain.com meeting_id=63904d28-064a-4a50-8214-b0c8169724ac] JitsiMeetConferenceImpl.terminateParticipant#824: Terminating 6dc6612a, reason: gone, send session-terminate: false
Jicofo 2022-02-23 13:57:59.212 INFO: [253] AbstractOperationSetJingle.terminateSession#479: Terminate session: woodenmonitorsendorsebadly@conference.my.domain.com/6dc6612a, reason: gone, send terminate: false
Jicofo 2022-02-23 13:57:59.214 INFO: [253] [room=woodenmonitorsendorsebadly@conference.my.domain.com meeting_id=63904d28-064a-4a50-8214-b0c8169724ac] JitsiMeetConferenceImpl.terminateParticipant#852: Removed participant 6dc6612a removed=true
Jicofo 2022-02-23 13:57:59.216 INFO: [253] [room=woodenmonitorsendorsebadly@conference.my.domain.com meeting_id=63904d28-064a-4a50-8214-b0c8169724ac bs_id=9844b6] BridgeSession.terminate#201: Expiring channels for: Participant[woodenmonitorsendorsebadly@conference.my.domain.com/6dc6612a]@1659781290 on: Bridge[jid=jvbbrewery@internal.auth.my.domain.com/6a99ce57-7d20-4510-8970-45e0c7784390, relayId=null, region=null, stress=0.00]
Jicofo 2022-02-23 13:57:59.221 INFO: [253] [room=woodenmonitorsendorsebadly@conference.my.domain.com meeting_id=63904d28-064a-4a50-8214-b0c8169724ac] JitsiMeetConferenceImpl.rescheduleSingleParticipantTimeout#1845: Scheduled single person timeout.
Jicofo 2022-02-23 13:58:19.221 INFO: [84] [room=woodenmonitorsendorsebadly@conference.my.domain.com meeting_id=63904d28-064a-4a50-8214-b0c8169724ac] JitsiMeetConferenceImpl$SinglePersonTimeout.run#1981: Timing out single participant: 42f8db57
Jicofo 2022-02-23 13:58:19.222 INFO: [84] [room=woodenmonitorsendorsebadly@conference.my.domain.com meeting_id=63904d28-064a-4a50-8214-b0c8169724ac] JitsiMeetConferenceImpl.terminateParticipant#824: Terminating 42f8db57, reason: expired, send session-terminate: true
Jicofo 2022-02-23 13:58:19.222 INFO: [84] AbstractOperationSetJingle.terminateSession#479: Terminate session: woodenmonitorsendorsebadly@conference.my.domain.com/42f8db57, reason: expired, send terminate: true
Jicofo 2022-02-23 13:58:19.223 INFO: [84] [room=woodenmonitorsendorsebadly@conference.my.domain.com meeting_id=63904d28-064a-4a50-8214-b0c8169724ac] JitsiMeetConferenceImpl.terminateParticipant#852: Removed participant 42f8db57 removed=true
Jicofo 2022-02-23 13:58:19.224 INFO: [84] [room=woodenmonitorsendorsebadly@conference.my.domain.com meeting_id=63904d28-064a-4a50-8214-b0c8169724ac bs_id=9844b6] BridgeSession.terminate#201: Expiring channels for: Participant[woodenmonitorsendorsebadly@conference.my.domain.com/42f8db57]@856267658 on: Bridge[jid=jvbbrewery@internal.auth.my.domain.com/6a99ce57-7d20-4510-8970-45e0c7784390, relayId=null, region=null, stress=0.00]

Here are my config files I thought relevant;

pjsua;

--video
--vcapture-dev=-1
--no-color
--log-level=4
--app-log-level=4
--nameserver 8.8.8.8
--auto-update-nat 0
--disable-stun
--no-tcp
--dis-codec GSM
--dis-codec H263
--dis-codec iLBC
--dis-codec G722
--dis-codec speex
--dis-codec pcma
--dis-codec pcmu
--dis-codec opus
--add-codec pcmu
--add-codec pcma
--add-codec speex
--add-codec G722
--add-codec opus
--no-vad
--ec-tail 0
--quality 10
--log-file=/tmp/pjsua.log

jibri

    xmpp {
      // See example_xmpp_envs.conf for an example of what is expected here
      environments = [
              {
                name = "prod environment"
                xmpp-server-hosts = ["my.domain.com"]
                xmpp-domain = "my.domain.com"

                control-muc {
                    domain = "internal.auth.my.domain.com"
                    room-name = "JibriBrewery"
                    nickname = "jibri-nickname"
                }

                sip-control-muc {
                    domain = "conference.my.domain.com"
                    room-name = "TheSipBrewery"
                    nickname = "jibri-nickname"
                }

                control-login {
                    domain = "auth.my.domain.com"
                    username = "jibri"
                    password = "jibri_password"
                }

                call-login {
                    domain = "recorder.my.domain.com"
                    username = "recorder"
                    password = "recorder_password"
                }

                strip-from-room-domain = "conference."
                usage-timeout = 0
                trust-all-xmpp-certs = true
            }]
    }

I’ve added this to the sip-communicator properties of jicofo;

org.jitsi.jicofo.jibri.SIP_BREWERY=TheSipBrewery@conference.my.domain.com

Additional info;
All components are installed on the same machine.
I am using the PJSUA from GitHub - jitsi/pjproject: PJSIP fork used in Jibri https://github.com/jitsi/jibri
I’ll be happy to provide additional info on request.

From what I can gather, Jibri runs PJSUA successfully at first, but then it somehow crashes. I can see this

Jicofo 2022-02-23 13:57:58.962 INFO: [261] JibriSession.processJibriIqFromJibri#435: Updating status from JIBRI: <iq xmlns='jabber:client' to='focus@auth.my.domain.com/focus' from='thesipbrewery@conference.my.domain.com/jibri-nickname' id='Zm9jdXNAYXV0aC52bS1iZ2VyLWppdHNpLTAyLnR1eDQyLmNoL2ZvY3VzAEs4UTFOLTE1MQD70Wqx7HZK+tmXNqP++lyO' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' status='off' sipaddress='my-sip@address' failure_reason='error' should_retry='true'/></iq> for woodenmonitorsendorsebadly@conference.my.domain.com

in Jicofo logs.

Hello,

The problem might be the MTU size being too large to be sent over UDP.

I suggest forcing PJSUA to use TCP, so you’ll need to remove the --no-tcp from pjsua.config.

From the pjsua docs: By default, TCP transport will be created and initialized. However, TCP will not be used automatically unless the destination URL has “;transport=tcp” parameter in it. (Note: this behavior may change once we support resolving NAPTR records).

Considering this, the destination should look like sip:the_sip_address@device;transport=tcp

Hope it works!

Hi.

I’ve tried as you suggested. I removed the --no-tcp line from the pjsua.config, and added ;transport=tcp. Pjsua logs show that it’s indeed using tcp now. But, everything else is, unfortunately, the same. It still disconnects due to Request Timeout, Jibri still crashes and Jicofo still shows the same error. Thanks for your attention, though.

Maybe add also --use-tls in the pjsua.config.
If it still doesn’t work, please paste the pjsua logs again to have another look.

I’ll take issue with the statement that TCP can’t suffer from MTU problems. In my experience it can very much happen. In theory it should not happen, because competent network admins let pings flow through their infra and well-designed network stacks adjust the packet size dynamically. Unfortunately first assertion is very often false. Since you and only you know what’s really in your log it’s not possible to assert that packets are really going from your device to your sip Gateway, but if that is the case, MTU problems are very much the #1 suspect TCP or not TCP. If that is the case, try to lower MTU and MSS on the network stack of your gateway.

sudo ip link set dev eth0 mtu 1300
or
sudo ip link set dev yournetworkinterface mtu 1300

Thank you, but it still doesn’t work in the exact same way. Here are the new pjsua logs

15:26:10.993         sip_endpoint.c  .Module "mod-pjsua-log" registered
15:26:10.993           pjsua_core.c  .Nameserver 8.8.8.8 added
15:26:10.993         sip_endpoint.c  .Module "mod-tsx-layer" registered
15:26:10.993         sip_endpoint.c  .Module "mod-stateful-util" registered
15:26:10.993         sip_endpoint.c  .Module "mod-ua" registered
15:26:10.993         sip_endpoint.c  .Module "mod-100rel" registered
15:26:10.993         sip_endpoint.c  .Module "mod-pjsua" registered
15:26:10.993         sip_endpoint.c  .Module "mod-invite" registered
15:26:11.016             alsa_dev.c  ..ALSA driver found 24 devices
15:26:11.016             alsa_dev.c  ..ALSA initialized
15:26:11.016                  pjlib  ..select() I/O Queue created (0x55c7fd7302d8)
15:26:11.020            pjsua_vid.c  ..Initializing video subsystem..
15:26:11.020                  vpx.c  ...VPX codec initialized
15:26:11.020             v4l2_dev.c  ...Video4Linux2 has 0 devices
15:26:11.055              sdl_dev.c  ...SDL 2.0 initialized
15:26:11.055         colorbar_dev.c  ...Colorbar video src initialized with 2 device(s):
15:26:11.055         colorbar_dev.c  ... 0: Colorbar generator
15:26:11.055         colorbar_dev.c  ... 1: Colorbar-active
15:26:11.055         sip_endpoint.c  .Module "mod-evsub" registered
15:26:11.055         sip_endpoint.c  .Module "mod-presence" registered
15:26:11.055         sip_endpoint.c  .Module "mod-mwi" registered
15:26:11.055         sip_endpoint.c  .Module "mod-refer" registered
15:26:11.055         sip_endpoint.c  .Module "mod-pjsua-pres" registered
15:26:11.055         sip_endpoint.c  .Module "mod-pjsua-im" registered
15:26:11.055         sip_endpoint.c  .Module "mod-pjsua-options" registered
15:26:11.056           pjsua_core.c  .1 SIP worker threads created
15:26:11.056           pjsua_core.c  .pjsua version 2.10-jitsi3 for Linux-5.10.0.11/x86_64/glibc-2.31 initialized
15:26:11.056           pjsua_core.c  .PJSUA state changed: CREATED --> INIT
15:26:11.056         sip_endpoint.c  Module "mod-default-handler" registered
15:26:11.056           pjsua_core.c  SIP UDP socket reachable at my.ip.address:5060
15:26:11.056      udp0x55c7fd722d90  SIP UDP transport started, published address is my.ip.address:5060
15:26:11.056            pjsua_acc.c  Adding account: id=<sip:my.ip.address:5060>
15:26:11.056            pjsua_acc.c  .Account <sip:my.ip.address:5060> added with id 0
15:26:11.056            pjsua_acc.c  Modifying account 0
15:26:11.056            pjsua_acc.c  Acc 0: setting online status to 1..
15:26:11.056             tcptp:5060  SIP TCP listener ready for incoming connections at my.ip.address:5060
15:26:11.056            pjsua_acc.c  Adding account: id=<sip:my.ip.address:5060;transport=TCP>
15:26:11.056            pjsua_acc.c  .Account <sip:my.ip.address:5060;transport=TCP> added with id 1
15:26:11.056            pjsua_acc.c  Modifying account 1
15:26:11.056            pjsua_acc.c  Acc 1: setting online status to 1..
15:26:11.057             tlstp:5061  SIP TLS listener is ready for incoming connections at my.ip.address:5061
15:26:11.057            pjsua_acc.c  Adding account: id=<sip:my.ip.address:5061;transport=TLS>
15:26:11.057            pjsua_acc.c  .Account <sip:my.ip.address:5061;transport=TLS> added with id 2
15:26:11.057            pjsua_acc.c  Modifying account 2
15:26:11.057            pjsua_acc.c  Acc 2: setting online status to 1..
15:26:11.057            pjsua_acc.c  Adding account: id=My ID <sip:jibri@127.0.0.1>
15:26:11.057            pjsua_acc.c  .Account My ID <sip:jibri@127.0.0.1> added with id 3
15:26:11.057            pjsua_acc.c  Acc 3: setting online status to 1..
15:26:11.057           pjsua_pres.c  Adding buddy: sip:sip-address@device;transport=tcp
15:26:11.057           pjsua_pres.c  .Buddy 0 added.
15:26:11.057           pjsua_pres.c  ..Buddy 0: updating presence..
15:26:11.057           pjsua_core.c  PJSUA state changed: INIT --> STARTING
15:26:11.057         sip_endpoint.c  .Module "mod-unsolicited-mwi" registered
15:26:11.057           pjsua_core.c  .PJSUA state changed: STARTING --> RUNNING
15:26:11.057                 main.c  Ready: Success
15:26:11.057           pjsua_call.c  Making call with acc #3 to sip:sip-address@device;transport=tcp
15:26:11.057            pjsua_aud.c  .Set sound device: capture=-1, playback=-2
15:26:11.057            pjsua_app.c  ..Turning sound device -1 -2 ON
15:26:11.057            pjsua_aud.c  ..Opening sound device (speaker + mic) PCM@16000/1/20ms
15:26:11.058            pjsua_acc.c  .Warning: cannot use source TCP/TLS socket address for Contact when nameserver is configured.
15:26:11.058          pjsua_media.c  .Call 0: initializing media..
15:26:11.058          pjsua_media.c  ..RTP socket reachable at my.ip.address:4000
15:26:11.058          pjsua_media.c  ..RTCP socket reachable at my.ip.address:4001
15:26:11.058          pjsua_media.c  ..RTP socket reachable at my.ip.address:4002
15:26:11.058          pjsua_media.c  ..RTCP socket reachable at my.ip.address:4003
15:26:11.058          pjsua_media.c  ..Media index 0 selected for audio call 0
15:26:11.059             resolver.c  ....Transmitting 40 bytes to NS 0 (8.8.8.8:53): DNS SRV query for _sip._tcp.facegate.biz: Success
15:26:11.059            pjsua_app.c  .......Call 0 state changed to CALLING
15:26:11.078             resolver.c !Transmitting 28 bytes to NS 0 (8.8.8.8:53): DNS A query for ygg1.vp.vc: Success
15:26:11.078             resolver.c  Transmitting 28 bytes to NS 0 (8.8.8.8:53): DNS A query for ygg2.vp.vc: Success
15:26:11.091     tcpc0x7fdda40013d8  TCP client transport created
15:26:11.091     tcpc0x7fdda40013d8  TCP transport my.ip.address:54971 is connecting to guessing.device.ip:5060...
15:26:11.091           pjsua_core.c  TX 1751 bytes Request msg INVITE/cseq=11590 (tdta0x55c7fd7428f8) to TCP guessing.device.ip:5060:
INVITE sip:sip-address@device;transport=tcp SIP/2.0
Via: SIP/2.0/TCP my.ip.address:54971;rport;branch=z9hG4bKPj8f9b6a98-f485-40a1-a7b9-e6f127264452;alias
Max-Forwards: 70
From: "My ID" <sip:jibri@127.0.0.1>;tag=53c9372f-cd85-44b0-a005-b789d6b7de9e
To: sip:sip-address@device
Contact: "My ID" <sip:jibri@my.ip.address:5060;transport=TCP;ob>
Call-ID: 930851c3-59d5-4867-84f3-c8ca78304e65
CSeq: 11590 INVITE
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Supported: replaces, 100rel, timer, norefersub
Session-Expires: 1800
Min-SE: 90
User-Agent: PJSUA v2.10-jitsi3 Linux-5.10.0.11/x86_64/glibc-2.31
Content-Type: application/sdp
Content-Length:   995

v=0
o=- 3854701571 3854701571 IN IP4 my.ip.address
s=pjmedia
b=AS:2742
t=0 0
a=X-nat:0
m=audio 4000 RTP/AVP 96 9 97 98 99 8 0 120 121 122 123
c=IN IP4 my.ip.address
b=TIAS:96000
a=rtcp:4001 IN IP4 my.ip.address
a=sendrecv
a=rtpmap:96 opus/48000/2
a=fmtp:96 useinbandfec=1
a=rtpmap:9 G722/8000
a=rtpmap:97 speex/32000
a=rtpmap:98 speex/16000
a=rtpmap:99 speex/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:120 telephone-event/48000
a=fmtp:120 0-16
a=rtpmap:121 telephone-event/8000
a=fmtp:121 0-16
a=rtpmap:122 telephone-event/32000
a=fmtp:122 0-16
a=rtpmap:123 telephone-event/16000
a=fmtp:123 0-16
a=ssrc:835749965 cname:1ffa59f21f452534
m=video 4002 RTP/AVP 97 102
c=IN IP4 my.ip.address
b=TIAS:2500000
a=rtcp:4003 IN IP4 my.ip.address
a=sendrecv
a=rtpmap:97 H264/90000
a=fmtp:97 profile-level-id=42801f; packetization-mode=1
a=rtpmap:102 VP8/90000
a=fmtp:102 max-fr=30; max-fs=580
a=ssrc:1809964580 cname:1ffa59f21f452534
a=rtcp-fb:* nack pli

--end msg--
15:26:43.059            pjsua_app.c  ....Call 0 is DISCONNECTED [reason=408 (Request Timeout)]
15:26:43.059     pjsua_app_common.c  ....
  [DISCONNCTD] To: sip:sip-address@device
    Call time: 00h:00m:00s, 1st res in 32001 ms, conn in 0ms

I do not have eth0, but I have ens3. I have lowered its MTU from 1600 to 1300, but no cigar, I’m afraid.

Usually when it’s a MTU problem 1300 is sufficient. But is it a MTU problem though, I don’t know. The important test is to see if any packet is coming from your device to your gateway. If no packet at all is coming, it may be another network problem (routing, firewall)

@ralu

The kernel can reconstruct fragmented TCP packets, not so UDP ones.

Is that the full log? Are you using an IP address as the target or a DNS domain? Is 8.8.8.8 able to resolve that name? The locally generated timeout indicates no response was received to that INVITE. Do you have control over the server? If so, do a packet dump and check if the INVITE is received and where the reply is sent.

kernel can do UDP fragmentation. Fragmentation is at the IP layer.

That is everything that’s logged upon trying to make an invite, yes. I am using a DNS domain. I have control over the Jitsi server, but not the server I am inviting. I can ask, though.

The locally generated timeout indicates no response was received to that INVITE.

Does it clearly mean that the INVITE was sent, but maybe didn’t reach also? I would like to eliminate possible issues with my setup.

You can try ngrep on the JIbri machine to see if the INVITE is sent out. You should actually see it re-transmitted if you don’t get a “100 Trying” reply back.

I don’t think an INVITE is being sent out. I ngrep’ed everything but the port 22 (because I’m using ssh), only the following bit caught my eye. Is there anything I should be on the look out for?

U ip.of.jitsi.server:50361 -> 8.8.8.8:53 #77
  ............._sip._tcp.sip.domain..!..
#
U 8.8.8.8:53 -> ip.of.jitsi.server:50361 #79
  ............._sip._tcp.sip.domain..!.....!.........2.....ygg2.vp.vc....!...............ygg1.vp.vc.
#
U ip.of.jitsi.server:50361 -> 8.8.8.8:53 #80
  .............ygg1.vp.vc.....
#
U ip.of.jitsi.server:50361 -> 8.8.8.8:53 #81
  .............ygg2.vp.vc.....
#
U 8.8.8.8:53 -> ip.of.jitsi.server:50361 #82
  .............ygg2.vp.vc..................yXB
#
U 8.8.8.8:53 -> ip.of.jitsi.server:50361 #83
  .............ygg1.vp.vc.................[..B

Looks like PJSUA is doing the full RFC3263 lookup: NAPTR, then SRV, then A. Can you share the results of this:

dig naptr sip.domain

dig srv _sip._tcp.sip.domain

Thanks for your help. I really appreciate it. Here are the results;

dig naptr sip.domain;

; <<>> DiG 9.16.22-Debian <<>> naptr sip.domain
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59122
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;sip.domain.                  IN      NAPTR

;; AUTHORITY SECTION:
sip.domain.           14      IN      SOA     ns1.dns-cloud.ch. hostmaster.dns-cloud.ch. 2019090508 28800 7200 604800 86400

;; Query time: 0 msec
;; SERVER: 95.128.34.42#53(95.128.34.42)
;; WHEN: Fri Feb 25 14:03:09 CET 2022
;; MSG SIZE  rcvd: 93

dig srv _sip._tcp.sip.domain;

; <<>> DiG 9.16.22-Debian <<>> srv _sip._tcp.sip.domain
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21530
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;_sip._tcp.sip.domain.                IN      SRV

;; ANSWER SECTION:
_sip._tcp.sip.domain. 3600    IN      SRV     10 10 5060 ygg1.vp.vc.
_sip._tcp.sip.domain. 3600    IN      SRV     50 10 5060 ygg2.vp.vc.

;; Query time: 76 msec
;; SERVER: 95.128.34.42#53(95.128.34.42)
;; WHEN: Fri Feb 25 14:04:31 CET 2022
;; MSG SIZE  rcvd: 100

Ok. Now:

dig ygg1.vp.vc
dig ygg2.vp.vc

Are the returned IP addresses routable from your machine?

Yes. Both of them are routable.

The try running this: ngrep -d any -W byline port 5060 that should reveal the outgoing SIP traffic. Do you see any?

Thanks again. I’ve run that before, and I ran it again. Previously, it returned only ######. Now, I’ve tried again, it returned;

#####
U some.ip.address:24531 -> my.ip.address:5060 #5
OPTIONS sip:censysinspect@censys.io SIP/2.0.
To: <sip:test.echo@sip5060.net>.
From: Censys <sip:censysinspect@censys.io>.
CSeq: 1 OPTIONS.
Call-ID: a84b4c76e66710.
Max-Forwards: 70.
Via: SIP/2.0/UDP 127.0.0.1.
Accept: application/sdp.
Content-Length: 0.
.

#
U my.ip.address:5060 -> some.ip.address:5060 #6
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 127.0.0.1;received=some.ip.address.
Call-ID: a84b4c76e66710.
From: "Censys" <sip:censysinspect@censys.io>.
To: <sip:test.echo@sip5060.net>.
CSeq: 1 OPTIONS.
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS.
Accept: application/sdp, application/pidf+xml, application/xpidf+xml, application/simple-message-summary, message/sipfrag;version=2.0, application/im-iscomposing+xml, text/plain.
Supported: replaces, 100rel, timer, norefersub.
Allow-Events: presence, message-summary, refer.
User-Agent: PJSUA v2.10-jitsi3 Linux-5.10.0.11/x86_64/glibc-2.31.
Content-Length:  0.
.

#
U other.ip.address:40011 -> my.ip.address:5060 #7
OPTIONS sip:censysinspect@censys.io SIP/2.0.
To: <sip:test.echo@sip5060.net>.
From: Censys <sip:censysinspect@censys.io>.
CSeq: 1 OPTIONS.
Call-ID: a84b4c76e66710.
Max-Forwards: 70.
Via: SIP/2.0/UDP 127.0.0.1;rport.
Accept: application/sdp.
Content-Length: 0.
.

#
U my.ip.address:5060 -> other.ip.address:40011 #8
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 127.0.0.1;rport=40011;received=other.ip.address.
Call-ID: a84b4c76e66710.
From: "Censys" <sip:censysinspect@censys.io>.
To: <sip:test.echo@sip5060.net>.
CSeq: 1 OPTIONS.
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS.
Accept: application/sdp, application/pidf+xml, application/xpidf+xml, application/simple-message-summary, message/sipfrag;version=2.0, application/im-iscomposing+xml, text/plain.
Supported: replaces, 100rel, timer, norefersub.
Allow-Events: presence, message-summary, refer.
User-Agent: PJSUA v2.10-jitsi3 Linux-5.10.0.11/x86_64/glibc-2.31.
Content-Length:  0.
.

##

This seems to be rare occasion, however. I’ve tried 8 times after this one. I’ve got ###### out of 6 of them.