Solved Fax server gone after upgrade from v16 to v18?

[Just-a-volunteer]

Hi there, we're a small non-profit where I'm the tech volunteer. We were running v16 and had a system crash. I was able to salvage backups, but not the original FQDN for a number of reasons beyond my control. We were using a *.3cx.us FQDN, which was no longer an option on the new installation. The closest thing was *.state.3cx.us so I created a new FQDN there. The place had been on the 3cx system for at least 7 years - maybe longer.

After I brought the system back to life using a V16 iso, I restored a backup (no FQDN, license) so I wouldn't have to re-provision all the phones. That worked great. I tested everything, then decided to upgrade to V18 since we were using the phone apps and knew we'd be losing that feature at the end of the month on v16.

Unfortunately, many of original features are now gone - like faxing capabilities. We were using the Fax Manager for incoming faxes and an old ATA (with an old Fax machine) for outgoing. These no longer work. The fax number says that it's no longer service since it can't reach the PBX.

I can't provision my iPhone anymore either. The app just hangs when I try to scan the QR code. I'm running the latest version.

Did I miss something along the way? This is my first 3cx install. I've been doing a lot of reading, but I'm sure there's a lot I still don't know. I'm also not proficient in Debian, which is the version we've been using. Any insights would be greatly appreciated.

 

[Evolute IT]

Hi there, we're a small non-profit where I'm the tech volunteer. We were running v16 and had a system crash. I was able to salvage backups, but not the original FQDN for a number of reasons beyond my control. We were using a *.3cx.us FQDN, which was no longer an option on the new installation. The closest thing was *.state.3cx.us so I created a new FQDN there. The place had been on the 3cx system for at least 7 years - maybe longer.

After I brought the system back to life using a V16 iso, I restored a backup (no FQDN, license) so I wouldn't have to re-provision all the phones. That worked great. I tested everything, then decided to upgrade to V18 since we were using the phone apps and knew we'd be losing that feature at the end of the month on v16.

Unfortunately, many of original features are now gone - like faxing capabilities. We were using the Fax Manager for incoming faxes and an old ATA (with an old Fax machine) for outgoing. These no longer work. The fax number says that it's no longer service since it can't reach the PBX.

I can't provision my iPhone anymore either. The app just hangs when I try to scan the QR code. I'm running the latest version.

Did I miss something along the way? This is my first 3cx install. I've been doing a lot of reading, but I'm sure there's a lot I still don't know. I'm also not proficient in Debian, which is the version we've been using. Any insights would be greatly appreciated.

Run a firewall check to see if you have misforwarded ports or closed ports. Also, the fax server is still there, but moved to Advanced in the console.

 

[Just-a-volunteer]

Thanks for the reply. I did the firewall test multiple times but it would only work sometimes. After going back and forth checking everything, it looks like it was a DNS problem. The FQDN had not propagated all the way - at least from what I can tell. It works now.

the only thing not working still is the ATA. It's the "Patton 4 Port FXS GW". I wonder if it's still supported?

 

[ChrisC_3CX]

Thanks for the reply. I did the firewall test multiple times but it would only work sometimes.

You mean the firewall only passes sometimes? That indicates that some additional configuration on the firewall may be required.

it looks like it was a DNS problem.

If the 3CX's FQDN was not resolvable it shouldn't have affected the Firewall checker in any way.

In any case, sounds like you got it sorted so glad to hear everything seems fine now.

the only thing not working still is the ATA. It's the "Patton 4 Port FXS GW". I wonder if it's still supported?

You can check our currently supported devices here: https://www.3cx.com/sip-phones/
Is it one of these?

Also, bear in mind that to be supported the FXS device must either be local or provisioned via the 3CX SBC.

 

[Just-a-volunteer]

Thanks for the reply on the ATA. I did confirm that it was still supported, but unreachable through the local network. As it turned out, its IP address was on the blacklist. I updated it to "allow" and it worked fine from there.

 

[ChrisC_3CX]

Excellent, glad to hear you tracked down what was causing the issue!

Do let us know if you need anything else!