El acta de inspección de trabajo como medio de prueba

The phone maintains a local contact directory. The directory can be

downloaded from the provisioning server and edited locally (if configured in that way). Contact information from previous calls may be easily added to the directory for convenient future access.

The directory is the central database for several other features including speed-dial, distinctive incoming call treatment, presence, and instant messaging. The maximum number of entries in the local contact directory is phone-dependent. Central (provisioning server) Configuration file: sip.cfg

Enable or disable persistent headset mode.

For more information, refer to User Preferences <up/> on page A-29. Enable or disable hands-free speakerphone mode.

• For more information, refer to User Preferences <up/> on page A-29.

Configuration file:

phone1.cfg

Specify whether or not the electronic hookswitch is enabled and what type of headset is attached.

• For more information, refer to User Preferences <up/>on page A-128.

Local Web Server (if enabled)

Enable or disable persistent headset mode.

Navigate to: http://<phoneIPAddress>/coreConf.htm#us Local Phone User

Interface

Enable or disable persistent headset mode through the Settings menu (Settings > Basic > Preferences > Headset > Headet

Memory Mode).

Enable or disable hands-free speakerphone mode through the Settings menu (Settings > Advanced > Admin Settings > Phone

Settings).

Changes are saved to local flash and backed up to <Ethernet

address>-phone.cfg on the provisioning server. Changes will

permanently override global settings unless deleted through the Reset Local Config menu selection.

Note If a user makes a change to the local contact directory, there is a five second timeout before it is uploaded to the provisioning server as

<mac-address>-directory.cfg.

If so configured, the first and last name fields of the local contact directory entries which match incoming calls will be used for caller identification display and in the call lists (instead of the name provided through network signaling).

Configuration changes can be performed centrally at the provisioning server or locally:

Local Contact Directory File Format

An example of a local contact directory is shown below. The subsequent table provides an explanation of each element. Elements can appear in any order. <?xml version=”1.0” encoding=”UTF-8” standalone=”yes” ?>

<directory> <item_list> <item> <ln>Doe</ln> <fn>John</fn> <ct>1001</ct> <sd>1</sd> <lb>Mr</lb> <rt>1</rt> Central (provisioning server) Configuration file: sip.cfg

Set whether the directory uses volatile storage on the phone.

• For more information, refer to Local Directory <local/> on page A-81.

Specify whether or not the local contact directory is read only.

• For more information, refer to Local Directory <local/> on page A-81.

XML file:

000000000000-direct ory.xml

A sample file named 000000000000-directory~.xml (Note the extra “~” in the filename) is included with the application file distribution. This file can be used as a template for the per-phone <Ethernet

address>-directory.xml directories (edit contents, then rename to

<Ethernet address>-directory.xml). It also can be used to seed

new phones with an initial directory (edit contents, then remove “~” from file name). Telephones without a local directory, such as new units from the factory, will download the 00000000000-directory.xml directory and base their initial directory on it. These files should be edited with an XML editor. These files can be downloaded once per reflash.

For information on file format, refer to the next section, Local Contact Directory File Format.

XML file: <Ethernet

address>-directory. xml

This file can be created manually using an XML editor.

For information on file format, refer to the next section, Local Contact Directory File Format.

Local Local Phone User Interface

The user can edit the directory contents if configured in that way. Changes will be stored in the phone’s flash file system and backed up to the provisioning server copy of <Ethernet

address>-directory.xml if this is configured. When the phone boots,

the provisioning server copy of the directory, if present, will overwrite the local copy.

<ad>0</ad> <ar>0</ar> <bw>0</bw> <bb>0</bb> </item> ... <item> <ln>Smith</ln> <fn>Bill</fn> <ct>1003</ct> <sd>3</sd> <lb>Dr</lb> <rt>3</rt> <dc/> <ad>0</ad> <ar>0</ar> <bw>0</bw> <bb>0</bb> </item> </item_list> </directory>

Element Permitted Values Interpretation

fn UTF-8 encoded string

of up to 40 bytes

first name

Note: In some cases, this will be less than 40 characters due to

UTF-8’s variable length encoding.

ln UTF-8 encoded string

of up to 40 bytes

last name

Note: In some cases, this will be less than 40 characters due to

UTF-8’s variable length encoding.

ct UTF-8 encoded string

containing digits (the user part of a SIP URL) or a string that constitutes a valid SIP URL

contact

Used by the phone to address a remote party in the same way that a string of digits or a SIP URL are dialed manually by the user. This element is also used to associate incoming callers with a particular directory entry.

Note: This field cannot be null or duplicated.

sd Null, 1 to 9999 speed-dial index

Associates a particular entry with a speed dial bin for one-touch dialing or dialing from the speed dial menu.

Note: On the SoundPoint IP 32x/33x and the SoundStation IP 6000