Toggle sidebar Toggle sidebar

Call drops after 30 mins.

Status
Not open for further replies.

pedroben

Joined
Aug 2, 2016
Messages
10
Reaction score
0
Recently started having this issue with call drops after 30 mins. I had my carrier send me their logs and i can see clearly that when they send us a re-invite at 15 mins, we respond however the next re-invite, we get no response from the PBX.

The issue does not happen with every call and i cannot reproduce it at will.

There's one change i did make to the system before i started getting these reports and that was modifying MAXCALLDURATION to 32400. Reason for this is the previous value was set to 3 hrs and my COO was on a call that was over 3 hours and got disconnected.

Anyone know if adjusting this value could trigger a weird bug with call drops?

upload_2018-10-19_11-52-9.png

Left side is between the far end party that initiated the call and right side is between carrier and 3cx.

As it happens, its just one carrier on the entire call which makes things easier.

I unfortunately dont have the logs from 3cx as Verbose logging was not enabled. Waiting on a fresh sample but in the mean time, i'm hoping someone might have an idea where the problem is.

The call does terminate with a 102 session timer expiry.

User-Agent: 3CXPhoneSystem 15.5.15502.6
 
Hello @pedroben

You will need to get a capture from the PBX to see what is going on as the provider may be sending the Re-Invite but is the PBX getting it? Or if the Re-Invite does reach the PBX what does the PBX respond? You could run a t-shark command on the PBX to capture traffic until this happens again.
 
Hi, thanks for the response. As the issue is random, its not so easy to run a trace as i dont know when it will happen.

It just happened again and i'm just going over the logs. Will post shortly.
 
I have attached the latest log though i do not see any definitive reason for the drop.

Code: 
10/19/2018 4:36:55 PM - L:16698.2[Extn:9551] got Terminated Recv Req BYE from 10.44.10.73:5060 tid=cb73f086F9935362 Call-ID=X3_PHlI8nPGkBfDwLtI-wA..:
BYE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.44.10.73;branch=z9hG4bKcb73f086F9935362
Max-Forwards: 70
Contact: <sip:[email protected]>
To: <sip:[email protected]:5060;nf=e>;tag=f0197214
From: "Boardroom MeetingRoom" <sip:[email protected]>;tag=DD66AF6-301C132
Call-ID: X3_PHlI8nPGkBfDwLtI-wA..
CSeq: 1 BYE
Accept-Language: en-us, en;q=0.9
User-Agent: PolycomSoundStationIP-SSIP_6000-UA/4.0.7.2514
Content-Length: 0

10/19/2018 4:36:55 PM - L:16698.2[Extn:9551] Sending: OnSendResp Send 200/BYE from 0.0.0.0:0 tid=cb73f086F9935362 Call-ID=X3_PHlI8nPGkBfDwLtI-wA..:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.44.10.73;branch=z9hG4bKcb73f086F9935362
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]:5060;nf=e>;tag=f0197214
From: "Boardroom MeetingRoom" <sip:[email protected]>;tag=DD66AF6-301C132
Call-ID: X3_PHlI8nPGkBfDwLtI-wA..
CSeq: 1 BYE
Content-Length: 0

10/19/2018 4:36:55 PM - Call(C:16698), Extn:9551 on exit: DlgInfo(16698-3551/Terminated / R)
10/19/2018 4:36:55 PM - Call(C:16698), Extn:9551 on entry: DlgInfo(16698-3551/Confirmed / R)
10/19/2018 4:36:55 PM - Notify dialog-info: Extn:9551: sip:[email protected]:5060, Call(C:16698)
10/19/2018 4:19:59 PM - Reneg. from L:16698.2[Extn:9551], answer
10/19/2018 4:19:59 PM - Leg L:16698.2[Extn:9551] raised event RecvdRemoteSdp
10/19/2018 4:19:59 PM - Remote SDP is set for leg L:16698.2[Extn:9551]
10/19/2018 4:19:59 PM - NAT/ALG check:L:16698.2[Extn:9551] RESPONSE 200 on 'INVITE' - basic check passed. No information for extended checks


10/19/2018 4:19:59 PM - Answer SDP arrived on Leg L:16698.2[Extn:9551];
OnAnswer Recv 200/INVITE from 10.44.10.73:5060 tid=af77045b284f066e Call-ID=X3_PHlI8nPGkBfDwLtI-wA..:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.44.10.15:5060;branch=z9hG4bK-524287-1---af77045b284f066e;rport
Contact: <sip:[email protected]>
To: "Boardroom MeetingRoom" <sip:[email protected]>;tag=DD66AF6-301C132
From: <sip:[email protected]:5060;nf=e>;tag=f0197214
Call-ID: X3_PHlI8nPGkBfDwLtI-wA..
CSeq: 3 INVITE
Accept-Language: en-us, en;q=0.9
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER
Content-Type: application/sdp
Supported: 100rel, replaces
User-Agent: PolycomSoundStationIP-SSIP_6000-UA/4.0.7.2514
Allow-Events: conference, talk, hold
Content-Length: 209

v=0
o=- 1539961507 1539961509 IN IP4 10.44.10.73
s=Polycom IP Phone
c=IN IP4 10.44.10.73
t=0 0
a=sendrecv
m=audio 2236 RTP/AVP 8 101
a=sendrecv
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000


10/19/2018 4:19:59 PM - L:16698.2[Extn:9551] Sending: OnSendReq Send Req ACK from 0.0.0.0:0 tid=8e432e07b9541677 Call-ID=X3_PHlI8nPGkBfDwLtI-wA..:
ACK sip:[email protected] SIP/2.0
Via: SIP/2.0/ ;branch=z9hG4bK-524287-1---8e432e07b9541677;rport
Max-Forwards: 70
Contact: <sip:[email protected]:5060>
To: "Boardroom MeetingRoom" <sip:[email protected]>;tag=DD66AF6-301C132
From: <sip:[email protected]:5060;nf=e>;tag=f0197214
Call-ID: X3_PHlI8nPGkBfDwLtI-wA..
CSeq: 3 ACK
Content-Length: 0



10/19/2018 4:19:59 PM - Call(C:16698), Extn:9551 on entry: DlgInfo(16698-3551/Confirmed / R)
10/19/2018 4:19:59 PM - Notify dialog-info: Extn:9551: sip:[email protected]:5060, Call(C:16698)


10/19/2018 4:19:59 PM - L:16698.2[Extn:9551] Sending: OnSendReq Send Req INVITE from 0.0.0.0:0 tid=8e765566d729bc1a Call-ID=X3_PHlI8nPGkBfDwLtI-wA..:
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/ ;branch=z9hG4bK-524287-1---8e765566d729bc1a;rport
Max-Forwards: 70
Contact: <sip:[email protected]:5060>
To: "Boardroom MeetingRoom" <sip:[email protected]>;tag=DD66AF6-301C132
From: <sip:[email protected]:5060;nf=e>;tag=f0197214
Call-ID: X3_PHlI8nPGkBfDwLtI-wA..
CSeq: 3 INVITE
Alert-Info: <http://www.notused.invalidtld>;info=external
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE
Content-Type: application/sdp
Supported: replaces, timer
User-Agent: 3CXPhoneSystem 15.5.15502.6 (15502)
Content-Length: 415

v=0
o=3cxPS 453370707968 492914606083 IN IP4 10.44.10.15
s=3cxPS Audio call
c=IN IP4 10.44.10.15
t=0 0
m=audio 7868 RTP/AVP 8 0 9 3 18 112 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:9 G722/8000
a=rtpmap:3 GSM/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:112 opus/48000/2
a=fmtp:112 maxplaybackrate=16000;sprop-maxcapturerate=16000
a=rtpmap:101 telephone-event/8000
a=sendrecv



10/19/2018 4:19:59 PM - Call(C:16698), Extn:9551 on entry: DlgInfo(16698-3551/Confirmed / R)
10/19/2018 4:19:59 PM - Notify dialog-info: Extn:9551: sip:[email protected]:5060, Call(C:16698)
10/19/2018 4:19:59 PM - Providing SDP for L:16698.2[Extn:9551]
10/19/2018 4:04:59 PM - Reneg. from L:16698.2[Extn:9551], answer
10/19/2018 4:04:59 PM - Leg L:16698.2[Extn:9551] raised event RecvdRemoteSdp
10/19/2018 4:04:59 PM - Remote SDP is set for leg L:16698.2[Extn:9551]
10/19/2018 4:04:59 PM - NAT/ALG check:L:16698.2[Extn:9551] RESPONSE 200 on 'INVITE' - basic check passed. No information for extended checks


10/19/2018 4:04:59 PM - Answer SDP arrived on Leg L:16698.2[Extn:9551];
OnAnswer Recv 200/INVITE from 10.44.10.73:5060 tid=1a731f22e4794445 Call-ID=X3_PHlI8nPGkBfDwLtI-wA..:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.44.10.15:5060;branch=z9hG4bK-524287-1---1a731f22e4794445;rport
Contact: <sip:[email protected]>
To: "Boardroom MeetingRoom" <sip:[email protected]>;tag=DD66AF6-301C132
From: <sip:[email protected]:5060;nf=e>;tag=f0197214
Call-ID: X3_PHlI8nPGkBfDwLtI-wA..
CSeq: 2 INVITE
Accept-Language: en-us, en;q=0.9
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER
Content-Type: application/sdp
Supported: 100rel, replaces
User-Agent: PolycomSoundStationIP-SSIP_6000-UA/4.0.7.2514
Allow-Events: conference, talk, hold
Content-Length: 209

v=0
o=- 1539961507 1539961508 IN IP4 10.44.10.73
s=Polycom IP Phone
c=IN IP4 10.44.10.73
t=0 0
a=sendrecv
m=audio 2236 RTP/AVP 8 101
a=sendrecv
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000


10/19/2018 4:04:59 PM - L:16698.2[Extn:9551] Sending: OnSendReq Send Req ACK from 0.0.0.0:0 tid=d0765e2b18680b4b Call-ID=X3_PHlI8nPGkBfDwLtI-wA..:
ACK sip:[email protected] SIP/2.0
Via: SIP/2.0/ ;branch=z9hG4bK-524287-1---d0765e2b18680b4b;rport
Max-Forwards: 70
Contact: <sip:[email protected]:5060>
To: "Boardroom MeetingRoom" <sip:[email protected]>;tag=DD66AF6-301C132
From: <sip:[email protected]:5060;nf=e>;tag=f0197214
Call-ID: X3_PHlI8nPGkBfDwLtI-wA..
CSeq: 2 ACK
Content-Length: 0

10/19/2018 4:04:59 PM - Call(C:16698), Extn:9551 on entry: DlgInfo(16698-3551/Confirmed / R)
10/19/2018 4:04:59 PM - Notify dialog-info: Extn:9551: sip:[email protected]:5060, Call(C:16698)


10/19/2018 4:04:59 PM - L:16698.2[Extn:9551] Sending: OnSendReq Send Req INVITE from 0.0.0.0:0 tid=da4f3e0bff336b7b Call-ID=X3_PHlI8nPGkBfDwLtI-wA..:
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/ ;branch=z9hG4bK-524287-1---da4f3e0bff336b7b;rport
Max-Forwards: 70
Contact: <sip:[email protected]:5060>
To: "Boardroom MeetingRoom" <sip:[email protected]>;tag=DD66AF6-301C132
From: <sip:[email protected]:5060;nf=e>;tag=f0197214
Call-ID: X3_PHlI8nPGkBfDwLtI-wA..
CSeq: 2 INVITE
Alert-Info: <http://www.notused.invalidtld>;info=external
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE
Content-Type: application/sdp
Supported: replaces, timer
User-Agent: 3CXPhoneSystem 15.5.15502.6 (15502)
Content-Length: 415

v=0
o=3cxPS 453370707968 492914606082 IN IP4 10.44.10.15
s=3cxPS Audio call
c=IN IP4 10.44.10.15
t=0 0
m=audio 7868 RTP/AVP 8 0 9 3 18 112 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:9 G722/8000
a=rtpmap:3 GSM/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:112 opus/48000/2
a=fmtp:112 maxplaybackrate=16000;sprop-maxcapturerate=16000
a=rtpmap:101 telephone-event/8000
a=sendrecv
The log has been stripped a bit but i've attached the complete log as an attachment.
 

Attachments

pedroben said:
Hi, thanks for the response. As the issue is random, its not so easy to run a trace as i dont know when it will happen.
Click to expand...
This is why i suggested running a T-shark which will keep running until the issue occurs but will create several small files which will not overload or crush the system. If you let me know if your PBX is running on windows or linux i can provide the commands for running it.

Unfortunately the logs provided contain the call leg between the 3CX phone system and the Polycom conference phone and not the call leg between the phone system and the provider so we do not have the full picture.
 
YiannisH_3CX said:
This is why i suggested running a T-shark which will keep running until the issue occurs but will create several small files which will not overload or crush the system. If you let me know if your PBX is running on windows or linux i can provide the commands for running it.

Unfortunately the logs provided contain the call leg between the 3CX phone system and the Polycom conference phone and not the call leg between the phone system and the provider so we do not have the full picture.
Click to expand...

Thanks for the response. Its running on a windows environment.
 
  1. Make sure that Wireshark is installed on the server
  2. Run the following command from the DOS prompt instead of running the usual PCAP: cd "C:\Program Files\Wireshark\ tshark -F libpcap -i 1 -f "udp port 5060 or udp port 5090 or tcp port 5090 or udp portrange 7000-8499 or udp portrange 9000-10999" -b filesize:10240 -w c:\3cx.pcap (or any folder you want)
  3. Wait for the issue to occur, and when this happens write down date/time/caller/callee. Stop the capture by pressing Ctrl + C . Doing the above, Wireshark will cut your capture into file chunks of 10MB. You will to locate the files that are relevant to the issue and check them.
 
Many thanks for that. Running it now. Very useful this.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,900
Messages
589,630
Members
164,765
Latest member
domi
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom