Article ID:3848893

Yealink - Overrides Master List

Written By Jexter Reyes (Administrator)

Updated at July 20th, 2026

Objective

Contains all overrides for Yealink devices
 

Symptoms

  • VIP - Yealink Custom Overrides
  • VIP - Yealink Headsets Support
  • VIP - Yealink overrides - INTERCOM BLF KEYS
  • VIP Add Yealink T4x and T5x to YMCS Server Override
     

Procedure

Network Settings

Network Types: 801.1X (Replace X with number value)

network.802_1x.mode="X"

EAP-MD5 1
EAP-TLS 2
EAP-PEAP / MSCHAPv2 3
EAP-TTLS / EAP-MSCHAPv2 4
EAP-PEAP / GTC 5
EAP-TTLS / EAP-GTC 6
EAP-FAST 7
 
 

Setting Up VLANs

This section shows the override that Crexendo supports on the VIP platform for setting up VLANS. This override will need to be added to the device on the system needing the tags.

static.network.vlan.internet_port_enable="1"
static.network.vlan.internet_port_vid="vlan ID"
static.network.vlan.internet_port_priority="1"
static.network.vlan.pc_port_enable="1"
static.network.vlan.pc_port_vid="vlan ID"

 
 

LLDP

static.network.lldp.enable="1"

 
 

Static IP Address and Static DNS

Static IP Address

network.internet_port.type ="2"
network.internet_port.ip ="10.1.10.105"
network.static_dns_enable ="1"
static.network.primary_dns="8.8.8.8"
static.network.secondary_dns="8.8.4.4"
network.internet_port.mask ="255.255.255.0"
network.internet_port.gateway ="10.1.10.1"

static.network.wifi.ip_address_mode="0"
static.network.wifi.internet_port.type="2"
static.network.wifi.internet_port.ip="10.100.10.92"
static.network.wifi.internet_port.mask="255.255.0.0"
static.network.wifi.internet_port.gateway="10.100.0.100"
static.network.wifi.primary_dns="10.100.0.1"
static.network.wifi.secondary_dns="10.100.0.6"


Static DNS

static.network.static_dns_enable="1"
static.network.primary_dns="8.8.8.8"
static.network.secondary_dns="8.8.4.4"

 
 

Wi-Fi Setup

static.wifi.enable="1"
static.wifi.1.ssid="MyWiFi"
static.wifi.1.label="MyWiFi"
static.wifi.1.security_mode=:"WPA2-PSK"
static.wifi.1.password="Thisisareallybadpassword"

 
 

T4x / T5x - Adding to YMCS Server

#!version:1.0.0.1
dm.enable="1"
dm.server.port="443"
dm.server.http_enable="0"
dm.server.https_enable="0"
dm.server.retry_min_interval"="5"
dm.server.retry_interval_multiplier="2000"
dm.server.retry_interval_max_power="5"
features.usb_call_recording.enable="1"
voice.rtcp_xr.enable="1"
dm.server.address="dmtcp.yealink.com"

 
 

T58/59 Codec Override

account.1.codec.g722.priority="1"

 
 

 


Call Settings

Call Waiting and Call Waiting Tone

Call Waiting Tone

call_waiting.enable="1"
call_waiting.tone="0"


Enable Call Waiting

call_waiting.enable="1"

 
 

Distinctive Ring

NOTE: This feature works by adding a department name to the extension.

 

account.1.alert_info_url_enable="1"
distinctive_ring_tones.alert_info.1.text="Restaurant"
distinctive_ring_tones.alert_info.1.ringer="2"

Once done, submit a ticket to SD3

 
 

Headset and Ringer Speaker

Enable Headset Mode

features.headset_mode.enable ="1"


Ring Speaker and Headset

features.headset_mode.enable ="1"
features.ringer_device.is_use_headset="2"

 
 

Ringer Volume

NOTE: It is sometimes necessary to lock the ringer volume at the administrative level. This can be done by setting the value below to 0 through 15, with 15 being the loudest.

If any value is set, the rocker switch will not work. You can set this value to blank to restore volume rocker functionality.

 

force.voice.ring_vol="10"

 
 

Disable Sleep Mode

features.power_saving.enable="0"

 
 

DND

features.dnd.allow="0"

 
 

BLF into Intercom Keys

Turn BLF into Intercom Keys. This will remove the BLF transfer option. 

features.blf.intercom_mode.enable="1"
features.intercom.mode="1"
features.intercom.feature_access_code="*71"

 
 

Barge

features.intercom.barge="0"
features.intercom.allow="0"

 
 

T5xW / T4xS - Headset Support

This section is to help support agents resolve issues with Headsets for the Yealink series devices with the WH series headsets.

T5xW

This override will install the firmware for 96.86.0.127, which has been provided by Yealink as a beta firmware to fix the headset issues.

firmware.url="http://endpoints.crexendovip.com/frm/T5Beta.rom"


T4xS

This override will allow the installation of the firmware for 66.86.0.76, which is the beta firmware for headset support.

firmware.url="http://endpoints.crexendovip.com/frm/V42T4xS.rom"

 
 

W60B/W70 - Individual Line Ringing

Incoming Lines

handset.1.incoming_lines="1"
handset.2.incoming_lines="1"
handset.3.incoming_lines="1"
 

Dial Out

handset.X.dial_out_default_line="1,2,3,4"

handset.X.dial_out_lines="1,2,3,4"

EXAMPLE

Assume there are 3 handsets assigned to 3 different extensions:

  • Line Key 1 = Macky's extension
  • Line Key 2 = Sean's extension
  • Line Key 3 = TJ's extension

To configure the following overrides on the base:

handset.1.incoming_lines="1"
handset.2.incoming_lines="2"
handset.3.incoming_lines="3"

handset.1.dial_out_default_line="1"
handset.2.dial_out_default_line="2"
handset.3.dial_out_default_line="3"

Then, if all three users need the ability to place outbound calls using any of the available line keys, use these:

handset.1.dial_out_lines="1,2,3,4"
handset.2.dial_out_lines="1,2,3,4"
handset.3.dial_out_lines="1,2,3,4"

 
 
 

 


Others

Multicast Paging

Listen

This override allows a device to receive multicast pages from other devices.

multicast.listen_address.X.ip_address="ip address"
multicast.listen_address.X.label="Page All"

EXAMPLE

multicast.listen_address.1.ip_address="239.0.0.4:10004"
multicast.listen_address.1.label="Page All"
multicast.receive_priority.priority="0"

 

TIP:

  • listen_address.X – Identifies the multicast listening entry on the phone.
  • ip_address – Must match the sender’s multicast IP address and port.
  • label – Specifies the name displayed for the listening group.
  • receive_priority – Controls how an incoming page behaves when the phone is already on a call. Use the priority value that best meets the customer’s paging requirements.
    • Priority 0 – The page does not interrupt an active call.
    • Priority 1 – The page may interrupt an active call.
 

 


Broadcast

This override allows a device to send multicast pages to other devices.

linekey.X.type="24"
linekey.X.value="235.0.0.1:10001"
linekey.X.label="Page All"

EXAMPLE: This example creates a Page All button on line key 12.

linekey.12.type="24"
linekey.12.value="239.0.0.4:10004"
linekey.12.label="Page All"

 

TIP

  • linekey.X – Identifies the physical or virtual line key used for the paging button.
  • type=“24” – Assigns the multicast paging feature to the line key.
  • value – Specifies the multicast IP address and port used for paging.
  • label – Specifies the name displayed on the phone.
 

 


Paging from Yealink to All Polycom Phones (Default Paging Group)

This override allows a Yealink phone to send multicast pages to Polycom phones using the default Polycom multicast IP address and port.

linekey.12.type="24"
linekey.12.value="224.0.1.116:5001"
linekey.12.label="Page All"
linekey.12.extension="1"

TIP

  • linekey.12 – Identifies the line key used for the paging button.
  • type=“24” – Assigns the multicast paging feature to the line key.
  • value – Specifies the default Polycom multicast IP address and port.
  • label – Specifies the name displayed on the phone.
  • extension - Should equal the page group number
    • E.g., For Page All, extension="1". If the 2nd page group is Sales, the extension should be extension="2".
 

NOTE

  • Polycom phones must be subscribed to the appropriate paging group to receive multicast pages.
  • 224.0.1.116:5001 is the default multicast IP address and port used by Polycom phones.
  • If the Polycom multicast IP address or port has been customized using ptt.address or ptt.port, update linekey.12.value to match.
  • The Yealink and Polycom must use the same multicast IP address and port for paging to function correctly.
  • Both devices must be on the same network, or multicast routing must be configured between networks.
 

 


Paging from Yealink to Polycom

This override allows a Yealink phone to send multicast pages to Polycom phones.

Yealink (Sender)

linekey.X.type="24"
linekey.X.value="224.0.1.116:5001"
linekey.X.label="<Insert Page Group Name>"
 

Polycom (Receiver)

ptt.pageMode.group.X.subscribed="1"

TIP

  • linekey.X – Identifies the physical or virtual line key used for the paging button.
  • type=“24” – Assigns the multicast paging feature to the line key.
  • value – Specifies the multicast IP address and port used to send the page.
  • label – Specifies the name displayed on the phone. Replace <Insert Page Group Name> with the desired paging button label.

Polycom

  • ptt.pageMode.group.X.subscribed=“1” – Subscribes the Polycom phone to the specified paging group.
  • Replace X with the desired Polycom paging group number.
 

NOTE

  • The Yealink sends multicast pages to a multicast IP address and port. It does not specify a Polycom paging group.
  • The Polycom phone must be subscribed to the desired paging group to receive multicast pages.
  • 224.0.1.116:5001 is the default multicast IP address and port used by Polycom phones.
  • If the Polycom multicast IP address or port has been customized using ptt.address or ptt.port, update linekey.X.value to match.
  • The Yealink and Polycom must use the same multicast IP address and port for paging to function correctly.
  • Both devices must be on the same network, or multicast routing must be configured between networks.
 

To learn more about multicast paging for Polycom, refer to Polycom - Overrides Master List

 
 

Force Remote Phonebook/History

directory_setting.remote_phone_book.enable="1"
directory_setting.history.enable="1"

 
 

Disable Voicemail Notification

features.voice_mail_popup.enable="0"
phone_setting.mail_power_led_flash_enable="0"

 
 

Missed Call Notification

features.missed_call_popup.enable="0"
account.1.missed_calllog="1"
phone_setting.missed_call_power_led_flash.enable="0"

 
 

 

Escalation Information

Escalation Information: SD2

If you have any questions, concerns, or issues, contact the Service Desk II (SD2) team.

IMPORTANT: Before escalating to SD2, refer to this article.

 

 

Change Log

Date Description
Jun 19, 2026 Article migrated and revamped