Skip to end of metadata
Go to start of metadata

VX currently has a large number of items that need to be configured in order to pass a single call. In the case where VX is installed as a Unified Communications (UC) or Unified Messaging (UM) gateway, the configuration is almost the same for every situation. The VX configuration system has been updated to allow you to choose from pre-loaded templates during initial bring-up. This enables almost instantaneous passing of calls after the startup configuration. Different templates for UC and UM in gateway mode are available.

Templates Description

A template is pre-defined configuration containing subset of an full configuration. VX configuration template files have the (*.vct) file extension similar have a format similar to exported VX configuration (*.cfg) files. The following templates are provided with VXbuilder:

  • Basic SIPUCTemplate.vct - Unified Communications SIP - SIP basic gateway.
  • Basic UCTemplate.vct - Unified Communications ISDN - SIP basic gateway.
  • Basic UMTemplate.vct - Unified Messaging ISDN - SIP basic gateway.
  • EUCF Template.vct - Unified Communications ISDN - SIP Extended UC Features gateway.

These templates are installed with VXbuilder in the following location: <vx-builder-install-dir>\Templates

You can use these templates to configure a node in the above mentioned scenarios. The templates contain values for the configuration items necessary to bring up a node in one of the above mentioned scenarios. The rest of the configuration items will have default values.

The templates do not contain the values for the static portion of the configuration (the node-specific parameters provided by the user when the start-up script is run). These include:

  • Node ID
  • Node Name
  • License key
  • IP Address and Netmask

The templates have a header similar to that of the config files that contains the version control information.

Please note that template is a subset of the configuration, and not a complete configuration in itself. Therefore, you cannot run "Config Verify" nor have a separate upgrader for a template. When a template is applied to the VXbuilder, it is merged with the Configuration tree and becomes a complete configuration. This configuration can now be verified or transmitted to the node.

There are three ways to apply a template:

  1. You can choose to apply a standard template when configuring a new node. This option is provided when after running the setup script on a new node:
    • Click the Receive button of the VXbuilder window. An Open dialog window pops up as shown below.
      Open File Dialog

    • Select the type of file to be opened as ".vct" and browse to the location where the standard template is stored. (The Templates directory in the VXbuilder Installation directory.)
    • When the template is loaded into the existing VXbuilder configuration tree, the configuration items specific to the template are overwritten with the values present in the template. The static portions of the configuration remain unaffected and the rest of the configuration items on the VXbuilder have default values.

  2. You can choose the New Template Based Configuration option.
    • In the File menu, choose New Template Based Configuration. An Open dialog window now pops up which prompts you to browse to the location where the standard template is stored (same as the location of VXbuilder).

      Open File Dialog


      When the template is loaded to the existing VXbuilder configuration tree using this option, the configuration items specific to the template are overwritten with the values present in the template. The rest of the configuration items (including the static items) on VXbuilder are replaced with default values. This functionality is very similar to the New Blank Configuration option.

  3. You can use the Import button.
    • Click Import (or choose the File > Import menu option). An Open dialog window now pops up.
    • Select the type of file to be opened as .vct and browse to the location where the standard template is stored (same as the location of VXbuilder).

When the template is loaded to the existing VXbuilder config tree, only the configuration items specific to the template are overwritten with the values present in the template and the rest of the configuration remains unaffected.

After the template is applied, you can either run a wizard or finish the configuration manually. The configuration is complete now. You can transmit the configuration to the VX node and bring up calls on the node.