|
Starting with firmware version 10.1.21.0, the user interface on the phones can be completely customized. The colour and transparency values of all user interface elements, as well as all visible icons and images are open for modification. These extensive configuration options in turn allow you to create your own custom Themes that fit your company and brand identity.
Custom Icons and Images are an essential part of the customization process and the snom phones allow to modify and change all of them.
All snom icons are available and bundled with every firmware release. The Customization files can be downloaded on the release specific pages found here. Please note that each release contains customization files specific to that release and phone. Using customization files that do not match the firmware or phone will lead to issues.
snomD385-10.1.42.14-SIP-r.bin requires snomD385-10.1.42.14-customizing.tar.gz |
When the customizing.tar.gz is downloaded and extracted it should look like this. The actual content of the files depends on the phone and firmware version.
For testing or previewing purposes, as well as smaller installations, the phones support the upload of custom images via web interface. A general description how this works can be found here.
For longterm solutions and large installations it is recommended to start provisioning the image files via xml and tar file. A detailed description how this method works can be found here. Below you will find a short summary of what needs to be done for devices with a color as well as a monochrome display.
The Icons on monochrome devices are not stored in regular image files such as .png or .jpg but are Bitmap fonts that include every icon used in the UI. In the private use area of the unicode table starting at U+EB00 the snom icons are defined and can be directly modified with tools such as "Font Forge".
Opening the Bitmap font file with Font Forge should show a list of icons that are currently in use. The actual content of the files depends on the phone and firmware version.
Context-Sensitive Key Icons 17x17 - Baseline x → 0 / y → -2 Titlebar Icons 17x17 - Baseline x → 0 / y → -2 Label Panel Icons 17x17 - Baseline x → 0 / y → -2 Maximum Size of Icons 32x32 |
Context-Sensitive Key Icons 7x7 - Baseline x → 0 / y → 0 Titlebar Icons 7x7 - Baseline x → 0 / y → 0 SmartLabel Icons 7x7 - Baseline x → 0 / y → 0 Maximum Size of Icons 32x32 |
When exporting the files from Font Forge please utilize the following settings below
After having exported the files create a tar file containing the newly created file with the name of the file that is going to be replaced
tar -cvf fonts.tar fontfile.bdf |
The final step is then to include the tar file in your settings provisioning file with the type set to "font".
<?xml version="1.0" encoding="utf-8" ?> <settings> <uploads> <file url="http://192.168.23.54:8080/fonts.tar" type="font" /> </uploads> </settings> |
The icons and images on devices with a color display store their icons in PNG format. This allows for easy editing in pretty much all current image editors. However it is advised to optimize the png files with tools such as optipng, pngquant or pngcrush after editing and saving them to remove any redundant information.
Context-Sensitive Key Icons 24x24px SmartLabel Icons 24x24px & 18x18px Titlebar Icons 18x18px Menu Icons 18x18px Call Screen Icons 18x18px - 48x48px File Format: PNG The name of newly created / modified Icon has to match the name and location of the icon that it is going to replace otherwise the changes will not be applied. When saving all file size, color profile and exif information should be discarded. |
When creating a tar file for color display phones please be advised that the folder structure and the xml are not identical to the one created for devices with a monochrome display.
Navigate to the /bmp folder of the customizing.tar that was included with the Firmware Release. From this folder execute:
tar -cvf icons.tar colored |
This should keep the folder structure intact and correctly extract all files and folders when provisioned.
You can find the new subfolders "Dark", "Colorful" and "Industrial" inside the colored folder. These folders are containing the icons for the new added themes. The old subfolders are still containing the icons for the default color theme "Light", which has no additional folder. Furthermore the custom images will now be extracted to a different location on the phone than before ("/snom/html/custom_image_upload") to avoid overwriting original icons. To save space on the phone only the exchanged icons should be added to the new tar file. You can do this by using the "–newer" option to add only files that are newer than the date that is given in the option. From the /bmp folder execute (but insert the right date instead of the template):
|
This is the current icon directory structure:
├── call_icons
│ ├── 18x18
│ ├── 24x24
│ ├── 36x36
│ └── 48x48
├── call_overlay
│ ├── 36x36
│ ├── 48x48
│ ├── 60x60
│ ├── 72x72
│ ├── 84x84
│ └── 96x96
├── circle_overlays
│ ├── 36x36
│ ├── 48x48
│ ├── 60x60
│ ├── 72x72
│ ├── 84x84
│ └── 96x96
├── contact_state_icons
│ ├── 18x18
│ ├── 24x24
│ ├── 36x36
│ └── 48x48
├── contact_state_overlays
│ ├── 36x36
│ └── 48x48
├── contact_type_icons
│ ├── 18x18
│ ├── 24x24
│ ├── 36x36
│ └── 48x48
├── error_icons
│ ├── 18x18
│ ├── 24x24
│ ├── 36x36
│ ├── 48x48
│ ├── 60x60
│ ├── 72x72
│ ├── 84x84
│ └── 96x96
├── extraicontype_icons
│ └── 18x18
├── fkey_icons
│ ├── 18x18
│ └── 24x24
├── icontype_icons
│ ├── 24x24
│ ├── 36x18
│ └── 36x36
├── identity_state_icons
│ ├── 18x18
│ ├── 24x24
│ ├── 36x36
│ └── 48x48
├── input_info_images
├── other_images
├── settings_window_icons
│ └── 24x24
├── theme_colorful
│ ├── call_icons -> ../call_icons
│ ├── call_overlay -> ../call_overlay
│ ├── circle_overlays -> ../circle_overlays
│ ├── contact_state_icons -> ../contact_state_icons
│ ├── contact_state_overlays -> ../contact_state_overlays
│ ├── contact_type_icons -> ../contact_type_icons
│ ├── error_icons
│ │ ├── 18x18
│ │ ├── 24x24
│ │ ├── 36x36
│ │ ├── 48x48
│ │ ├── 60x60
│ │ ├── 72x72
│ │ ├── 84x84
│ │ └── 96x96
│ ├── extraicontype_icons
│ │ └── 18x18
│ ├── fkey_icons
│ │ ├── 18x18
│ │ └── 24x24
│ ├── icontype_icons
│ │ ├── 24x24
│ │ ├── 36x18
│ │ └── 36x36
│ ├── identity_state_icons -> ../identity_state_icons
│ ├── input_info_images
│ ├── other_images
│ ├── settings_window_icons
│ │ └── 24x24
│ └── titlebar_icons
│ └── 18x18
├── theme_dark
│ ├── call_icons -> ../call_icons
│ ├── call_overlay -> ../call_overlay
│ ├── circle_overlays -> ../circle_overlays
│ ├── contact_state_icons -> ../contact_state_icons
│ ├── contact_state_overlays -> ../contact_state_overlays
│ ├── contact_type_icons -> ../contact_type_icons
│ ├── error_icons
│ │ ├── 18x18
│ │ ├── 24x24
│ │ ├── 36x36
│ │ ├── 48x48
│ │ ├── 60x60
│ │ ├── 72x72
│ │ ├── 84x84
│ │ └── 96x96
│ ├── extraicontype_icons
│ │ └── 18x18
│ ├── fkey_icons
│ │ ├── 18x18
│ │ └── 24x24
│ ├── icontype_icons
│ │ ├── 24x24
│ │ ├── 36x18
│ │ └── 36x36
│ ├── identity_state_icons -> ../identity_state_icons
│ ├── input_info_images
│ ├── other_images
│ ├── settings_window_icons
│ │ └── 24x24
│ └── titlebar_icons
│ └── 18x18
├── theme_industrial
│ ├── call_icons -> ../call_icons
│ ├── call_overlay -> ../call_overlay
│ ├── circle_overlays -> ../circle_overlays
│ ├── contact_state_icons -> ../contact_state_icons
│ ├── contact_state_overlays -> ../contact_state_overlays
│ ├── contact_type_icons -> ../contact_type_icons
│ ├── error_icons
│ │ ├── 18x18
│ │ ├── 24x24
│ │ ├── 36x36
│ │ ├── 48x48
│ │ ├── 60x60
│ │ ├── 72x72
│ │ ├── 84x84
│ │ └── 96x96
│ ├── extraicontype_icons
│ │ └── 18x18
│ ├── fkey_icons
│ │ ├── 18x18
│ │ └── 24x24
│ ├── icontype_icons
│ │ ├── 24x24
│ │ ├── 36x18
│ │ └── 36x36
│ ├── identity_state_icons -> ../identity_state_icons
│ ├── input_info_images
│ ├── other_images
│ ├── settings_window_icons
│ │ └── 24x24
│ └── titlebar_icons
│ └── 18x18
└── titlebar_icons
└── 18x18
|
The XML settings file has to have its type set to "gui" and thereby allowing the phone to replace the current UI Icons with the newly created ones.
<?xml version="1.0" encoding="utf-8" ?> <settings> <uploads> <file url="http://192.168.23.54:8080/icons.tar" type="gui" /> </uploads> </settings> |
The icons in the idle screen that are displayed in the Context-Sensitive Keys Area can be fully customized to load any icon or image regardless of what function is configured. This can be achieved by either modifying the Icon in the phone user interface Settings → Preferences → Function Keys → Context-Sensitive Keys → Key → Icon
or by modifying the setting value
before 10.1.51.0: <gui_fkey1_icon_type>VALIDVALUE</gui_fkey1_icon_type> <gui_fkey2_icon_type>VALIDVALUE</gui_fkey2_icon_type> <gui_fkey3_icon_type>VALIDVALUE</gui_fkey3_icon_type> <gui_fkey4_icon_type>VALIDVALUE</gui_fkey4_icon_type> since 10.1.51.0: <context_key_icon_type idx="0">VALIDVALUE</context_key_icon_type> <context_key_icon_type idx="1">VALIDVALUE</context_key_icon_type> <context_key_icon_type idx="2">VALIDVALUE</context_key_icon_type> <context_key_icon_type idx="3">VALIDVALUE</context_key_icon_type> |
The setting supports loading icons from an external URL for color phones in addition to the names that are listed under Settings → Preferences → Function Keys → Context-Sensitive Keys → Key → Icon
|
On the left are Context-Sensitive Keys with their default icons while on the right they were modified via phone user interface configuration.
The icons in the Label Panel Display and SmartLabel can be fully customized to load any icon or image regardless of what function is configured. This can be achieved by either modifying the Icon in the phone user interface Settings → Preferences → Function Keys → Line Keys → Key → Icon
or by modifying the setting value
<fkey_icon_type idx="0">VALIDVALUE</fkey_icon_type> <fkey_icon_type idx="1">VALIDVALUE</fkey_icon_type> <fkey_icon_type idx="2">VALIDVALUE</fkey_icon_type> <fkey_icon_type idx="3">VALIDVALUE</fkey_icon_type> <fkey_icon_type idx="4">VALIDVALUE</fkey_icon_type> <fkey_icon_type idx="5">VALIDVALUE</fkey_icon_type> [...] |
Examples
It is possible to hide the Label for the Context-Sensitive Keys by configuring the following setting to OFF
<text_softkey>VALIDVALUE</text_softkey> since 10.1.51.0: <context_key_text>VALIDVALUE</context_key_text> |
On Color phones the result is that the label text for all Context-Sensitive Keys is hidden.
The behavior on monochrome devices is different. The setting will toggle between icon only and text only view. |
In order to use custom icons in XML files, icon names can be used to directly add or replace icons in those.
|
The XML above should show you the following results.
Phones with a primary monochrome display do not support loading Icons or Images from an external URL. These devices only support loading the existing Icons on the phone via Icon Name |
XML Definitions support showing custom icons and labels when configured for both monochrome and color phones. Below is an example of a settings file where the phone is setup as a Hotel Room Phone with four Speed Dials that have a custom icon and label
|
|
All phones with a monochrome display show icons on the monochrome display by loading a font that contains a set of icons in a specific unicode area. This means that it is possible to combine Icons and text in a label setting or xml tag. Detailed Instructions on how to do this can be found here.
The default Account Icon can be updated to show a Custom Photo in different ways.
Each method has a separate priority and is overwritten if a method is configured that has a higher priority.
Picture information that is sent via vCard e.g. Broadsoft
Picture that is configured for user_pic
Picture from Local Directory Contact that matches configured Identity
If the snom phone receives a vCard containing a URL to a valid picture URL it will automatically utilize the supplied picture in the vCard and display it in the idle and call screen. This is currently only possible when a valid XMPP ID is configured for server type Broadsoft.
All color phones support loading and displaying a user picture from a valid picture URL that is then displayed in the idle and call screen. This can be achieved by configuring:
<user_pic idx="INDEX">VALIDVALUE</user_pic> |
If the phone can successfully fetch a picture from the url that was configured in the setting, it will send a header with every SIP Invite that points to the picture, so that the called party can display the user picture from the incoming call.
Call-Info: <http://192.168.23.54:8080/picture.png>;purpose=icon |
The snom color phones also support a purely cosmetic approach to adding a user picture. This method can be utilized to differentiate several different users locally on the phone without sending any identifying photo information in a call. A detailed description of this feature can be found here. A quick description can be found below
In the web interface browse Identity → Photo → Browse, select a picture and press Apply. As soon as the picture is correctly loaded it will be displayed in the idle screen for this specific identity.
Alternatively this can also be done by
In the following example the background of the phone has been changed with a new image by providing the URL to the server where the phone can find the image
This was done by modifying the setting:
<custom_bg_image_url>VALIDVALUE</custom_bg_image_url> |
A reachable valid URL to an image has to be set in this setting. As soon as the setting is changed, the background image will be replaced.
You can either change this setting via provisioning by adding the <custom_bg_image_url> tag with a valid value to your xml file or by changing it manually via WUI → Preferences → Appearance.
If this setting is empty or the URL or the image is wrong, then the default phone background image will be used.
In order to see the background image prior to version 10.1.33.33 the backgrund color has to be set to fully transparent. This has to be done because the background image is located on the layer beneath the standard background color. It can be achieved by either provisioning an alpha value of 0 for the background color:
or by manually editing the alpha value of the setting in the web interface:  |
Starting from firmware version 10.1.33.33, the background color transparency will adopt automatically to the background image shown on the phone. However it will not be fully transparent. In order to achieve full transparency the setting <background_color> still needs to have an alpha value of 0. |
In order for the the background image to be properly displayed it has to be saved in png, jpg, gif, bmp or tga. We strongly suggest to use .png files and optimize them with "optipng" in order to reduce file size and improve performance when drawing.
To find a selection of pictures in the respective format of different phone models...
|
From Firmware Version 10 on, the color phone user interface can be fully modified in regards to Color & Transparency. This allows tuning the user interface for perfect legibility, clarity, color preference and to further adopt e.g. the corporate identity of a company to the phone.
New settings parameters for GUI customisation
To see a list of Settings...
|
You can define the value to each setting by using the web user interface (WUI) (from 10.1.25.0 onwards), or by including the parameters into your auto-provisioning configuration file.
| FW: 10.1.25.0 | FW: 10.1.42.10 |
|---|---|
|
|
New tab Appearance in the phone preferences
By adding the XML tag <InvertColor> to a <MenuItem> with the value of 1, the background of the line is inverted as well as all elements inside the line.
<?xml version="1.0" encoding="UTF-8"?> <IPPhoneMenu speedselect="off"> <MenuItem name="A"> <InvertColor>1</InvertColor> </MenuItem> <MenuItem name="Alice"> </MenuItem> <MenuItem name="Alfred"> </MenuItem> <MenuItem name="Andy"> </MenuItem> <MenuItem name="B"> <InvertColor>1</InvertColor> </MenuItem> <MenuItem name="Bob"> </MenuItem> <MenuItem name="Barney"> </MenuItem> <MenuItem name="Becky"> </MenuItem> </IPPhoneMenu> |
The fonts on all snom phones are freely customizable and can be changed via provisioning. Please be aware that if the currently used TrueType Font or Bitmap Font is replaced with a custom one, certain inconsistencies might occur when Text is rendered, since the user interface is optimized for one specific TrueType font.
In order to replace any font a tar file has to be created containing the new font, named after the of the old font that is going to be replaced
tar -cvf fonts.tar fontfile.ttf |
This tar file then needs to be referenced in your xml file so that it properly loads when the phone restarts.
<?xml version="1.0" encoding="utf-8" ?> <settings> <uploads> <file url="http://192.168.23.54:8080/fonts.tar" type="font" /> </uploads> </settings> |
Any language and its translations can be changed via Provisioning of the specific language files. This method is recommended if you want to make major changes to a lot of translations and apply the specific translations to certain phone models.
A more detailed explanation of this can be found here
Any text on the phone can be customized via settings. Similar to the provisioning of regular settings, the translation keys can be provisioned in the settings and dynamically updated. This method is recommended if you want to optimize certain texts without having to constantly maintain the complete language from version to version. A detailed explanation of this feature can be found here
The Identity relevant information in the Idle / Call screen and for Call Forwarding Targets can be masked by changing the following settings
<user_idle_text idx="INDEX">VALIDVALUE</user_idle_text> <user_idle_number idx="INDEX">VALIDVALUE</user_idle_number> <user_idle_cfwd idx="INDEX">VALIDVALUE</user_idle_cfwd> |
The call screen will display and replace the values from user_idle_text and user_idle_number but not actually utilize these for the call flow. These settings have a purely cosmetic effect and don't affect the SIP Flow in any way. |
Default view
with user_idle_text changed
with user_idle_number changed
with user_idle_cfwd changed
Since every element in the user interface can be customized, it is possible to create complete themes that transform the phone from its original look & feel to a visually new user interface.
Dark Theme
|
Colorful Theme
|
Starting with firmware version 10.1.53.0 there are 4 predefined themes on the phone. You can switch between the themes by changing the setting ui_theme. The themes are named "Light", "Dark", "Colorful" and "Industrial". "Light" is the default theme and corresponds to the old appearance of the phone and the other themes are new. The difference between the themes are their color settings and their icons including the background image.
Theme Light (Default):
Theme Dark:
Theme Colorful:
Theme Industrial:
