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.

FusionPBX: Monitoring a Voicemail Box with a BLF Line Key

Recently I had a customer request the ability to monitor a Voicemail box using a BLF Line Key on their phone.

This request isn’t new however. We’ve had numerous customer request this in the past. I decided to add this functionality to the already incredible amount of features that FusionPBX has.

FusionPBX uses a prefix when monitoring different types of applications. For example, Call Flows, Parking, DND etc.

Call Flows as an example uses the flow+ prefix to the extention.

Parking uses park+ as the prefix.

Voicemails as of FusionPBX version 5.0.1 and beyond use the voicemail+ prefix.

Below is an example of what that will look like when programming this for any phone.

As usual, please comment if you like this article and/or you’d like some assistance.

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.

Blocking unauthenticated SIP INVITES on FreePBX / PBXact

Today I noticed a new PBX (PBXact) we deployed for a customer was accepting unauthenticated SIP INVITES from the internet. I had opened port 5060 to the world. Risky, I know. But I had a false sense of security I guess since I was under the impression that FreePBX / PBXact will block and eventually ban failed SIP communication attempts.

It’s true that it was working for incorrect registrations however I noticed that the repsonsive firewall was still allowing random SIP INVITES from anywhere to be routed.

The fix was simple, go tio Settings > Asterisk SIP Settings

In the General SIP Settings tab, set Allow SIP Guests to No

That’s all. Now, when running sngrep, I no longer see my PBXact accepting INVITES from random locations. Instead it sends a 401 Unauthorized message.

Below are the logs (before and after) I got from sngrep

BEFORE

AFTER