July, 2014 - IP Office Assistance

July 31, 2014August 28, 2014IP Office

IPOA Configuration Issue

When setting up the IPOA image, we deploy an ISO or OVA image, then we log into admin and convert from IP Office Server Edition, to IPOA.

There is an issue with 9.0.800-941, where part way through the process, you get an error that stops the process altogether…lets take a look and fix it….

Not sure what release this is or will be fixed in…..

After you have the image installed, you see IP Office installed, as shown by all the services running.

Next, we need to uninstall the “IP Office” package.

July 23, 2014IP Office

How to Manipulate Digits In VM Pro

Would like to thank Andy Ertle at Tier4 Industries (aertle@tier4industries.com – (303) 632-0411)
for pointing us in the direction of “Digit Manipulation” for this post.

For some of our other posts we routed calls by Area code. If receiving 10 digits those would work. But, for whatever reason, if you are inserting a “1” or “91” so you can dial from the call log.

If you are having caller ID come in and include the “1” for instance, we can strip that digit off.

July 21, 2014August 9, 2014IP Office

Route Calls by Area Code in Voicemail Pro

There are a couple ways to route calls via caller ID. Using database routing is neat and simpler, but you need Advanced Edition, so this will not work for Server Edition. Using the “Variable Routing” action, makes this possible on Server Edition though. Not as clean as a database, but it is what it is.

Voicemail Pro can use a “Variable Routing” action, to route a call based on a variable. The variable we, obviously would use to route a call by area code, would be $CLI.

July 15, 2014IP Office

How to set up remote access menu

How to create a remote access menu, compliments to Kyle L Holladay, Sr. R.I.P.

1. Download and extract the pre-configured module and associated .wav files

2. Copy the .wav files to x:\Program Files\Avaya\IP Office\Voicemail Pro\VM\WAVS\yyy\Custom (where x=the drive where VMP is installed and yyy=your locale, such as enu)

3. Import the module contained in the menuRemote.mod file into your current Voicemail Pro configuration.

4. Click on the Save & Make Live icon in Voicemail Pro to save the current configuration.

July 9, 2014September 22, 2014IP Office

Set Up Delayed Ringing To Embedded Voicemail

Forward to Embedded VM AA after ringing a hunt group
Compliments of Kyle L Holladay, Sr, R.I.P.

In this example we will route inbound calls to a hunt group and then forward to an Embedded Voicemail Auto Attendant if unanswered after 15 seconds or immediately based on a time profile or “night service” button.

1. Create your Embedded Voicemail Auto Attendant.

2. Create a Short Code (such as *90 in the picture below) that is used to access the Auto Attendant.

3. Create a phantom user and assign it an unused extension (such as 1999 in the picture below) that will be used to forward to the Auto Attendant. On the User’s forwarding tab enable forwarding options (see image) and enter the short code you created above as the forwarding number.

July 6, 2014July 7, 2014IP Office

IP office Remote Access Options

The following are the Avaya recommended remote access options.

• Remote Manager: Default RAS connection to the IP Office.
• Dameware: 3rd party application supplied with each IP Office application CD and is a free install. This software needs to be installed on any PC on which the application requiring support is running. For example, if Voicemail Pro is installed on a separate PC from that of Manager, then
Dameware needs to be installed on both PCs for access to both applications.
• PC Anywhere: Third party application that is licensed to the host and client. PC Anywhere is NOT provided by or licensed through Avaya. This software needs to be installed on any PC on which the application requiring support is running. For example, if Voicemail Pro is installed on a separate PC from that of Manager, then PC Anywhere needs to be installed on both PCs for access to both applications. Avaya Technical Support will use PC Anywhere to aid in the troubleshooting of certain issues, but the business partner must provide connectivity to the site
and username and password information.
• Webex: This third party application is a client service and requires customer interaction. This application is NOT provided by or licensed through Avaya. Avaya Technical Support can also use Webex as a remote desktop client for troubleshooting and data collection. With this application, the Avaya Tier 3 engineer assigned to the trouble ticket will provide access information to an Avaya qualified BP engineer. Internet Explorer 6.0 or newer must be available to use Webex.