Using Enhanced DSS Keys on Yealink IP Phones
3
Macro Action
Description
$T<type>$
The embedded action type. Multiple actions can be
defined. Supported action types include:
invite
dtmf
refer
intercom (not applicable to CP860 IP phones)
Example: *338$Tdtmf$ defines sending the *338 by the
type of dtmf.
Note: We recommend that you always define this field.
If it is not defined, the supplied digits are dialed using
INVITE.
$M<macro>$
The embedded macro. The <macro> string must begin
with a letter. If the macro name is not defined, the
execution of the action string will be ignored.
Example: $MAA$ means invoking the EDK macro AA.
$S<softkey ID>$
The functionality of performing this action is the same
as that of pressing the desired soft key.
Each soft key has a unique identifier on the IP phone,
you can configure this parameter according to the
system-defined softkey ID. If the softkey ID is not
defined on the phone or there is no matched soft key on
the current screen, the execution of the action string will
be ignored. The softkey ID is case-insensitive.
Example: $Sanswer$ means pressing the Answer soft
key.
Yealink IP phones support customizing soft keys. When
invoking a custom soft key, the prefix “#” must be
added.
Example: If the custom softkey label is IVR1, the custom
softkey ID is custom_macro, then
$S#custom_macro$ means pressing the IVR1 soft key.
Note: To view the softkey ID, you can configure the
value of the parameter “edk.id_mode.enable” to 1
(Enabled) and then long press the Volume Up key when
the phone is idle. For more information, refer to
Configuring EDK ID Mode
.
$K<key name>$
The functionality of performing this action is the same
as that of pressing the desired hard key.