IP Office IP Phone issues

[Laxboye]

Guys

I have an IP office 403 v 2.1(24) at home and I want to use Avaya 4621SW IP phones. As i understand it I have to use v 3.1 to support this phone. However Avaya's support site is not very help full with this older product. Some things I read say I have to get the 403 up to 2.99 then 3.0 and onward to 3.1 is this right? If so how can I find the files?

Here is the sysmon when I plug in the 4621SW phone.


********** SysMonitor v6.2 (23) **********

********** contact made with 192.168.42.1 at 10:26:14 7/6/2013 **********

********** System (192.168.42.1) has been up and running for 8mins and 27secs(507621mS) **********

********** Warning: TEXT File Logging selected **********


********** Warning: TEXT Logging to File STOPPED on 7/6/2013 10:26:14 **********
507621mS PRN: Monitor Started IP=192.168.42.2 IP 403 2.1(24) 00E0070128F6
507621mS PRN: LAW=U PRI=1, BRI=0, ALOG=4, ADSL=0 VCOMP=5, MDM=2, WAN=0, MODU=0 LANM=0 CkSRC=0 VMAIL=1(VER=2 TYP=1) CALLS=0(TOT=0)
513512mS RES: Fri 7/6/2013 10:26:20 FreeMem=5850736(10) CMMsg=2 (3) Buff=100 631 500 1327 Links=10384
520514mS RES: Fri 7/6/2013 10:26:27 FreeMem=5845080(10) CMMsg=2 (3) Buff=100 631 500 1327 Links=10381
531027mS RES: Fri 7/6/2013 10:26:38 FreeMem=5844984(10) CMMsg=2 (3) Buff=100 631 500 1327 Links=10379
542512mS PRN: 24 bytes @ffe8efb8 were allocated by ffe61998 00000000 at 475873 mS
542512mS PRN: 24 bytes @ffe8efe8 were allocated by ffe61998 00000000 at 474823 mS
542513mS PRN: 24 bytes @ffe8f018 were allocated by ffe61998 00000000 at 473711 mS
542513mS PRN: 24 bytes @ffe8f048 were allocated by ffe61998 00000000 at 473447 mS
542513mS PRN: 24 bytes @ffe8f078 were allocated by ffe61998 00000000 at 463141 mS
549275mS PRN: DHCP type=DHCPMsgInform HTYPE=01
560513mS RES: Fri 7/6/2013 10:27:08 FreeMem=5844888(10) CMMsg=2 (3) Buff=100 631 500 1327 Links=10377
563787mS PRN: DHCP type=DHCPMsgDiscover HTYPE=01
563787mS PRN: FindAddressHint for {00040DE96094}
563788mS PRN: DHCP::SetState DHCPAInit->DHCPAInit
563788mS PRN: DHCP::SetState DHCPAInit->DHCPAChecking
563788mS PRN: DHCP:ing c0a82a03
565802mS PRN: DHCP::SetState DHCPAChecking->DHCPAOffering
565803mS PRN: DHCPSVR::Unsupported option (43) requested
565803mS PRN: DHCPSVR::Unsupported option (42) requested
566018mS RES: Fri 7/6/2013 10:27:14 FreeMem=5849832(11) CMMsg=2 (3) Buff=100 630 500 1327 Links=10377
567271mS PRN: DHCP type=DHCPMsgRequest HTYPE=01
567272mS PRN: DHCP::SetState DHCPAOffering->DHCPABound
567272mS PRN: DHCPSVR::Unsupported option (43) requested
567272mS PRN: DHCPSVR::Unsupported option (42) requested
571415mS PRN: Decode Failed!
571520mS RES: Fri 7/6/2013 10:27:19 FreeMem=5848028(13) CMMsg=2 (3) Buff=100 631 500 1327 Links=10361
576272mS PRN: Decode Failed!
580509mS RES: Fri 7/6/2013 10:27:28 FreeMem=5840976(12) CMMsg=2 (3) Buff=100 631 500 1327 Links=10342
581141mS PRN: Decode Failed!
586686mS PRN: Decode Failed!
587012mS RES: Fri 7/6/2013 10:27:35 FreeMem=5836628(7) CMMsg=2 (3) Buff=100 631 500 1327 Links=10305
591545mS PRN: Decode Failed!
596419mS PRN: Decode Failed!
596513mS RES: Fri 7/6/2013 10:27:45 FreeMem=5832796(3) CMMsg=2 (3) Buff=100 631 500 1327 Links=10269
601957mS PRN: Decode Failed!
602019mS RES: Fri 7/6/2013 10:27:50 FreeMem=5830900(3) CMMsg=2 (3) Buff=100 631 500 1327 Links=10251
603013mS PRN: 10272 bytes @ffe020b0 were allocated by ffe065f4 00000000 at 507620 mS
606824mS PRN: Decode Failed!
611689mS PRN: Decode Failed!
612005mS RES: Fri 7/6/2013 10:28:01 FreeMem=5827260(3) CMMsg=2 (3) Buff=100 631 500 1327 Links=10217
617233mS PRN: Decode Failed!
617507mS RES: Fri 7/6/2013 10:28:06 FreeMem=5825736(3) CMMsg=2 (3) Buff=100 631 500 1327 Links=10207
622094mS PRN: Decode Failed!
626013mS RES: Fri 7/6/2013 10:28:15 FreeMem=5829464(6) CMMsg=2 (3) Buff=100 631 500 1327 Links=10191
626961mS PRN: Decode Failed!
631028mS RES: Fri 7/6/2013 10:28:20 FreeMem=5827544(5) CMMsg=2 (3) Buff=100 631 500 1327 Links=10173
632506mS PRN: Decode Failed!
637370mS PRN: Decode Failed!
637507mS RES: Fri 7/6/2013 10:28:27 FreeMem=5823904(5) CMMsg=2 (3) Buff=100 631 500 1327 Links=10139
642242mS PRN: Decode Failed!

 

[intrigrant]

The 4620 is supported from version 3.0 and newer versions.
The intermediate software builds are installed together with the 3.x Managaer software.
Upgrade procedure : 2.1 > 2.99 > 3.x


A simple mind delivers great solutions

 

[Laxboye]

I can't find the software on Avaya's web site any longer. Does anyone have it and could send it to me, or know where I can download 3.0?

 

[Bas1234]

Try here;

http://support.avaya.com/downloads/...contentId=C2011122910141160_8&productId=P0160

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

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________

 

[Laxboye]

The links to v3.2 dont work. This is very frustrating I find.

 

[intrigrant]

Download any manager you can and download the 3.2 binary files here

A simple mind delivers great solutions

 

[Laxboye]

Ok I was able to upgrade it to 3.2 however the default user name and password changed. Do you guys know what it would be now?

 

[tlpeter]

Administrator and Administrator

BAZINGA!

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

 

[IPOLackey]

If you were used to the 2.1 Manager then 3.2 Manager looks a bit different now right?

Before you had a username and password to open Manager, then a password for the kit. Now it's just Administrator - Kit password.

So if before you had Administrator/Administrator to open Manager, then password to open a config, it is now Administrator/password.

 

[Laxboye]

I got it upgraded and logged in as well. Thanks for all your help guys!!!