W52P Non audio on some external calls - Printable Version +- Yealink Forums (http://forum.yealink.com/forum) +-- Forum: Dect Phone Series (/forumdisplay.php?fid=6) +--- Forum: W52P (Wireless) (/forumdisplay.php?fid=23) +--- Thread: W52P Non audio on some external calls (/showthread.php?tid=40848) |
W52P Non audio on some external calls - dstamour - 05-12-2017 02:59 PM We have a W52P with firmware v25.80.0.15. The problem we have is that some external calls have no audio both ways. The only way to get the audio is to put de call on hold and pull it back. I've done a TCPdump to get more details and here's what I've found: (All this is from the phone perspective) Sends SIP INVITE Gets SIP 100 Trying Gets SIP 183 Session Progress (From there RTP in both ways) Gets SIP 180 Ringing (Here the phone send RTCP Goodbye and stop sending RTP and send ICMP Port unreachable when receving RTP from PBX) So my question is, why does the W52P closes his RTP port when receiving the 180 Ringing at this point? The only way to fix this is to put the call on hold and pull it back so this will send an INVITE to the PBX and the RTP from the PBX will be accepted by the W52P. Thanks RE: W52P Non audio on some external calls - complex1 - 05-12-2017 03:52 PM Quote:The problem we have is that some external calls have no audio both ways. Audio issues are most of the time caused by the router. Please make sure SIP ALG is disabled and the RTP ports are forwarded to the W52P base. RE: W52P Non audio on some external calls - dstamour - 05-15-2017 12:54 PM The call does not go through a NAT router. The phone is on the same network as the PBX and the situation occurs between the W52P and the PBX. I'am 100% sure it's not a "one way audio" or "no audio" situation cause by a router. The phone sends a "RTCP Goodbye" packet just after receiving the "180 Ringing" and start responding "ICMP Destination unreachable" when receiving RTP packets from the PBX. RE: W52P Non audio on some external calls - Kevin_Yealink - 05-16-2017 08:43 AM (05-15-2017 12:54 PM)dstamour Wrote: The call does not go through a NAT router. The phone is on the same network as the PBX and the situation occurs between the W52P and the PBX. I'am 100% sure it's not a "one way audio" or "no audio" situation cause by a router. The phone sends a "RTCP Goodbye" packet just after receiving the "180 Ringing" and start responding "ICMP Destination unreachable" when receiving RTP packets from the PBX. Hi To solve the issue, please export all pacp,syslog,config.bin files to me, then we can do more troubleshooting. You can refer to this FAQ to get those files. http://support.yealink.com/faq/faqInfo?id=311 I need to check with you on this issue: 1. when you use W52P to make internal call, will this issue happened? 2. If you register the account on other phone, will this issue happened? If not, please export pacp,syslog,config.bin files to me. 3. Does the issue happened every time when you make external call? 4. How many phones in your side? How many phones have such issue? BR Kevin |