Solved Can't register extensions on a second FXS adapter

[apitsos]

Hi there,

I am having a installation with four (4) FAX devices. For this reason we need 2x 2-port FXS adapters. We are using Grandstream HT802, because they are compatible and supported.

I did the following procedure:

1. Creation of the extensions
2. Addition of the Grandstream HT802 under "FXS/DECT"
3. Addition of two extensions on each adapter
4. Right click and saved the .xml configuration file of each adapter
5. Uploaded the configuration .xml file on each adapter in order to provision the device

So, basically I followed the procedure described here: https://www.3cx.com/voip-gateways/grandstream-ht-fxs

I have done that in 3 installations, but with just one 2-port Grandtream HT-series FXS adapter on each installation.

So, the problem I am facing here is that the first adapter has the extensions registered immediately after the reboot, but the second adapter is not registering neither of the two extensions! I also compared the configuration files (the .xml files downloaded from 3CX and uploaded to the adapters) and they are identical (except the extension details of course).

I am thinking a possible conflict regarding ports, but I am not sure if that could be a problem.

Anyone who has more than one FXS adapters in an installation and knows what the problem could be or what configuration should I do?

 

[leejor]

Being fax extensions , I assume that the ATAs are local to the server. That being the case, each extension, on a device, is going to have to be configured as a unique local port (both can't be 5060).
The 3CX activity Log should show you how the devices are attempting to register, or IF they are attempting to register.

 

[apitsos]

Hi @leejor!

Thanks a lot for your answer. Actually they are "voice" extensions, the normal ones. Not FAX. Our provider (BITel) supports G.711 A-law codec and that's what they have suggested us to configure (I mean the codec, not the extension). I have tried to configure FAX extensions as well, but they are not working properly.

As for the ATAs, yes they are local. They are on the same network, no remote connections, public IPs or anything else. Just local network, same network switch.

Yesterday night, after changing the local ports and make them different, I tried again and I still wasn't able to make any of the two extensions on the 2nd FXS adapter to register. But I tried the following:
I loaded the configuration of the first ATA to the second one and vise versa. Guess what! The other extensions that were initially configured on the 2nd ATA and now were configured on the first one were registered, while the extensions that were initially configured on the first ATA and registered before, were not registering after the loading of the configuration on the second ATA!

So, based on the above, I am thinking that maybe I am having issues with the hardware. What I did in order to prove that, was to flash the device with the latest firmware once again. Unfortunately I was not there and was working remotely, otherwise I would also try a hardware factory reset. But this is something that I will try today. Also I will get with me another FXS adapter in order to replace it and see if the problems will be solved.

Of course I will post here the results.

 

[AWS2P]

Apitsos, It's a pleasure to follow your steps,you write its clear and precise and easy to follow. it makes the reader want to help.

 

[leejor]

I would do Factory Reset, just to be certain. Did you assign a static IP, or use DHCP? Did you check the IP Blacklist? Did you check the Activity Log for a registration attempt?

I have had several Grandsteam ATA devices fail on me in the past, just refuse to respond at all.

 

[apitsos]

Hi again!

As I mentioned on my previous post, the local ports were changed, so the two ATAs had different local ports and conflicts should be avoided. I also tried to exchange the configuration between the two ATAs and I noticed that the 2nd one was always the one that didn't register.

So, I went to the client yesterday morning in order to replace the problematic Grandstream HT802 with another happened to have in stock. Before doing that I reset it also into factory defaults and loaded the configuration once again, but without success. But everything was worked like a charm, exactly after loading the same configuration on the new Grandstream. So I got the problematic one with me, in order to test if further at the office.

But... I noticed something that made me think further. That second ATA was extremely hot. Then I tried to see how it was the first one, sitting just beside. That didn't have so high temperature. Both of them were sitting on top of provider's SBC box!

Long story short, the right side of the SBC box of BITel was really hot, while the left side wasn't so much. Most probably the processor was underneath, but who cares. Having devices stacked one on top of the other is not very clever. The rack didn't have enough selves and that's why they were stacked.

Bottom line is that the second ATA was most probably malfunctioning because of the high temperature, while the other one having more normal temperature was just fine. After replacing it I put them both on a different way in the rack in order not to get hot again. Now, after a day, I confirm that both ATAs are working properly.

Just for the records, the problematic ATA is now configured and operating at our office, also without problems! So there wasn't any permanent damage on it. That proves that the reason of the malfunction was exactly the one I noticed.

Thank you all for your help, your posts, your time and everything. @aws2p, it's a pleasure for me also to write here, because this strong community provides support very quick and with high level of accuracy. I really enjoy that.

I think that issue has been solved and we may consider this thread as "Solved".

 

[AWS2P]

Well done, it was a very good investigation