Tuesday, April 26, 2016

CENTOS Missing network interface virtual machine move

We had a situation that was in our virtual environment where the network interface disappeared from our centos 6 virtual server.  This happened when we moved the image to a new server, but similar things can happen to users.

Our symptoms were, upon booting, the boot sequence was indicating that the NIC was not found/valid.
When we logged into the console and did an "ifconfig" all it showed was the loopback interface.

Here's what we did to recover the NIC

goto the directory /etc/udev/rules.d/

Delete (or if you prefer, rename) the file 70-persistent-net.rules
Reboot your box.

go back to the directory /etc/udev/rules.d/ and look at the 70-persistent-net.rules file again
" cat 70-persistent-net.rules "

Note both the MAC (hardware) address that should be in this file now, as well as the interface name (more than likely ETH0, but its possible it could be something else)

Goto the directory /etc/sysconfig/network-scripts

Do a directory listing and note the "ifcfg-XXX" files in there.  Assuming there is a file in there that matches the interface name that was in your  70-persistent-net.rules (in our example it is ifcfg-eth0)

Simply edit that file (vi or NANO) and change the HWADDR to be the same as the one in 70-persistent-net.rules

save your changes and reboot.  That should fix the problem.

IF by chance the system is showing a different ifcfg-ethX value than the one in the 70-persistent-net.rules file, make a copy of the original file  “ cp ifcfg-ethORIGINAL ifcfg-ethNEW “ and edit it with the same HWADDR change mentioned above.  Also ensure that the "DEVICE=ETHX" matches the name of both the file you are editing and the ETHX value in 70-persistent-net.rules

Tuesday, April 5, 2016

Upgrade 1100 series phones from UNISTIM to SIP firmware

When an 1100 series Nortel/Avaya phone boots from a fresh factory build, it will need its configuration data to be entered for it to work.  You can manually enter this information, but its so cumbersome I don't even want to explain it.

1100 series phones use TFTP to obtain their configuration files from a TFTP server.
By placing appropriate firmware files and configuration files in this location, we can upgrade the phone to the SIP firmware and get its configuration started.


1.  Download the SIP firmware .BIN file from the Avaya Support website and put it in the TFTP folder you've configured. 
At the time of writing, the SIP version is, so I've successfully tested with that release with Asterisk.

Unless the link gets changed, you can start looking for the latest firmware builds at this link:

2. Create a file 1120e.cfg in your TFTP directory and put in the following lines.
VERSION SIP1120e04.04.26.00.bin
FILENAME SIP1120e04.04.26.00.bin
SERVER_IP x.x.x.x


(*** note: Change X.X.X.X. = IP address of your TFTP server. ***)

3. Save the file.

4. Create a file 1120eSIP.cfg in your TFTP directory and put in the following lines.
VERSION SIP1120e04.04.26.00.bin
FILENAME SIP1120e04.04.26.00.bin
SERVER_IP x.x.x.x


(*** note: Change X.X.X.X. = IP address of your TFTP server. ***)

5. REBOOT Your phone.

The phone should reboot and obtain a base configuration from your TFTP folder.  Once the update is completed, you'll see something like the following on your phone.

Avaya/Nortel 1100 series phone to work with Asterisk

Outlined here is how I got Nortel/Avaya series 1140e/1120e/1160 series phones and also 1230 phones using SIP to work with Asterisk.  And they WORK.  No problems. Hundreds registered, tens of thousands of calls.

I followed Michael McNamara's Link (this guy has forgotten more about Nortel stuff than I will ever know!) to get things running and its well written and should be read.  I'm just another resource trying to save this info.

The asterisk version I used is built on CENTOS 6.7 using IncrediblePBX 13-12.2
UPDATE: I've since deployed it on FreePBX distro's 10.13.66 and Elastix 2.5 as well.

We'll be focusing on the 1120e series of phones for our example, but you can just substitue any 11XX reference with your own phone model (1120/40/60 and 1230)

Also, you need to be aware that this stuff is CASE SENSITIVE. So watch your configuration names and values and file names. Its important.

If you bought an 1140 off ebay, and don't have a licence server, it will still work, but you will be limited on some features.  The one that seemed to jump out at me the most was USB headset wouldn't work.  Mostly everything else does.

High-level for this document
  1. Factory reset the phone
  2. Upgrade Phone to SIP firmware
  3. Create Extension in Asterisk
  4. Create the configuration files for your specific installation
  5. SpeedDial list on your phones


    Monday, April 4, 2016

    Creating a phone in asterisk

    I'm not going to get too deep into this.

    You will need to create a SIP phone in your asterisk box.  I wont explain how to do this via config files in asterisk.  Its just annoying.

    For those of you using FreePBX distro, you will want to create an extension in your PBX and assign it a "secret" (aka Password)

    Once you have done this, save/apply/reload the changes as necessary.

    Pointing your 1100 series phone to a TFTP server

    The 1120e 1140e 1230 phones can be deployed by typing in the information into the phone directly through the keypad (hint - SOME usb keyboards will work on the usb port on the back of the phone) or you can do it through a TFTP server, which is the way I recommend doing it. Especially as this is the only way to apply firmware updates. 

    I use TFTPD64 for windows.  The install is fairly self explanatory, and I used all default settings.  It sets up a default "TFTP" directory and this is the location you would put all the necessary files.

    You will need to provide the phone with the TFTP IP address for it to go to to find the necessary files the phone will be automatically looking for.

    There are two potential ways you can do this.  DHCP server options or manually typing it in.

    OPTION 1 “DHCP Options”

    Careful when using DHCP options in a network. Don't just throw this into a network without you understanding the ramifications.  For example if you have other devices, specifically 1120 or 1140 phones that are functioning on the network that would respond to a DHCP request, changing their existing configuration values and you might unintentionally update and probably break their ability to function.

    DHCP option 66 to be the IP of your TFTP server. This step depends on the DHCP server you are using.  I used a windows server so I had to put in the following:

    In the above example, I've gone into the "SCOPE OPTIONS" of my DHCP server and assigned option 66 "Boot Server Host Name" and put in the IP address of my TFTP server.

    When the phone boots up, it will perform a DHCP request, and option 66 will respond with the TFTP server.  The phone will then take this information and use it to get additional configuration information from the appropriate .conf files.

    Additionally, Option "191" for VLAN.  In my case I use VLAN 200 for voice, so my DHCP scope options were VLAN-A:90.  (yes with the period at the end)

    OPTION 2 "Manually configure the provision address in the phone"
    1. Power up your 
    2. When the phone boots, after the "AVAYA" or "Nortel" text appears, Press "SERVICES" on the phone twice quickly and get into the "Network Configuration" menu. 
    3. If it prompts for a password, you can try the default one of 26567*738.
      If this one will not work for you, a possible work around is a factory reset the phone.
    4. The LCD will show and option AUTO. Press the button under that.
    5. Use the right arrow button and move down to the word "PROVISION"
    6. Select it so that the checkbox disappears. (middle button in the middle of the arrow keys)
    7. Press "CONFIG"
    8. Use the arrow keys to move through the lines to the word PROVISION.
    9. Select that and enter in the IP address of your TFTP server.
      Usually double tapping the "*" key will give you the "." period, or press "1" a couple times to scroll through special characters if that doesn't work.
    10. Press APPLY

    Reboot your phone.  
    Look at your TFTP log file.  If you got things configured properly in either example, you should see SOME sort of activity in your TFTP log, even if you dont have any files in it, you should see some attempts or activity.

    Factory reset 1140 / 1120 phone

    If I buy phones or am having issues I like to factory reset them first.  This doesn't change the firmware version they are on, only the settings that would be entered into make it work with a particular PBX.

    On a Nortel/Avaya 1120e 1140e 1160 or 1230, you can do a factory reset of the configurations on the phone by typing in the pattern.


    You would need to translate the A-F letters to their numeric phone keypad equivelent.  So if your phone MAC is 00AF34FE you would type it as:


    You can type this most anytime during the boot process after you see the little “AVAYA” or “NORTEL” text show after it first powers up. 

    The characters may not necessarily echo to the screen as you type them, but the phone is always monitoring for it.  
    You will know that its successful if, within 10 seconds of pressing ## the phone will either automatically reboot or it will ask you to "Reset to factory". If it doesn't, verify the MAC and repeat the process.