Upgrade DCP End-points With Ease
In this post “Upgrade DCP End-points With Ease” I have created steps that I normally take whenever upgrading digital end-points such as the 1400, 2400, and the 9400 series phones.
In the summer of 2013 I got sent to deploy a new VoIP solution in Okeechobee FL. For starters the building wiring infrastructure was old and antiquated to deploy a Voice Over IP solution. Most of the IDFs had Category 3 cabling (TIA/EIA CAT3) which is not suitable to run Ethernet 802.3x. Unfortunately this wasn’t taken under consideration in the Site Survey process. It makes you wonder sometimes; who are we sending to conduct site surveys?, or why are we rushing to deploy new solutions without taking the necessary steps?.
After shipping the VoIP phones back, and receiving the new DCP phones, we proceeded with the installation schedule. That humid summer night here in FL, I had two helpers helping me placing phones, and doing some other odd jobs that I needed done. When it came to start connecting phones, I noticed that my test phone wasn’t working earlier that day, prompting me to quickly start upgrading each individual phone.
Here are the 4 steps that I took=
- 1.- Understand the upgrade process
- 2.- Tools and apps
- 3.- Firmware and upgrade files
- 4.- Batch your upgrade
1.- Understanding the upgrade process
As a road service engineer it is hard to do research on the go. But in the same token it is important to take time to do your homework for each particular deployment, that is if you really want to succeed. Understanding the upgrade process might take you some research time. Things to look out for=
Sold Solution. For me, it was easier to make decisions in this project, because I knew the solution and had read some best practices before going out to site.
Do I really need to upgrade?. In some cases you might find yourself not needing to upgrade any of the TN Circuit Packs, Media Modules, nor phones. When the equipment is shipped with the lasted firmware version from your distributor there is no need to upgrade.
What do I need?. Time, is another big factor. Schedule time to upgrade the digital sets. Depending on the file size, each phone might take up to 15 minutes to upgrade, making this process tedious.
2.- Tools and apps
No matter which methods you use to upgrade, you will need tools and applications to help you through the upgrade process. In my case I was using the Communication’s Manager TFTP Utility, therefore a TFTP Server was needed.
Directory – A file directory containing the files is required (this directory could reside in your local service laptop, or a shared folder somewhere in the customer’s network.
TFTP Server – I normally use the Avaya TFTP application. There are a bunch of TFTP Servers for you download. Solarwinds is a free TFTP Server available, just select its name and you will be directed to the download page.
Avaya Support – To get the firmware, you will need to secure log into the http://support.avaya.com website and download the software needed based on your system’s version. Always keep in mind that TN Circuit Packs, and Media Modules release/version when downloading any firmware.
Firewalls – Adding services to your access lists will be recommended to allow communication between the phone, phone system, and the tftp server. Port 69 will be used for the TFTP default port transmission.
Switch ports – Even though Digital Ports are not related directly to Ethernet, its firmware is sent via UDP.
CLAN / Processor Ethernet “PROCR” (S8300) – These are the gateways used to connect to the TFTP Server and allow transmission.
3.- Firmware and upgrade files
For best practices, the phone files should be stored in a specific directory for easy access. To avoid file corruption always check the file size before and after the download.
Before deploying the files, as a best practice upgrade one phone first, then test its features and functionalities.
These are some of the files that can be use to update your digital phones. Click/Select each one to be directed to the support.avaya download portal.
- Application Code: 1400R36.bin (This file is good for both 1408 and 1416)
- Language File: lng_R10_v11_Pack01.bin
- dcpa94xxR12.bin (Phone application) for both 9404 and 9408.
- 94xxlng_v86.bin (Language file)
- Zarlink_CM_IPO_R0_09.bin (Echo canceller file)
4.- Batch your upgrade
No matter how you decide to upgrade the end-points, you can schedule one or multiples at the same time. Here I will walk-through how I was able to update a 2420 from Release 2 to Release 5.
Download the firmware, and assign a home directory.
Configure the TFTP Server’s directory to point to the TFTP home directory. In the case of Solarwinds TFTP Server – navigate to “File/Configure/Storage/TFTP Server Root Directory”. The program is configured to accept and send by default.
It’s not necessary to static address TFTP Server, but I will suggest you do. By doing so, it will make it easier for you to troubleshoot any type of connectivity issues.
Use Communications Manager (CM) SAT Terminal. Run the command “change node-names ip”.
Give it relevant name to the TFTP
Server (something easy to remember), then save by pressing enter.
Configure CM’s TFTP Server options. run the command “change tftp-server”
- Local Node Name’= procr (is using an S8300 Srvr) / CLAN node-name
- TFTP Server Node Name= self explanatory
- TFTP Port= default
- File to retrieve= type the file name (no misspellings)
Schedule the upgrade. For a single a range of DCP station updates. Run the command “change firmware station-download”. Schedule it about 15 minutes ahead, this will give you time to fill out the form without rushing.
To status the process, run the command “status firmware station-download
This is just one way to update DCP Phones. what ways do you normally use to update your digital phones?, and
Please note: I reserve the right to delete comments that are offensive or off-topic.