Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Additional IP 400 Expansion module to an IP 406 controller? 2

Status
Not open for further replies.

mlc9

MIS
Aug 15, 2007
255
US
I currently am running an IP 406 Office V2 control unit, with three IP 400 Digital Stations V2 running off of it. The 406 controller is running version 3.2(17) and the Expansion modules are on version 5.2(17). Yea, old, I know.

I purchased an identical, used IP 400 Digital Expansion module to add to this setup. I plugged it in, seemingly got it added to the controller, and have done a reboot. When viewing the IP Office Manger GUI, this new module shows up within Control Units section and even shows as another module with 30 ports when I look at Extension view. The problem is actually plugging a phone to it. When I try and put our normal Avaya 5410 model phone on it, the phone only says "5410D + Rel 2.0 + Date + Please wait..."

Just like always, I assigned an extension to the module/port, saved, and rebooted. The only difference I see is that my other Expansion modules are on v5.2(17), and this new one is showing as v6.2(11). Though different versions, I assumed it would be backward compatible. Any thoughts would be appreciated.
 
You assumed wrongly, it needs to be upgraded to match (using Manager). Also if the handsets are new they may need upgrading/downgrading too :)

 
Ughh. That's what I get for assuming. Can you please tell me what exactly needs the upgrading? Are there separate software versions for the controller (v3.2.17) and the expansion modules (v5.2.17)? Or must all physical units be running the same software and versions?

I can see that by going to File > Advanced that I have an Upgrade option. By choosing that, will it just upgrade everything automatically. I only ask this b/c we've got no support or contract on the system and I was just wondering if it just goes out and downloads the newest software that will work on this equipment. Thanks
 
Now you see the value of a support contract. While upgrading is easy, recovering from a failed one or finding/resetting upgrade passwords isn't. If when selecting upgrade it shows the correct version (that matches the other modules) next to the new module then go ahead and upgrade it, it will only upgrade units that are ticked. Password is "password" by default :)

 
Agreed on support, but......$$$

Ok, when selecting upgrade it does give me the list of what is available, which isn't much. The only option is gives is to take the new module back from 6.2.11 to 5.2.17 like the others (at least that sounds like going back). If true, and I know it sounds crazy, will it work if I were to just do that and "downgrade" that new one? Ofcourse, I would backup from here to eternity before doing so. Thanks for your help.
 
That is such a non valid reason.
I bet there are support contract on printers and other stuff like that.
So why not on the PBX?
What happens is you cannot make and receive calls???


BAZINGA!

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

 
Thanks for the input tlpeter. And no, we have no support on printers either.
 
Then i hope nothing breaks down as this will give big costs.
But that choice has been taken and i am not blaming you.
Sometimes you have to deal with these kind of situations :)


BAZINGA!

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

 
Just go ahead and hit upgrade, yes even though it's actually a downgrade. As long as the password is correct it will work, if it says "all/some units failed to upgrade" or similar then the installer changed the password :)

 
Will do. I know the password, as I make changes often. Thanks very much amriddle01.

tlpeter.....I still agree with you, but as you know, those decisions are a few pay grades above me. [bigsmile]
 
It's not the same password as the one you use for configuration changes, it's different :)

 
Oh, ughh. Since I inherited this system then I do not know said password. Is there a way to recover or change it?
 
Did you try "password" or the one you know, they may have made them the same, I think on early firmware it shows in the system programming anyway :)

 
Well, I'll likely try it over the weekend, as I am a little scared to do anything during business hours (though the downgrading of the one module that isn't up anyway may have no effect on PBX). I know it's not the same as current config password, as I was made to change that by an auditor, and I don't remember the previous one. If none of that works, I guess it's on to more research.
 
3.2 uses the system password for authentication not the service user password so it should be the password you know.
Long time ago we all knew that, haha


Joe W.

FHandw, ACSS

 
I thought it was still different, I started at 3.2 as well, has been a while :)

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top