FreePBX 17 Phones Not Registering Properly on Physical Server

Previously, I had installed FreePBX 17 on a virtual machine (VM), and all my phones were successfully registered and working perfectly.

Later, I installed FreePBX 17 on a physical computer. I copied the exact same XML configuration files to the new system. I also configured the IP settings, firewall, and all other necessary parameters correctly.

However, now out of many phones, only two of them register with difficulty. They can call each other once, but then they stop working properly.

In the CLI, I am also receiving messages indicating that authentication is failing or not being accepted. I have already shared an example of these messages.

At this point, I would like to know what the proper solution is. Should I switch back to using the VM, or can this issue be resolved on the physical PC?

Below is a sample SIP log for reference:

<— Transmitting SIP request (477 bytes) to TCP:172.xx.xx.14:50903 —>
OPTIONS sip:[email protected]:50903;user=phone;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 172.xx.xx.254:5060;rport;branch=z9hG4bKPjcc155b53-d67e-453b-bc8c-23287402e75b;alias
From: sip:[email protected];tag=56ac04da-bcac-438a-9bf4-82c1077cb057
To: sip:[email protected];user=phone
Contact: sip:[email protected]:5060;transport=TCP
Call-ID: 2809cdbb-fcea-4327-9ac6-a4ac895feeaa
CSeq: 13767 OPTIONS
Max-Forwards: 70
User-Agent: FPBX-17.0.28(22.7.0)
Content-Length: 0

<— Received SIP response (1327 bytes) from TCP:172.xx.xx.14:50903 —>
SIP/2.0 200 OK

I would appreciate your guidance on resolving this issue.

Hi @faizi
You don’t need to switch to VM you can carry on on the Hardware side..
I m thinking could be your Extensions Password or details are not applied corrctly to your FreePBX side. ? So How you restored Extensions from VM to HW ? Full backup or you did use Bulk Handler ?

  • Check 1st Extensions Password and change it 1 more time at FreePBX side.
  • Compare XML phone configuration side PJ_SIP Port and Extension details ( Ext number and Secret )
    and use SNGREP tool to get more details with Asterisk CLI..

Nothing has been messed with; I know that a small mistake can cause a big problem.