Configuration Files

<fontName> is a free string of characters that typically carries the meaning of the font. Examples are “fontFixedSize” for a fixed-size font, or “fontProportionalSize” for a proportional size font.

<fontHeightInPixels> describes the font height in number of screen pixels.

<fontRange> describes the Unicode range covered by this font. Since .fnt or .fon are 256 characters based blocks, the <fontRange> is Uxx00_UxxFF (.fnt file) or Uxx00_UyyFF (.fon file). For more information, refer to Multilingual User Interface on page 4-30.

<fontExtension> describes the file type. Either .fnt for single 256 characters font or .fon for multiple .fnt files.

If it is necessary to overwrite an existing font, use these <fontName>_<fontHeightInPixels>:

SoundPoint IP 320, 330, 430, 500 and 501

“fontProp_10”

This is the font used widely in the current implementation.

“fontPropSoftkey_10”

This is the soft key specific font.

SoundPoint IP 550, 560, 600, 601, 650, and 670

“fontProp_19”

This is the font used widely in the current implementation including for

 

soft keys.

“fontProp_26”

This is the font used to display time (but not date).

“fontProp_x”

This is a small font used for the CPU/Load/Net utilization graphs, this

 

is the same as the “fontProp_10” for the SoundPoint IP 500.

If the <fontName>_<fontHeightInPixels> does not match any of the names above, then the downloaded font will be applied against all fonts defined in the phone, which means that you may lose the benefit of fonts being calibrated differently depending on their usage. For example, the font used to display the time on the SoundPoint IP 650 is a large font, larger than the one used to display the date, and if you overwrite this default font with a unique font, you lose this size aspect. For example:

to overwrite the font used for SoundPoint IP 500 soft keys for ASCII, the name should be fontPropSoftkey_10_U0000_U00FF.fnt .

to add support for a new font that will be used everywhere and that is not currently supported. For example, for the Eastern/Central European Czech language, this is Unicode range 100-17F, the name could be fontCzechIP500_10_U0100_U01FF.fnt and fontCzechIP600_19_U0100_U01FF.fnt .

When defining a single .fon file, there is a need for a font delimiter, currently “Copyright Polycom Canada Ltd” is used as an embedded delimiter, but this can be configured using font.delimiter. The font delimiter is important to retrieve the different scrambled .fnt blocks. This font delimiter must be placed in the “copyright” attribute of the .fnt header. .fon files are useful if you want

A - 73

Page 227
Image 227
Polycom SIP 3.1 manual SoundPoint IP 320, 330, 430, 500, SoundPoint IP 550, 560, 600, 601, 650

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.