Learn how to import pure configurations without advanced features using the anynode frontend with this comprehensive guide.

Import

Essentially, anynode's configuration import function is compatible with files generated by older anynode versions.

If you intend to use a configuration file on an older version of anynode, we strongly recommend updating that anynode version to at least the level at which you saved the configuration file. While you can import the node structure, essential new features such as support for certificate issuance providers, Zoom Phone, or Microsoft Teams Direct Routing may not be available. Some functionality will be significantly limited in this case.

To import an anynode configuration, you should first check if you have written access.

If not, click on Configuration and Take Control in the upper menu.

Navigate to Configuration in the upper menu and choose Import.

Do not use the Configuration Backup Restoration Assistant (via Restore)!

Screenshot: anynode frontend with import configuration function. Screenshot: anynode frontend with import configuration function.
anynode frontend with import configuration function.

Click on the Choose File button and load your configuration file.

Enabling network controller mapping ensures a smooth transition when importing configurations between different environments or hardware. It helps adapt the saved configuration to the specific network setup of the current SBC. We recommend choosing the default value with enabled network controller mapping.

If you are using the same hardware on which you saved and exported the configuration, green checkmarks on the left menu indicate that no further actions are required here. If the configuration file was generated on different hardware, adjust the network controller for each node in the following steps. In our example, we are using the same hardware and do not need to adjust the network controller.

You can click the Finish button now.

Screenshot: anynode configuration import assistant with uploaded configuration file. Screenshot: anynode configuration import assistant with uploaded configuration file.
anynode configuration import assistant with uploaded configuration file.

Enabling network controller mapping ensures a smooth transition when importing configurations between different environments or hardware. It helps adapt the saved configuration to the specific network setup of the current SBC. We recommend choosing the default value with enabled network controller mapping.

If you are using the same hardware on which you saved and exported the configuration, green checkmarks on the left menu indicate that no further actions are required here. If the configuration file was generated on different hardware, adjust the network controller for each node in the following steps. In our example, we are using the same hardware and do not need to adjust the network controller.

Screenshot: anynode configuration import assistant with mapping of network controller for the VoIP provider. Screenshot: anynode configuration import assistant with mapping of network controller for the VoIP provider.
anynode configuration import assistant with mapping of network controller for the VoIP provider.

You can click the Finish button now.

Utilize the Commit function to permanently apply the imported configuration.