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.

Resetting WebLM Password on Avaya SBC Enterprise (ASBCE)

I ran into an issue today when upgrading to version 8.1.3 where my WebLM username/password did not work anymore and the licenses got uninstalled. Apparently this is a known issue. It’s now known to me.

Below are the steps to reset the password to the default admin user.

Step 1: Stop the service

Run the following command to stop WebLM:

service ipcs-ems stop-weblm

Step 2: Modify the Users.xml file that WebLM uses

Change your directory to where the Users.xml file is located:

cd /usr/local/weblm/server/webapp/admin

Backup the existing file

cp Users.xml Users.xml.original

Extract the Users.xml file from the upgrade tar.gz. Below is where it is located inside the file:

sbce-8.1.3.0-31-21052-563c74d7bdc7b0d1115031a5fa0f1927.tar.gz\sbce-8.1.3.0-31-21052.tar\sbce-8.1.3.0-31-21052.iso\Packages\weblm-server-8.1.3.0-2.noarch.rpm\weblm-server-8.1.3.0-2.noarch.cpio\.\usr\local\weblm\server\webapp\admin\Users.xml

Move the file from the tar.gz to the server

Step 3: Restart the service

Run the following command to stop WebLM:

service ipcs-ems start-weblm

Step 4: Login with the default credentials

Username: admin

Password: weblmadmin

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.

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.

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

Installing Certificates on IP Office and an Avaya SBC

This port will cover the commands required to generate a p12 file for upload in both IP Office and an Avaya SBC.

IP Office requires a (.p12) file to be uploaded while an Avaya SBC requires that the key, certificate and chain be upload separate rather than packaged in a (.p12) file.

 

Getting the client certificate file

This file should be provided by your certificate authority. They may provide it as a (.pem) file. For our purposes save the file as client-cert.pem

Avaya IP Office DHCP Option 242

Option 242 is used to give the phone the required parameters that it should use to connect to the PBX. There are two scenarios in which you can use option 242.

 

I am going to use the following VLAN IDs in my examples:

• VLAN 100 – PC/Server Network
• VLAN 200 – Voice over IP Netowrk

 

Scenario 1: Separate VLAN for Voice and Data

This is the most common configuration for VoIP networks. This works by having the option 242 set in both VLANs however it will be different in both.

Useful Avaya IP Office URLs

IP Office 500v2

Web Manager: https://<ip-address&gt;:8443/WebMgmtEE/WebManagement.html

IP Office Server Edition or Application Server