Grandstream HT801 ATA cannot be assigned

[john.liu]

I bought a Granstream HT801 ATA to replace old Cisco ATA because it is said supported by 3CX.
When it is connected to network, it has got dynamic IP and shows up on 3CX PNP Phones page.
But it displays differently with the other SIP phones, its IP shows 127.0.0.1 while the other SIP phones show like 10.128.20.74:5059 via SBC BC1SBC10.
The worst thing is I cannot assign the ATA to a user. When it is selected in the PNP Phones list, the "Assign" button is grayed out.
I have tried to upgrade the ATA to the latest firmware 1.0.55.5 from 1.0.51.1 and factory reset it, but it didn't help at all.
I checked the ATA status on its web page, there is line showing "Provision: Not running, Last status : Downloading file from url."
My 3CX is a hosted 3CX Pro.
Can anybody help me to solve the problem? Or tell me this model is not really supported by 3CX, so I can return it.

Thanks a lot!

 

[AramS_3CX]

Hello john.liu,

The PNP provisioning for ATA devices is not supported.
All ATA devices must be provisioned manually.
More information can be found in the Configuring Grandstream HT Series FXS VoIP Gateways guide.

 

[dlewis061]

This article must be old because it is not relevant anymore. You can NOT download the xml link so that it can be uploaded to the HT device. I am having the same issues and there is zero support on this.

Hello john.liu,

The PNP provisioning for ATA devices is not supported.
All ATA devices must be provisioned manually.
More information can be found in the Configuring Grandstream HT Series FXS VoIP Gateways guide.

 

[JohnS_3CX]

This article must be old because it is not relevant anymore. You can NOT download the xml link so that it can be uploaded to the HT device. I am having the same issues and there is zero support on this.

You must be using the Update 5 alpha build then correct? This build is not meant for production, only for testing and there is no support for Alpha builds. The stable build for Update 4 will allow you to download it.

For now, use the link it gives you and add cfgMAC.xml at the end like this example:
https://fqdn/provisioning/xxxxxxx/cfgAAAAAAAAAAAA.xml