For SIP endpoints that are attached to a DPMA-configured Digium phone, the subscribe_to parameter should point to a special hint automatically created by DPMA. This hint is in the format "auto_hint_<peer>," e.g.:
In this case, it is not necessary to create a dialplan hint, as it is automatically created by DPMA.
For non-DPMA-configured endpoints, no "auto_hint" is created, and subscriptions should be a normal SIP URI that is provided by the target system, e.g..:
or, simply to an extension, where the phone will automatically subscribe to the registered server, e.g.:
Also, when DPMA is not used, it is necessary to create a dialplan hint, e.g.:
Users of DPMA with older versions of Asterisk, or chan_sip instead of chan_pjsip, should note that the callcounter sip.conf parameter is necessary.
mandatory, unique identifier for the action, used by blf_item definitions. One id with the reserved name "primary" should be used for each contact, to designate the primary action, that occurs when no other action is matched.
Magic action ids "intercom," "monitor," "sendtovm" and "dial_vm" will result in special icons displayed for the action.
optional, number, e.g. 1234, or URI like sip:host or sip:user@host, to be passed to the phone application and dialed for this action
optional, number to be prepended before dial, where be passed to the phone application and dialed for this action
optional, identifier for an application to which events or functions are sent. The identifier should be either one of the phone default applications (contacts, voicemail, parking, status, queues) or should be the identifier of a user-loaded custom application.
mandatory, pertinent information about the number for the Contacts application, e.g. SIP Extension, Cell; appears to the left of the number or application within the contact's information screen
mandatory, a name for this action, used as its language key within applications, e.g. custom applications; appears to the right, in square brackets, of the number or application within the contact's information screen
Digium's D80 telephone can display pictures for contacts within its Rapid Dial application and Drawer as well as the picture for the phone's local user within the Navigation drawer. Pictures should be in PNG format, 150 pixels wide, and 200 pixels high. To find the local match the D80 will compare its own account_id from its account configuration to the account_ids of its loaded contacts for a match, and display the appropriate picture. The D80 will download and cache contact pictures and will only perform a new download if the URL of the picture changes.
For Contact pictures, the D80 telephone can connect to regular HTTP urls as well as TLSv1.0 encrypted HTTPs URLs. For Contact pictures, the D80 does not support TLSv1.1 or TLSv1.2 HTTPs connections.