A-Phone Configuration via Config Files
During the initial boot process the A-phone will: (1) Attempt to retrieve its IP address from a DHCP server , (2) Attempt to set its VLAN ID based on learned VLAN from LLDP-MED , (3) Present the User with a language selection screen and (4) Attempt to retrieve its configuration as directed by DHCP Option 66.
An example DHCP daemon configuration specifying option 66 would look like the example below:
ddns-update-style none;
option domain-name "example.com";
option domain-name-servers 192.168.0.1;
default-lease-time 600;
max-lease-time 7200;
authoritative;
log-facility local7;
option boot-server code 66 = string;
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.10 192.168.0.255;
option domain-name-servers 192.168.0.1;
option domain-name "example.com";
option routers 192.168.0.1;
option broadcast-address 192.168.0.255;
default-lease-time 600;
max-lease-time 600;
option boot-server "http://server.example.com/phoneprov/";
}
That directive, option boot-server, tells phones to contact the server http://server.example.com/proneprov/ for their configuration files and it w ill attempt to retrieve two files, a common configuration file, that contains settings that can apply to more than one phone, and a device configuration file, that contains settings that apply to only one phone, if the phone fails to retrieve the files, it will make 4 more attempts, and then stop. The successful retrieval of files will stop the process, as the phone will load the files and startup using the specified settings.
Common configuration file
Each phone model has a unique common configuration file, listed below.
- A20: f0A20hw1.100.cfg
- A22: f0A22hw1.100.cfg
- A25: f0A25hw1.100.cfg
- A30: A0V0A3000000.cfg
As mention before, the common file must contain parameters are common across all phones, the idea of this files is that you don't have to repeat the same information on multiple device configuration files and therefore any edit that apply to all phones can be done on a single file. Please note that the common configuration file follows the extructure than device configuration file, you just need to remove the configuration modules that are unique to each phone. See below (device configuration file) for examples.
Please note that if you see the phone making multiple GET requests for a file, it is because the phone was not able to successfully retrieve or parse the first file. Also If the configuration file does not include a Version identifier in its first line, the phone will not parse it successfully.
Device configuration file
The device configuration file will be the MAC address of the phone with a .cfg extension at the end. The Phone will request the common file first and then the device configuration file second. As mentioned before you want to to populate the common file with settings that all phones will utilize while populating the device configuration file with device specific settings such as the phones pjsip account credentials.
A20, A22, and A25 TXT Configuration
A30 TXT Configuration
For a basic PJSIP line configuration to be added to your device configuration file you should review the SIP CONFIG MODULE Elements within the text configuration file at the link above.
