IP Office - IP Office Assistance

February 14, 2014July 27, 2014IP Office

Upgrading a UCM to R9

Because release 9 has an OS update for CentOS, you can NOT use the zip files to upgrade a UCM to release 9. You must re-image the UCM (or Application server) If you do this all settings will be lost, so please backup first here….

Application servers will use a DVD for re-imaging, not the USB stick.

First you should backup all data that is necessary, See the post here on how to backup all files.

Second, you will need to build a USB stick for this. Per Tech Tip 260 from Avaya, below are the supported USB devices.

February 14, 2014July 18, 2014IP Office

Restoring UCM or Application Server settings

Earlier, we backed up our config on an Application server.

Then we upgraded the Application Server.

Now we need to restore the Application server info.

Lets restore voicemail first.

Find the “Wavs” folder you backed up. Using your SSH (maybe FileZilla) replace the “wavs” folder with your folder. This will put all recordings on the Voicemail server. Remember, you will navigate to the root directory of the machine.

In the remote site entry, erase everything except the “/”, or at the top folder where it says filename, double click on that, until you are at the top level directory (root directory)

February 14, 2014July 18, 2014IP Office

Backing up UCM or Application Server

Questions have been coming in regards to the process of backing up a UCM or Application server for an upgrade to R9. While this is mostly the same as a Windows upgrade, there are a few different steps.

First you are going to need an SSH client, to connect to the server. I like Filezilla, but the choice is yours.

First lets backup Voicemail Pro.

You will need to set up your connection to the UCM/APP Server, below are the settings:

Host: IP Address of the server
Username: Administrator (older units default used “web”)
Protocol: SFTP or SSH
Port: 22
Password: Administrator (older units default used “webcontrol”)

January 2, 2014July 18, 2014IP Office

R9 Mobility (VoIP setup)

With IP Office Release 9, Avaya made some enhancements to the mobility client (video here).

If you followed the following tutorial, on setting up Preferred Mobility on 8.1, you are half way there. Once that you have the Preferred mobility set up, you can follow these next steps, to get the VoIP portion set up to take full advantage of the new features.

First, we need to go into the IP Office and enable some features.

We need to turn on the “SIP Remote Extension Enable” by ticking the box in the LAN1 (or LAN2, but not both)>VoIP tab

November 25, 2013September 24, 2014IP Office

Deleting VM Pro backups in Linux Installs

If you are doing automatic backups in Voicemail Pro, those backups have a unique file name, for every file. If you are doing daily backups, the file name has the date of the backup in the name.

The problem here, is that the backup does not overwrite itself, and you will soon have a bunch of backups. Normally this isnt an issue, but with the UCM, and a more limited storage, can take up a of space.

So, lets see how to remove some of these files. Luckily Avaya has a perl script built into the UCM, so we just need to point to that and BOOM! WE GOOD!

November 4, 2013September 11, 2015IP Office

Basics of Virtualization with IP Office

Updated for 9.1

This is not intended to be the only document needed for implementation, but merely to spell out the general steps needed to begin deployment.

The first benefit of Virtualized Server Edition, is that there is no hardware or server to purchase. You can have an SCN of any mixture of virtual, server based or IP500 appliances in that SCN.

For EVERY virtual server edition, you will need a “Virtual Server Edition” license (275694-IPO R9 VRTULZD SE ADI LIC) and for every server based and/or IP500 appliance, you will need a “Server Edition” license (275658-IPO R9 SE ADI LIC).

October 31, 2013May 18, 2014IP Office

Delayed Auto Attendant on IP Office

Auto Attendants on IP Office are very capable with either Voicemail Pro or Embedded VM. Both are a very good solution, but can be cumbersome in setting up a delayed Auto Attendant. While there are several ways to accomplish this, this article describes the most reliable and versatile way of accomplishing the task. Basically, HG -> User -> SC -> AA is the method.

1. The first step is to creat the AA in voicemail (pro or embedded) and create a shortcode that calls the Auto Attendant. For Embedded Voicemail the code would be:

September 15, 2013June 17, 2014IP Office

Allow users to change their own VM Passwords

So, a few days ago, I posted a blog about a module from Austin, for a way to take a range of extensions, and change the mailbox password in Voicemail Pro. This is pretty awesome if you need to set a default password, and don’t want to leave it blank.

But, it came up that someone wanted to automate it so the telephony admin would never be needed. If a user lost their mailbox password, they wanted to give the end user the ability to reset it, with out the admins intervention.

At the bottom is a link to download the module for Voicemail Pro.

September 13, 2013July 9, 2014IP Office

Change range of Voicemail Passwords – VM Pro

This was reprinted , with the permission of the author, Austin A.

Necessity is the mother of all invention. I needed a way to setup voice mail codes quickly for a lot of extensions. Wrote up this VM Pro module to do the work.
Module asks for start of range, end of range, and pass-code to set. Then loops through extension list finding valid user/mailbox extensions. If it finds a HG or non-existent extension, it skips it. Does this until the last one, then notifies you of completion and then disconnects.

September 11, 2013July 9, 2014IP Office

How to set up Overlap Dialing in Voicemail Pro

Sometimes it will come up that a customer wants to use a certain selector code, that interferes with the dialing plan. I don’t know if there is a technical term, so from this moment on, I will refer to it as “Overlap Dialing”. So, to go along with this massively creative title, we will discuss how we can overcome this obstacle.

Below is a generic Auto Attendant. Note that the extensions are in the 2XXX range.

So, as you see, anyone that dials an extension that begins with a 2, it transfers to the appropriate user. But, what if we need to set up a selector code, that allows the button press of 2, to transfer to the Group, “Service”.