Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Implemented Replacement option for licence key FQDN binding

Discussion in 'Ideas' started by Platonik, Jul 17, 2017.

Implemented Replacement option for licence key FQDN binding 5 5 3votes
5/5, 3 votes

  1. Platonik

    Joined:
    Dec 29, 2016
    Messages:
    9
    Likes Received:
    0
    When provisioning a server with a key for an experimental / Trial version of 3CX we are not able to reuse the same FQDN that was used on the provisioned system unless a release of the key is made in order to rebind it to the production key. The release of FQDN can create issues when a ''hot'', ''sought after'' domain suffix like 3cx.us is used and that 3CX has reached their quota for this suffix.

    My feature request is the ability to ''Replace'' the key that is bound to the FQDN instead of releasing the FQDN from the trial key.