Polycom SIP 3.1 Administrator's Manual page 100

Sip 3.1
Table of Contents

Advertisement

Administrator's Guide SoundPoint IP / SoundStation IP
Note
Central
Configuration file:
sip.cfg
(boot server)
Configuration file:
phone1.cfg
XML file: <Ethernet
address>-directory.
xml
4 - 46
The macros provide a generic and easy to manage way to define the prompt to
be displayed to the user, the maximum number of characters that the user can
input, and action that the phone performs once all user input has been
collected. The macros are case sensitive.
If a macro attempts to use a prompt that is disabled, the macro execution fails.
A prompt is not required for every macro.
Expanded Macros
Expanded macros are prefixed with the "^" character and are inserted directly
into the local directory contact field. For more information, refer to
Contact Directory File Format
Configuration File Changes
The configuration file changes and the enhanced feature key definitions can be
included together in one configuration file.
A sample configuration for this feature—including the enhanced feature keys
definitions shown in the following section, Examples— may be included with the
SIP 3.1 release.
Create a new configuration file in the style of sip.cfg in order to make configuration
changes. For more information on why to create another configuration file, refer to
the "Configuration File Management on SoundPoint IP Phones" whitepaper at
www.polycom.com/support/voice/
Configuration changes can performed centrally at the boot server:
Turn this feature on or off.
For more information, refer to
Specify two calls per line key.
For more information, refer to
This file holds the macro names which correspond to the mname fields
in the configuration file where the enhanced feature keys are defined.
Macro names must be embedded into the contact (cn) fields with the
"!" prefix. You can also add labels in the first name (fn) fields.
For information on file format, refer to
Format
on page 4-10.
Useful Tips
The following information should be noted:
Activation of the enhanced feature key will fail if configured values are
invalid except where noted in previous sections.
All failures are logged at level 4 (minor).
on page 4-10.
.
Feature <feature/>
Registration <reg/>
Local Contact Directory File
Local
on page A-92.
on page A-107.

Advertisement

Table of Contents
loading

Table of Contents