Calls dropping around 29:30 mark

[SpaceCowboy]

Hi, we have a 3CX hosted in AWS.

Calls keep dropping for mobile numbers around the 29:30 mark. I've seen many posts with this same issue before.

Firewall checker comes back fine, SIP provider has confirmed there is no call refresh at the 30-minute mark of the call.

Looking at this log, who is terminating the call? 3CX or is this from the SIP provider side?

Any ideas?


--

20-07-2023 20:32:28:501 | 9 | L:1182.1[Line:10000<<04****4681] Sending: OnSendResp Send 200/BYE from 0.0.0.0:0 tid=49a1.6211f964.0 Call-ID=4325e487-1d1e-4442-8257-978f36260c38:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 58.96.1.2:5060;branch=z9hG4bK49a1.6211f964.0;cid=2
Via: SIP/2.0/UDP 58.96.11.60:5060;received=58.96.11.60;rport=5060;branch=z9hG4bKPj62148820-69d6-45ec-89af-3646ac77020f
Record-Route: <sip:58.96.1.2;lr;ftag=7063e460-6b13-4114-861e-1573eaa94bb3>
Contact: <sip:[email protected]:5160>
To: <sip:[email protected]>;tag=e20e4320
From: <sip:[email protected]>;tag=7063e460-6b13-4114-861e-1573eaa94bb3
Call-ID: 4325e487-1d1e-4442-8257-978f36260c38
CSeq: 4877 BYE
Content-Length: 0

20-07-2023 20:32:28:501 | 9 | L:1182.1[Line:10000<<04****4681] got Terminated Recv Req BYE from 58.96.1.2:5060 tid=49a1.6211f964.0 Call-ID=4325e487-1d1e-4442-8257-978f36260c38:
BYE sip:[email protected]:5160 SIP/2.0
Via: SIP/2.0/UDP 58.96.1.2:5060;branch=z9hG4bK49a1.6211f964.0;cid=2
Via: SIP/2.0/UDP 58.96.11.60:5060;received=58.96.11.60;rport=5060;branch=z9hG4bKPj62148820-69d6-45ec-89af-3646ac77020f
Max-Forwards: 68
Record-Route: <sip:58.96.1.2;lr;ftag=7063e460-6b13-4114-861e-1573eaa94bb3>
To: <sip:[email protected]>;tag=e20e4320
From: <sip:[email protected]>;tag=7063e460-6b13-4114-861e-1573eaa94bb3
Call-ID: 4325e487-1d1e-4442-8257-978f36260c38
CSeq: 4877 BYE
User-Agent: SUPERLOOP-VOIP
Reason: Q.850;cause=16
Content-Length: 0


20-07-2023 20:32:28:501 | 9 | Leg L:1182.1[Line:10000<<04****4681] is terminated: Cause: BYE from 58.96.1.2:5060

20-07-2023 20:32:28:501 | 9 | Removing leg L:1182.1[Line:10000<<04****4681]

20-07-2023 20:32:28:501 | 9 | Stop call record for leg L:1182.1[Line:10000<<04****4681]

20-07-2023 20:32:28:502 | 9 | SendMsg from "0290638203:MobileInbound:Main Call Queue"<sip:04****[email protected]:5160;nf=q>;tag=672aa113 to <sip:[email protected]:5160>;tag=0bbef538

20-07-2023 20:32:28:502 | 9 | L:1182.3[Extn:461] Sending: OnSendReq Send Req BYE from 0.0.0.0:0 tid=f801ed482b6dca6e Call-ID=sCH18e8_7jNwuDkOmFjlqw..:
BYE sip:[email protected]:5063;rinstance=d7288a0cf4c9899d SIP/2.0
Via: SIP/2.0/ ;branch=z9hG4bK-524287-1---f801ed482b6dca6e;rport
Max-Forwards: 70
Contact: <sip:04****[email protected]:5160>
To: <sip:[email protected]:5160>;tag=0bbef538
From: "0290638203:MobileInbound:Main Call Queue"<sip:04****[email protected]:5160;nf=q>;tag=672aa113
Call-ID: sCH18e8_7jNwuDkOmFjlqw..
CSeq: 2 BYE
Content-Length: 0
--

20-07-2023 20:32:28:502 | 9 | Terminated from <sip:[email protected]:5160>;tag=0bbef538 to "0290638203:MobileInbound:Main Call Queue"<sip:04****[email protected]:5160;nf=q>;tag=672aa113; reason: LocalBye

20-07-2023 20:32:28:502 | 9 | L:1182.3[Extn:461] got Terminated Send Req BYE from 0.0.0.0:0 tid=6c1bdf37f2d06978 Call-ID=sCH18e8_7jNwuDkOmFjlqw..:
BYE sip:[email protected]:5063;rinstance=d7288a0cf4c9899d SIP/2.0
Via: SIP/2.0/ ;branch=z9hG4bK-524287-1---6c1bdf37f2d06978;rport
Max-Forwards: 70
Contact: <sip:04****[email protected]:5160>
To: <sip:[email protected]:5160>;tag=0bbef538
From: "0290638203:MobileInbound:Main Call Queue"<sip:04****[email protected]:5160;nf=q>;tag=672aa113
Call-ID: sCH18e8_7jNwuDkOmFjlqw..
CSeq: 2 BYE
Content-Length: 0

20-07-2023 20:32:28:507 | 9 | L:1182.1[Line:10000<<04****4681]: destroying InvADS.ADS(670396)

 

[NikolasA_3CX]

Hi @SpaceCowboy

From the logs provided the call is being terminated by the provider which in this case seems to be Exetel.