Macro Actions

The action string is executed in the order it displays.

User input is collected before any action is taken. The action string can contain the fields shown in the following table.

Action String



This is the label for the entire operation. The value can be any string including the null string (in this case, no label displays). This label is used if no other operation label collection method worked (up to the point where this field is introduced). Make this the first entry in the action string to be sure this label is used; otherwise another label may be used and this one ignored.


The digits to be sent. The appearance of this parameter depends on the action string.


This is the command. It can appear anywhere in the action string. Supported commands (or shortcuts) include:

hangup ( hu )

hold ( h )

waitconnect ( wc )

pause <number of seconds> ( p <num sec> ) where the maximum value is 10


The embedded action type. Multiple actions can be defined. Supported action types include:

invite dtmf refer intercom

Polycom recommends that you always define this field. If it is not defined, the supplied digits are 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 embedded macro. The <macro> string must begin with a letter. If the macro name is not defined, the execution of the action string fails.

$P<prompt num>N<num digits>$

The user input prompt string.

$S<speed dial index>$

The speed dial index. Only digits are valid. The action is found in the contact field of the local directory entry pointed to by the index

$F<internal function>$

An internal key function.


A URL. Only one per action string is supported.