Busy Signal/Beeping while on a call

[Mark1972]

Randomly we will receive busy signal/beeping noise on a call when some extensions pickup. The caller cannot hear it, just the person who picks up the call. We use 3CX v11, Patton 4114 gateways, 1 T28 and 10 T26 phonesets. The T28 does not have this issue which is why we suspect the T26 phones. All phonesets have the recommended firmware 6.70.0.103 support by 3cx. Any ideas?

--Mark

[briankelly63]

use a tool like Wireshark to look at RTP stream and see whats coming from where. You may be able to use Wireshark to look at the pcap file from the phone itself also.

[ppickens]

(10-04-2013 09:53 PM)briankelly63 Wrote:  use a tool like Wireshark to look at RTP stream and see whats coming from where. You may be able to use Wireshark to look at the pcap file from the phone itself also.

Ah, I've actually seen this issue too and have not found a solution. It's with two different clients (who are both behind grandstream gateways). This is an isolated issue with some extensions, all of which use the T2x series of phones (T26 and T28). They are both running the supported firmware by 3cx, one is a remote PBX and one is on-site. If I run a packet capture, I can get all audio in wireshark except for the "busy signal", and there is nothing out of the ordinary on the SIP and/or RTP packets.

This only happens when the phone is the initial point of contact (in my experience) for an inbound call from an external line. We have tried different ethernet cables, ports, and ports on the switches just to eliminate any kind of layer one issues. Also it is not easily replicated due to the fact that I have called in twice from the same cell phone and gotten the issue one time and the next there was no unwanted audio signal at all.

Well if there are any questions about this that would help me troubleshoot, it would be much appreciated.

Thanks!

[Yealink Support]

Hi all,
Could you upgrade to our latest firmware x.71.0.140 to check again?
If the problem is still, could you provide PCAP trace, syslog(level 6) and config.bin file to us, so we can analyze?
Before you export the syslog, please set log level as 6, and reboot the phone, then click Start,and reproduce the issue, then click Stop,and export the trace, syslog, config,bin to us.
(About where to export these files, please refer to attached screenshot.)
These three files are very important for us, hope you can kindly understand.
Thanks.

[ppickens]

I have updated to the suggested firmware, we are waiting to see if the problem arises again as it is sporadic.

[ppickens]

So far so good for our client, I'll post back up if it does resurface.