Provisioning QR-Code Problem

Status
Not open for further replies.

B.Fluehmann

Customer
Joined
Jan 7, 2017
Messages
27
Reaction score
1
In our setup, the qr-code provisioning of 3cx-clients does not work.
The problem is the hostname of the encoded link. It seems that the hostname is hardcoded to the hostname of the server. This does not work for us since we use a common dns name for the 3cx service.

Example:
Server-hostname: 3cx-server-01
service-name (public dns name): 3cx.company.com

The public name is properly set under Extension/phone-provisioning/network/"interface for registering and provisioning". Therefore i was assuming that this name is used as well in the barcode.

Please let me know how this can be fixed.
 
Have you run the firewall check, to see if all the required ports are open and no issues

Are you trying to provision the devices remotely (not connected to your local lan), if so you need to open port 5001 on your firewall.

If the devices are local, does 3cx.company.com resolve to the IP address of the 3CX server. If not you may have to setup spit dns https://www.3cx.com/docs/creating-fqdn-split-dns/
 
Firewall check is ok.

Yes. phones are provisioned remotely. This is working fine by using the email attached config files.
The only thing that does not work is the qr-code provisioning.

We are using split dns entries and resolving works fine. The only problem as already mentioned is that both our internal and external server are pointing to let's say pbx.example.com but the hostname itself is called let's say 3cx-server-01.company.com.

As described in the original post, pbx.example.com can be selected as interface in the extension configuration, but the link in the qr-code contains the hostname of the server itself instead of the one used by the dns servers.
 
Status
Not open for further replies.

Forum statistics

Threads
111,852
Messages
589,389
Members
164,691
Latest member
Daz1964