set procstat 1

[puregold]

I have been messing with my 46xx files.

I was seeing what the above does, i set it to 1 which disables local procedure access.

ie. i can no longer do any hold R-E-S-E-T # or any of the other commands. Nor do i get a * to program on boot of the IP handset.

This is documented as what will happen if you do this.

I want to get my phone back the way it was.

I have set procstat to 0 and also have tried ##'ing it out.

It will not come back at all.

There is a post on another IPO community that says "its a pain to get it back" but does not expand any further and i am not a member of that community to ask how he did it.

Does anybody know how to retrieve this?

Gracias

ACE - Avaya Certified Expert
ACI - Avaya Certified Instructor

 

[tlpeter]

Empty the 46xxsettings.txt file and only put in the line you want

Can you try that ?

If that does not help put older firmware on it


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[tlpeter]

I did a search and found this



Solution:

############# LOCAL PROCEDURE ACCESS SETTINGS ############
##
## Restrict Local Procedure Access
## Controls whether local (dial pad) procedures can be
## used to administer the telephone.
## 0 means local procedures can be accessed from the
## telephone.
## 1 means local procedures can not be accessed from the
## telephone.
## CAUTION:Be absolutely sure before setting PROCSTAT to 1
SET PROCSTAT 0
##
## Local Procedure Password
## Sets password for local (dial pad) procedure access.
## (1 to 7 ASCII numeric digits). See your telephone's
## Administrator's guide for the default password
## supported by your release.
SET PROCPSWD
##
###############


reboot the phone.....

then edit the file again:

############# LOCAL PROCEDURE ACCESS SETTINGS ############
##
## Restrict Local Procedure Access
## Controls whether local (dial pad) procedures can be
## used to administer the telephone.
## 0 means local procedures can be accessed from the
## telephone.
## 1 means local procedures can not be accessed from the
## telephone.
## CAUTION:Be absolutely sure before setting PROCSTAT to 1
## SET PROCSTAT 0
##
## Local Procedure Password
## Sets password for local (dial pad) procedure access.
## (1 to 7 ASCII numeric digits). See your telephone's
## Administrator's guide for the default password
## supported by your release.
## SET PROCPSWD
##
###############


that way all phones that reboot again will be unaffected.


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[puregold]

that did not work.

I even pasted the text from here in.

?

ACE - Avaya Certified Expert
ACI - Avaya Certified Instructor

 

[tlpeter]

Did you try to upload other firmware ?
That default the phone also,then the procstat is gone


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[tlpeter]

Another thing

0 is enabeld and 1 is disabled

So the docs are wrong !!!




Documentation states: (in settings file and other places)

Local Procedure Access
## Controls whether local (dial pad) procedures can be
## used to administer telephone.
## 0 for disabled, 1 for enabled
## SET PROCSTAT 0
##


however this is wrong!!!!

correction:

0 is enabled and 1 is disabled

i know many folks have had issues with this.


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[puregold]

I have downgraded my handset using the 2_3 bin files with a totally new script file etc, basically the entire bin folder from the 3.2 admin cd was used.

Phone downgraded, still the same.

From what i can see there is no way back at all.

Try it and you will see.



ACE - Avaya Certified Expert
ACI - Avaya Certified Instructor

 

[tlpeter]

Did you read this :

0 is enabled and 1 is disabled

You need to set it to 1 !!!

ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[shadesta]

I am in the same boat as the OP. I have a whole slew of 4620SW phones that seemingly bypass the ethernet programming stage and jump directly to DHCP with a VLAN setting already defined. I followed your suggestions, tlpeter, I removed the commenting from the 46XX file with PROCSTAT set to both 0 and 1 to no avail. For &^%$s and giggles, I even tried to "break" a known working phone and it refused to break. I only used Manager's built in TFTP and not any 3rd Party TFTP suite, so, perhaps that is the issue. Maybe these phones were flashed with a more robust TFTP program :/

A very non cost effective solution has been swapping out the flash chips. I assume the OP does not have access to this procedure and as I already stated - not exactly the best way to go about it. If I get thetime in the nest few days, I'll try a better TFTP program and maybe that'll give the phones the proper kick in the pants they so badly need.

 

[VoiceonData]

dont know if this is relevant

http://www.avayausers.com/showthread.php?p=14650

 

[VoiceonData]

Also i found this as well

The solution is to put the following in the 46xxsettings.txt file

SET PROCPSWD 1234
SET PROCSTAT 0

rebobot the phone and issue the following command on the keyboard:

<mute>1234CLEAR#

This clears the password and restores the phone to almost "factory" settings.

Reboot the phone and you'll see the * to Program option again

Might be helpful ???

 

[puregold]

Yes, i should have posted a reply, i have sorted it by doing the above.

Enable procstat with a password.

Use that password to do hold clear #

Unplug phone before it downloads the script file again.

Take out the procstat settings.

Reboot phone.

Happy days.

apologies for not posting my fix but not been on for a while due to workload.

ACE - Avaya Certified Expert
ACI - Avaya Certified Instructor

 

[shadesta]

*weep*

Unfortunately, none of the advice works in my case. Not sure about the original poster. I opened TFTP log and nothing even appears. What has apparently happened, these phones were programmed for Mr. X's network using VLAN ID of 112. Let's say MR X runs has his network 10.x.x.x and I have mine 192.168.x.x, I'm just incapable of seeing this phone. Tried running ethereal in the background to sniff the phone's IP, but all I ever see is my control unit sending out a generalized broadcast via 255.255.255.255. There is some other jargon, but I am not a network analyst and so it means nothing to me. If anyone here can understand the captured data, I'll merrily paste it for your reading pleasure, but I don't think there is much to discern from it.

Also, the phone constantly tries to load a20d01b2_4.bin no matter what working directory I have the TFTP server pointed to.

To recap: I have tried running a TFTP suite that is more robust than Manager's. I have set PROCSTAT to 0 and I have set a PROCPWD to 1234. I have done the whole <mute>123425327# and even <hold>123425327#. I re-comment out the PROC settings and still cannot do anything with this phone other than see how long this phone will look for its DHCP server.

Essentially, if you disable the local procedures on one network, you are going to have hell trying to re-enable those procedures if you are on a different subnet.

This is probably why I was able to buy these phones dirt cheap

Not very helpful, I know, just letting those who are facing the same issue know they are not alone.