secondary_server_transport
tcp or udp
The transport type used for registration and calling to/from the secondary server
userid
string, e.g. bob1234
This line's SIP username. Defaults to the line's name
authname
string, e.g. bob1234
SIP authorization name if different than userid. If blank, defaults to userid.
secret
string, e.g. mymagicpassword
The SIP secret this line should used
register
yes / no
Indicates whether or not this line should register
callerid
string
Caller ID field to use for this line
*Example: *
In this example:
The address of the external registration server is otherpbx.mycompany.com
The contact port of the external registration server is 5061
The transport method of the external registration server is TCP
The address of the secondary external registration server is otherpbx2.company.com
The contact port of the secondary registration server is 5061
The transport method of the secondary external registration server is UDP
The SIP username is bob1234
The SIP authname is bob4321
The SIP password (secret) is mymagicalpassword
Registration is enabled
Caller ID is set to "Bob Jones <555-1234>"
Example External Line Configuration.
[bob1234]
type=external_line
server_address=otherpbx.mycompany.com
server_port=5061
transport=tcp
secondary_server_Address=otherpb2.mycompany.com
secondary_server_port=5061
secondary_server_transport=udp
userid=bob1234
authname=bob4321
secret=mymagicalpassword
registration=yes
callerid=Bob Jones <555-1234>
Contacts
Digium Phones provide a Contacts application that integrates speed-dial, device busy-lamp field and user presence. The Contacts application is
related to the Status application in that both are concerned with presence. The Status application is concerned only with setting the local user's
presence. The Contacts application is concerned with the presence status of other users - those to which it's been programmed to subscribe.
Contacts without presence subscriptions may be loaded locally onto the phone by the phone's user. Most deployments of Digium phones will see
the administrator specifying XML lists of contacts to load onto phones. Here, we will discuss the methods to direct the phone to load contacts as
well as the contents of the contacts XML files.
Loading a Contact List
Contacts files that the phone should load are defined in the phone's configuration XMl file and are served up by the DPMA. Contact file are
specified for a phone configuration using the phone configuration parameter:
contact
as noted above. Multiple "contact" lines may be used for each phone configuration.
Rapid Dial Keys
Rapid Dial, or BLF, keys are set using the phone configuration parameter:
blf_contact_group
