Yep, it's a bad deal. Maybe Avaya will come around, I doubt it though. I had a customer in the same situation. They pulled out the Call Pilot and installed Avaya Aura Messaging. It works OK, but is not as friendly as Call Pilot. Plus it requires SIP trunks for integration which pushes you into System and Session Manager if done by the book. You can do it with NRS but not fully supported. You have about a year left before 2003 Server goes end of support.
Look into AVST CallXpress. It is a great Voice Mail system that integrates well with Avaya. It also comes with different emulations so you don't need to retrain users.
With AAM 6.3 there is now a CallPilot TUI...makes it a LITTLE easier to migrate. If you had a 1006 server, you could also use the same hardware (with upgrade kit).
Best you can do for now is upgrade to CallPilot 5.1 and apply any service updates or patches to get yourself up to the most current release. What's that? Can't get those files? Gotta call your Nortel/Avaya vendor and have them do that for you.
MS will likely still support 2003 if it's an embedded version past the date they stop supporting OEM/retail. I suspect in the upcoming months, this will be addressed by Avaya.
In the meantime, you will want your CallPilot system to reside as far far away as possible from the internet too, as Nortel/Avaya does not like when people just start throwing MS patches on CallPilot systems (the 'approved' MS security updates are part of the normal SU/patch updates). Generally speaking - so long as traffic to/from the CallPilot system cannot be routed to/from the internet, they're updated exactly to Nortel/Avaya specs by a vendor, and you're not adding any 3rd party applications to it, the WinNT and Win2003 OS's running CallPilot are extremely stable and should not pose any risk to your enterprise.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.