Avaya 9620L, stuck at LLDP, does not pull Dhcp

[hotelmotelpatel]

HI, I have quite a few 9620l that are stuck at LLDP, they never pull a DHCP. All sets were set up with a VLan. The problem is the CRAFT password was changed on all the sets. On half the sets I did get the phones to pull DHCP and set the CRAFT password back so I could clear all the settings. There OK now but the remaining sets are still stuck at LLDP and not pulling DHCP. I also tried the 9600 series patch that avaya made for 9600 series stuck at LLDP, I download the patch put the bin files in the manager folder, removed the Old 9600 txt file and replaced it with the one avaya created for the fix. Did not make a difference.
This is what I used

http://downloads.avaya.com/css/P8/documents/100092537

Any help would be appreciated, Thanks!

 

[holdmusic34]

Reset System Values
9600 Series Phones
1.While the phone is on-hook and idle, press the following sequence: MUTE 27238 # (MUTE CRAFT #).
2.Scroll the menu and select Clear.
3.Press Clear again to confirm the action. The phone settings are cleared and the phone restarts.
is your default command.

If your programming password was changed on your system by someone else, try opening your 46xxsettings.txt file and searching for this line:
## SET PROCPSWD 572958

It may have been changed to something different, which will likely be your new password.

If they were changed outside of this, it may have been done by CM or PPM as per the caveat below:

Setting this parameter via CM (for H.323) or PPM (for SIP) is more secure
## because this file can usually be accessed and read by anyone on the network.
## Setting the value in this file is intended primarily for configurations with
## versions of telephone or server software that do not support setting this
## value from the server.

If this doesn't reveal much, try CM or PPM. Failing that, you're now probably left with two options. Send back to Avaya or leave near the microwave in the kitchen for a week.

 

[tlpeter]

When it does pull the 46xxsettings.txt and you can change that then you can change the password.
Change the 46xxsettings.txt file, save it and reboot the phone.
It is easier to create a DHCP server with the right settings then sending these phones back.
Here is the part you need to change:

############# LOCAL PROCEDURE ACCESS SETTINGS ############
##
## PROCSTAT specifies whether local (craft) procedures can be used to configure the telephone.
## Value Operation
## 0 Local procedures can be used (default)
## 1 Local procedures cannot be used
## Note: Be very careful before setting PROCSTAT to 1
## This parameter is supported by:
## 96x1 H.323 R6.0 and later
## 96x1 SIP R6.0 and later
## 96x0 H.323 R1.0 and later
## 96x0 SIP R1.0 and later
## 46xx H.323 R1.0 and later
## 46xx SIP R2.2 and later
## 16xx H.323 R1.0 and later
## 16CC SIP R1.0 and later
## 1603 SIP R1.0 and later
## 1692 H.323 R1.4 and later
## SET PROCSTAT 1
##
## PROCPSWD specifies an access code for access to local (craft) procedures.
## Valid values contain 0 through 7 ASCII numeric digits.
## The default value is 27238 (CRAFT) unless indicated otherwise below.
## A null value implies that an access code is not required for access.
## Note: Setting this parameter via CM (for H.323) or PPM (for SIP) is more secure
## because this file can usually be accessed and read by anyone on the network.
## Setting the value in this file is intended primarily for configurations with
## versions of telephone or server software that do not support setting this
## value from the server.
## This parameter is supported by:
## 96x1 H.323 R6.0 and later (must contain at least 4 digits for R6.2.4 and later,
## else default value 27238 is used)
## 96x1 SIP R6.0 and later
## 96x0 H.323 R1.0 and later (default is null ("") prior to R1.2, must contain at
## least 4 digits for R3.2.1 and later else default value
## 27238 is used)
## 96x0 SIP R1.0 and later (must contain at least 4 digits for R2.6.10 and later
## else default value 27238 is used)
## 46xx H.323 R1.0 and later (default is null (""))
## 46xx SIP R2.2 and later (default is null (""))
## 364x SIP R1.1 and later
## 16xx H.323 R1.0 and later (default is null ("") prior to R1.3.3, and
## must contain at least 4 digits for R1.3.3 and later)
## 16CC SIP R1.0 and later
## 1603 SIP R1.0 and later
## 1692 H.323 R1.4 and later
## SET PROCPSWD 572958
##


BAZINGA!

I'm not insane, my mother had me tested!

 

[smokinjoe2938]

I recently was on a big install and didn't have the time to figure it out so what I did was let the phone ask me to press * to program, I hit star then scrolled down to vlan id and entered it manually and phone now was able to do DHCP. I know this was only a temp fix but it did work!

ACSS-SME,ACSS Avaya Aura Session Manager and System Manager,ACSS Avaya Scopia Solution,ACSS Avaya one-X UC Soft Clients,ACSS Avaya Session Border Controller, ACSS Avaya Aura Messaging,
ACSS Avaya Aura Call Center Elite, ACSS Avaya Aura CM and CM Messaging,ACIS Avaya Aura CM and CM Messaging, ACIS SME, ACIS Avaya CM 5.2.1