Configuration File Guide; Guidelines For The Mac-Specific Configuration File; Securing Configuration Files With Aes Encryption - Alcatel Temporis IP150 Administration And Provisioning Manual

audio.x.rtcp_xr.enable
"file" Module: Imported File Settings on page 230.

Configuration File Guide

All configuration settings are initially stored in a configuration template file. Copy,
rename, and edit the template file to create a general configuration file and the MAC-
specific configuration files you will need. You can store the general configuration file and
the MAC-specific files on your provisioning server.
Do not modify the header line that includes the model and firmware version.
Note empty parameters will not overwrite values stored in the phone. To delete the
content of a parameter use the value %NULL.
To save yourself time and effort, consider which settings will be common to all (or the
majority of) phones. Such settings might include Call settings, language, and
programmable feature key settings. You can then edit those settings in the configuration
template and save it as the general configuration file. The remaining settings will make
up the MAC-specific configuration file, which you will have to copy and edit for each
phone.

Guidelines for the MAC-Specific Configuration File

The phone downloads the MAC-specific configuration file after the Main configuration file.
You must create a unit-specific configuration file for each phone in your system. The file
name must contain the phone's MAC address, which is printed on a label on the back of
the phone, or available on the MENU > Status > Product Info screen. For example, an
IP2015 DECT base with the MAC address of 74:65:D1:16:12:34 would download the
IP2015_7465D1161234.cfg file.
The MAC-specific configuration file contains settings intended exclusively for that phone.
Such settings will include SIP account settings such as display name, user ID,
authentication ID, and voicemail mailbox ID.

Securing Configuration Files with AES Encryption

You can encrypt your configuration files to prevent unauthorized users modifying the
configuration files. The system encrypts files using the AES 256 algorithm. After
encrypting a file and placing it on your provisioning server, you can enable the phone to
decrypt the file after fetching it from the server.
To decrypt a configuration file you will need a 16-character AES key that you specified
when you encrypted the file. The key (or passphrase) is limited to 16 characters and
supports special characters ~^`%!&-_+=|.@*:;,?()[]{}<>/\# as well as spaces.
Note: The encryption of configuration files is supported only for the auto provisioning
process. Encrypt files only if you intend to store them on a provisioning server. Do not
encrypt files that you intend to manually import to the phone. You cannot enable
decryption for manually imported configuration files.
Business IP Range Administration and Provisioning Guide
Enables or disables
reporting of RTCP
XR via SIP to a
collector server.
RTP Control
Protocol Extended
Reports (RTCP XR)
are used for voice
quality assessment
and diagnostics.
Group C 0:disabled
1:enabled
ed 2.2 197/247
0