I tested the process Friday and it worked as advertised. Here’s how I set everything up… please bare in mind there are many many ways to set this up so the following example is just how I decided to set everything up.

Avaya Ethernet Routing Switch 5520s

I configured the edge/closet Avaya Ethernet Routing Switch 5520s running software release 6.2.4 exactly as I’ve previously documented in this blog post. We’ll be using ADAC/LLDP-MED to assign the IP Phones a voice VLAN and to set the proper QoS tags.

DHCP – Infoblox

With that done I turned my efforts toward DHCP. I created a DHCP range in the voice VLAN with two special settings. I created a filter on the IP range to check for the DHCP vendor option “Nortel-i2004-A”. This will help make sure that only IP phones are provided an IP address from this DHCP range. Next I added DHCP option 244 with the following value,

Nortel-i2004-B,prov=http://10.1.20.1/avaya/sitea;

That’s all I did for the DHCP component, the magic comes in the next step.

HTTP/TFTP Server

In my example I used a CentOS Linux server at 10.1.20.1 which had Apache running with a directory structure of /var/www/html/avaya/sitea. In that folder I had the following files; system.prv and sitea.prv (this file was actually blank). You can deploy the provisioning files via HTTP or TFTP. You can utilize Microsoft’s IIS or whichever web server you’re more comfortable with. Please refer to the references listed at the end of this document for additional steps to get IIS to recognize the .prv files

Here’s what I put in the system.prv file;

file=zdt;
zone=sitea;
s1ip=10.1.2.40;
p1=4100;
a1=1;
r1=10;
s2ip=10.1.2.40;
p2=4100;
a2=1;
r2=10;
vq=y;
vcp=3;
vmp=4;
vlanf=y;
pc=y;
pcs=a;
pcd=a;
dq=n;
lldp=y;
stickiness=y;
cachedip=n;
igarp=n;

I chose to configure the Avaya IP Phones around a geographic basis. Within each location all the IP phones are configured identically but the settings can vary from location to location depending on the model and on the actual CS1000E for that site. I chose to break them down using different directories and then set DHCP option 244 to the appropriate directory for that site. In one voice VLAN the DHCP server might return “Nortel-i2004-B,prov=http://10.1.20.1/avaya/sitea;” but in another voice VLAN the server might return “Nortel-i2004-B,prov=http://10.1.20.1/avaya/siteb;” Utilizing the different directories allows me an easy way to control the different settings per geographic location. It also makes troubleshooting much easier and straightforward.

Testing

With everything setup I preceded to test my configuration. I unboxed a new Avaya 1120e IP phone and connected it to Avaya Ethernet Routing Switch 5520. The IP phone powered up and appeared to pull a DHCP address from the voice VLAN – I believe the factory configuration now has LLDP-MED enabled by default, that’s the only way the Avaya IP phone would have gotten a DHCP address from the voice VLAN. I purposely didn’t create any DHCP ranges in the data VLAN just to see how the Avaya IP phone would react. With an IP address the IP phone read the DHCP option 224 and proceed to download system.prv, sitea.prv and 00AABBCCDDEE.prv (the MAC address of the actual IP phone). After reading the provisioning files the IP phone rebooted itself and eventually came back up to a NODE and TN prompt which was expected. Once the technician entered the NODE and TN the IP phone upgraded itself to the version of software that we had loaded on the CS1000E. It rebooted again and came right up without any additional intervention.

You can eliminate technician needing to enter the NODE and TN information by creating REG entries with the MAC address of the IP phone and the NODE and TN information in the provisioning files – you can find additional information regarding the REG entries in the references below. Since this is a greenfield installation I thought it would be more work to actual document the MAC address of each IP phone than it would be if the technicians just went cube to cube configuring the proper NODE and TN information for each user.

Cheers!

References;

Avaya IP Phone Fundamentals for Communication Server 1000
Avaya IP Telephony Deployment Technical Configuration Guide

• 0621C8A for the 2007 IP deskphone
• 0623C8A, 0624C8A, 0625C8A, 0627C8A, 0626C8A for the 1110, 1120E, 1140E, 1150E and 1165E IP deskphones
• 062AC8A for the 1200 series IP deskphones

This release of firmware adds support for the following features;

• Support for wideband (G.722) codecs on 1120E, 1140E, 1150E, 1165E, 1220, and 1230 IP Deskphones.
• Support for Avaya Notification Solution (ANS) and Avaya Push API which provides the ability to push text, graphics, and audio messages to 1100 Series, 1200 Series and the 2007 IP Deskphones.
• Support for a Wireless Markup Language (WML) browser for 1140E, 1150E, and 1165E IP Deskphones.

Product Advisement for UNIStim 5.0 related to Zero Touch Provisioning:

For customers who have pre-configured the REG entries (which includes the MAC address, the TN, and Node) within the provisioning file to enable Zero Touch for the IP Deskphones, be advised that a problem can occur related to parsing of the REG entry that may result in the IP Deskphones not coming up as expected, and instead continuing to reboot when UNIStim 5.0 is loaded onto the units. The issue will impact IP Deskphones that have been pre-configured for Zero Touch and where the REG lines still exist in the REG entry. This is a known issue that will impact IP Deskphones that have a matching MAC address already pre-configured in the REG entry. This issue will be fully addressed in the upcoming UNIStim 5.1 maintenance release expected in March 2011, and customers may want to delay updating IP Deskphones and Call Servers until that time due to this issue.

In the interim, to avoid this issue the following workaround is recommended: Before loading UNIStim 5.0 onto the IP Deskphones, customers are advised to add a comma before the semi-colon of the REG entry. If UNIStim 5.0 is already loaded, and the issue exists (where the phones continue to reboot instead of coming up), the customer can then add a comma as specified above and the IP Deskphones will come up.

Example: reg= 0021e1ff59cb cs1k s1 3380 096 00 00 18,;

I also recently had a discussion with another telephony expert around the issues of running a PC at 100Mbps (connected to the IP phone) when the 1100 series IP phone is connected to the network via 1Gbps or vice-versa. Here’s the relevant blurb from the release notes that details the problem.

Throughput may be slow for large file transfers on conversions from GigE to 100Mbit (applies to the 1120E, 1140E, 1150E and 1165E IP Deskphones)

In networks in which a PC is connected to the IP Deskphone’s PC port and the PC’s NIC speed is 100Mbit but the network speed is at GigE, large file transfers to the PC can take quite a long time. This is an issue with large file transfers only. Due to the speed mismatch between the phone’s two ports the buffers in the phone can overflow resulting in retransmissions. Although the IP Deskphones support Ethernet flow control (802.3x), the support is only implemented on the phone’s PC port, not on the phone’s network port. Ethernet flow control is a mechanism were the IP Deskphone can request a brief “pause” from the transmitting Ethernet device if the IP Deskphone buffers are about to overflow.
Ethernet flow control cannot be implemented on the phone’s network port, since it impacts the phone’s voice quality. As a result, in environments were the network is GigE but the PC NIC is only 100Mbit, large file transfers from the network to the PC can take quite a long time. On the other hand, since Ethernet flow control is implemented on the phone’s PC port, in environments were the PC NIC is GigE but the network is only 100Mbits, large file transfers should be well managed by the phone’s Ethernet flow control mechanism.

You can find the release notes on Avaya’s website along with the actual firmware/software for the IP phones.

Cheers!

Thankfully Avaya has done something that I truly applaud them for, something that Nortel always had issues with either allowing or executing (not completely sure which it was). What am I talking about you ask? Avaya allows Google to index their support website with all those juicy technical configuration guides. You only need to ask Google to show you the light;

http://www.google.com/search?q=technical%20configuration%20guide%20site%3Asupport.avaya.com&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a&source=hp&channel=np

You can either enter the following query or you can click on the link above;

technical configuration guide site:support.avaya.com

So while Greg over at Etherealmind is complaining about Cisco’s website I’ve found my way around Avaya’s website thanks in no small part to Google. I’m not sure why Greg doesn’t just use Google himself?

Cheers!

If time allows I hope to post an update in the very near future covering the new Nortel-i2004-B option string. While working with the SIP 4.0 software release in the past few articles I did learn that the Avaya SIP IP phones can utilize a new DHCP vendor class, Nortel-SIP-Phone-A which can allow you a little flexibility when configuring them via DHCP and TFTP.

In the same file below I setup four DHCP scopes; one for 2111/2212/6020/6040 wireless handsets, one for i2002/i2004/1100/1200 series IP phones, one for 1100/1200 series IP phones running SIP and one for all other devices (laptops, desktops, etc). Just a quick note about the example below, you’ll notice that I have no pools in the 192.168.1.0/24 network. All the pools are in the 192.168.25.0/24 network.

#
# DHCP Server Configuration file.
#   see /usr/share/doc/dhcp*/dhcpd.conf.sample
#
# Sample dhcpd.conf file for Avaya (legacy Nortel) IP Phones
#
# Notes: example dhcpd.conf file to illustrate how to configure Avaya
# IP Phones with specific DHCP options for 2000/1100/1200 series IP
# Phones and the 2200/6100 series Wireless IP Phones.
#
# *** WARNING *** WARNING *** WARNING *** WARNING ** WARNING ***
#
# This is just an sample file with specific IP information. You'll
# need to customize this file to your specific IP address scheme
# before you can use it in your environment.
#
# *** WARNING *** WARNING *** WARNING *** WARNING ** WARNING ***
#

ddns-update-style none;
not authoritative;

option nortel-callserver code 128 = string;
option nortel-2245 code 151 = ip-address;
option tftp-server-name "192.168.1.20";

# Vendor Class for i2002/i2004/1120e/1140e/1150e Internet Telephones
class "Nortel-i2004-A" {
  match if substring (option vendor-class-identifier, 0, 14) = "Nortel-i2004-A";
    option nortel-callserver "Nortel-i2004-A,192.168.200.2:4100,1,5;192.168.200.2:4100,1,5.";
    option vendor-class-identifier "Nortel-i2004-A";
}

# Vendor Class for 2210/2211 Wireless Phones
class "Nortel-221x-A" {
  match if substring(option vendor-class-identifier, 0, 13) = "Nortel-221x-A";
    option nortel-callserver "Nortel-i2004-A,192.168.200.2:4100,1,5:192.168.200.2:4100,1,5.";
    option nortel-2245 192.168.99.10;
    option vendor-class-identifier "Nortel-221x-A";
}

# Vendor Class for Avaya 1100/1200 IP SIP Phones (SIP firmware loaded)
class "Nortel-SIP-Phone-A" {
  match if substring(option vendor-class-identifier, 0, 18) = "Nortel-SIP-Phone-A";
    option vendor-class-identifier "Nortel-SIP-Phone-A";
}

# Network Definition
shared-network "mynetwork" {
   subnet 192.168.1.0 netmask 255.255.255.0 {
   option subnet-mask 255.255.255.0;
   option routers 192.168.1.1;
   option domain-name "home";
   option domain-name-servers 192.168.0.1;
   next-server 192.168.1.20;
   default-lease-time 28800;
   max-lease-time 86400;
   }
}

# Network Definition 192.168.25.0/24
shared-network "192-168-25-0" {
   subnet 192.168.25.0 netmask 255.255.255.0 {
   option subnet-mask 255.255.255.0;
   option routers 192.168.25.1;
   option domain-name "home";
   option domain-name-servers 192.168.1.1;
   next-server 192.168.1.20;
   default-lease-time 28800;
   max-lease-time 86400;

   # IP Address Pool for generic devices
   pool {
      range 192.168.25.50 192.168.25.100;
      deny members of "Nortel-i2004-A";
      deny members of "Nortel-221x-A";
      deny members of "Nortel-SIP-Phone-A";
   }

   # IP Address Pool for i2002/i2004/1120e/1140e/1150e
   pool {
      range 192.168.25.150 192.168.25.175;
      allow members of "Nortel-i2004-A";
      deny members of "Nortel-221x-A";
      deny members of "Nortel-SIP-Phone-A";
   }

   # IP Address Pool for 2210/2211
   pool {
      range 192.168.25.176 192.168.25.199;
      allow members of "Nortel-221x-A";
      deny members of "Nortel-i2004-A";
      deny members of "Nortel-SIP-Phone-A";
      }

   # IP Address Pool for Avaya 1100/1200 IP SIP Phones
   pool {
      range 192.168.25.200 192.168.25.224;
      allow members of "Nortel-SIP-Phone-A";
      deny members of "Nortel-i2004-A";
      deny members of "Nortel-221x-A";
      }

 }
}

Cheers!

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!

Several enhancements have been included in SIP Release 3.0 for the 1100 series phones including User Interface and Preferences enhancements, Multi-user Login, Emergency Services support, USB device support, Wide-band Codec, Provisioning and Licensing.

The SIP software Release 3.0 for IP Deskphones also continues to improve the overall quality of the IP Deskphone software through the delivery of ongoing resolution of CRs. Numerous quality improvements have been delivered and 9 customer cases have been closed in SIP 3.0.

I’ve only performed very limited SIP testing with the 1120E, 1140E, and 1220 IP phones in non-production environments. I did notice a few feature called “Multi-user Login” which allows a SIP IP phone to connect to multiple SIP servers at the same time. Here’s the blurb from Avaya on the feature (it’s a direct quote from the release notes);

Multi-user Login

The Multiuser feature in SIP Release 3.0 allows multiple SIP user accounts to be in use on the IP Deskphone at the same time. Multiple users, each with their own account, can share a single IP Deskphone allowing each user to receive calls without logging off other users. One user can have multiple user accounts (for example, a work account and a personal account) active at the same time on the same IP Deskphone. You can register each account to a different server, and for each account, the IP Deskphone exposes the functionality available to that account. One account is considered a primary account and is used by default for most IP Deskphone operations. Each account is associated to a line key; the primary account is always on the bottom right line key of the IP Deskphone (this is the first key, Key 01), and an arbitrary key (including a key on an Expansion Module) can be selected for additional accounts.

The following operations are supported:

• Start dialing
• Place a call using the corresponding user account
• Answer an incoming call targeted to that account
• Initiate a call without pressing a line key (for example, by dialing digits at the idle screen and lifting the handset) uses the primary account.

A running IP Deskphone is associated to a single profile that represents one configuration of the IP Deskphone with all relevant persistent data such as preferences and call logs. A different profile is associated to each account used as a primary account. The IP Deskphone can store up to five different profiles; the IP Deskphone takes data from the profile associated to the current primary account. A number of configurations are independent of profiles and tied directly to an account making them available to that account regardless of the primary account you use (for example, voice mail ID).
The IP Deskphone receives and answers calls targeted at any of the registered accounts; the incoming call screen indicates who the call is for. You can place an outgoing call using any of the accounts; the account that you use is displayed on the dialing screen. When a call is active, information from both local and remote parties appear on the screen.
Regardless of which account receives the call, incoming call logs, outgoing call logs, and instant messages appear in a single list. The IP Deskphone indicates the local user in the detailed view of the entry.

Some features are only available to the primary account, such as instant messaging, retrieving parked calls by token, and establishing ad-hoc conference calls.
Please refer to the product bulletin and the release notes for all the details.

Cheers!

After digging through the net and all my documentation I came up with the following reference in one of the UNIStim release notes.

A constant humming noise is sometime heard through the headset when either the Enhanced USB Headset Adapter or the Mobile USB Headset Adapter is connected to the 1120E, 1140E, 1150E or 1165E IP Deskphone. The humming noise heard within the headset can be corrected by upgrading the Headset Adapter firmware to version 2.00.98 or greater.
The USB Headset Adapter firmware version 2.00.98 is available for download from the “Software Download” link under “Support and Training” on the Nortel website located at: http://support.nortel.com. The firmware is available for the 1120E, 1140E, 1150E and 1165E IP Deskphone models under “Phones, Clients and Accessories” as file Adapter3v2.0098.zip.

To load the version 2.00.98 firmware onto the USB Headset Adapter perform the following procedure:

1. Download the firmware file Adapter3v2.0098.zip from the Nortel Technical Support web site
2. Load the file Adapter3v2.0098.zip onto a PC
3. Uncompress (unzip) the file to obtain Adapter3v2.0098.exe.
4. Connect the USB Headset Adapter to the PC
5. Start the Adapter3v2.0098.exe application to load the firmware onto the device.

Hopefully this helps someone else out. It took me quite sometime to locate any reference and I had almost given up.

I’ve placed copies of the zip archive and the readme file on my server.

Cheers!

• 0621C7G for 2007 IP Deskphone
• 0623C7M for 1110, 0624C7M for 1120E, 0625C7M for 1140E, 0627C7M for 1150E and 0626C7M for 1165E IP Deskphones
• 0627C7M for 1200 Series IP Deskphones
• VPN Configuration Wizard release 01.00_00.25

The major change in this software release is the re-branding of the IP deskphone to Avaya from Nortel.

UNIStim 4.2 is the minimum software release that includes changes related to re-branding of the IP Deskphone software to Avaya from Nortel. All instances of Nortel branding within the IP Deskphone software including the start-up splash screen, User Interface elements, and Certificates have been changed to Avaya branding. In addition, the VPN Configuration Wizard software has been rebranded to Avaya

Please refer to the release notes and the product bulletin for complete details.

Cheers!

Update: Monday August 16, 2010

Avaya has re-released the bulletin because of a typo in the document.

The following enhancements are now available;

The following issues have been resolved;

• (091210-67218/091216-70624) 2050 is not marking QoS values in packets (see Technical Advisory Section)
• (091030-43866) IP Call Recording stops working after retrieve call from Hold
• (091203-63291) Unable to configure annotation feature keys in Expansion Module.
• (091008-30561) i2050.exe process does not release GDI Objects
• (100224-05132) 2050 IP Softphone on CICM: Delay when hanging up from a call
• (100310-13208) Configuration tool does not support customized skins
• (100312-14320) Configuration tool errors when applying Node/TN info. The configuration tool will now allow empty values for any parameter in the config.ini file and will not overwrite the registry entry if it is blank. This allows customers to upgrade to new configuration settings without changing selected values such as the Node/TN information that may already be set in the registry.
• (100405-25547) Inconsistent behavior of IP 2050 Settings for first launch if ConfigurationTool
• (090812-96650) GN Netcom 8110 USB adaptor does not work on the docking station

• 0621C7D for 2007 IP Deskphone,
• 0623C7J, 0624C7J, 0625C7J, 0627C7J and 0626C7J for 1110, 1120E, 1140E, 1150E and 1165E IP Deskphones respectively and
• 062AC7J for 1200 Series IP Deskphones

UNIStim 4.1 adds the following features;

• UNIStim 4.0 functionality delivered onto the 1165E IP Deskphone
• Quality improvements to Secure Signaling using DTLS
• Adjustable open-microphone warning tone during Zone Paging
• UNIStim VPN client interoperability extended to include Avaya VPN Gateways

The two product bulletins covering the software release can be found here and here.

Notice any formatting differences between the two bulletins?

Cheers!

If you recently purchased an Avaya/Nortel 1150e IP phone and that phone was manufactured between December 10, 2009 and December 25, 2009 you might need to RMA the phone. Apparently problems can appear when you try to upgrade the firmware/software on the phone.

In addition, if you recently purchased a new Avaya/Nortel 1150e IP phone you should not attempt to downgrade the firmware/software. There is now a minimum supported firmware/software version for all newly manufactured phones because of the hardware change.

You can view the official customer service bulletin here.

The 1150e IP phone is primarily designed as a Contact Center handset. It has no physical handset since Contact Center users traditionally use wired/wireless headsets. We have about 100 1150e IP phones deployed throughout the organization and have been very happy with the product.

Cheers!

I should warn folks that the phone is sold with different SKUs depending if you want it running the UNIStim or SIP protocol. Upgrading the phone between the UNIStim and SIP firmwares is not supported by Avaya/Nortel. With that said I was successful in upgrading/converting a UNIStim SKU’d phone with the SIP firmware available from Avaya/Nortel’s Software Communication System (SCS). I did have some issues downgrading/converting the same set back to UNIStim, although I eventually found the workaround that was needed to trick the SIP firmware into believing I had newer firmware. I can share that with anyone that is interested or if anyone is stuck in a similar position.

The default configuration password is:

26567*738

Cheers!

Update: Monday February 22, 2010

It might be easier to remember the password as follows:

COLOR*SET

Nortel has released UNIStim firmware 4.0  for their IP phones;

• 0621C7A for IP Phone 2007,
• 0623C7F, 0624C7F, 0625C7F and 0627C7F for IP Phone 1110, 1120E, 1140E and 1150E respectively and
• 062AC7F for IP Phone 1210, 1220, and 1230

No UNIStim software release 4.0 is being offered for the Phase II IP Phone 2001, Phase II IP Phone 2002, and Phase II IP Phone 2004.  The Nortel IP Phone 200x series (except the 2007) was manufacture discontinued as of November 29, 2009.

The enhancements available with UNIStim software release 4.0 for IP Phones include:

• UNIStim VPN Client (UVC) in the IP Phone 1100 series
• Feature and Application Licensing
• Secure Signaling using DTLS
• Secure Call Recording (SCR)
• Designed for Operability (DfO)
• Enhancements to Certificate Support

The product bulletin for the 4.0 release listed the same fixes (two of which were for the 2004 model) as the previous UNIStim 3.4 release. I’m going to guess that someone forgot to update that section of the product bulletin with some relevant information.

The big news with this release is the built in VPN client for the IP Phone 1100 series, the UNIStim VPN Client (UVC). Unfortunately this initial release doesn’t support encrypting/tunneling the traffic to/from the PC port, only the traffic to/from the Signaling Server and Voice Gateway Media Cards is encrypted with the VPN connection. The initial release is certified to work wtih Nortel VPN Router (NVR) family running software release 8.00 or greater. (NVR software release 8.00 has been qualified on the NVR 1010, 1050, 1100, 600, 1600, 17xx, 27×0, 4600 and 5000).

Please refer to the release notes and the product bulletin for complete details.

Cheers!

The following enhancements are available;

• Support for Microsoft Windows 7
• Log file improvements

The following issues have been resolved;

• (090304-89596) IP Softphone 2050 freezes when calls are answered on Nortel USB Headset
• (081009-83319) IP Softphone 2050/3.3 One-way speech path
• (090903-09977) IP Softphone 2050 getting double DTMF tones on CS2100
• (090317-99855) New Call Voice Notification fails to say the CLID properly
• (090526-47034) Translation error in GUI – correct word “Release” in French, German and Spanish
• (090515-40414) Agent voice is recorded on IPCR after Mute key is activated
• (090510-36664) IP Softphone 2050 Logs have no limit in size

There were some qualifications that should be mentioned. The release notes specifically indicate that 64-bit versions of Windows XP, Windows Vista and Windows 7 are not supported although it doesn’t mention that they don’t work. The release notes also make mention that while the IP Softphone 2050 may run in VDI (Virtual Desktop Interface) from both VM Ware and Citrix Xen Desktop, neither are supported. I couldn’t imaging the potential issues of running a softphone in a VDI configuration but I guess someone has been toying with the idea.

We have about ten Contact Center users utilizing the IP Softphone 2050 v3.x with Contact Center 6 on a Nortel Succession 1000 4.5 Call Server. These users work out of their home and are connected across a Juniper SSL VPN SA4000 appliance utilizing Juniper’s Network Connect client software. We provide them an HP NC6900 laptop with all the software and they connect to their home network and Internet broadband. It’s been very successful so long as the Internet broadband connection remains stable.

You can find the complete release notes here and here.

Cheers!

The document covers standalone Nortel IP Phone sets and how they can be deployed on various Nortel switches. It also covers features on Nortel switches related to VoIP with configuration examples. Overall, topics that will be covered include the following:

Ethernet switch platforms that support PoE:

• Ethernet Switch 470-PWR
• Ethernet Routing Switch 5xxx: 5520-24T-PWR, 5220-48T-PWR, 5650TD-PWR, 5698TFD-PWR,
• Ethernet Routing Switch 45xx: 4526T-PWR, 4550T-PWR, 4524GT-PWR, 4526GTX-PWR, 4548GT-PWR
• Ethernet Routing Switch 25xx: 2526T-PWR, 2550T-PWR
• Ethernet Routing Switch 8300

VoIP technologies:

• Power over Ethernet (PoE)
• Auto configuration via DHCP for VoIP Phone sets
• Auto provisioning using tftp or http
• Quality over Service (QoS)
• Authentication using EAPoL (802.1x)
• Auto Detection Auto Configuration (ADAC)
• LLDP

If you are working with Nortel IP telephony products I would highly recommend you give this document a quick review.  It’s about 257 pages in length it’s very detailed providing lots of examples.

Cheers!

• 0604DCN for Phase II IP Phones (2001, 2002 & 2004),
• 0621C6R for IP Phone 2007,
• 0623C6T, 0624C6T, 0625C6T and 0627C6T for IP Phone 1110, 1120E, 1140E and 1150E respectively and
• 062AC6T for IP Phone 1210, 1220, and 1230

The enhancements available with UNIStim firmware release 3.4 for IP Phones include:

• Screen Saver support (including slideshow) on the IP Phone 2007
• Support for Voice Signaling Application in LLDP-MED Network Policy TLV
• Incoming calls accepted during Zone Paging
• AG interface enhancement – forwarding of cookie deletion events
• GXAS interface enhancement – expanded Status Updates commands
• OS Diagnostics support on the IP Phone 1100 series

Here are a list of fixes included in release 3.4:

• 090708-75234 Slight chance that the IP Phone 2004 may freeze when ending an IP Call
  Recording (IPCR) call
• 090824-03336 Problem with the IP Phone 2004 obtaining an IP address when 802.1Q is
  enabled
• 090805-92397 Issue with Mouse Cursor on the IP Phone 2007 when backlight turns off
• 090713-78022 Issue with menu access when Lock Menu is enabled
• 090519-43214 SSH challenge prompt causes issue on IP Phone 1100 series
• 090728-87526 Concern with lowest ring tone setting on the IP Phone 1120E

Please refer to the release notes and the product bulletin for complete details.

Cheers!

Perhaps a few folks at Nortel can fill us in on the technical specifications of this new product. While it looks like a great phone I’m not sure what functionality a business user might benefit from over the 1140E or 1120E?

Cheers!

• 0604DCL for Phase II IP Phones (2001, 2002 & 2004),
• 0621C6P for IP Phone 2007,
• 0623C6R, 0624C6R, 0625C6R and 0627C6R for IP Phone 1110, 1120E, 1140E and 1150E respectively and
• 062AC6R for IP Phone 1210, 1220, and 1230

The enhancements available with UNIStim firmware release 3.3 for IP Phones include:

• HTTP transport for provisioning and configuration files
• DSCP provisioning precedence override
• DSCP tagging (QoS) for duplicate media stream
• DHCP provisioning information window
• New icons and colors on the IP Phone 2007
• Double-line edit boxes and drop-down boxes on selected menu items
• GXAS inactivity timer lower limit restricted to 10 seconds
• GEM firmware included in IP Phone 1100 series firmware image
• Default for LLDP changed to Enabled
• OS Diagnostics support on the IP Phone 2007

Please refer to the release notes and the product bulletin for complete details.

Cheers!