1.
2.
a.
b.
i.
c.
3.
4.
1.
2.
DPMA module for the open source "-digiumphones" branch of Asterisk version 10 will be made available at a later date. The DPMA is not
compatibile with any other open source version of Asterisk.
Certified Asterisk and DigiumPhones Branches
The DPMA is not compatible with mainline releases of Asterisk because of the release policies of open source Asterisk. Per release policy, once a
branch of Asterisk, e.g. 1.4, 1.6.2, 1.8, 10, etc. is created, bugs are fixed, security vulnerabilities are closed, but new features are not added. Over
time, this has proven to be an effective policy at limiting the introduction of regressions and making upgrades between branch versions an easy
process.
Because the Digium Phone module for Asterisk requires new features - APIs, SIP messaging infrastructure, voicemail changes, etc. - that are not
currently available in a mainline version of Asterisk, and because Digium phones will require new changes in the future as additional phone
applications are provided, a new branch was required. For Asterisk 1.8 users, all of the code necessary to support the DPMA, as well as changes
to Asterisk applications, such as voicemail, parking, user presence, etc. is available in the Certified Asterisk releases, beginning with the
asterisk-1.8.11-cert1 release. For more information about Certified Asterisk, please see the overview on the
10 users will be provided in a 10-digiumphones branch of Asterisk that will track the mainline branch of Asterisk with respect to features and
bugfixes, but also support for the DPMA. As with any other branch of Asterisk, both Certified Asterisk and -digiumphones branches are licensed
under the GPLv2 and are made available for download via subversion, as tarballs, and as packages.
Provisioning
Digium Phones may be assigned SIP account configuration a number of different ways:
Option 66 DHCP directive
The phone’s boot menu
Digium Configuration Server (DPMA, manual address)
Fetch Configuration file from URL
HTTP, HTTPs
Manual SIP account entry
The phone’s web-based configuration tool
DPMA, Bonjour / mDNS
When the phone is configured via Option 66 DHCP directive or it's told to manually fetch its configuration from a URL, the phone will first request
a configuration file matching the name <MAC>.cfg, e.g. 0019159bd025.cfg; and, if that file is not found, will then go on to request a configuration
file named 000000000000.cfg.
When the phone is configured to talk to a Digium Configuration server, either manually by plugging in the address of the server or automatically
through mDNS discovery, the phone will communicate with and retrieve its configuration directly from Asterisk via the DPMA.
DPMA Concepts
DPMA uses two internal concepts:
Phones
Lines
A
is a set of configuration parameters that represent the device on your desk. A Phone is abstracted because in most cases, it represents
Phone
an individual user’s configuration, e.g. Bob’s Phone. Bob’s Phone has line keys that are specific to Bob, it has a contacts list that’s specific to Bob,
it has Rapid Dial keys that are specific to Bob.
A
is a key on phone that is mapped to an Asterisk SIP identity ("friend," technically, since that's a better way to go if you want to assign more
Line
than one SIP identity to the same physical device) and labeled in a particular way. Because, in Asterisk, there’s a one-to-one relationship between
physical device and SIP identity, a Line also maps one-to-one to a SIP identity, since it will only appear on one physical device at a time.
DPMA Configuration
Phones and Lines are configured in the res_digium_phone.conf configuration file – normally located at /etc/asterisk/res_digium_phone.conf. The
file contains one reserved section:
[general]
The
section contains settings that are specific to the operation of the DPMA itself.
[general]
Two other section types are available for user configuration, each contains a
definition. The type definition determines the function of the
type
section. The three
are:
types
phone
line
