Search results for query: *

I have absolutely no problems in going from 2.1 to 2.99 to 3.2! The 2.99 replaces the boot-loader so that 3.2 can be loaded.

Why via the 3.1(65) ??

First upgrade it to the 2.99 build. Then the 3.2(54) build. Nice and easy ;-)

Have you disabled "H323 fixup" ?? If not, then i bet that's why the phone is registered wrong!

Disable "H323 fixup" in the Pix, and maybe the ASA :) That's it!

About multiple voice-servers in SCN enviroment: We have systems running with SCN enabled, and multiple VM Pro servers at different locations. We haven't run in to specific issues in this scenario. But as mentioned above, it's not supported by Avaya...

It should work fine with those extension numbers! I would use this setup: Create an IP route for the other site Now check that you can ping both IPO's from the remote sites. Make a VoIP-line with the following settings: Line number: Use a number that's different from the other lines...

one error: "Gateway" on the VOIP-tab should not be set to the local gateway, it should be set to the IPO in the other end.

All released 412's can run the the newest versions :)

What about the "Display msg" function? Haven't had a chance to play with it in this scenario though.

Maybe it's the future upgrade to 4.x he's worried about. Sadly, 4.x is a no go for pre PCS06 V2's, and some PCS07's Funny thing though: All the PCS07's I've seen has been 64MB versions.

We also have a couple of INDeX guys.... But they have trown away that old routine now! :) We only use intermediate steps if the loader needs an upgrade. Works perfect!

One of my observations: Many "network-only" guys are very unexperienced in working with QoS. We have just had a case, also with Cisco equipment involved, where the Cisco-guys had major problems in getting the QoS working properly. We prefer equipment where we can monitor the routers, and...

Nice to know that it (almost) worked as planned :)

We haven't seen any problems with 412's running the newest versions. That includes some of the first 412's out there, installed when 1.2 was GA. We haven't seen problems on 403DT's running 3.2 either. We haven't seen any documentation stating that "early" boxes, 403DT for instance, should have...

@norstartecky: Why is 3.2(53) unatended for this 412? 3.2(53) is a rather good build, which runs perfectly at many of our customers.

Why talk about DT-related problems when it's mentioned that only analog phones are used? There doesn't exist any 3.1.99 for the 412 :) (only 403/406 needs this boot-loader upgrade) Why wouldn't you upgrade an IP412 with analog extensions only to 3.2 (53) ?!?

Nice warning... Especially when he's running all analog phones! There is no problem in going to 3.2(53) with this setup!

Personally I would go directly to the desired SW on a 412, since it doesn't need any boot-loader upgrade. Instead I would concentrate more on the cfg! As suggested earlier, a rewrite of the cfg would be a good idea :)

I have just installed a system using Cisco equipment (Pix 506 v 3005 concentrator). My phones (4610SW) also came up with blank screens. We disabled the H323 fixup in the Pix, and it have worked perfect ever since :)