Overview
Yealink IP phones support a provisioning parameter that allows administrators to enforce a fixed ringer volume, preventing users from adjusting the ringing level using the phone's volume controls.
This feature is particularly useful in high-call-volume environments, such as dealership reception areas, BDC departments, and customer service teams, where incoming calls must remain audible.
However, locking the ringer volume alone does not guarantee that incoming calls will produce an audible ringtone.
Users may still be able to silence or reject incoming calls or select a silent ringtone, effectively bypassing the intended ringer volume restriction.
This article explains these limitations and outlines additional Yealink provisioning configurations that can provide stronger control over incoming-call behavior.
1. Understanding the Fixed Ringer Volume Limitation
The following parameter enforces a fixed ringer volume:
force.voice.ring_vol="10"
Parameter: force.voice.ring_vol
Permitted values: 0–15
Example setting: 10
When configured, the phone uses the specified ringer volume rather than allowing the user to adjust it through the standard volume controls.
How Users Can Bypass the Fixed Volume
Even with a fixed ringer volume, users may still be able to:
- Silence an incoming call: Stop the ringtone for the current incoming call.
- Reject an incoming call: Dismiss the incoming call before it is answered.
- Select Silent.wav: Change the phone's ringtone to a silent audio file.
These actions bypass its intended purpose by preventing the phone from producing an audible incoming-call alert.
2. Configure a Standard Ringtone
The first step toward stronger ring control is to configure a known, audible ringtone.
account.1.ringtone.ring_type="Ring1.wav"
This parameter assigns Ring1.wav as the ringtone for Account 1.
Important: Assigning a ringtone does not prevent the user from subsequently changing it.
To restrict access to ringtone selection, additional user access-level configuration is required, as described in the next section.
Refer to the Yealink Administrator Guide for supported ringtone values and model-specific behavior.
3. Restrict Ringtone Changes Using User Access Levels
Yealink supports access-level restrictions that allow administrators to control which phone settings are available to end users.
The following provisioning parameters work together to enable user access-level functionality and reference an external configuration file that restricts ringtone selection.
Provisioning Parameters
static.security.var_enable="1" static.security.default_access_level="0" static.web_item_level.url="https://endpoints1-iad.callrevutel.com/cfg/RNG_TYP_SET_1.cfg"
Parameter Descriptions
| Parameter | Purpose |
|---|---|
static.security.var_enable |
Enables user access-level configuration. |
static.security.default_access_level |
Sets the phone's default access level to User (0). |
static.web_item_level.url |
Specifies the location of the CFG file containing the phone's access-level restrictions. |
Understanding the CFG File
The static.web_item_level.url parameter directs the Yealink phone to retrieve an external configuration file containing restrictions for specific phone settings.
In this example, the file is named:
RNG_TYP_SET_1.cfg
The file contains the following configuration:
[ GUI ] #Turn off Ringtone Selection ring_type_setting = 01
Configuration breakdown:
-
[ GUI ]— Identifies the configuration section for GUI access-level settings. -
#Turn off Ringtone Selection— Comment describing the purpose of the restriction. -
ring_type_setting = 01— Configures the ringtone selection access-level restriction.
This configuration is intended to prevent users operating at the restricted access level from changing the ringtone through the phone's settings interface.
Where the CFG File Is Stored
The CFG file is uploaded and maintained in NDP under System → Files & Firmware
Example file URL:
https://endpoints1-iad.callrevutel.com/cfg/RNG_TYP_SET_1.cfg
Important: The provisioning URL must point to the correct hosted CFG file. The access-level parameters alone do not prevent ringtone changes; the CFG file defines the specific restriction.
Related Documentation
How to Lock Menu Items on Yealink Devices
4. Remove Incoming-Call Softkeys (Silence, Forward, and Reject)
Even after restricting ringtone selection, users may still be able to silence, forward, or reject incoming calls using the softkeys displayed on the Yealink phone.
Yealink supports custom softkey layouts that allow administrators to control which softkeys are displayed during specific call states.
The following configuration is designed to remove the Silence, Forward, and Reject softkeys during an incoming call, leaving Answer as the available softkey. Note: The Forward softkey is already disabled globally by CallRevu and does not require additional configuration.
Provisioning Parameters
phone_setting.custom_softkey_enable="1" phone_setting.custom_softkey.apply_to_states="CallIn" custom_softkey_call_in.url="https://endpoints1-iad.callrevutel.com/frm/CallIn.xml"
Parameter Descriptions
| Parameter | Purpose |
|---|---|
phone_setting.custom_softkey_enable |
Enables custom softkey functionality. |
phone_setting.custom_softkey.apply_to_states |
Applies the custom softkey configuration to the incoming-call state (CallIn). |
custom_softkey_call_in.url |
Specifies the URL of the XML file defining the incoming-call softkey layout. |
Understanding the XML File
The custom_softkey_call_in.url parameter directs the Yealink phone to retrieve an external XML file that defines which softkeys should be displayed or hidden during an incoming call.
In this example, the file is named:
CallIn.xml
The file contains the following configuration:
<CallIn>
<Disable>
<Key Type="Silence"/>
<Key Type="Forward"/>
<Key Type="Reject"/>
</Disable>
<Enable>
<Key Type="Answer"/>
</Enable>
<Default>
<Key Type="Answer"/>
</Default>
</CallIn>XML Configuration Breakdown
| XML Element | Purpose |
|---|---|
<CallIn> |
Defines the softkey configuration for the incoming-call state. |
<Disable> |
Identifies the softkeys to remove from the incoming-call screen. |
<Key Type="Silence"/> |
Removes the Silence softkey. |
<Key Type="Forward"/> |
Removes the Forward softkey. |
<Key Type="Reject"/> |
Removes the Reject softkey. |
<Enable> |
Identifies the softkey that should remain available. |
<Key Type="Answer"/> |
Enables the Answer softkey. |
<Default> |
Defines the default softkey for the incoming-call state. |
This configuration reduces the user's ability to suppress, redirect, or dismiss incoming calls using the displayed softkeys.
Where the XML File Is Stored
The XML file is uploaded and maintained within NDP under System → Files & Firmware
Example file URL:
https://endpoints1-iad.callrevutel.com/frm/CallIn.xml
Note: Softkey behavior can vary by Yealink model and firmware version. Validate the expected layout on the specific device before applying the configuration across multiple phones.
Related Documentation
Yealink Softkey Layout Documentation
5. Additional Configuration Considerations
For environments requiring stricter incoming-call behavior, consider disabling other features that allow users to prevent incoming calls from ringing normally.
Disable Do Not Disturb (DND)
features.dnd.allow="0"
Disables user access to the phone's DND feature, reducing the ability to suppress incoming-call notifications through DND.
Disable Call Forwarding (CF)
features.fwd.allow="0"
Restricts the phone's call-forwarding functionality, reducing the ability to redirect incoming calls through the phone interface.
Note: The Forward softkey is already disabled globally by CallRevu.
Enforce a Fixed Ringer Volume
force.voice.ring_vol="10"
Sets the fixed ringer volume to level 10.
Adjust the value according to the customer's requirements. Phone supported range 0–15.
Configure the User Access Password
static.security.user_password="user:6499"
Sets the phone's User access-level password to the specified value.
Summary
The Yealink force.voice.ring_vol parameter is useful for enforcing a consistent ringer volume, but it is not a complete solution for preventing users from suppressing incoming-call alerts.
For stronger ring control, administrators can combine:
- Fixed ringer volume to prevent volume adjustments.
- Ringtone configuration and access restrictions to prevent selection of a silent ringtone.
- Custom incoming-call softkeys to remove the displayed Silence and Reject options.
- Disabling DND to limit additional methods of suppressingcalls.
Together, these configurations provide greater control over incoming-call behavior while reducing opportunities for users to bypass the intended ringer settings.