Moving from subscription to NFR License

[SpaceCowboy]

Hi All,

I'm trying to apply our NFR license to our current paid 3CX, but I am getting "NFR keys cannot be specified as New license key".

Looking through some previous threads i.e. here, looks like I need to rebuild the system using the NFR key and restore a backup from our current system.

I'm in the process of doing this, but I can't take a backup of our current system excluding the license/FQDN as I can't see an option for this in v20, I can see the option in v18.

See below.

Any help would be great.

v18

v20

 

[bitn2]

In v20 there is no option to get a backup without this information. You can try to download the backup and adjust the xml file or start from scratch.

 

[SpaceCowboy]

Is there any KB/how to's for adjusting the xml file?

 

[NicholasP_3CX]

Is there any KB/how to's for adjusting the xml file?

No because we do not endorse this.

 

[SnakeRiverWebDevelopment]

The only way I know of is by command line, if using Debian and you have SSH access.

cd /var/lib/3cxpbx/Instance1/Data/Backups/

sudo -u phonesystem /usr/sbin/3CXBackupCmd --options=MIN --file=pbx_min_bak.zip

3CX Backup command line tool.

--log=VALUE Path including log file name enclosed in quotes,

example: --log="/var/lib/3cxpbx/text.log"

--file=VALUE Backup file name to create in Default Backup Location specified in Management Console.

Or path including zip backup file name enclosed in quotes,

example: --file="/var/lib/3cxpbx/Instance1/Data/Backups/backup.zip"

--options=VALUE What options you wish to include in the backup. The Value ALL includes everything.

To select certain options in the backup use the below strings comma separated,

example: --options=LIC,FQDN which will take a backup with License and FQDN only.

CH - includes CallHistory

LIC - includes your license information

FQDN - includes FQDN

PROMPTS - includes Prompts

FW - includes Firmware

REC - includes Recordings

VM - includes VoiceMails

MIN - minimal backup (backup only PhoneSystem configuration

--pwd=VALUE Specify the --pwd parameter to set a password to encrypt the backup.

Password must be enclosed in quotes. Example: --pwd="this is my pass"

Password must contain alpha numeric characters - no special characters allowed.

--noemail Optional. Do not send email after backup is finished. If not specified email will be sent.

--help Show this help

 

[SteveITS]

xml file

read through:
https://www.3cx.com/community/threads/change-of-fqdn-in-version-20.129954/post-618615
https://www.3cx.com/community/threads/v20-change-fqdn.124814/post-618578

 

[Dominique_CH]

You can still perform a backup w/o license information in V20 very easily, even for a hosted instance which doesn't offer SSH-access: on the admin-console, go to Advanced > Parameters and search for Backup: you'll find two values Backup_License and Backup_FQDN to either include (default=1) or exclude (=0) this information in your backups.

 

[bitn2]

You can still perform a backup w/o license information in V20 very easily, even for a hosted instance which doesn't offer SSH-access: on the admin-console, go to Advanced > Parameters and search for Backup: you'll find two values Backup_License and Backup_FQDN to either include (default=1) or exclude (=0) this information in your backups.

This values arent there anymore.

EDIT: they are gone since U2

 

[Dominique_CH]

This values arent there anymore.

EDIT: they are gone since U2

That's incorrect: you probably didn't click on 'Parameters' before performing the search

 

[bitn2]

That's incorrect: you probably didn't click on 'Parameters' before performing the search

Sorry, i am not stupid. Did you tried it on U2 or U3? They are not there anymore. You can read this also here in the forum. ;-)

 

[Dominique_CH]

I didn't mean you're being stupid, but we all can make simple mistakes. I just retried on 2 different U2-builds and these parameters are still around. I'm using them on all our managed customer instances.

 

[bitn2]

Ich checked it again, its gone since U3.

 

[bitn2]

U2:

U3:

 

[NicholasP_3CX]

I can confirm these parameters are no longer there.

Please refrain from giving out such information. Unless you are willing to take the support calls on our behalf (For free) for someone who messes things up because of following this information.

Because we usually get support calls for corrupted backups from partners/customers who followed a forum post and then demand we fix it for them, despite us instructing not to do this.

The parameters should only be touch IF instructed to do so by our support team.

 

[Dominique_CH]

@NicholasP_3CX: the ability to perform a backup w/o FQDN- and license information was a built-in feature on the backup-interface under V18 and removed as such in V20. It was very appreciated by 3CX-partners for various reasons, among which when copying an existing configuration from one system to another in relation to a company-merger or simply to test an existing configuration onto a lab-system. Several forum members called for recovering this feature under V20 but are visibly unheard from 3CX .

 

[NicholasP_3CX]

@NicholasP_3CX: the ability to perform a backup w/o FQDN- and license information was a built-in feature on the backup-interface under V18 and removed as such in V20. It was very appreciated by 3CX-partners for various reasons, among which when copying an existing configuration from one system to another in relation to a company-merger or simply to test an existing configuration onto a lab-system. Several forum members called for recovering this feature under V20 but are visibly unheard from 3CX .

This option was misused.

What do I mean with this?

When you create a backup, the provisioning folder is also backed up.

Alot of partners would create a "Generic customer template" and use this to create their PBXs. This of course would replicate the provisoning folder name across ALL the customer PBXs.

This could make it potentially very easy for an attacker to guess the provisioning URL of the devices and you could potentially expose ALL your customers if one customers PBX is breached. You are essentially negating one of the main security measures of 3CX.

We have made it easy for a new PBX to be created now with the configuration file and/or the configuration API.

3CX does not discount on security matters for ANYONE!