Assist - IP Office Assistance

December 13, 2024December 13, 2024IP Office

IP Office Release 12.1

IP Office Release 12.1 went GA on December 5, 2024 and here’s what to expect with the update.

R12.0 License is Valid for R12.1

There is no specific 12.1 license – the R12.0 license is valid for both 12.0 & 12.1. Version 12.2 may be released sometime in 2025 but we don’t know if it will require unique licenses or not.

Linux Versions contain IPv6 Support

The Linux versions of IP Office (Server Edition, Virtualized, etc.) now contain IPv6 support. It appears this support only extends to communications between SIP phones and/or a session border controller. There is an implication in the release notes indicating external SIP trunk IPv6 support does not exist at this time. The 500v2 chassis does not support IPv6.

August 21, 2024August 21, 2024IP Office

Troubleshoot Avaya Workplace – Failed to Parse all Certs

Problems with registering the Avaya Workplace Client for Windows? We have some troubleshooting tips for you! Follow this step-by-step guide.

Avaya IP Office CLI runaway Java process

August 8, 2024August 8, 2024IP Office

IP Office Runaway Java Issue on R12

Read this article for tips and tricks to deal with the IP Office runaway Java issue - the high usage process causes Web Manager to become unavailable.

May 14, 2024May 15, 2024IP Office

IPO R12 Now Available

Avaya IP Office release 12 is now available on PLDS.

One of the things we noticed right away was that our Demo IPO 500v2 with an R11 license seemed to run without errors or warnings on R12. We’re not sure if this is intentional or whether the system will go into grace mode eventually because it’s only been a few hours so far.

The GA bulletin regarding R12 has been published as GlobalIPOfficeTechnicalBulletinR12.0GA and of particular note in the document is the statement “There are no additional Service Packs planned for R11.1 after 11.1.3. Service Pack 2 June 2024 all future fixes will be delivered in R12 Service Packs.”

April 25, 2024May 14, 2024IP Office

IP Office Release 12

IP Office Release 12 is planned for general availability by April 30, 2024 and here’s what to expect with the update.

OS Change to Rocky Linux

The backend OS for Server Edition and Application Servers is changing from CentOS 7 to Rocky Linux 9. This is coming just in time since CentOS 7 is slated to be end-of-life as of June 30, 2024. It also means that the upgrade is more complex than some previous major releases. It is, however, expected to be much the same as the process was for going from R11.0 to R11.1. Fortunately, Rocky Linux should be much easier to upgrade than the process was for CentOS 6 > CentOS 7 > Rocky Linux 9.

January 6, 2023April 30, 2024IP Office

Set time on IP Office

VM Pro/Manager:

The time is normally obtained using Time protocol (RFC868) requests. Note this is different from Network Time Protocol (NTP). The Voicemail Pro server and the Manager program can both act as Time servers, other RFC868 server sources are not supported.

If the IP Office system time is wrong, open Manager, and check:

System ➤ System tab ➤ Time Setting Config Source = VoiceMail Pro/Manager

Note that if you are running Manager when the Voicemail Server starts, Voicemail does not start it’s time server daemon. Therefore, always close Manager before you start or restart Voicemail Pro.

September 3, 2021April 30, 2024IP Office

Re-config IP500 w/DTE

The DTE port on the back of an IP Office Control Unit is not normally used when configuring an IP Office system. However the DTE port can be used to erase the system’s operational software and/or configuration if necessary.

Due to the drastic nature of these actions they should only be performed if absolutely necessary to return a system back to working order. In either case you must ensure that you have a backup copy of the system configuration.

Access to the DTE port requires a serial cable between your PC/Laptop and the IP Office (such as a standard modem cable).

June 29, 2021April 30, 2024IP Office

Editing an IP Office configuration in Excel

Back to IPOfficeHelp.com

HOWTO: Editing an IP Office configuration in Excel
Kyle L Holladay, Sr

Many items in your IP Office configuration can be edited directly in the configuration.csv file outside of the Manager application saving a large amount of time. This guide will provide basic information on how to export your configuraiton.csv and edit select User information. Until you are comfortable with this method I would suggest that you limit its use to a lab environment

Note: You MUST NOT add nor delete any records when using this method. (i.e. you cannot add/delete an extension, user, incoming call route). You must create all records in Manager before doing your Export. You can then modify the information associated with that record using the method below.

February 22, 2021May 3, 2024IP Office

Use hunt group status in Voicemail Pro call flows

This post describes you how to use the different status of a hunt group (in service, night service, out of service) as a switch within Voicemail Pro call flows. Posted from Florian Wilke’s site: (https://blog.fwilke.com/use-hunt-group-status-in-voicemail-pro-call-flows/#more-865)

The challenge

Didn’t you have the challenge that the local users should be able to switch between different ways a call should flow through Voicemail Pro? And wouldn’t it be nice if it were possible to do this through a phone button? And furthermore… shouldn’t it be possible to light the button if a chosen condition is set? And all that from different users and phones?

September 25, 2020May 3, 2024IP Office

Configure Avaya CPaaS SIP Trunks with IPO

There is a commercial offering for Avaya SIP trunks, See this doc.

In a pinch if we needed some trunks for a customer, we have used Avaya CPaaS for SIP trunks. This is (so I have heard) the equivalent of a Twilio SIP trunk.

You can claim a number in less than 10 minutes, and provision the IPO in as much.

First, let’s set up the SIP trunk and grab a new number. Go to cloud.zang.io.

CREATE A DOMAIN

From the dashboard, go to SIP>DOMAINS.

Click on Create SIP Domain

Assign the domain name. The Domain name you enter will prepend the “sip.zang.io”. Give the Domain a friendly name.