Asterisk 15 and Sangoma Vega duplicated calls

Hi

I seam to have a problem with a Sangoma Vega PRI gateway and calls routing to my Asterisk 15 server. Looking at the logs it seams like the Sangoma is sending 2 calls for the same incoming caller:

14:07:23.477508 IP 192.168.9.2.5060 > XXX.XXX.XXX.XXX.5060: SIP: INVITE sip:0860726222@XXX.XXX.XXX.XXX:5060 SIP/2.0
E…>…@.=…B… …
…*…INVITE sip:0860726222@XXX.XXX.XXX.XXX:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.9.2:5060;rport;branch=z9hG4bK-vega1-BE43C3DB74DA-000A-0001-0160-25BF319E
From: sip:Mia-Samsung@XXX.XXX.XXX.XXX;tag=00FB-0252-D154F008
To: sip:0860726222@XXX.XXX.XXX.XXX
Max-Forwards: 70
Call-ID: 00FC-003F-7641CE42-00000063@74E25E2883AF7D937
CSeq: 46890057 INVITE
Contact: sip:00215961840@192.168.9.2:5060
Supported: replaces, privacy, norefersub, pw-info-package
Allow: INVITE,ACK,BYE,CANCEL,INFO,NOTIFY,OPTIONS,REFER,SUBSCRIBE,UPDATE
Accept-Language: en
Content-Type: application/sdp
Privacy: none
P-Preferred-Identity: sip:00215961840@XXX.XXX.XXX.XXX
User-Agent: VEGA/15.02.12.0xS009
Content-Length: 353

v=0
o=Vega 64657 64657 IN IP4 192.168.9.2
s=Sip Call
c=IN IP4 192.168.9.2
t=0 0
m=audio 10286 RTP/AVP 18 0 8 4 13 98 101
a=rtpmap:18 G729/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:4 G723/8000
a=rtpmap:13 CN/8000
a=rtpmap:98 CLEARMODE/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15,16
a=fmtp:18 annexb=no
a=sendrecv

14:07:30.123768 IP XXX.XXX.XXX.XXX.5060 > 192.168.9.2.5060: SIP: BYE sip:00215961840@192.168.9.2:5060 SIP/2.0
E…l…@.^C…
… …uZ;BYE sip:00215961840@192.168.9.2:5060 SIP/2.0
Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;branch=z9hG4bK09e2b36c;rport
Max-Forwards: 70
From: sip:0860726222@XXX.XXX.XXX.XXX;tag=as7e094521
To: sip:Mia-Samsung@XXX.XXX.XXX.XXX;tag=00FB-0252-D154F008
Call-ID: 00FC-003F-7641CE42-00000063@74E25E2883AF7D937
CSeq: 102 BYE
User-Agent: Asterisk PBX 15.4.1
Proxy-Authorization: Digest username=“Mia-Samsung”, realm=“asterisk”, algorithm=MD5, uri=“sip:XXX.XXX.XXX.XXX”, nonce=“750eef69”, response=“b5aa9a248a7eae9e9c8d72f2fd6bd5f6”
X-Asterisk-HangupCause: No user responding
X-Asterisk-HangupCauseCode: 18
Content-Length: 0

14:07:30.228983 IP 192.168.9.2.5060 > XXX.XXX.XXX.XXX.5060: SIP: SIP/2.0 481 Call Leg/Transaction Does Not Exist
E…@.=… …
…+XSIP/2.0 481 Call Leg/Transaction Does Not Exist
Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;branch=z9hG4bK09e2b36c;rport=5060
From: sip:0860726222@XXX.XXX.XXX.XXX;tag=as7e094521
To: sip:Mia-Samsung@XXX.XXX.XXX.XXX;tag=00FB-0252-D154F008
Call-ID: 00FC-003F-7641CE42-00000063@74E25E2883AF7D937
CSeq: 102 BYE
Contact: sip:00215961840@192.168.9.2:5060
User-Agent: VEGA/15.02.12.0xS009
Content-Length: 0


14:07:27.196139 IP 192.168.9.2.5060 > XXX.XXX.XXX.XXX.5060: SIP: INVITE sip:0860726222@XXX.XXX.XXX.XXX:5060 SIP/2.0
E…>…@.=…B… …
…*Q.INVITE sip:0860726222@XXX.XXX.XXX.XXX:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.9.2:5060;rport;branch=z9hG4bK-vega1-BE43C3DB74DA-000A-0001-0166-A432A7EB
From: sip:Mia-Samsung@XXX.XXX.XXX.XXX;tag=0103-01DC-DAD56A03
To: sip:0860726222@XXX.XXX.XXX.XXX
Max-Forwards: 70
Call-ID: 00FC-0040-39FB41A6-00000063@74E25E2883AF7D937
CSeq: 46890796 INVITE
Contact: sip:00215961840@192.168.9.2:5060
Supported: replaces, privacy, norefersub, pw-info-package
Allow: INVITE,ACK,BYE,CANCEL,INFO,NOTIFY,OPTIONS,REFER,SUBSCRIBE,UPDATE
Accept-Language: en
Content-Type: application/sdp
Privacy: none
P-Preferred-Identity: sip:00215961840@XXX.XXX.XXX.XXX
User-Agent: VEGA/15.02.12.0xS009
Content-Length: 353

v=0
o=Vega 64668 64668 IN IP4 192.168.9.2
s=Sip Call
c=IN IP4 192.168.9.2
t=0 0
m=audio 10288 RTP/AVP 18 0 8 4 13 98 101
a=rtpmap:18 G729/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:4 G723/8000
a=rtpmap:13 CN/8000
a=rtpmap:98 CLEARMODE/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15,16
a=fmtp:18 annexb=no
a=sendrecv

14:07:59.222580 IP XXX.XXX.XXX.XXX.5060 > 192.168.9.2.5060: SIP: BYE sip:00215961840@192.168.9.2:5060 SIP/2.0
E…D`…@…R…
… …rZ8BYE sip:00215961840@192.168.9.2:5060 SIP/2.0
Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;branch=z9hG4bK5aa18188;rport
Max-Forwards: 70
From: sip:0860726222@XXX.XXX.XXX.XXX;tag=as1c569215
To: sip:Mia-Samsung@XXX.XXX.XXX.XXX;tag=0103-01DC-DAD56A03
Call-ID: 00FC-0040-39FB41A6-00000063@74E25E2883AF7D937
CSeq: 102 BYE
User-Agent: Asterisk PBX 15.4.1
Proxy-Authorization: Digest username=“Mia-Samsung”, realm=“asterisk”, algorithm=MD5, uri=“sip:XXX.XXX.XXX.XXX”, nonce=“66670927”, response=“193cc0353430137f29791aafde353056”
X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16
Content-Length: 0

14:07:59.291532 IP 192.168.9.2.5060 > XXX.XXX.XXX.XXX.5060: SIP: SIP/2.0 200 OK
E…@.=… …
…~…SIP/2.0 200 OK
Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;branch=z9hG4bK5aa18188;rport=5060
From: sip:0860726222@XXX.XXX.XXX.XXX;tag=as1c569215
To: sip:Mia-Samsung@XXX.XXX.XXX.XXX;tag=0103-01DC-DAD56A03
Call-ID: 00FC-0040-39FB41A6-00000063@74E25E2883AF7D937
CSeq: 102 BYE
Contact: sip:00215961840@192.168.9.2:5060
User-Agent: VEGA/15.02.12.0xS009
Content-Length: 0

Below is what the Sangoma log look like:

LOG: 29/03/2021 14:07:22.600 ISDN (I)R01C11 incoming
call ref=[f103065e] srce=TEL:00215961840 [0]

LOG: 29/03/2021 14:07:22.600 ROUTER (I)R0bC00 FINDROUTE profile:20(To_SIP) plan:1
call ref=[f103065e] ← ISDN [1,1] dest=TEL:0860726222
→ SIP [2,1] dest=TEL:0860726222

LOG: 29/03/2021 14:07:22.865 SIP (I)R04C18 disconnect(disc ind) 21
call ref=[f103065e]

LOG: 29/03/2021 14:07:22.865 ISDN (I)R04C11 send disconnect 21
call ref=[f103065e]

LOG: 29/03/2021 14:07:26.295 ISDN (I)R01C11 incoming
call ref=[f10505dc] srce=TEL:00215961840 [0]

LOG: 29/03/2021 14:07:26.295 ROUTER (I)R0bC00 FINDROUTE profile:20(To_SIP) plan:1
call ref=[f10505dc] ← ISDN [1,1] dest=TEL:0860726222
→ SIP [2,1] dest=TEL:0860726222

LOG: 29/03/2021 14:07:28.740 SIP (I)R03C19 connect g711Alaw64k (Profile 1 - Voice)
call ref=[f10505dc]

LOG: 29/03/2021 14:07:28.740 ROUTER (I)R0bC00 call proceeding
call ref=[f10505dc]

Vega is a Sangoma commercial product. Please contact technical support for assistance with it.