Provisioning URL not working?

[rdg154]

I setup 3cx on AWS cloud - seems pretty nice.

I am trying to provision a Yealink phone - but the URL is not accessible

https://main_domain/provisioning/unique_number - this does not load - 404
https://main_domain/provisioning - this does not load - 404
https://main_domain - this loads just fine

Also when I goto the main menu and click: Phones - nothing shows up on this menu, but I have several Yealink phones on Users configured (yet not provisioned due to the problem above)

Any idea what I am missing here?

 

[eddv123]

How are you connecting the phone to the cloud ? VPN, SBC or STUN ?

Also what ports are you using for HTTP and HTTPS provisioning as entered on install.

 

[rdg154]

Direct SIP - STUN

Port 80 / 443 are used - I did not setup anything specifically just for provisioning?

 

[Evolute IT]

The URL won't be accessible for you.

The phone will add a suffix for it's config file. The URL itself is just a vhost so when accessing it, you should see a Forbidden error. Or possibly a 404 Not Found.

Just put the URL as is in the phone and it will work.

 

[rdg154]

Any idea why the phones aren't not showing up then under the Phones page? They so show up under Extensions -> User -> Phone Provisioning

 

[Evolute IT]

Any idea why the phones aren't not showing up then under the Phones page? They so show up under Extensions -> User -> Phone Provisioning

They will show up once they're registered. They don't when simply added to an extension.

 

[Evolute IT]

I recommend you go through the academy to help you learn how 3CX works.

https://www.3cx.com/3cxacademy/

 

[eddv123]

Port 80 / 443 are used - I did not setup anything specifically just for provisioning?

You dont need to, 3CX uses 443 for things such as provisioning, access to the management console presence from external sources etc https://www.3cx.com/docs/ports/

 

[eddv123]

I recommend you go through the academy to help you learn how 3CX works.

https://www.3cx.com/3cxacademy/videos/intermediate/configuring-remote-extensions/

Explains STUN rather well.