[YMCS/YDMP Free Trial Program]Yealink would like to offer Free Trial Program of Yealink device management service for our current eligible customers. You can see the details below.
https://www.yealink.com/ydmp-freetrial-2020


Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Strange audio
Author Message
PDJ Offline
Junior Member
**

Posts: 4
Joined: Jan 2019
Reputation: 0
Post: #1
Strange audio
We are moving from Auerswald to Yealink phones, now we have 2 Yealink phones 1 W60B and a T46G.
Both have a strange issue.
The phones are working fine, but when I call a phone number I can talk but I don't hear the other side.
when I get called, audio works both sides.

It's not a NATted network.

Thanks in advance.

The syslog on the phone shows this part extra when I place the call (not when I receive)

<134>May 1 13:16:30 sua [1116]: SUA <6+info > [000] ****eCore event:(0x0022)ECORE_CALL_MESSAGE_ANSWERED ****
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.598.030:MMI <5>HookOn ActLS:0
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.599.357:
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.599.918:MMI <5>tapp_dee_HookOn LCB:0x0,RelReason:0x0
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.600.479:
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.601.038:MMI <5>HookOn Line:0 Hs:1
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.601.597:
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.602.178:MMI <5>tapp_dee_HookOn u8_RelReason:0,u8_CallType:0,u32_CallInstance:0x2
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.603.081:
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.603.641:MMI <5>u8_SessionStatus:0x0
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.604.200:
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.604.765:MMI <5>tapp_util_MediaChannelStop Channel:0 Codec:6 SlotScheme:3
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.605.327:
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.605.956:CSM <5>p_cs16_HookOn LSID:0
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.606.515:CAT <5>ResetLineSession LSID:0
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.607.078:
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.607.637:MMI <5>Line:0, PS[1]=0
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.608.985:
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.609.134:FTMI_ID/0,0,229,0x1,0x0,1,<0>
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.609.460:
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.609.601:AUD <5>ChannelStop: No line found for MediaChannel ID:0
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.609.720:
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.609.835:FTMLP_ID/0,3,8,0x0,0x0,0,<0>
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.609.947:
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.610.058:TX[0] HS 1 --> T[23586] {CC-RELEASE-COM} [HS-1] P_IT(30)
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.610.170: <<RELEASE-REASON>> (0xe2)
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.610.281: Partial release
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.610.389:
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.611.822:
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.611.980:FTMLP_ID/0,3,8,0x0,0x0,0,<0>
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.612.112:
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.612.728:FTMLP_ID/0,3,7,0x2,0x0,2,<0>
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.929.657:Mips:119,min:80,max:119
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.929.838:Slot Used:long=2,full=2
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.929.964:c0,te:3,rf:4
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.930.080:cmbs_stat_ok

What I found in the logfile is this line:
<133>May 1 13:16:30 DEBS[916]: DCX <5+notice> 590.609.601:AUD <5>ChannelStop: No line found for MediaChannel ID:0

Is this the actual error? (I don't know where to look for)
(This post was last modified: 05-01-2019 01:32 PM by PDJ.)
05-01-2019 12:42 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
PDJ Offline
Junior Member
**

Posts: 4
Joined: Jan 2019
Reputation: 0
Post: #2
RE: Strange audio
I think I found the problem.
I saw in the pcap file that the yealink is using a pcmu codec while it is receiving pcma.
I removed all codecs and kept pcma as only enabled codec and now audio is working both ways.
05-01-2019 01:46 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Post Reply 


Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  W60 connectivity and audio issues shadokkhan 4 5,204 05-06-2022 10:49 PM
Last Post: complex1
  Audio delay when call answered tjwesto 4 11,129 09-15-2020 01:56 PM
Last Post: complex1
  W60B + W56H strange calls from 100, 200 Jaceli 1 6,678 04-20-2018 11:47 PM
Last Post: complex1

Forum Jump:


User(s) browsing this thread: 1 Guest(s)

Contact Us   Yealink   Return to Top   Return to Content   Lite (Archive) Mode   RSS Syndication