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.

read more
IP 500v2 Release 12

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.

read more

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/Managermantad1.png

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.

read more
IP 500v2 Release 12

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).

read more

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.

read more
Avaya J169 SIP Phone

Install SIP phones on IP Office

Had a few calls from customers on SIP phones.  Obviously, if you are using the J100 series on IP Office R11, you are going to have to implement SIP phones.  J100 ONLY run SIP, when connected to IP Office R11.  HOWEVER, they do work on R10.1, but ONLY as h323 phones.  So, why would you downgrade all those phones just to run them on 10.1, when 10.1 will be going EOS with the next major release?  Just upgrade the damn IPO.

So, to get the J series working, we need some settings within IPO set, and then the IPO will autogenerate the 46xxsettings.txt file.

read more
Log into multiple hunt groups Avaya IP Office

Logging into Multiple Hunt Groups

(This post is some info we found from Intrigant on the Tek-Tips SiteMany thanks for sharing this….)

Often, we get asked how a users can be a part of numerous hunt groups, and only log into a couple of them.

Obviously a user can set up a button (“Hunt Group Enable”) and 2 things (well, really 3 now) can happen.

  1.  They leave the “Action Data” blank, which would log the users out of ALL groups that they are a member of.
  2.  They can define a group number or name in the”Action Data” field, and that button will ONLY log them in/out of that specific button.

There is now a third way, again, thanks toIntrigant” that you don’t have to use a button for each group, but can still be a part of many groups and pick and choose which you are logged into…friggin awesome.

read more

SIP Remote Worker

With SIP remote worker, there a re a few things that need to be done, prior to anything working. If using TLS, you need a certificate (Here we created a 3rd party certificate for IP Office).

Once the certificate is set, you need some settings in the IP Office.  Once those are set, your 46xxsettings.txt file should auto-generate.

Here is a video of the specific settings for IP Office:

Equinox Client Setup.  Now you can configure the equinox client.  if you need to configure Spaces, see this thread (Automate Spaces Install).

read more