Windows
Running VMPro on Server 2008
by DougR on Jul.16, 2010, under Avaya, Documentation, IP Office, Server 2008, Windows
Voicemail Pro has been compatible with Microsoft Server 2008 for some time. The server platform can offer some robust features and better security, but can also be a source of frustration. A few things to watch for are the new firewall settings and UAC. While these are nothing new for Microsoft operating systems, not everyone is familiar with them. (continue reading…)
Windows 7 launch
by DougR on Oct.27, 2009, under Avaya, IP Office, Microsoft, Win7, Windows
Thursday, October 22nd was the big date for a Windows launch. There is a great deal of buzz surrounding the launch of Microsoft’s new OS. Many experts predict that a slowdown in PC sales have been due to the anticipation of the new operating environment. Based on this theory, the expected result is a sharp adoption rate of the new OS. Most likely you will have a customer that adopts the new OS and forces you to look at the compatibility of Windows 7 and the communications infrastructure. Both the voice and data network interactions have changed somewhat. Evaluating both systems is important, for now lets look at the voice portion and the status of IP Office features.
netstat with sanity
by DougR on Jun.26, 2009, under Documentation, General, Microsoft, Technology, Windows
The command netstat is a handy tool for displaying the active ports and addresses on a Windows or *nix machine. For the Windows environment often the output scrolls past the buffer for the command prompt window, thus loosing important information about lower port numbers.
Test IMAP with Telnet
by DougR on May.26, 2009, under Avaya, Best Practices, Documentation, IP Office, Windows
So the new UMS server enables users to connect via IMAP (a standard email protocol) from any client. The new interface frees users from the confines of IMS requirements of Exchange and Outlook, and the required cumbersome process of installation. UMS simply installs and it’s good. Setting up clients are about as easy as setting up any other email account. In the rare case that a client does not connect, here is a simple method to test the the IMAP interface on the UMS server is responding correctly.
GOT QUESTIONS – GET THE MATRIX
by Glenn Griffin on Mar.27, 2009, under Avaya, Documentation, General, Hardware, IP Office, Juniper, Microsoft, Windows
CAN’T REMEMBER THE UPGRADE PATH TO GET FROM 3.0.x to 4.2.14?
DOES THE 4406 PHONE WORK ON A 500?
WHAT KIND OF SERVER AND OS DO I NEED FOR UMS?
-All these questions and many more answered by the IP Office Matrix. The matrix is a multi-tabbed spreadsheet you can download from the partner website. If you already have a login for the partner site simply login and search for ‘IP Office R4.2 Matrix’ . If you don’t have an account you can sign up for one.
2009 IP Office Microsoft Compatibility
by DougR on Jan.05, 2009, under Avaya, Documentation, IP Office, Microsoft, Windows
Avaya released an update to the software compatibility with Microsoft OS, and browsers. The update is released in Technical Tip 218 and includes many of the newer options for installation with Microsoft products. Included are Server 2008, Vista, and 64-bit compatibility references.
http://marketingtools.avaya.com/knowledgebase/ipoffice/mergedProjects/bulletins/techtips/218_techtip.htm
Server Options for 1600 series firmware
by DougR on Dec.04, 2008, under Avaya, Best Practices, Documentation, IP Office, Windows
The new 1600 series phones are a value version of the 9600 series phones. The phones are different from the 4600 based phones that have been used in the past. The first difference is that the phones use the SSON (Site Specific Option Number) 272 in DHCP to set the options for the phone. The second difference deals with how the phone firmware is updated.
Traditionally phones contacted a server via TFTP to download firmware and settings files. The 1600 and 9600 series phones use HTTP. This offers several advantages and makes administration a bit more main stream. Here are a few options for the HTTP server required for these phones.
Test SMTP via telnet
by DougR on Nov.05, 2008, under Avaya, Best Practices, IP Office, Microsoft, Windows
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. (continue reading…)
Debugging Windows Time Server
by DougR on Nov.03, 2008, under Avaya, IP Office, Microsoft, Server 2008, Windows
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.
UMS Webservice gets IIS Start page
by DougR on Oct.27, 2008, under Avaya, Best Practices, IP Office, Microsoft, Mobility Solutions, Server 2008, Windows
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…
