ip office 2.1.41 software

• Aug 8, 2005

• #2

AdamBiscoe

IS-IT--Management

Oct 19, 2004

13

GB

Hello,

Please can you point me in the direction of this update.

We are having the same issues.

Many thanks,

Adam

 

Upvote 0 Downvote

• Aug 8, 2005

• Thread starter
• #3

woodlee

Technical User

Jul 15, 2005

61

Hi Adam

sorry mate just found out that it isn't released yet but due out this month.

so sorry for wasting peoples time.

cheers

lee

 

Upvote 0 Downvote

• Sep 8, 2005

• #4

AdamBiscoe

IS-IT--Management

Oct 19, 2004

13

GB

Hello Lee,

Have you upgraded to 2.1.44

If so, have you had any problems?

Many thanks,

Adam

 

Upvote 0 Downvote

• Sep 23, 2005

• #5

Beefy80

IS-IT--Management

Apr 26, 2004

67

GB

Hi guys. I am having the same problems on 2.1(31) has upgrading resolved the issues for you?

 

Upvote 0 Downvote

• Sep 23, 2005

• Thread starter
• #6

woodlee

Technical User

Jul 15, 2005

61

Hi Beefy

the problem appears to be right through the software fom 2.1.31 up to the latest level i would recomend stay with the software levels prior the these releases

regards
woody

 

Upvote 0 Downvote

• Sep 23, 2005

• #7

mytelecoms

Vendor

Jul 18, 2005

179

GB

Version 2 was changed so much, that if you changed your firmware without changing your Manager version to match, the software corrupted very easily.

This lead to, as you say, problems which were "all really wierd".

The answer is to always program your unit with the Manager version which is designed for your firmware version. To fix a corrupted config file, I'm afraid it's a rewrite.

I suggest you backup your config, and upgrade your Manager, firmware and Voicemail to the August releases (2.0(44)). Then run your IP Office through the wizard and redo the config. I'm sure you'll find your problems go away.

Also consider the benefits of version if it's possible. Much more benefits and new features. We're up to 3.0(59) and it's pretty good!

 

Upvote 0 Downvote

• Sep 23, 2005

• #8

mytelecoms

Vendor

Jul 18, 2005

179

GB

Sorry, I meant 2.1(44) rather than 2.0!! Typo ;-)

 

Upvote 0 Downvote

• Sep 23, 2005

• Thread starter
• #9

woodlee

Technical User

Jul 15, 2005

61

i believe the 2.1.44 has a known issue's with cli and ringng on slt so i think this is more the problem than corruption as i have new installs programmed with the same version manager and system fileshave the problem which i have curretly logged with avaya.

regards

woody

 

Upvote 0 Downvote

• Sep 23, 2005

• #10

Beefy80

IS-IT--Management

Apr 26, 2004

67

GB

The system was upgraded with the correct manager program it the other 2 computers that have manager were also upgraded at the time. So I doubt that my config is corrupt. Woody will you let me know if you get any responce from Avaya.

 

Upvote 0 Downvote

• Sep 23, 2005

• #11

JeSTeROCK

Technical User

Feb 27, 2005

633

AU

What version did you upgrade from ?

I have had some issues when i try to skip too many versions when upgrading.

As mytelecoms said the best way is to rewrite if suspecting some sort of corruption. Although i have had some success when upgrading through multiple versions ie. 1.3.37 - 2.0.18 - 2.1.15 - 2.1.44

i know it sounds long winded but better than rewriting but a pain if doing 8 sites like i did yesterday/today with a combo of 406 and 403's

 

Upvote 0 Downvote

• Sep 23, 2005

• #12

Beefy80

IS-IT--Management

Apr 26, 2004

67

GB

Upgraded from 2.0(18) to 2.1(31) this was arranged from my maintainer. We run a 412 here although I have a 403 on another site but I have not upgraded this yet as there was more to do with the additional patch to go on 1st.

 

Upvote 0 Downvote

• Sep 23, 2005

• #13

casadeseus

IS-IT--Management

Feb 4, 2005

8

US

Just as a sanity check, 2 weeks ago we were having issues with the remote IP phones, Avaya support recommended to update from 2.1.15 (for known issues) to 2.1(44) because it’s a more stable version along with Vmail pro to 2.1.20 and the IP office Manager. Since them we have lost the inbound CLI (running on PRI not a T1. As I learned there is also issues with T1’s, and 3.0(x) versions), and the IP phones are loosing their registration, and not re-registering gracefully to the system (another thread). Does anyone know if there is a patch/release to fix these issues on 2.15(44), and also has anyone found other issues affecting this version. Ill like to know ahead of my users.

Cheers all;

 

Upvote 0 Downvote

• Sep 23, 2005

• #14

JeSTeROCK

Technical User

Feb 27, 2005

633

AU

Seems to work fine so far for me. I suspect your CLI issues have been discussed on here recently with new versions and disabled protocols.

I personally found 2.1(15) to be quite stable if not using certain features. Keep it on this if so.

IP phones seem to be ok when upgraded to the correct firmware and network working well.

 

Upvote 0 Downvote

• Sep 26, 2005

• #15

IPGuru

Vendor

Jun 24, 2003

8,391

GB

2.1(15) was prown to TFTP lockup if used with VM Pro
this would prevent downloading of the cfg & stop useres from changing various functions from the handset (DND etc.)

Currently I would advise V2.1(27) as the least propblematic version of V2.1 firmware

 

Upvote 0 Downvote