Solved Updated to 16.0.5.454 to resolve an Issue now 2 Patton 4112's won't work

[stubss411]

I have not had any faxing issues until updating to this version of Beta which I am aware of yes it is Beta but, Fax should not cut off. I have two fax devices Patton 4112's that for years have worked great no issues then I updated and poof issues. These are not fun to troubleshoot, They both were sending internally to each other but not to customers outbound or inbound although our cell phones worked fine calling and receiving calls from the fax.

I grabbed the config for one and re-installed but, the config didn't do anything and it would not work still. So we reset the Patton but then it would not come back online and although lights are on the network is on it won't work and find an IP and I can't connect to it to config it. This is not my strong suite honestly with these Pattons as I hardly touch them.

Does anyone know why the faxing won't go outside and handshake and two why one Patton after the reset I can't get into it? I might be doing something totally dumb I'm aware and If so I have no problem admitting it.

 

[leejor]

If the use of these fax machines is critical, and it is not working on the Beta, why not simply re-install the previous, working, 3CX version?

I have always found that it is not necessarily the best idea, to be the first, when there are new versions released, of any software/firmware, not just 3CX, unless, it can be done on a test installation, for that purpose...testing.

 

[stubss411]

If the use of these fax machines is critical, and it is not working on the Beta, why not simply re-install the previous, working, 3CX version?

I have always found that it is not necessarily the best idea, to be the first, when there are new versions released, of any software/firmware, not just 3CX, unless, it can be done on a test installation, for that purpose...testing.

First @leejor I appreciate your reply. The beta resolves other issues that I do not want to go back on and cannot at this point. The non-beta was already supposed to be out I was told by 3CX and it is not updated yet so I am not able to go to the stable version with the fixes I needed. Fax is important and everything was tested before except the fax hardware as we had no access to it and frankly forgot about those devices.

I am with you on not being first occasionally it can't be helped this is one of those oh crud moments. I'd like to not have to purchase an analog line to resolve this at this point and will do what I can to get this working. I don't mind testing and re-testing at all over and over and over.

One challenge though is that one Patton after the update and new config I can't get into after restarting and even seeing it on the network. If it has another IP or subnets my network would still pick it up and see it. It's been reset but I cannot do anything with it and the network lights are on. Any ideas? I don't want to buy another this is only 18 months old.

 

[leejor]

If you do a factory reset" on the one Patton, not responding, are you able to get into it, or see it on the network, prior to a config file being downloaded? Was the Patton software changed at all?

 

[stubss411]

If you do a factory reset" on the one Patton, not responding, are you able to get into it, or see it on the network, prior to a config file being downloaded? Was the Patton software changed at all?

I reset the Patton but, I am not able to get into it yet. The software or firmware was not changed before. Thank you for your assistance so far....

 

[leejor]

A full reset should allow you back in, as if the unit were new. There is always a possibility of faulty hardware, or power supply (if a separate unit).

 

[eddv123]

You have already identified this however I must reiterate - BETA versions are not for live environments.

With this being said I am aware that this recent release has some fixes for webmeeting which are pretty mission-critical - so under the current circumstances exceptions I guess can be understood.

Please first identify the issue - for example you say you cant FAX, however are the FAX extensions on 3CX registered firstly ? I have a set of detailed debugging commands you can do via commandline to tell us exactly why they are failing but I would (due to the potential age of the units do the following first):

* Check and update the firmware on the Pattons if on an outdated version:
https://www.patton.com/support/upgrades/index.asp?um=SmartNode 411x

* When done ensure you check the method of setup (as this has changed probably since you set these up) also re-provision with a new template from 3CX v16: https://www.3cx.com/voip-gateways/patton-smartnode-sn4112-fxs/

Once this is done and you can confirm registration and connection to 3CX I will provide the commandlines from the Patton.

Note: If you are resetting the Patton the following applies:

The reset button has three functions:

• Press (for less than 1 second) and release the Reset button to restart the unit with the current startup configuration.
• Restart the unit with factory default configuration—Press the Reset button for 5 seconds until the Power LED starts blinking to restart the unit with factory default configuration.

The third option boots in bootloader mode which gives redboot options for training engineers (not necessary at current).

The device should boot in default mode as DHCP accessible so do an IP scan of the network or check your DHCP server for the IP address allocated.

 

[stubss411]

You have already identified this however I must reiterate - BETA versions are not for live environments.

With this being said I am aware that this recent release has some fixes for webmeeting which are pretty mission-critical - so under the current circumstances exceptions I guess can be understood.

Please first identify the issue - for example you say you cant FAX, however are the FAX extensions on 3CX registered firstly ? I have a set of detailed debugging commands you can do via commandline to tell us exactly why they are failing but I would (due to the potential age of the units do the following first):

* Check and update the firmware on the Pattons if on an outdated version:
https://www.patton.com/support/upgrades/index.asp?um=SmartNode 411x

* When done ensure you check the method of setup (as this has changed probably since you set these up) also re-provision with a new template from 3CX v16: https://www.3cx.com/voip-gateways/patton-smartnode-sn4112-fxs/

Once this is done and you can confirm registration and connection to 3CX I will provide the commandlines from the Patton.

Note: If you are resetting the Patton the following applies:

The reset button has three functions:

• Press (for less than 1 second) and release the Reset button to restart the unit with the current startup configuration.
• Restart the unit with factory default configuration—Press the Reset button for 5 seconds until the Power LED starts blinking to restart the unit with factory default configuration.

The third option boots in bootloader mode which gives redboot options for training engineers (not necessary at current).

The device should boot in default mode as DHCP accessible so do an IP scan of the network or check your DHCP server for the IP address allocated.

OK Since 2012 I have not had too many issues even though I'm finally coming to this forum and posting I have used it in the past a fair amount to learn as an end-user. I finally surpassed our Vendor in 2016 with supporting 3CX internally but didn't want to. I removed myself from the IT world because as much as I love it I have a tough time working with the end-users like me hahaha. Anyway, This is the only beta that has ever been live and funny enough that wasn't the issue at all, in fact, this particular beta has been pretty solid.

I came back to post what I found out the issue was with a good friend's eye.

I hired an external company to take care of our IT and then after some time they just went downhill so we fired them and I took back overspent two months fixing issues along with my other job internally and issues are popping up all over still but it's slowing down.

The answers after the problem, I had two Patton devices not sending faxes out of the blue for no apparent reason other than a beta upgrade of system software. Being remote I had someone reset the Patton at one location but it was reset incorrectly and I could not find the right reset timing sequence (thank you
eddv123 for providing that answer) and the other wouldn't send outside out network although both could fax to each other internally before the reset. The answer was super simple...someone changed the "Default Caller ID" of the Fax number in 3cx. that was really it for us and it always is those small mundane things like a comma or something that gets missed.

Anywho there it is