Posts tagged VOIP

Asterisk Now with Avaya IP Phones

0
January 15, 2012
by Michael McNamara in ,

There’s been a lot of discussion lately around connecting Avaya (legacy Nortel) IP phones with third-party SIP capable call servers. I’ve personally toyed with Asterisk on a number of occasions and have always been impressed so I recently setup an Asterisk Now installation (AsteriskNOW-1.7.1-i386.iso) on a CentOS 6.2 KVM host so I could re-test the interoperability between the latest version of Asterisk (v1.6.2.20) and the 1100 and 1200 series IP phones from Avaya running SIP v4.0 and SIP v4.3 respectively.

The installation was pretty straight forward, however, there were a few small issues that I had to deal with. Initially I was unable to connect to the server and found that the firewall was enabled, so I had to disable the firewall with the following commands, service iptables stop, chkconfig iptables off. I was also getting a weird error in the FreePBX gui when I tried to apply the configuration;

exit: 126
sh: /var/lib/asterisk/bin/retrieve_conf: Permission denied

…this turned out to be an issue with SELINUX, so I had to edit /etc/selinux/config and disable SELINUX (a reboot is required for the change to take effect). Once I did those few steps I was ready to create some extensions so I created 1001 and 1002 and set their password (secret) to ‘abc123′.

The Avaya (legacy Nortel) IP phones can be provisioned from a TFTP server so I installed a TFTP server on my Asterisk server using yum install tftp-server. Then I enabled the TFTP server with chkconfig tftp on and finally I had to restart xinetd with service xinetd restart. I placed the files I needed in the /tftpboot directory including 1220SIP.cfg, 1120eSIP.cfg and users.dat (these filenames are case sensitive on a Linux server – if you use a Windows server such as TFTPD32 then the case is not an issue). I configured my local DHCP server to offer DHCP option 66 (TFTP Server) and I was off and running. The 1220 and 1120e both booted, download the provisioning files from the TFTP server, and connected to the Asterisk server. I entered the username and passwords and I was logged in and running in seconds placing calls between the two handsets.

I had to refer to my original post on the forums on what settings I needed to disable the extended license;

http://forums.networkinfrastructure.info/nortel-ip-telephony/disabling-features-from-extended-feature-set-on-ip-deskphone/

Here’s what the configuration files on the TFTP server looked liked, the 1220SIP.cfg file contained the following lines;

[FW]
DOWNLOAD_MODE AUTO
VERSION SIP12x004.03.09.00
FILENAME SIP12x004.03.09.00.bin
PROTOCOL TFTP

[DEVICE_CONFIG]
DOWNLOAD_MODE FORCED
VERSION 000200
FILENAME users.dat

[DIALING_PLAN]

The 1120eSIP.cfg file contained the following lines;

[FW]
DOWNLOAD_MODE AUTO
VERSION SIP1120e04.00.04.00
FILENAME SIP1120e04.00.04.00.bin
PROTOCOL TFTP

[DEVICE_CONFIG]
DOWNLOAD_MODE FORCED
VERSION 000200
FILENAME users.dat

[DIALING_PLAN]

The users.dat file contained the following lines;

DNS_DOMAIN local
SIP_DOMAIN1 asterisk.local
SERVER_IP1_1 192.168.1.10
SERVER_PORT1_1 5060
SERVER_RETRIES1 3

VMAIL 5000
VMAIL_DELAY 300

DEF_LANG English
DEF_AUDIO_QUALITY High

ADMIN_PASSWORD 26567*738
SSH YES
SSHID admin
SSHPWD admin
# Settings to disable extended license
MAX_LOGINS 1
USB_HEADSET LOCK
EXP_MODULE_ENABLE NO
ENABLE_SERVICE_PACKAGE NO
IM_MODE DISABLED
AVAYA_AUTOMATIC_QoS NO
VQMON_PUBLISH NO
SIP_TLS_PORT 0
ENABLE_BT NO

I did have to re-configured the 1220 to AllAut before it would honor the settings in the TFTP provisioning file.

Cheers!

Avaya 1100 Series IP Phone Upgrade to SIP

108
January 17, 2011
by Michael McNamara in , ,

Over the past weekend I set out to setup Asterisk, an open source communication server, to test some of the issues reported in a thread over on the discussion forums. I had an Avaya 1120e and 1165e IP phone available to test with, however, both phones were running the UNIStim software for the Avaya Communications Server 1000. I needed to upgrade them to support SIP.

About a year ago I posted how I setup Asterisk to work with an i2002 IP phone utilizing the UNIStim channel driver. This time around I was looking to utilize the standard SIP channel driver with the 1120e and 1165e.

SIP Software

You’ll need to download the SIP software from the Avaya Support website. You should be able to retreive the SIP software from this link without needing to log into Avaya’s website. You should download the software for the appropriate model you’ll be working with. In my case I downloaded the following two files;

  • SIP1120e04.00.04.00.bin
  • SIP1165e04.00.04.00.bin

TFTP Server

You’ll need a TFTP server to host the files that the IP phone will download. You can use any TFTP server you already have on the network. If you don’t have a TFTP server you can use TFTPD32 from Philippe Jounin on any Microsoft Windows XP, Vista or Windows 7 personal computer. I download the zip and exploded the files to D:\Temp.

TFTP Files

With the TFTPD32 software in D:\Temp I then copied the two firmware images (SIP1120e04.00.04.00.bin and SIP1165e04.00.04.00.bin) to the same directory. At this point I needed to create some configuration (provisioning) files which the IP phones would download. The first file 1120e.cfg will be used for the 1120e IP phone;

[FW]
DOWNLOAD_MODE AUTO
VERSION SIP1120e04.00.04.00
FILENAME SIP1120e04.00.04.00.bin
PROTOCOL TFTP
SERVER_IP 192.168.1.3
SECURITY_MODE 0

I also created a file 1165e.cfg that would be used for the 1165e IP phone;

[FW]
DOWNLOAD_MODE AUTO
VERSION SIP1165e04.00.04.00
FILENAME SIP1165e04.00.04.00.bin
PROTOCOL TFTP
SERVER_IP 192.168.1.6
SECURITY_MODE 0

You’ll need to substitute the IP address above (192.168.1.6) with the IP address of the personal computer that will be running TFTPD32. Now that you have all the files you’ll need for the upgrade, you can start the TFTPD32 executable. You should see a window similar to the figure to the right.

Upgrade

You need to make sure that the IP phones know which TFTP server to use. This can be accomplished via DHCP option 66 or it can be set in the device configuration on the actual IP phone itself. I was utilizing the DHCP server built into my Verizon FiOS router so I had to set the TFTP server manually via the IP phone configuration.

When you are ready just reboot the phone. As the IP phone boots up it will request an IP address from the DHCP server and it will check the TFTP serve. The IP phone should download the 1120e.cfg (or 1140e.cfg of 1165e.cfg depending on the model). Once the phone realizes there is a software update it will boot into BOOTPC mode in order to perform the actual upgrade.

You should see something similar to the following;

[FW] reading...
SIP1120e04.00.04.00.bin
VERSION SIP1120e04.00.04.00

Shortly followed by;

[FW] writing...
SIP1120e04.00.04.00.bin
VERSION SIP1120e04.00.04.00

Once the upgrade is complete the IP phone should reboot. I will warn you that you should I’ve seen some odd behavior between the settings on the IP phone and the settings that should be applied via the provisioning files. There have been a few cases where I needed to reconfigure the IP phone even though it appeared to be configured properly. In the few cases I’ve experienced reconfiguring the IP phone solved the problem.

Once the 1100 series IP phone is upgraded to SIP it will start looking for a new configuration file, 1120eSIP.cfg (or 1140eSIP.cfg or 1165eSIP.cfg depending on your model). Here’s a quick example;

[FW]
DOWNLOAD_MODE AUTO
VERSION SIP1120e04.00.04.00
FILENAME SIP1120e04.00.04.00.bin
PROTOCOL TFTP
#SERVER_IP 192.168.1.3
#SECURITY_MODE 0

[DEVICE_CONFIG]
DOWNLOAD_MODE FORCED
VERSION 000002
FILENAME users.dat

[DIALING_PLAN]
DOWNLOAD_MODE FORCED
VERSION 000002
FILENAME dialplan.txt

Here’s a copy of the users.dat file which gets called from the 1120eSIP.cfg file above;

DNS_DOMAIN asterisk.home
SIP_DOMAIN1 asterisk.home
SERVER_IP1_1 192.168.1.6
SERVER_PORT1_1 5060
SERVER_RETRIES1 3
DEF_USER2 ASTERISK
VMAIL 5000
VMAIL_DELAY 300
DEF_LANG English
DEF_AUDIO_QUALITY High
ENABLE_LLDP YES
ADMIN_PASSWORD 26567*738
ADMIN_PASSWORD_EXPIRY 0
# Settings to disable extended license
MAX_LOGINS 1
USB_HEADSET LOCK
EXP_MODULE_ENABLE NO
ENABLE_SERVICE_PACKAGE NO
IM_MODE DISABLED
AVAYA_AUTOMATIC_QoS NO
VQMON_PUBLISH NO
SIP_TLS_PORT 0
ENABLE_BT NO
# Enable SSH
SSH YES
SSHID admin
SSHPWD admin

The settings above disable any advanced features and allow the IP phone to run a basic SIP configuration.

Cheers!

SIP Software Release 3.2 for IP Deskphones

11
September 8, 2010
by Michael McNamara in

Avaya has released SIP software release 3.2 for their 1100 and 1200 series IP deskphones. This release adds support for the 1120e, 1140e, 1165e, 1220, and 1230 model IP deskphones.

Here are some of the enhancements made in the new software release;

  • Improved Licensing
  • SIP Support for 1220,1230 and 1165E IP Deskphones
  • Shared Call Appearances – CS1000
  • IPv6 Support
  • SRTP Media Security
  • TLS Signaling Security
  • Certificate-based Authentication
  • Enhanced Screensavers
  • Background images
  • Support for Avaya Aura™ Communication Manager / Session Manager

I was having a discussion with “Mike” in the comments section of any earlier post entitled, SIP Software Release 3.0 for IP Deskphones, in which he pointed out some of the issues with the new licensing model. Well it looks like Avaya was paying attention to that thread and made some changes to the licensing that should satisfy the majority of users. (I’m just going to quote directly from the readme.)

Improved Licensing

Licensing was introduced in the SIP 3.0 release. With SIP 3.2, the following changes are made to the licensing mechanism:

  • The Standard feature set is now available on all desksets without a token. This provides a basic set of SIP features conforming to RFC 3261 (SIPPING 19) at no additional cost.
  • Now, when the phone is registered to a recognized Avaya call server (Avaya AuraTM, AS 5300, CS1000 or CS2100), the Extended feature set is available as well without a token.
  • The Advanced feature set is reserved for Federal and DoD features on the AS 5300 call server only
  • The feature packages have been re-organized
    • Wideband is part of Standard feature set
    • IPv6 and Broadworks SCA are part of Extended feature set
    • Security is now part of the Extended feature set

If you connect your IP deskphone to a Avaya Call Server (Avaya AuraTM, AS 5300, CS1000 or CS2100), you’ll get all the standard features you would get with the UNIStim firmware. The licensing really only comes into play if you decide to connect your Avaya IP deskphone to a third party call server or SIP provider.

Please make sure to review the product bulletin and the readme for all the details.

Cheers!

Go to Top