Posts tagged Nortel

Cisco Router as a DHCP Server for Avaya IP Phones

4

Here’s a sample configuration detailing how to configure a Cisco router as a DHCP server for Avaya (formerly Nortel) IP phones including the Avaya/Nortel specific DHCP options 128 and 191. I thought I would share this information with the Nortel/Avaya users in case they are utilizing (or wish to utilize) the DHCP server functionality built-in to the Cisco IOS platform. The key is to configure the Cisco router to reply with the correct DHCP vendor options so the IP phone will boot properly.

!
no aaa new-model
!
ip routing
ip subnet-zero
no ip source-route
no ip finger
no ip domain-lookup
ip cef
!
!
!### 1) SET UP EXCLUSIONS FOR STATIC IP DEVICES ###
!### START ADDRESS (SPACE) END ADDRESS ###
!
!### VLAN2 DATA EXCLUSIONS ###
ip dhcp excluded-address 10.10.10.1 10.10.10.30
ip dhcp excluded-address 10.10.10.200 10.10.10.254
!
!### VLAN701 VOICE EXCLUSIONS ###
ip dhcp excluded-address 192.168.1.1 192.168.1.30
ip dhcp excluded-address 192.168.1.200 192.168.1.254
!
!### VLAN702 VOICE EXCLUSIONS ###
ip dhcp excluded-address 192.168.2.1 192.168.2.30
ip dhcp excluded-address 192.168.2.200 192.168.2.254
!
!
!### 2) SET UP DHCP FOR FOR DATA VLAN/SUBNET ###
!
ip dhcp pool Nortel_Data_VLAN2
network 10.10.10.0 255.255.255.0
default-router 10.10.10.1
option 128 ascii Nortel-i2004-A,192.168.1.21:4100,1,10.
option 191 ascii VLAN-A:701+702.
!
!
!### 3) SET UP DHCP FOR FOR VOIP-PHONES VLAN/SUBNET ###
!
!
ip dhcp pool Nortel_Voice_VLAN701
network 192.168.1.0 255.255.255.0
default-router 192.168.1.1
option 128 ascii Nortel-i2004-A,192.168.1.21:4100,1,10.
option 191 ascii VLAN-A:701+702.
!
!
ip dhcp pool Nortel_Voice_VLAN702
network 192.168.2.0 255.255.255.0
default-router 192.168.2.1
option 128 ascii Nortel-i2004-A,192.168.1.21:4100,1,10.
option 191 ascii VLAN-A:701+702.
!
!
!
!### 4) SET UP INTERFACES ###
!
!
interface fast 0/0
description ### VLAN TRUNK & ROUTE LINK TO LAN SWITCH ###
no ip address
speed 100
full-duplex
no shutdown
!
!
int fast 0/0.2
desc ### VLAN 2 DATA SUBNET ###
ip add 10.10.10.1 255.255.255.0
no ip red
no ip dir
no shut
!
int fast 0/0.701
desc ### VLAN 701 VOIP PHONES SUBNET ###
ip add 192.168.1.1 255.255.255.0
no ip red
no ip dir
no shut
!
!
int fast 0/0.702
desc ### VLAN 702 VOIP PHONES SUBNET ###
ip add 192.168.2.1 255.255.255.0
no ip dir
no ip red
no shut
!
ip route 0.0.0.0 0.0.0.0 10.10.10.254 name DEFAULT-ROUTE
!

Cheers!
Alex

-Editor, Thanks to Alex for writing this post and allowing me to re-post it here. -Michael

Avaya VPN Client Release 10.04.108 for Windows 7

Avaya has released version 10.04.108 of their VPN client that supports both 32-bit and 64-bit versions of Windows 7. This single client supports the following operating systems (in both 32-bit and 64-bit versions);

  • Windows XP
  • Windows Vista
  • Windows 7

The new client is now rebranded as the Avaya VPN Client, although the installation routine still bears the name “Nortel VPN Client” in the title bar and the desktop icon created by the installation gets the label “Nortel VPN Client”. The new client also supports a (completely) quiet installation;

Previously, when users install the client, they need to acknowledge UAC prompts before the installation can continue. If they do not want the UAC prompts to show up, they would have to manually install Avaya certificate to the Trusted Publisher store, or check on the “Always trust software from Avaya Inc.” during earlier installation NVC. In this release, a new option is introduced that the procedure can be automated. To use it, users will need to pass in “TrustAvaya=TRUE” (the “TRUE” must be in uppercase) to the installer at command line (in administrative context). For example,

C:\NVC32-10.04.108.exe /S /v”/qn TrustAvaya=TRUE”

or

C:\msiexec /i “Nortel VPN Client.msi” /qn TrustAvaya=TRUE

There are quite a few bugs resolved in this release including the following;

  • wi00568576 Wireless users are disconnected intermittently. IPSec users which are behind a wireless cable modem are disconnected intermittently. Users are able to authenticate successfully, but after some time they get disconnected and the client pops up the message “VPN tunnel is disconnected due to routing table change”. This is because the operating system changes the metric of wireless interface according to various parameters when Automatic Metric option is enabled. This is the default configuration for network interfaces in Windows. This causes the client to consider that the routing tabled has been hacked and disconnects the tunnel.
  • wi00595275 Screen Saver policy enforced at user level only. End user machine’s screen saver settings can be enabled at user level or group level (via Active Directory group policy). When the VPN client enforces the screen saver policy (pushed from server), it only checks the user level setting.
  • wi00595280 Unable to ping the local interface after a tunnel is disconnected. The issue occurs on Windows Vista/7 with mandatory tunneling only.
  • wi00666178 Inaccurate message when the QOTD banner message is not received. If the quote-of-the-day banner message gets lost (due to networking issue), the tunneling attempt failed with error message of “User did not acknowledge the banner”, which may confuse users. The message has been reworded as “The banner message from the VPN Router was not received, or the user didn’t acknowledge the banner. Please contact your Network Administrator or Helpdesk for assistance.”
  • wi00823633 On Windows XP the client fails to start if only Microsoft .NET 4.0 is available. On machines that have only .NET Framework v4.0 but no v3.5 or earlier versions available, the client fails to start.
  • wi00840078 Local IP address is unreachable on Windows 7. On Windows 7/Vista, when a tunnel is up (in mandatory tunneling mode), the local host IP address is not accessible.
  • wi00595473 Preconfigured profiles were not displayed in some cases.
  • wi00841234 NVC GUI takes very long time to launch up when using IPSec profiles having saved passwords.
  • wi00827126 Certificate based SSL tunneling fails when EACA (NHA/TG) is enabled. When Avaya EAC Agent (formerly Nortel Health Agent or TunnelGuard) is enabled, certificate-based SSL tunneling attempt will fail with error of “Banner fetching failed.”
  • wi00830401 On Windows 7/Vista the DNS settings for the VPN connection is not used if the connection is through a mobile broadband card connection. It’s an issue with the operating system’s DNS resolution. Please use Microsoft’s workaround described here: http://support.microsoft.com/default.aspx?scid=kb;en-us;311218
  • wi00841109 Occasionally tunneling attempts may fail with error of “Activating VPN adapter failed” error is displayed.
  • wi00841089 Sometimes the log clear function doesn’t work. The log shows there are query errors.

A number of readers posted comments to the previous software release, Nortel VPN Client Release 10.04.016, around the first issue above where users were getting disconnected with the following message; VPN tunnel is disconnected due to routing table change. If you don’t feel like upgrading the client you can implement a workaround provided by a reader.

You can find the complete release notes right here.

You can find the client software on the Avaya support website.

I’m going to make the AVC software available here unless I’m contacted by Avaya.

NVC64-10.04.108.exe (64bit)
NVC32-10.04.108.exe (32bit)

Cheers!

Updated Sunday April 10, 2011

I can no longer host the Avaya VPN client software do to the enormous bandwidth utilization on my host. In addition there are just too many people abusing my gesture. I had a single IP address from China download the client software so many times that it consumed 10GB of bandwidth.

Avaya USB Headset Adapter humming

0

I use the Nortel/Avaya Mobile USB headset with my laptop and 2050 softphone. On occasion I’ll use it on my 1140E desktop phone and have noticed a humming from time to time.

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!

Go to Top