Administrator’s Guide SoundPoint IP / SoundStation IP

 

Note

If a user makes a change to the local contact directory, there is a five second

 

 

 

timeout before it is uploaded to the boot server as <mac-address>-directory.cfg.

 

 

 

 

 

 

 

 

Configuration changes can performed centrally at the boot server or locally:

 

 

 

 

Central

 

Configuration file:

Set whether the directory uses volatile storage on the phone

(boot server)

 

sip.cfg

 

(required on the SoundPoint IP 500 platform for directories greater

 

 

 

 

than 25 entries).

 

 

 

 

For more information, refer to Local Directory <local/> on page

 

 

 

 

A-68.

 

 

 

 

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

 

 

 

 

For more information, refer to Local Directory <local/> on page

 

 

 

 

A-68.

 

 

 

 

 

 

 

XML file:

 

A sample file named 000000000000-directory~.xml(Note the extra

 

 

000000000000-direct

“~” in the filename) is included with the application file distribution.

 

 

This file can be used as a template for the per-phone <Ethernet

 

 

ory.xml

 

 

 

 

 

address>-directory.xmldirectories (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

This file can be created manually using an XML editor.

 

 

address>-directory.

For information on file format, refer to the next section, Local Contact

 

 

xml

 

Directory File Format.

 

 

 

 

Local

 

Local Phone User

The user can edit the directory contents if configured in that way.

 

 

Interface

 

Changes will be stored in the phone’s flash file system and backed up

 

 

 

 

to the boot server copy of <Ethernet address>-directory.xmlif this

 

 

 

 

is configured. When the phone boots, the boot server copy of the

 

 

 

 

directory, if present, will overwrite the local copy.

 

 

 

 

 

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>

<lb>Mr</lb>

<ln>Doe</ln>

<fn>John</fn>

4 - 10

Page 64
Image 64
Polycom SIP 3.1 manual Direct, Ory.xml, Xml, ?xml version=1.0 encoding=UTF-8 standalone=yes ? directory

SIP 3.1 specifications

Polycom SIP 3.1 is an advanced session initiation protocol designed to enhance voice and video communication in various business environments. As a pivotal component of Polycom’s telecommunication solutions, SIP 3.1 offers several features and characteristics that cater to the evolving needs of modern enterprises, particularly those that rely on seamless and efficient communication.

One of the standout features of Polycom SIP 3.1 is its robust interoperability. This protocol supports a wide range of endpoints and platforms, allowing organizations to integrate their existing systems with new technologies effortlessly. This flexibility ensures that businesses can leverage their previous investments while upgrading to the latest communication tools.

Another key aspect of Polycom SIP 3.1 is its enhanced call management capabilities. The protocol facilitates efficient call handling, enabling users to manage multiple calls seamlessly. Features like call hold, transfer, and conferencing are streamlined, which enhances productivity by allowing for efficient collaboration among team members. Additionally, it is optimized for low latency and high-quality audio, ensuring that conversations are clear and free from disruptions.

Security is paramount in today’s digital landscape, and Polycom SIP 3.1 addresses this concern with advanced encryption standards. By integrating security features such as Transport Layer Security (TLS) and Secure Real-time Transport Protocol (SRTP), it protects sensitive communication from unauthorized access and ensures that data remains confidential throughout the call.

Polycom SIP 3.1 also boasts compatibility with various video codecs, making it a versatile choice for video conferencing. This compatibility ensures high-quality video streams, which is essential for effective visual communication in remote meetings. Furthermore, the support for the H.264 codec provides efficient bandwidth usage, making high-definition video conferencing accessible, even in varying network conditions.

Moreover, the protocol provides strong support for presence and instant messaging, which enhances real-time communication among users. This integration of voice, video, and messaging capabilities fosters a more connected and collaborative work environment, allowing teams to engage effectively regardless of their geographical locations.

In summary, Polycom SIP 3.1 stands out as a sophisticated solution tailored to meet the demands of modern business communication. With its emphasis on interoperability, call management, security, video quality, and real-time collaboration, it caters to companies of all sizes seeking to optimize their communication infrastructure and enhance productivity in the workplace. As businesses continue to navigate the complexities of digital communication, Polycom SIP 3.1 remains a compelling choice in the market.