Provisioning WallTech ATA 172 Plus

[Vito]

Hi guys,
I'm having trouble getting Walltech ata172plus provisioned
I followed the instructions at https://www.3cx.com/voip-gateways/

- I set two extensions (I read that for a bug of the product you have to set them both)
- I checked that the office ip is not blacklisted

The Status Log list this event
10 <2018-04-03 23:50>Get file Fail!!!
11 <2018-04-03 23:50>HTTP Get file...


My 3CX is in clooud on Debian, public ip outside my company network.
Maybe this could be the problem?

Ideas?

Thank you for help
Vito

 

[cobaltit]

Top of the document you linked:

Notes:

The device must be local to 3CX, in the same subnet and/or locally routed subnet (including site to site VPN)

 

[Vito]

Hy, thank you for reply.

Unfortunately, my 3CX server is a debian virtual Machine the cloud, public IP address. It isn't on the same office subnet. I thought the provisioning was in the same way as other SIP phones (yealink).

How else can I connect analog peripherals to the voip pabx?
Why must be it in the same subnet?

 

[Vito]

Hy, thank you for reply.

Unfortunately, my 3CX server is a debian virtual Machine the cloud, public IP address. It isn't on the same office subnet. I thought the provisioning was in the same way as other SIP phones (yealink).

How else can I connect analog peripherals to the voip pabx?
Why must be it in the same subnet?

I installed my 3cx server on OVH as described in the document
(https://www.3cx.com/docs/cloud-pbx-ovh/)

Could it be an idea to install on prem 3CX SBC (Session Border Controller) and configure Walltech ATA172Plus towards this voip proxy?