How To: Enable Root Login on a UC Module (IP Office)

Below are the steps to enable root access on a UC Module using WinSCP

1. SSH into the UC Module using the Administrator account
2. Edit the sshd_config file by entering `vi /etc/ssh/sshd_config`
   • To begin editing in ‘vi’ type the letter i
   • Go to the line that says “PermitRootLogin” and change no to yes
3. Save the file
   • To save press the Esc button then type 😡
4. Restart the ssh daemon by using the command `/etc/init.d/sshd restart`

That should be all you need. Thanks to my coworker for providing this useful tip.

Avaya IP Office – SIP proxy list is empty

Today I ran into an issue at a customer’s location that was preventing any J-Series phones (specifically a J139…not that it matters) from working.

We had DHCP option 242 configured so that phone would auto-provision themselves. We would get to the point where the phone would give us an error saying:

SIP proxy list empty

Checking the Monitor

I launched IP Office Monitor and cleared all my filters. I then added the following filters:

• Services > HTTP (Verbose)
• System > Error
• System > Print

I then rebooted the test phone.

I saw in the Monitor logs that it was attempting to connect to the IP Office however it was being given a 404 from the IP Office. See the sample output below:

2022-03-28T16:29:24    5244557mS PRN: Service Access Connection from 10.4.70.40(37138) to Port 80
...
GET /J100Supgrade.txt HTTP/1.1
...
2022-03-28T16:29:39    5259348mS HTTP: File Load Timeout: /J100Supgrade.txt
2022-03-28T16:29:39    5259349mS HTTP: DisconnectIndication reason 2 code 0
2022-03-28T16:29:39    5259349mS HTTP: SendErrorResponse Code: 404, Entity: Relay Server File Does Not Exist

This told me that the phone was unable to pull down the J100Supgrade.txt file which updates the firmware of the phones as well as it points to the 46xxsettings.txt file which populates the configuration.

The Fix

The fix was to go into Web Manager and set the System > System > Phone File Server Type to be Memory Card instead of Manager.

Credit goes to Jason where I found the solution. I wanted to post about in for the next guy that may run into this issue.

Avaya IP Office 46xxsettings error

Today I got the error

URI contains invalid FQDN. DNS failure.

when trying to download the 46xxsettings.txt file.

The solution was to populate the DNS Server IP Address in IP Office Manager.

Go to System > DNS tab

There you can enter the DNS server you’d like to use.

Avaya Equinox – Configuration file is invalid

The problem

I had a problem with Avaya’s Equinox the error was “Configuration file is invalid”.

The 46xxsettings file is correct however it is NOT auto-generated. This is because I needed some custom settings.

The solution

The solution ended up being that according to Avaya, if I have a custom 46xxsettings file then I am not allowed to have the “GET 46xxspecials.txt” part at the end of my file. Instead I needed to merge my 46xxspecials with my 46xxsettings. Once I did that the error went away.

Screenshot

 

Avaya Equinox – Failed to download all certificates

The problem

I recently encountered a problem with Avaya’s Equinox where I got the error “Failed to download all certificates”. The 46xxsettings file is correct and this worked fine up until now. Just all of a sudden it started doing this.

The solution

The solution ended up being that my WebRootCA certificate is missing. WHen I navigated to https://<ipo-ip-address>/WebRootCA.pem I was not presented with a Save dialog box. On other systems I was. I had to reupload the 3rd party signed certificate and then it worked like a charm.

Screenshot

Disable PC Port Avaya IP Office via 46xxspecials.txt

Disabling the PC port in IP Office is a simple edit of the 46xxspecials.txt file. I will refer to this file as 46xx in this doc to avoid retyping. Keep in mind that you can also disable the port in the CRAFT menu however on some older versions of IP Office this may be necessary.

Check for auto generated 46xxspecials.txt

First thing we need to do is check if you have an autogenerated 46xxspecials file. Navigate to https://<ipo-ip>/46xxsepcials.txt

If the top line contains “AUTOGENERATED” then you are fine to create a brand new 46xx. Otherwise if it is not auto generated then you should take a copy of the custom file and modify it then reupload.

How to upgrade Avaya J-Series phones to SIP 4.0 to use JEM24

The Avaya JEM24 requires SIP version 24 to work. Otherwise you will plug the unit in and receive a black screen. The page button will light up but the unit will not be usable.

Avaya Vantage K175 – Login Issues

I’ve recently had the “pleasure” *insert sarcasm* to deploy an Avaya Vantage K175. This is the full touch screen Android based phone. I ran into an issue where the phone was not using Vantage Basic. Instead it was using the standard Vantage application which requires a license that the customer does not want to purchase.

The solution is get the phone to use Vantage Basic instead. When I went to the Android settings I am unable to change the settings. When I click “Admin login” nothing happens. There is where I could typically change the setting. What I ended up having to do was go to the root of the IP Office HTTP server and create the 46xxsettings.txt file. Add the following:

IF $MODEL4 SEQ K175 GOTO SETTINGSK175

# SETTINGSK175
SET ACTIVE_CSDK_BASED_PHONE_APP “com.avaya.android.vantage.basic”

 

Save the file and reboot the phone. This will tell the phone to use the Vantage Basic application.

Let me know if this helps you out.

 

 

Custom Backgrounds on Avaya J169 and J179 Endpoints

Custom backgrounds on the J series phones are very easy. It requires settings to be placed in the 46xxsettings.txt file located on the root of the IP Office’s HTTP server. It is advised that this file stay auto-generated. At the bottom of the file is a line that includes the 46xxspecials.txt file. This is where we will make our customization.

One thing to keep in mind is that the image resolution MUST be 320×240 otherwise it will not work.

Parameters

The lines that need to be added are:

SIP Trunks between 2 IP Office PBXs

There are the steps I took to configure two IP Offices to be connected via a SIP trunk.

Intro

First lets go over a few things to verify before you start:

1. Both systems are licensed
2. Both systems have SIP Trunking enabled (System>LAN1>VoIP – Check SIP Trunks Enable)

Here is some information about the systems I am connecting:

IP Office 1 (IPO1)

• Version: 11.0
• IP Address: 192.168.42.230
• Incoming/Outgoing Group: 16

IP Office 2 (IPO2)

• Version 10.1
• IP Address: 192.168.99.95