Overview

When configuring Yealink devices with the Single Button Park/Retrieve feature through the Modify Device Keys interface, administrators may notice automatic adjustments to specific device parameters. Enabling this feature sets the transfer.dsskey_deal_type parameter to 0 and introduces two additional parameters:

• features.call_park.park_mode

• features.call_park.enable

These changes are expected and part of the device’s call park implementation logic.

However, if issues arise after applying or removing this configuration, it is important to verify whether conflicting or duplicate device parameter groups exist—particularly in testing environments, where multiple test groups may remain active. Conflicting settings (e.g., having transfer.dsskey_deal_type set to both 2 and 0 across different groups) can lead to inconsistent device behavior.

Solution

To ensure proper functionality and avoid conflicts when using or troubleshooting the Single Button Call Park/Retrieve feature, follow the steps below:

1. Remove or Disable the Single Button Call Park/Retrieve Feature

If the issue persists after applying the feature, remove it temporarily and test again. This will help verify whether it is contributing to the behavior.

2. Review Device Parameter Groups

Inspect the device parameter configurations associated with the affected devices, keeping in mind that conflicts can occur when multiple parameter groups define different values for transfer.dsskey_deal_type.

Ensure that:

• No redundant or unused parameter groups remain active.

• Duplicate groups in the environment are removed.

• The device is assigned only to the correct and intended group.

3. Provide Additional Subscriber Information

If the issue continues after removing the feature and cleaning up parameter groups, provide support with:

• Another affected subscriber in the environment.

• A corresponding device MAC address.

This allows for deeper investigation into configuration inheritance, overrides, and device-specific anomalies.