/
How to Remove a Deployment ID-License File from your PBX

How to Remove a Deployment ID-License File from your PBX

Owned by Nathaniel Halbrooks
Last updated: Jan 25, 2024
3 min read

All commercial modules are purchased for a specific deployment. Each deployment is locked to a specific hardware box when you register your PBX to a Deployment ID.

We allow you to reset the hardware lock on any deployment up to two times. After you reset a hardware lock, you can register your deployment to a new hardware box, which will allow the commercial modules to work on your new hardware.

After you have used the hardware reset option twice, the option will no longer exist. In this case you would need to contact the sales team atĀ http://support.schmoozecom.comĀ to request an exception to be made, and for us to perform a reset.

You can reset your hardware lock from within the System Admin module of your PBX GUI as described below.

Alternatively, you can reset the hardware lock from the Portal atĀ http://portal.sangoma.comĀ as described in the wikiĀ How to Move a PBX Deployment to a New PBX.

Ā 

System Admin 12.0.19 or Newer: Removing the License File

You can remove the license file from within the System Admin module. This will accomplish a Zend reset and allow you to use the Deployment ID on different hardware.

  1. Log into your PBX GUI.

  2. In the top menu go toĀ Admin.

  3. In the drop-down menu go toĀ System Admin.

  4. Click onĀ Activation in the navigation menu.

    Ā 

  5. Press the De-Activate button near the bottom ofĀ the page.
    In our example we have already used this option once, so there is only one reset remaining. If you have performed two resets, the option will no longer exist, and you will need to contact the sales team atĀ http://support.schmoozecom.comĀ for assistance.

    Ā 

  6. The license file and information will now be removed from your PBX. You can now apply the Deployment ID to a different system. See the wikiĀ Registering your PBX for Commercial Modules and SupportĀ for more information.

System Admin 12.0.18 or Older: Removing the License File

If you are using System Admin v12.0.18 or older, you can remove the license file through the Linux CLI.

  1. Determine the location of the license file on the PBX. Depending on what version you are using, the license file is either located in:

    1. /var/lib/asterisk/agi-bin
      orĀ 

    2. /etc/schmooze

  2. The license file should be aĀ license-xxxxxxxxx.zl with xxxxxx representing a Deployment ID Number. Ā Remove this file with the following command, replacing the xxxxx with the actual file name:

    1. rmĀ /var/lib/asterisk/agi-bin/license-xxxxxxxxx.zl
      or

    2. rm /etc/schmooze/license-xxxxxxxxx.zl

      Removing License file from agi-bin directory on older systems.

      cd /var/lib/asterisk/agi-bin Ā Ā  ls Ā Ā  [root@2222222 agi-bin]# ls backuprecordings.phpĀ  encĀ Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā  phpagi-asmanager.php broadcast_log.phpĀ Ā Ā Ā  enumlookup.agiĀ Ā Ā Ā Ā Ā Ā Ā Ā Ā  phpagi.php calllimitĀ Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā  fax.agiĀ Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā  queue_devstate.agi calllimit.agiĀ Ā Ā Ā Ā Ā Ā Ā  fixlocalprefixĀ Ā Ā Ā Ā Ā Ā Ā Ā Ā  sql.php checksound.agiĀ Ā Ā Ā Ā Ā Ā  license-123456789.zlĀ Ā Ā  update_license.phprm license-123456789.zl

      Removing license file from /etc/schmooze on newer systems.

      cd /etc/schmooze Ā Ā  ls Ā Ā  [root@222222222 schmooze]# ls license-22222222.zlĀ  pbx-brandĀ  pbx-failsafeĀ  pbxidĀ  pbx-version [root@22222222 schmooze]# Ā rm license-22222222.zl

  3. You also need to remove the pbxid file. Determine the location of this file. Depending on what version you are using, the license file is either located in:

    1. /etc/asterisk/pbxid
      orĀ 

    2. /etc/schmooze/pbxid
      Ā 

  4. Remove the pbxid once you find it, with this command:

    1. rm /etc/asterisk/pbxid
      or

    2. rm /etc/schmooze/pbxid

    Removing PBXID from asterisk directory on older systems.

    cd /etc/asterisk/ Ā Ā  ls Ā Ā  [root@123456789 asterisk]# ls asterisk.confĀ Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā  confbridge_custom.confĀ Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā  features_featuremap_additional.confĀ  iax_custom.confĀ Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā  logger_general_custom.confĀ Ā Ā Ā Ā Ā  musiconhold.conf ccss.confĀ Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā  dahdi-channels.confĀ Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā  features_featuremap_custom.confĀ Ā Ā Ā Ā  iax_custom_post.confĀ Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā  logger_logfiles_additional.confĀ  musiconhold_custom.conf ccss_general_additional.confĀ  directoryproĀ Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā  features_general_additional.confĀ Ā Ā Ā  iax_general_additional.confĀ Ā Ā Ā  logger_logfiles_custom.confĀ Ā Ā Ā Ā  pbxidĀ Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā  ccss_general_custom.confĀ Ā Ā Ā Ā  enum.confĀ Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā  features_general_custom.confĀ Ā Ā Ā Ā Ā Ā Ā  iax_general_custom.confĀ Ā Ā Ā Ā Ā Ā Ā  manager_additional.confĀ Ā Ā Ā Ā Ā Ā Ā Ā  phone.confĀ Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā  [root@123456789 asterisk]# rm pbxid

    Removing PBXID file from /etc/schmooze on newer systems.

    Ā 

  5. Restart Apache to clear out any cache.

    Removing PBXID file from /etc/schmooze on newer systems.

  6. You can nowĀ register your PBX as usual, following this guide:Ā Registering your PBX for Commercial Modules and Support

Return to Documentation Home I Return to Sangoma Support