Posts tagged 1140E
SIP Software Release 3.0 for IP Deskphones
7
Avaya has released SIP software release 3.0 for their 1120E and 1140E IP deskphones. (There was no mention of the 1110E, 1150E, 1165E or 1200 series IP phones in any of the accompanying material).
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!
Avaya 1120e/1140e/1150e IP Phone SSH Access
7
I was recently testing the built-in UNIStim VPN Client (UVC) on the Avaya 1120e IP phone and needed to access the SSH console of the IP phone to check the status of the VPN connection to the Nortel VPN Router. I thought I’d take a few seconds to document for anyone that might be interested. You obviously need to be running firmware 0623C7F, 0624C7F, 0625C7F or 0627C7F (or later) for IP Phone 1110, 1120E, 1140E or 1150E respectively.
You can enable the SSH console by the following commands;
- Press the Services key twice in quick succession
- Select Local Diagnostics
- Select Advanced Diag Tools
- Place a checkmark in the box labeled Enable SSH
- Set the UserID
- Set the Password
- Apply the settings
There is no reboot required to enable the SSH console. Here’s a quick example of the help command;
[root@centos ~]# ssh 10.1.1.10 -l admin The authenticity of host '10.1.1.10 (10.1.1.10)' can't be established. RSA key fingerprint is 09:14:95:11:c2:e6:d7:93:98:2c:4e:ce:e4:2c:64:cc. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '10.1.1.10' (RSA) to the list of known hosts. admin@10.1.1.10's password: Welcome to Nortel problem determination tool. You are connected to IP Phone 1120E. HW version:18001365FF5E4FFFFF FW version 0625C7F MAC 001365FFFFF IP 10.1.1.10 Type "pdtHelp" for list of available commands. Bluetooth address 00140D01635B Type "pdtHelp" for list of available commands. Type "bye" to exit current shell. PDT> pdtHelp pdtHelp Print PDT shell help setLogLevel <loglevel> Set LogLevel, Critical:1, Major:2, Minor:3, Warning:4, Info:5 setRecoveryLevel <recovery level> Set RecoveryLevel, Critical:1, Major:2, Minor:3 setAutoRecoveryFlag <flag> Set auto recovery flag, turn on:1, turn off:0 printLogLevel Print current logLevel, Critical:1, Major:2, Minor:3, Warning: 4, Info:5 printRecoveryLevel Print current recoveryLevel, Critical:1, Major:2, Minor:3 printAutoRecoveryFlag Print auto recovery flag printUptime Print set uptime printLogFile [severity level] Print log files; Args - Critical:1, Major:2, Minor:3, Warning:4, Info:5 clearLogFile Clear content of error log file taskMonShow Show task monitor list taskMonAddTask <taskName | task id> Add a task to task minitor taskMonRemoveTask <taskName | task id> Remove a task from task monitor setCpuSamplingPeriod <value> Set CPU sampling period, range: 180-360s, step 10s i Print all task Info ti <taskName | task id> Complete info on TCB for task tt <taskName | task id> Task Trace memShow [level] Show system memory partition blocks and statistics checkStack <taskName | task id> Print a task's stack usage ls [dirname] [-f] List contents of directory, -f: include details lsr [dirname] Recursive list of directory contents cd [dirname] Set current working path usbFsShow Display MSDOS volume configuration data of USB memory stick usbls [dirname] [-f] List contents of USB directory, -f: include details usblsr [dirname] Recursive list of USB directory contents usbcd [dirname] Set current USB working path pwd print the current default directory ping <host ip> [# of pings] Test that a remote host is reachable tracert <host ip> [max hops] traceroute to any host netinfo Print common network info routeshow Display host and network routing tables and stats arpShow Display entries in the system ARP table listcerts List all trusted certificates printcert <index> Print a trusted certificate in detail listcrls Prints a detailed list of CRLs listdevcerts Prints all device certificates listsecuritylogs Lists all events logged through the security interface securitypolicy Prints the current Security Policy values gxasinfo Lists the GXAS configuration and current status reportWidgetData shows widgets info reportWindowData shows windows hierarchy turnOnScreenScrape turn Screen Scrape feature on turnOffScreenScrape turn Screen Scrape feature off setScreenScrapeDelay <delay> set delay in ms for the Screen Scrape process sendKey <code> <state> Emulate key with a code "code". State 0/1/2 = Key Down Message/Key Up Message/Key combination down followed by up. showVPNStatistics Show VPN Statistics showVPNStatus Show VPN Status showVPNFilter Show VPN Filter setVPNLogLevel <loglevel> Set VPN Log Level - 0:turn off log/1:log info/2:log info,error/3:log error,debug,info printVPNLogLevel Print current VPN logLevel - 0:turn off log/1:log info/2:log info,error/3:log error,debug,info showFIPSStatus Show FIPS Status setVPNNatKeepaliveIntervalOverride <interval> Set VPN NAT Keepalive Interval Override scrShow Show SCR Status printSetInfo Print HardwareID, FirmwareID and MAC address vxshell Switch to vxShell bye Exit current shell PDT>
I don’t know that I would advise someone to enable this feature on every IP phone they deploy but it can certainly be helpful if enabled when needed during troubleshooting.
Cheers!
UNIStim Firmware Release 3.1 for Nortel IP phones
0
We’ve been running on a very old version of firmware for the i2002, i2004, i2007, 1140e and 1150e for sometime now. We initially put a lot of time and effort assisting Nortel with troubleshooting the LLDP/ADAC integration between the Nortel Ethernet Routing Switches and the Nortel IP telephones. We had been running 0604DBG on the i2002 and i2004 models for the past 24 months with great success on about 350+ phones.
We have another large IP phone deployment coming up in the next few months and thought it would be a good time to upgrade prior to deploying potentially another 300+ IP phones.
We’ve just started upgrading our Data Center (our testbed if you will) with the latest firmware.
- 0604DCG for Phase II IP Phones (2001, 2002 & 2004),
- 0621C6H for IP Phone 2007,
- 0623C6J, 0624C6J, 0625C6J and 0627C6J for IP Phone 1110, 1120E, 1140E and 1150E respectively
- 062AC6J for IP Phone 1210, 1220, and 1230
I’m happy to report that everything appears to be working properly. The regular i2002 and i2004 handsets work fine. The 1140e works fine with the Plantronics Bluetooh headset and the 1150es still work fine in our three call centers. We are using LLDP/ADAC with all of our phones as a way to standardize their configuration. We utilize CRQM for Contact Recording and that seemed to work fine along with Contact Center 6.0 when used with the 1150e phones.
We did have one or two problems with the Default PVID changing on the Nortel ERS 5520 switch after the upgrade (power cycle). I initially thought it was related to our previous experiences with ADAC which I discussed in this post. However, this problem only involved the PVID and not the entire VLAN so additional testing will probably be required to try and isolate this issue.
I have yet to test either of the new provisioning options, including the new DHCP option (“Nortel-i2004-B”) or the new “Info Block” files retrieved over TFTP. I talked about the new DHCP options when firmware 2.3 was released back in May 2008. I’m curious if either of these options will help ease the initial configuration of the IP handsets.
You can find the release notes for the Nortel UNIStim Release 3.1 here.
Cheers!

