Spectralink 84-Series Series Wireless Telephones Administration Guide
1725-86984-000_P.docx
September 2016 116
The digits to be sent. The appearance of this parameter depends on the action string. If no digits are to be sent
it may not be necessary to include them. For example, if the macro includes a prompt to gather digits from the
user then it may not be necessary to supply digits. Valid digits are 0-9 and ‘*’ and ‘#’.
In the above example, the digits being sent by the macro action string are 20371. Note that the digits do not get
entered into the string with the ‘$’ on either end of the digits. This is because the digits are not a function that
must be interpreted by the handset.
This is a command that will be performed while processing the macro action string. It can appear anywhere in
the action string and may appear multiple times. Supported commands (or shortcuts) include:
• hangup (hu)
• hold (h)
• waitconnect (wc)
• pause <number of seconds> (p <num sec>) where the maximum value is 10
Note that the shortcut version of each command can be entered into the macro string instead of the full
command name.
In the above example, the command portion of the macro action string can be identified by the capital ‘C’. In this
case we are issuing a wait connect command, $Cwaitconnect$. The wait connect command causes the handset
to stop processing the macro action string until the call is connected to the far end. Using it at the end of the line
like this means that the handset will process everything before and then stop to wait for the call to connect. Since
we were collecting digits from the user the handset will not send these digits until the call is connected.
The type of action that will be performed if the macro action string is intended to initiate a call. Multiple actions
can be defined. Supported action types include:
• invite
• dtmf
• refer
Note: Spectralink recommends that you always define this field. If it is not defined, the supplied digits will be
dialed using INVITE (if no active call) or DTMF (if an active call). The use of refer method is call server
dependent and may require the addition of star codes. The refer method is the equivalent of a call transfer.
In the above example, the type of action being performed is, $Trefer$. Because this example is for a call park
scenario the refer action type is used because we are going to transfer the active call on the handset to a
network park location.
If you need to define multiple macros you can embed macros into a single macro string by using this option. The
<macro> string must begin with a letter rather than a digit. If the macro name is not defined, the execution of the
entire action string fails. Note that the <macro> is the actual name of another macro, not the macro action string.
You would define this embedded macro in the same you are defining this current macro. The macro name is the
efk.efklist.*.mname parameter.
$P<prompt num>N<num digits>$
You can use this option to cause the macro to prompt the user for additional input. That might be a name, a
phone number or whatever you need them to enter. See Prompt Macro Substitution for more details on how to
use this option.
In the above example, we defined a user prompt using, $P1N4$. This method uses the Prompt Macro
Substitution configuration to create the text that is displayed on the handset to prompt the user for more input. It
then collects the input, in this case, a maximum of 4 characters, and feeds that back into the macro for additional
processing.
Using this option you can define a directory entry as the location to collect the input needed to process the
macro. Only digits are valid for the <speed dial index> as only digits are used in the directory to define an index
location. The input collected is found in the contact field of the local directory entry pointed to by the index
number.
To Next Page
Loading...
