Example General Section configuration.
[general]
globalpin=344486
userlist_auth=disabled
config_auth=mac_globalpin
registration_address=10.10.10.10
registration_port=5060
service_name=Go 4 Phones
service_discovery_enabled=yes
firmware_url_prefix=http://10.10.10.10/digium_phones_firmware
firmware_package_directory=/var/www/digium_phones_firmware
file_directory=/var/lib/asterisk/digium_phones
message_context=dpma_message_context
Phone Configuration Options
Phones profiles are configured by defining a context with type option equal to “phone.” A Phone profile can have any number of lines associated
with it. Each line defined in the configuration is reflected as a separate line key on the phone; and, when provisioned, is ordered on the phone
itself as it is in the profile configuration.
The first line key associated with a Phone profile is set internally as the phone’s primary line. The primary line is the only one listed in the User list
on boot up. The primary line is also used to automatically match the phone to voicemail boxes.
The following options are provided for Phone configuration:
Option
Values
Description
mac
A MAC address, e.g.
0123456789ab
Optional. When set, and when the general config_auth option requires MAC, locks a phone
configuration to a device matching this MAC address.
pin
integer; e.g. 10101019
Optional. When set, and when the general config_auth option requires PIN, one must enter
this PIN on the phone before being able to pull the phone's configuration
line
entity defined as line in
res_digium_phone.conf
Maps directly to a sip.conf peer/friend entry. More than one line may be defined for a phone
configuration. The first line entry defined is adopted as the phone's primary line.
external_line
entity defined as
external_line in
res_digium_phone.conf
Maps directly to an external_line defined in this configuration file. External line are lines not
defined by SIP peers in sip.conf and generally do not register to this instance of Asterisk. If
an external line is defined as the primary extension for a phone, many of the advanced phone
application features will be disabled
config_file
file, e.g.
mycustomconfig.xml
The phone module automatically generates a configuration file for each phone based on the
lines assigned to it; but, it is possible to supply a custom configuration file instead. Using this
option will direct the DPMA to serve up the specified file, as found in the file_directory defined
directory, to the phone. For information about custom configuration files, see
.
[\#xmlconfig|]
Note that using a custom configuration file, as opposed to the provisioning generated by the
DPMA, precludes the phone's use of DPMA-specific applications, e.g. voicemail, parking,
user status, etc. This option allows users to make use of the DPMA's mDNS provisioning
capabilities, providing a simpler alternative to HTTP and Option 66 provisioning, but sacrifices
the DPMA-specific features.
full_name
string, e.g. Bob
Johnson
The full name of the person who will be using this phone, and what will appear in the user list
that the phone pulls
contact
file, e.g. contacts.xml
An xml file in the file_directory containing a list of contacts to serve to the phone. Multiple
contact options can exist in a single phone configuration.
blf_contact_group
string, a group from
contacts
Every contacts xml file will have at least one group defined in it. This setting controls which
loaded group the phone should subscribe to for its Rapid Dial (BLF) keys.
timezone
Timezone String, e.g.
America/Chicago
Sets the timezone used for the clock on this phone.
ntp_server
hostname, IP address,
e.g.
ntp.mycompany.com
Defines the NTP server to which phones will synchronize themselves
ntp_resync
seconds as integer,
e.g. 86400
Defines the interval between NTP synchronization
