2 weeks ago I upgraded a 406 v1 with DT phones (and some 64XX DS and 46XX IP phones) to an IP500 replacing all the DT phones with 56xx IP phones.
Everything went reasonably well if not long and a little tedious rebuilding the database by hand.
10 days after the upgrade it all went very wrong.
1st thing was voicemail would not work. One of our techs went to site and tried all manor of things and eventually got it working by changing the IP address of the IPO from 172.16.10.14 to 172.16.10.3. This should not make any difference but it sorted V/M.
Not 98% of the phone Managers will not find the IPO. also we have another IPOon the same subnet connected via SCN. 406v2 presently 3.2(59) waiting for upgraded memory 406 to replace it to make both units 4.0(10). Phone Managers do not find either machine via broadcast or by specifying either IP Addr.
All machines are small, good spec Dell PC's runnning very little. Machines are installed from a Ghost file and given to users. They are running FSceure AV but this has been uninstalled and makes no difference. PC's have MS Office, Lotus Notes and an AS400 Terminal client and not much else.
The TFTP server see's the PM PC's broadcast a TFTP request for nasystem/who_is but never see a response.
My laptop works fine, other Tech's laptop works fine, PM on VM Server works fine and approx 5 users out of 75 work no problem but not others.
I am pretty sure if he re ghosts his user machines they will start working. My concern is that this has been caused by a windows hotfix or something similar and we wil reghost 75 machines and then be at square one in 2 weeks or so!!!
Anyone seen anything similar??
IT is not the IPO. I took out another IP500 and connected it via a hub to a machine that doesn't work and it made no diffence. This is with the IPO in default and with the customer DB in place.
Me and the customer are now seriously considering giving up and working for the council on the bin's!!!!!!
Jamie Green
ACA:Implement - IP Office
ACS:Implement - IP Office
Fooball is not a matter of life and death-It is far more important!!!!
Everything went reasonably well if not long and a little tedious rebuilding the database by hand.
10 days after the upgrade it all went very wrong.
1st thing was voicemail would not work. One of our techs went to site and tried all manor of things and eventually got it working by changing the IP address of the IPO from 172.16.10.14 to 172.16.10.3. This should not make any difference but it sorted V/M.
Not 98% of the phone Managers will not find the IPO. also we have another IPOon the same subnet connected via SCN. 406v2 presently 3.2(59) waiting for upgraded memory 406 to replace it to make both units 4.0(10). Phone Managers do not find either machine via broadcast or by specifying either IP Addr.
All machines are small, good spec Dell PC's runnning very little. Machines are installed from a Ghost file and given to users. They are running FSceure AV but this has been uninstalled and makes no difference. PC's have MS Office, Lotus Notes and an AS400 Terminal client and not much else.
The TFTP server see's the PM PC's broadcast a TFTP request for nasystem/who_is but never see a response.
My laptop works fine, other Tech's laptop works fine, PM on VM Server works fine and approx 5 users out of 75 work no problem but not others.
I am pretty sure if he re ghosts his user machines they will start working. My concern is that this has been caused by a windows hotfix or something similar and we wil reghost 75 machines and then be at square one in 2 weeks or so!!!
Anyone seen anything similar??
IT is not the IPO. I took out another IP500 and connected it via a hub to a machine that doesn't work and it made no diffence. This is with the IPO in default and with the customer DB in place.
Me and the customer are now seriously considering giving up and working for the council on the bin's!!!!!!
Jamie Green
ACA:Implement - IP Office
ACS:Implement - IP Office
Fooball is not a matter of life and death-It is far more important!!!!