5620 IP Phone 2

[PatrickCT]

Recently upgraded firmware on a 406v2 from 3.0(56) to 4.2(20). After the upgrade the IP phones continue to work, make calls out/ call other extensions, but they are unable to login to their extensions(used for hot desking). What am I missing here? And thanks in advance.

 

[kwing112000]

DId the phones upgrade?

Kevin Wing
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries

 

[PatrickCT]

Yes, they did.

 

[Bas1234]

Check if the "Login Code" is still there.

In the Manager goto;

User > Telephony > Supervisor Settings.

You can try to remove it and the add it again.

Also check if you have Call Appearance keys on the user.

___________________________________________
It works! Now if only I could remember what I did...
___________________________________________

 

[Escorthosis]

In Before release 4.0 you didn't have to have a code to logout and login. As of 4.0 you do.

From the helpfile:

· For IP Office 4.0+ users can only log out if they have a Login Code set.

 

[PatrickCT]

That may well be the problem then, I haven't been on site yet to see what is exactly going on, but I don't think they use a code to log in and out.

 

[PatrickCT]

Checked into they do have to use a login code. The problem is that when they get to the phone and hit the login button, nothing happens.

 

[amriddle01]

When upgrading the unit, did you step the system (including expansion modules) through any loaders at all or just go straight from 3.0 to 4.2?

ACS - IP Office Implement

"I'm just off to Hartlepool to buy some exploding trousers

 

[amriddle01]

In fact that shouldn't be the issue, its 3.1 that needs to go through the loader, but any expansions if v2 do need to be stepped although that's obviuously not the cause here

ACS - IP Office Implement

"I'm just off to Hartlepool to buy some exploding trousers

 

[PatrickCT]

I did upgrade directly to 4.2 from 3.0, but not through conventional means.

Today I went on site, saw the phones firmware had not upgraded. So naturally I upgraded the firmware on them after they finished restarting the were just trying to Discover the phone system. Not sure why new firmware would cause them to lose connectivity when they have been working for a good 5 years now. All IP addresses are good, ports are opened etc etc.

Opened a ticket with Avaya on the issue, Catalyst Telecom wasn't any help they basically told me "Well that's weird they should be working." But if anyone has any other input I would greatly appreciate it.

 

[amriddle01]

When you say "Not through conventional means" do you mean you AT-X'd the system then it took the new bin files, it may be worth doing a correct installation of the firmware as upgrading the correct way allocates memory to certian areas and other things that AT-X does not do

ACS - IP Office Implement

"I'm just off to Hartlepool to buy some exploding trousers

 

[tlpeter]

No need to do that when you come from 3.0 !!!
Only 2.1 and 3.1 need to have the memory allocated.

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

 

[amriddle01]

I know that tlpeter, I said it myself further up the thread, but I have found that if you "cheat" upgrade systems by AT-Xing them you can get odd issues that is sometimes solved by upgrading them correctly using the wizard

ACS - IP Office Implement

"I'm just off to Hartlepool to buy some exploding trousers