T42G & T46G Echo and Hollow sound

[tlsallada]

I have a 3CX install using T42G and T46G phones and all have experienced echo and a 'hollow' sound during calls to the outside. It doesn't happen on intercom calls.
I see there are settings for echo and jitter but I can't find any documentation on Yealinks website or in the manuals for making any adjustments. Both phone types are running the current firmwares.
Help!!

[Yealink Support]

Hi tlsallada,

Can you provide more details for me?
1. Do you mean all your T42G and T46G have this echo issue?
2. Do your other phones don't have this issue?
3. Does the issue just happen in the outbounding call? Not happen in incoming call or intercom call?
4. Do you hear the echo and hollow sound in T4X or the other phones?
4. If all phones have this issue, it may relate to your switch.
Can you supply pcap for me along with syslog level 6 and config.bin ?
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.

[tlsallada]

(12-12-2013 05:49 PM)Yealink Support Wrote:  Hi tlsallada,

Can you provide more details for me?
1. Do you mean all your T42G and T46G have this echo issue?
2. Do your other phones don't have this issue?
3. Does the issue just happen in the outbounding call? Not happen in incoming call or intercom call?
4. Do you hear the echo and hollow sound in T4X or the other phones?
4. If all phones have this issue, it may relate to your switch.
Can you supply pcap for me along with syslog level 6 and config.bin ?
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.

---

1. Yes - All phones regardless of type (T42G & T46G) have the issue.
2. There are no other phones in the system. Just the two types of Yealink phones.
3. It happens on both inbound & outbound calls. Not on intercom calls.
4. Yes
Problem is it doesn't happen on all calls. It will be difficult to capture the file on a call when it occurs.

[Yealink Support]

Hi tlsallada,

How often does the issue happen? You can set syslog level as 6 and start pcap, wait the issue appearing, after the issue happened, then stop the pcap and export syslog, config.bin and pcap for me.
I will keep my eyes on your issue at the same time.

[tlsallada]

Here is the log when I try to call the number in Mexico..


Terry Sallada


To
terry@advancedcommsec.com











13-Dec-2013 11:13:46.350 L:1840.1[Extn:3265]: Terminating targets, reason:
13-Dec-2013 11:13:46.350 Leg L:1840.1[Extn:3265] is terminated: Cause: BYE from PBX
13-Dec-2013 11:13:46.350 L:1840.1[Extn:3265] Sending: OnSendResp Send 403/INVITE from 0.0.0.0:0 tid=1886629003 Call-ID=1460806@10.1.5.54:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 10.1.5.54:5062;branch=z9hG4bK1886629003
To: <sip:9011528999580285@10.1.5.28>;tag=ed694252
From: "Server Room"<sip:3265@10.1.5.28>;tag=921767165
Call-ID: 1460806@10.1.5.54
CSeq: 2 INVITE
Warning: 499 PATTON-SNBX "Forbidden"
Content-Length: 0
13-Dec-2013 11:13:46.336 [CM503020]: Call(C:1840): Normal call termination. Call originator: Extn:3265. Reason: Forbidden
13-Dec-2013 11:13:46.336 [CM503016]: Call(C:1840): Attempt to reach <sip:9011528999580285@10.1.5.28:5060> from Extn:3265 has failed. Reason: Busy
13-Dec-2013 11:13:46.335 [Flow] Call(C:1840): has built target endpoint: EndCall:EndCall for call from L:1840.1[Extn:3265]
13-Dec-2013 11:13:46.334 [CM503010]: Call(C:1840): Making route(s) from Extn:3265 to <sip:9011528999580285@10.1.5.28:5060>
13-Dec-2013 11:13:46.334 Remote SDP is set for leg L:1840.1[Extn:3265]
13-Dec-2013 11:13:46.334 [CM505001]: Endpoint Extn:3265: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Yealink SIP-T42G 29.71.0.91] PBX contact: [sip:3265@10.1.5.28:5060]
13-Dec-2013 11:13:46.331 [CM500002]: Call(C:1840): Info on incoming INVITE from Extn:3265:
Invite-IN Recv Req INVITE from 10.1.5.54:5062 tid=1886629003 Call-ID=1460806@10.1.5.54:
INVITE sip:9011528999580285@10.1.5.28:5060 SIP/2.0
Via: SIP/2.0/UDP 10.1.5.54:5062;branch=z9hG4bK1886629003
Max-Forwards: 70
Contact: <sip:3265@10.1.5.54:5062>
To: <sip:9011528999580285@10.1.5.28>
From: "Server Room"<sip:3265@10.1.5.28>;tag=921767165
Call-ID: 1460806@10.1.5.54
CSeq: 2 INVITE
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Conten

[Yealink Support]

Hi Terry,

1. Which PBX do you use now?
2. Can you please send me more information?
Please refer to post 2 about how to get those files.

[smb]

(12-23-2013 02:50 PM)Yealink Support Wrote:  Hi Terry,

1. Which PBX do you use now?
2. Can you please send me more information?
Please refer to post 2 about how to get those files.

hi
i have same problem with T42G.
i have echo canceler kit but there is echo on these phones ,i have T22P but i dont have any problem with these phones.
PBX:Elastix
Card:Openvox with echo canceler
phone firmware:29.73.0.50