Cisco 7906G SIP Configuration Files (for 3rd party PBXs)
During boot the handsets will discover the TFTP server via DHCP option 66 and/or DHCP option 150. For this example I set option 66 of our VoIP VLAN to the local IP address of our TFTP server. All of the configuration files, firmware files and other customisation files reside in the root directory of the TFTP server, in this case it was \TFTPBOOT.
Each handset will require an SEP configuration file. The filename must be SEP000000000000.cnf.xml where the 000000000000 is the MAC address of the Cisco handset.
In the example SEP configuration file, the following values have been set:
sip.provider.com <!-- This is the FQDN of the PBX, it can also be an IP address -->
123.123.123.123 <!-- This is the public IP address of the network the handset resides on, this if for NAT and may not be needed -->
222 <!-- This is the numerical extension number the handset will have, this must exist on the remote PBX first -->
pbx-username <!-- This is the register username for the extension -->
Pa$$w0rd <!-- This is the register password for the extension -->
*55 <!-- This is the direct dial for the PBX's voicemail -->
All other settings can be ignored for the purpose of the inital configuration. You must change every occurance of the above settings throughout the configuration file.
The firmware version that has been tested for these configuration files is SIP11.9-4-2SR1-1S. You can download the firmware files directly from Cisco - you will need to register for a free account. At the time of writing the link for the firmware files is here, however, I have included the firmware files in this repository for reference.
The included dialplan.xml gives some examples available. The dialplan file tells the handset how long to pause before dialling a number once it has been entered.
I have included a ringlist.xml file as an example of how to add new ringtones to the handsets. If you monitor the TFTP server logs when navigating the handset menu and requesting a new background or ringtone, you will see which files the handset requests. This is very useful when setting up the TFTP file structure.
When including ringtone .raw files, it's simplest to include them in the root directory of the TFTP server along with the firmware and configuration files.