How to known If Change FQDN, Why Client mobile can register with out Re-scan QR code?

[Masaki]

Hi 3CX Support

Server 3CX V.18.0.9.20
License : Ent 24SC
OS : windows Server 2019 STD
FQDN : Owner FQDN
Customer request change FQDN A to FQDN B

1. Create a backup of the system without licence and FQDN information
2. Un-install the PBX.
3. Access the customer portal and release the key from the current FQDN
4. Re-install the system using the licence key and select the FQDN you'd like.

If server restore complete, have somting wrong about.

Client A on 3CX app mobile with andriod, If open app can re-provision auto and get new FQDN B. Status on app "Ready for Calls" Icon Led Status is "Green" with-out Scan new QR Code.

Client B on 3CX app mobile with IOS, If open app can not re-provision auto and get FQDN A Status on app "Ready for Calls" Icon Led Status is "Gray" can not use, It can resolved scan new QR Code.

Why change FQDN, Client can change to new FQDN with-Out Scan new QR Code?


Thank you,
Suebpong Saengthongsuk

 

[TheodorosG_3CX]

Just to clarify, after changing the FQDN, the iOS app was able to register to the PBX?

 

[SweetAction]

All clients should need to rescan the QR code after a FQDN change, it shouldn't be possible to just reopen the app and have it work without a rescan.

 

[TheodorosG_3CX]

Moving forward to @SweetAction reply, changing the FQDN does not reprovision any client as the FQDN is not there to resolve it, so there is no endpoint for the client to contact.

 

[Masaki]

Just to clarify, after changing the FQDN, the iOS app was able to register to the PBX?

After change FQDN, Client IOS If open app Status on app "Ready for Calls" Icon Led Status is "Gray" can not use.

Yes client can register with old FQDN, test *777 echo > Log on server can call *777 in active call in dashboard but not complete test because FQDN is wrong.

All clients should need to rescan the QR code after a FQDN change, it shouldn't be possible to just reopen the app and have it work without a rescan.

I think so,too.

Moving forward to @SweetAction reply, changing the FQDN does not reprovision any client as the FQDN is not there to resolve it, so there is no endpoint for the client to contact.

Why change FQDN, Client andriod can change to new FQDN with-Out Scan new QR Code?

Is it possible to
Server use Old IP Public and map old FQDN. If Change FQDN to new.
If FQDN Old & New can solved DNS the same IP Public, somthing can do. Client can re-provision without re-scan new QR Code.

Thank you,

 

[TheodorosG_3CX]

Just to clarify, how is the FQDN changed? Is it released from the portal?

 

[Masaki]

Just to clarify, how is the FQDN changed? Is it released from the portal?

Yes I Confirm, My customer has released in the 3CX Portal after uninstall program 3cx complete.

 

[Masaki]

Hi 3CX Support
I have change FQDN again, and update and result in same this detail. I will change next job to 15-03-2024.

Before them scan QR Code for test between IOS & Android.

Server 3CX V.18.0.9.20
License : Ent 16SC
OS : windows Server 2019 STD
FQDN : Owner FQDN

Customer request change FQDN A to FQDN B

1. Create a backup of the system without licence and FQDN information
2. Un-install the PBX.
3. Access the customer portal and release the key from the current FQDN
4. Re-install the system using the licence key and select the FQDN you'd like.

After server restore complete at 18.05 today.

IOS : 9688 in old FQDN not change but ready for call. Led is gray but can register server. can call out but not complete.
Android : 9689 FQDN Change auto whit out scan qr code and ready to call. can use call in&Out 100%.

 

[TheodorosG_3CX]

I'm unable to reproduce this scenario from our side.
Can you please create a support ticket so we can check from there?