Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.




Html
<div class="fb-like" data-href="https://confluence.wildix.com/x/twM8AQ" data-layout="button_count" data-action="recommend" data-size="large" data-show-faces="true" data-share="true"></div>

...

Info

This document helps you understand Wildix licensing and explains how to activate a Wildix Per User PBX (Hardware, Virtual, Cloud).

Date: June 2018

Updated: December 2019

Permalink: https://confluence.wildix.com/x/twM8AQ

Toc

Understanding Per User Licensing

...

Details on each user profile: https://manuals.wildix.com/licensing/

Per User licensing is available for any PBX type:

...

  • Connect to PBX via HTTPS to access WMS using credentials admin : wildix

  • Change admin user password:

    • Select admin user and click Set passwords

    • Generate or create a new WEB password, click Ok

  • Upgrade WMS to the latest stable release

    • go to WMS Settings -> Tools and utilities -> Upgrade

    • In case there is a new version available, click Perform Upgrade 

  • Copy PBX key from WMP:

    Note

    Only for Virtual and Hardware PBXs. Cloud PBXs are activated automatically (wait for approximately 3 minutes after completing Step 1).


    • go to Customers tab, select your company, then select the PBX that you have created (Step 1)

    • click the Copy icon (Copy PBX key to clipboard):

...

Note

Newly created or exported users by default are assigned Essential license. It is necessary to manually set the correct license type. 

Move PBX to Cloud

You can move your Hardware and Virtual PBX to Cloud. It is possible to move Per User subscription-based PBXs (1 month/ 1 year/ 5 years).

Warning

Min supported WMS version (make sure your PBX is updated to this version before proceeding):

  • WMS 3.88: 3.88.44723.49
  • WMS 4.x: 4.03.44693.48

WMS Changelogs: https://www.wildix.com/new-releases-and-updates/

Warning

Limitations:

  • Only MySQL/ SQLite3 Database is supported for migration (WMS 4.0X)
  • Only SQLite3 Database is supported for migration (WMS 3.XX)
  • DB size for migration is limited by the root partition size on Cloud PBX: about ~6-7G

...

Warning

Limitations:

  • Only MySQL/ SQLite3 Database is supported for migration (WMS 4.0X)
  • Only SQLite3 Database is supported for migration (WMS 3.XX)
  • DB size for migration is limited by the root partition size on Cloud PBX: about ~6-7G

More a Subscription-based PBX to Cloud (1 month/ 1 year/ 5 years)

Step 1 - Create a new Cloud instance on WMP 

To move Per User subscription-based (1 month/ 1 year/ 5 years) PBX to Cloud, you need to access WMP where you have a button that allows creating a new Cloud instance instead of your current PBX. The licenses active on this PBX and the PBX serial will be moved to the new Cloud instance. 

...

  1. Access WMP using your credentials
  2. Select your company and your customer
  3. Click Options button (Three dots) and select Edit
  4. Click Advanced features
  5. Click Migrate to new WCloud PBX

Step 2 - Run the script on old PBX to move all the data 

Warning

Min supported WMS version (make sure your PBX is updated to this version before proceeding):

  • WMS 3.88: 3.88.44723.49
  • WMS 4.x: 4.03.44693.48

Now when you've create a new Cloud instance for your HW/ VM PBX, you need to launch the script on your old PBX that will move all the data from your old PBX to the new one.

Once again, please make sure that the requirements are met and the limitations are respected:

Run the script:

  1. Access WMS, Open Terminal on the PBX, select the option 11 (Shell), access as root (su - wildix)
  2. Run the command: migrate2cloud

More a Per-Service or a LifeTime PBX to Cloud 

Warning

Min supported WMS version (make sure your PBX is updated to this version before proceeding):

  • WMS 3.88: 3.88.44723.49 coming soon
  • WMS 4.x: 4.03.44693.48
Warning

Limitations:

  • Only MySQL/ SQLite3 Database is supported for migration (WMS 4.0X)
  • Only SQLite3 Database is supported for migration (WMS 3.XX)
  • DB size for migration is limited by the root partition size on Cloud PBX: about ~6-7G

Run the script:

...

  • 44733.50

Step 1 - Create a new Cloud instance on WMP 

Create a new Cloud PBX as described in chapter Add a new Per User PBX on WMP.

Step 2 - Run the script on old PBX to move all the data 

  1. Access WMS, Open Terminal on the PBX, select the option 11 (Shell), access as root (su - wildix)
  2. Run the command: migrate2cloud -s <serial of cloud pbx>

You will be prompted to enter the password of your new cloud PBX. During the script execution you will be prompted to confirm, which data you would like to be moved. As soon as the script finishes its execution, the data will be moved and you will be able to access the Cloud PBX using the password of your old PBX. 

Enable SSH port on Cloud PBXs (optional) 
Anchor
Sshport
Sshport

Direct access to SSH port on Cloud PBXs is blocked for security reasons. Now it’s up to you to temporarily enable/ disable SSH port 2222 via WMP:

...

  • Confirm the operation by clicking Yes


Note

Note: The change will be applied at 1AM.


Warning

Important: After you have increased the storage size, it will not be possible to decrease it.

Increase / decrease the amount of Per User accounts

...