In several functions of IP Office and network equipment management, email is sent from an automated process to a recipient via SMTP. SMTP is a fairly simple protocol that can be emulated via command lines. Using these command lines, setup information can be verified about the server to which the message is being sent. The only tool necessary for this test is telnet. The commands do have to be fairly exact, but are not hard to implement. (more…)
In each Windows server resides a time server compatible with IP Office. There three methods of updating the IP Office time: manually, via Vociemail, or via a timeserver. Using a Windows server is the most universal, since it does not rely on Voicemail Pro being installed. On occasion the update does not happen. The update should run every hour to synchronize the IP Office with the time on the server. In order to debug this process logging can be enabled on the server.
On UMS default installs, users may get in the habit of entering just the server name, and not adding the entire sub-directory for accessing the web application. This results in an unexpected page with an Under Construction message or a picture displaying IIS7. Either way it’s not UMS, and could be frustrating for a end user. Changing the root directory to be the voicemail directory will break the application as the paths will break the UMS webservice. A simple solution is to setup a redirect. Read more to see how…
This is per Compas ID 136708 (TB 97).
The following are a list of applications and supported operating systems.
With the new proliferation of Vista on desktops in the marketplace, some traditional practices like fixing firewall permissions can get hung up. The easiest way to ensure that firewall permissions are correct is the AvayaFW.bat script. The script checks the registry to see what programs are installed then writes the ports associated into the exceptions in the firewall. On Windows XP, this batch file runs with a double click. On Vista and Server 2008 the batch file requires elevation to run properly. Right click on the AvayaFW.bat icon and choose ‘Run as Administrator…’. This action will require administrator level access or password.
Avaya released two new versions of firmware for it’s IP Office product line on Friday, July 11. The releases are the typical quarterly maintenance release for the 3.2 and the 4.1 firmware. Both releases clearly state that Windows XP Pro Service Pack 3 is supported for all applications supported on Windows XP Pro. Links in the full article.
Currently Server 2008 is not supported by Avaya for any IP Office Applications (Voicemail Pro, CCC, Contact Store, Delta Server, Wallboard Server, etc.). Some of the applications are supported on Vista Business. In the Microsoft development methodology, Server 2008 is for Vista like Server 2003 is for XP. So it may possibly work to some extent and I decided to give it a try.
Sometimes the Microsoft .NET install can get corrupted which can make it very hard to uninstall. This can also make your applications crash and get .NET 5000 error. This error can be seen in the event viewer on the under computer management.
There are several applications that have to run as an administrator user but you don’t want to make that user an admin on the domain. This can be accomplished by adding a regular domain user as a local admin to the computer where the apps are going to run. This does not mean make a local user on the computer and add them to the admin group.
Microsoft has announced that it will stop selling all retail versions of Windows XP on June 30th. System builders will be able to sell computers with XP installed until January of 2009, at which point they must sell these systems with Windows Vista. As of this writing the End of Sale for Server 2003 has not been announced. It’s replacement OS, Server 2008, has only been released in February, and is expected to ramp up strongly this year.