2.0(16) Upgrade

[wturner80]

Hello,

I just received a small office that has build 2.0(16) on it and I can't seem to contact it via manager. I currently have the 2.1(78) download installed. Here is the output from sysmonitor:
0mS PRN: Monitor Started IP=192.168.42.10 IP 401 NG DS 2.0(16) 00E0070502EC
1mS PRN: LAW=U PRI=0, BRI=0, ALOG=4, ADSL=0 VCOMP=16, MDM=0, WAN=0, MODU=0 LANM=0 CkSRC=0 VMAIL=0(VER=0 TYP=1) CALLS=0(TOT=50)
117mS RES: Tue 18/3/2008 14:57:22 FreeMem=5785124(14) CMMsg=4 (5) Buff=100 653 420 1465
239mS PRN: AtmIO 0: Trunk Release
239mS PRN: AtmIO 0: Block Forward OFF
239mS PRN: AtmIO 0: CLI Detection ON Equaliser OFF
1596mS PRN: AtmIO 0: CLI Detection OFF Equaliser OFF
5478mS PRN: AtmIO 0: Block Forward OFF
5478mS PRN: AtmIO 0: CLI Detection ON Equaliser OFF
5634mS RES: Tue 18/3/2008 14:57:27 FreeMem=5779628(13) CMMsg=4 (5) Buff=100 653 420 1465
8544mS PRN: AtmIO 0: CLI Detection OFF Equaliser OFF
13747mS PRN: AtmIO 0: Trunk Release
13747mS PRN: AtmIO 0: Block Forward OFF
13748mS PRN: AtmIO 0: CLI Detection ON Equaliser OFF
20647mS RES: Tue 18/3/2008 14:57:43 FreeMem=5785124(14) CMMsg=4 (5) Buff=100 653 420 1465
26171mS PRN: AtmIO 0: CLI Detection OFF Equaliser OFF
31373mS PRN: AtmIO 0: Trunk Release
31373mS PRN: AtmIO 0: Block Forward OFF
31374mS PRN: AtmIO 0: CLI Detection ON Equaliser OFF
32324mS PRN: AtmIO 0: CLI Detection OFF Equaliser OFF
37527mS PRN: AtmIO 0: Trunk Release
37527mS PRN: AtmIO 0: Block Forward OFF
37527mS PRN: AtmIO 0: CLI Detection ON Equaliser OFF
60790mS PRN: TFTPServer::RRQ(from 192.168.42.10) nasystem/who_is
61127mS RES: Tue 18/3/2008 14:58:24 FreeMem=5784136(14) CMMsg=4 (5) Buff=100 653 419 1465
65632mS RES: Tue 18/3/2008 14:58:28 FreeMem=5778640(13) CMMsg=4 (5) Buff=100 653 419 1465
71147mS RES: Tue 18/3/2008 14:58:34 FreeMem=5778720(13) CMMsg=4 (5) Buff=100 653 419 1465
77551mS PRN: TFTPServer::RRQ(from 192.168.42.10) config/$t%$'~ q
77556mS PRN: Config Write Wake Up
77626mS RES: Tue 18/3/2008 14:58:41 FreeMem=5777664(13) CMMsg=4 (5) Buff=100 653 419 1465
78061mS PRN: Sending Config out to ffe03618 started
78122mS RES: Tue 18/3/2008 14:58:41 FreeMem=5766900(13) CMMsg=4 (5) Buff=100 653 418 1461
80621mS RES: Tue 18/3/2008 14:58:44 FreeMem=5772396(16) CMMsg=4 (5) Buff=100 653 418 1461
111142mS RES: Tue 18/3/2008 14:59:15 FreeMem=5773384(16) CMMsg=4 (5) Buff=100 653 419 1461
115650mS RES: Tue 18/3/2008 14:59:19 FreeMem=5773456(16) CMMsg=4 (5) Buff=100 653 419 1461
125639mS RES: Tue 18/3/2008 14:59:30 FreeMem=5767968(14) CMMsg=4 (5) Buff=100 653 419 1461
128403mS PRN: WARNING:eviceConfigIO EOF during outstanding=0 len=19
128404mS PRN: Sending Config out to ffe03618 finished
128623mS RES: Tue 18/3/2008 14:59:33 FreeMem=5779788(13) CMMsg=4 (5) Buff=100 653 420 1465
140651mS RES: Tue 18/3/2008 14:59:45 FreeMem=5785276(14) CMMsg=4 (5) Buff=100 653 420 1465

********** contact lost with 192.168.42.1 at 09:05:16 18/3/2008 - reselect = 1 *********

Do I need an older version of manager in order to open the config on this IPO?

Thanks

 

[sizbut]

Possibly. Pre 2.1 you needed the same Manager as per the core software release. See

http://marketingtools.avaya.com/kno...edProjects/bulletins/techtips/052_techtip.htm

 

[tlpeter]

Go in to the system with DTE

Type AT

at-debug

system

Write down the macadres

In manager make an bootp entry with the right file !!!
Make sure your working directory is set up right !!!

Then go back to hyperterminal

Type upgrade

Then it does an offline upgrade

Good luck



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!

 

[wturner80]

Thanks. I'm currently downloading 4.0.14 to try. I don't have access to a DTE cable so I can't try peter's suggestion.

Thanks again.

 

[mattKnight]

You'll struggle with 4.0.14. I don't think the manager will see a 2.0.xx unit.

if you are trying to upgrade - I'd try upgradeing to 3.2.xx first (using a 3.2 manager or upgrade wizard)

However, if you are trying to access the config to change soemthing, you will need the correct core manager i.e. v2.0.16

Managers didn't become backwards compatible until version 3.2 and are only compatible to a v2.1 system.

Take Care

Matt
If at first you don't succeed, skydiving is not for you.

 

[wturner80]

Thanks Matt. Is 2.0.16 a private build? I can't seem to find it on the web anywhere.

Thanks again.

 

[tlpeter]

2.0.16 is an old version
Avaya ships the SOE 2.0.16
You can not access the SOE with a manager 2.1 or higher
You need to access it with a 2.0 manager
Why can't you DTE the unit ?


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!

 

[ronromano]

As we speak I am upgrading a 412 on 2.0 (16). I did it from 2.1 (15) manager. Maybe the SOE is different but I don't think so. Go get the 2.1 manager.

http://www.nu-tel.com

 

[tlpeter]

You can do it with 2.1 but not higher then 2.1.34 i believe
But that one can not be downloaded so you must have it already !!!
And the SOE is not different


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!

 

[wturner80]

Thanks for everyone's help. I installed the 2.1(78) download on a different computer and it worked.

Thanks again.

 

[ZebrAYA]

I am unpacking a new in box IPO SOE with 2.0 (16) from a retail store.

I’m using manager from release 4.0 (5)
It’s true that can’t open configuration from manager but it’s due to the initial release lets makes nothing except upgrade

When I use the advanced > upgrade I can see it

Would the intermediate version will be the 3.2? I’m trying to do it, but don’t wanna kill the little one


[Always Close your threads for avoiding other people to entangle]

 

[ZebrAYA]

When using the binaries of the 3.2 Admin CD I got this in the manager 4.0 advanced upgrade

Type VERSION AVAIL STATUS
IPO 401 NG 2.0 (16) 3.2 (17)


[Always Close your threads for avoiding other people to entangle]

 

[tlpeter]

Always go to a 3.2.999 version first !!!


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!

 

[jamie77]

All the binaries needed are on each Admin CD. SOE will go to the latest 4.1. Look at the Tech Bulletin for the procedure. New managers won't see the config but the Upgrade Wiz will.

2.0(16)>3.2(999)>4.1

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Football is not a matter of life and death-It is far more important!!!!

 

[ZebrAYA]

I killed the little IPO 4T 8A 3VCM.
Because I tried to move it from the non-operative 2.0 (16) to 3.1 (17)
Using 4.0 (14) Manager
I’m used to see the validate checkbox checked, but in this case was unchecked.
So when sending the release it first erases the current bios and later failed sending the new one.
So the machine became into a paperweight.

So now how to revive it?

Anyway I was blessed because I found the original 2.1 admin and user CD’s that were shipped when our company bought the first IPO SOE.
I used this binaries and the DTE port procedure to restore the machine.
(I used the 3.2 release Manager.)
So I got the 2.1 (17) fully functional version on the machine
Later I got 3.2 (17), later 3.2 (999), later 4.0 (5)

Anyway I got I weird behaviour
When calling from analog trunks to extensions, or from extension to extension I got a crackling noise like horse gallop, and later conversation or sometimes call is cut

Could I cause it by the upgrade path I’ve done?
telephony parameters are both in U-law as usually on my country,
could be trunk analog parameters, but that won’t answer why internal calls also show noise.

Any hints?




[Always Close your threads for avoiding other people to entangle]