CAUTION ALERT:
Test show changing from RFC2833 to INBAND will break the ability to check voice mail and pass tones between user and local automated attendant etc. So it fixes one issue and creates another.
As per ss 10/21/2019
We only support RFC2833
SR
Yealink CP8xx Conf Phone NOT transmitting DTMF Touch Tones to 3rd Party Conference Service
The Yealink phones are programmed to use the DTMF TYPE setting of RFC2833, which sometimes will NOT pass the DTMF Touch Tones to 3rd party conference services such as Free Conference, etc. this is usually Always the problem of the conference call company.
There is a work around but it has drawbacks !!
Below are the parameter settings, which can be found on the phones Web GUI
ACCOUNT > Advanced , DTMF Type
Valid Value: (0-INBAND;1-RFC 2833;2-SIP INFO;3-RFC2833 + SIP INFO)
0-INBAND, DTMF digits are transmitted in the voice band.
1-RFC2833, DTMF digits are transmitted by RTP Events compliant to RFC 2833.
2-SIP INFO, DTMF digits are transmitted by the SIP INFO messages.
3-RFC2833 + SIP INFO, DTMF digits are transmitted by RTP Events compliant to RFC 2833 and the SIP INFO messages.
DEFAULT IS = 1
By default it's set as
account.1.dtmf.type="1"
Change to DTMF = INBAND
account.1.dtmf.type="0"
Note: this will also apply to other Yealink phone models T4x, T5x, etc.
Remember this will fix the DTMF <BUT> it will break the ability for that phone to interact with our PBX voice mail, automated attendant etc.
Proceed with caution!
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article