Cisco Phone Support
Description
This module installs the firmware for Cisco IP Phones
Release notes
Version 4.2.0 - General deployment
- Feature: Includes support for Cisco 7942G phone. (M4678)
- Limitation: Install only if you want support for the Cisco 7942G phone. This version has not been tested extensively.
- Dependency:
- SMP version >= v1.4
- SOP API module version >= v2.10
Version 4.1.0 - General deployment
- Feature: Includes support for Cisco 7941G phone. Uses SIP firmware 8.5.3 for this specific phone. (M0004537)
- Dependency:
- SMP version >= v1.4
- SOP API module version >= v2.10
Version 4.0.0 - General deployment
- Includes old firmware files. This is the minimal required version when using TFTP 2.0 or higher
- Dependency:
- SMP version >= v1.4
- SOP API module version >= v2.10
Version 3.1.0 - General deployment
- Improved migration path from SCCP to SIP firmware for Cisco 7940/7960 models.
- Dependency:
- SMP version >= v1.4
- SOP API module version >= v2.10
Version 3.0.0 - General deployment
- Potential update impact level 3
: in the event this update contains a bug, it might have critical impact.
Given the complexity of the update, it is advised to contact ESCAUX support before applying this update.
- The firmware for the 7940/7960 model has been upgraded to P0S3-08-6-00 (8.6).
- The problem of 'leaking' sound through the handsfree speaker on a 7940/7960 model is resolved.
- Dialplan for the 7940/7960 model has been changed from Belgian dialplan based on internal extensions with 3 digits to a generic dialplan
- Improved time synchronization of the 7940/7960 model to the PBX by using unicast NTP instead of directedbroadcast.
- The external directory of the 7940/7960 model now respects the visibility flag of an extension
- Integrated browser improvements for the 7940/7960 model
- Various small fixes for use on stable-4 SMP release and use of the new firmware
- The supervision overview now limits the number of displayed extensions so that the phone browser limit is not reached.
- Dependency:
- SMP version >= v1.4
- SOP API module version >= v2.10
Version 2.1.0 - General deployment
- generates SIPDefault.cnf (must be reinstalled after tftp module)
- fix the DST problem in SIPDefault.cnf (last Sun of March)
Version 2.0.0 - General deployment
- generates SIPDefault.cnf (must be reinstalled after tftp module)
Version 1.2.0 - General deployment
- This contains xml applications (status, supervise). Note that status used to be part of API module.
- You need to have at least v2.0 of the cisco phone resource and point the services url to "http://[ip address]/cisco/MainMenu.php"
- This generates SIPDefault.cnf. Don't reinstall TFTP afterwards.
Version 1.0.0 - General deployment
- new xml applications (status, supervise). Requires API module.
- cisco phone resource version 2 or higher required and point the services url to "http://[ip address]/cisco/MainMenu.php"
Module configuration interface
create_resource_form: .:/usr/share/escaux/glue/lib:/usr/share/escaux/glue/bin/gen_wiki_documentation/src/lib:/usr/share/escaux/glue/bin/gen_wiki_documentation/src/lib/
Requirements
- SMP version 4 or higher
- SOP API 2.10 or higher
Upgrading Cisco 7940/7960 phones
Escaux does not recommend upgrading to a module version containing a new firmware unless for a valid reason.
When upgrading to a new firmware, be very cautious. We have extensively tested the firmware upgrade from version P0S3-06-3-00 (6.3) to P0S3-08-6-00 (8.6) and P0S3-07-5-00 (7.5) to P0S3-08-6-00 (8.6), other upgrade paths might not be possible. A failed firmware upgrade will render the phone unusable.
To check the current firmware on the phone

Navigate to: Settings > Status > Firmware Versions > Application Load ID
After the installation of a new firmware, the phone(s) should be restarted. A cautious approach would be to test the upgrade procedure on 1 phone, checking if the firmware upgrade is successful and if so, continue with the other phone(s).
Autoprovisioning
Please consult the
Customer DHCP Server configuration guide for more information about the DHCP options necessary for autoprovisioning of this type of device.