Dropped Incoming & Outgoing Calls

[DrainBamaged]

We have 3CX hooked up to a Patton 4960 and eight ISDN lines. Every now and then, we get a call drop after 3-6 minutes. It is happening randomly and rare enough that a wireshark would be difficult to capture.

This is affecting both inbound and outbound calls. The only clue I can see in the logs is this:

07/18/2019 6:36:36 AM - Leg L:1783.1[Extn:302] is terminated: Cause: BYE from 10.10.10.81:5062

It looks like the handset is hanging up (Yealink T22P). Any ideas how to proceed?

 

[FS_Mathieu]

Hello @DrainBamaged !

What is your PBX version ? Firmware of the deskphones ? On prem install ?

T22P are on end of life, don't you have a more recent phone to check if something happen ? That can already tell if it's a phone or maybe a patton problematic !

Mathieu

 

[DrainBamaged]

Enterprise v16.0.1.273 on prem
T22P Firmware (Not red in admin window) v7.73.0.60

Started opening a case with Patton until I saw the handset was sending the BYE message.

 

[FS_Mathieu]

Is it totally random ? Or maybe you saw on which patton line it happen and what kind of call (long, short)

Because you say after 3-6 minutes so if it's that frequent, you can maybe do a trace/wireshark

 

[FS_Mathieu]

And you don't have any other phone model to have a test ?

 

[DrainBamaged]

As I said, it's random and occurs so infrequently that wiresharking all sixteen lines would probably fill the drive before a call arrived. The phones in use are T-22P across the board.

 

[eddv123]

I think this would most likely be some sort of issue between SIP >> ISDN. The issues with running Wireshark is that you can only really see the SIP side of the call - do you have a capture from the PBX however ?

This could be related to Early media settings in the Patton (3CX does not support this):
https://www.3cx.com/community/threads/early-media.34472/#post-179641

This setting (if I recall from memory) should be found in the VoIP profile.

If you still experiencing issues then I would login the the command line of the device and run the following commands:

enable
show running‐config
debug call‐router
debug call‐control
debug ccisdn signaling
debug context sip‐gateway signaling detail 5
debug context sip‐gateway transport detail 5
debug context sip‐gateway error

Then "no debug all" after to cease the log flow (obviously replicating the fault during this process).

Feel free to send the log over to me via PM and I will take a look - you can also send it over to Patton support of analysis since you have a ticket with them, they are normally very helpful.

From this log you should at the very least be able to tell whether it is an issue with the configuration or the line itself.

 

[DrainBamaged]

Solid advice. Got onto the PATTON today (after finally locating the password) and see it has been up for almost 900 days. The version on the firmware was over two versions out of date. Updated that to latest version and rebooted it. Hopefully, we'll see an improvement.

 

[eddv123]

There is a chance that this would do the trick. I was hoping you would send over the running-config so I could identify the firmware version however glad you beat me to it.

Firmware would be a good bet like this string here: https://www.3cx.com/community/threa...to-hear-our-outbound-audio.66401/#post-285071

But if you continue to get issues then please feel free to follow the above and get an output of the issue.

 

[DrainBamaged]

I have a ticket open with PATTON. Will report findings. Thanks.

 

[eddv123]

Yeah that would be good, I do always appreciate users updating the strings with the fixes for the sake of the other users - despite the demise of the PSTN they are still popular models with 3CX.

Patton support may ask for the output I sent previously anyway so keep it in mind.