Browse Tag

T23G

Yealink – Adjusting the sending volume (outgoing volume) on the T2, T4 and T5 Series Phones

You may be getting reports from your customers saying that when they are on a call, the opposite party is telling them that their audio is too quiet, or maybe even too loud when they talk. Usually this isn’t a problem because the opposite party can adjust the volume of the person calling with their own phone, but what if the opposite party has already done that and it’s still too quiet or too loud?

If that is the case then you may be able to adjust three settings on the Yealink device. These can found on the web user interface by going to the ‘Features’ > ‘Audio’ page and adjusting the settings in the image below outlined in green.

An alternative way to think what these settings do is adjusting how sensitive the microphone is on the device. You can adjust the handset, headset and handsfree sensitivity to be weaker or stronger. The valid values are between -50 and 50. The higher the value, the louder it should be. The lower the value, the quieter it should be.

When adjusting this setting it is important to be cautious. Incorrectly configuring the value can have adverse effects on the audio quality so it’s advisable to gradually increase or decrease the value until you find the right spot.

If you control your own provisioning server and would like to configure this remotely you can use the provisioning parameters below:

voice.headset_send
voice.handset_send
voice.handfree_send

Hopefully after adjusting these settings it resolves the issue and provides a better experience for the end-user and the opposite party on the calls.

For further technical assistance with your Yealink devices please contact our support team by emailing support@provu.co.uk.

Yealink Provisioning: Common file mapping

This is perhaps more of a reminder to me for future reference, however, it may be useful for others too!

When a Yealink phone provisions, it requests a common provisioning file and a MAC specific one. The common one is referred to as such because each model requests a file which is unique to it.

Here are the Yealink models alongside the requested common files:

Model Common file Firmware code
CP860 CP860 y000000000037.cfg 37
T18P T18 y000000000009.cfg 18
T19P T19 y000000000031.cfg 31
T19P_E2 T19_E2 y000000000053.cfg 53
T20P T20 y000000000007.cfg 9
T21P T21 y000000000034.cfg 34
T21P_E2 T21_E2 y000000000052.cfg 52
T22P T22 y000000000005.cfg 7
T23G T23 y000000000044.cfg 44
T26P T26 y000000000004.cfg 6
T27P T27 y000000000045.cfg 45
T28P T28 y000000000000.cfg 2
T29G T29 y000000000046.cfg 46
T32G T32 y000000000032.cfg 32
T38G T38 y000000000038.cfg 38
T40P T40 y000000000054.cfg 54
T41P T41 y000000000036.cfg 36
T42G T42 y000000000029.cfg 29
T46G T46 y000000000028.cfg 28
T48G T48 y000000000035.cfg 35
VP530 VP530 y000000000023.cfg 23
VP530 VP-T49 y000000000051.cfg 51
W52P W52 y000000000025.cfg 25
W56P W56 y000000000025.cfg 25

Phew.. that should just about do it!