4.3.4.1 Details (Standard Solution/vApp)

NOTE: If “Openscape Voice Type” has been set to “Integrated Simplex” in the “General” tab, then the second IP address column for each field in this section will not appear.

•

Subnet Sharing (*) - Supports options for the Management, Billing and Signaling traffic to be on separate IP subnets or to use shared subnets. The following options exist:

–

Mgmt-Billing-Signaling-Separated (applicable to Standard Solution only)

–

Mgmt-Billing-Shared

–

Mgmt-Billing-Signaling-Shared

•

Share Admin and Cluster Interface -

•

Cluster Name (*) - This is the cluster name introduced in Node.cfg. It should be provided either when OSV is Integrated Simplex or Standard Duplex.

Important: Cluster Name is used in logicalBranchOfficeId of the OpenBranch Proxy/CSBC xml file so that OpenBranch Assistant can communicate with these modules. For a Central Deployment of Licenses, License Server(s) field should contain the IP Address of CMP.
Changing the Cluster Name in NCPE will result to a non compatible logicalBranchOfficeId provisioned in OpenBranch Modules.Though this can be changed manually from the OpenBranch Advanced tabs or from the OpenBranch local GUI.

Proxy logicalBranchOfficeId format:
<Cluster Name>:<Business Group>:<Branch Office Name>

CSBC logicalBranchOfficeId format:
<Cluster Name>:<Business Group>:<Endpoint Name>

Cluster Name Limitations:

–

Maximum 20 Digits Long

–

First Character must be alphabetical

–

Only Alphanumeric and “underscore” characters are allowed

–

Only lowercase characters should be used for consistency

The next section located after the ’Network for OpenScape Voice’ section allows the user to configure the subnet IP addresses (Network ID), Netmask, and Default Gateway settings which are then used for the OSV’s node.cfg configuration file. These network settings are grouped into settings for Node1 and Node2.

•

Node Hostname (*) - Configures the hostname of the OSV Server node to the entered name.

•

OpenScape Voice administration IP (Management) - The OpenScape Voice Management IP is the physical IP of the OSV server.

–

For OSEE configurations OSV server is acting as the primary DNS Server of the solution. Thus the user either has to fill this IP or ensure the generation of the node.cfg with CDC.

–

If you don’t manually prefill the IP address, it will be calculated automatically.

•

OpenScape Voice remote admin IP (RSA) - The OpenScape Voice Remote Admin IP address of the OSV server.

NOTE: If you don't manually prefill the IP address, it will be calculated automatically.

•

OpenScape Voice signaling IP - The OpenScape Voice Signaling IP address of the OSV server.

NOTE: If you don't manually prefill the IP address, it will be calculated automatically.

•

OpenScape Voice signaling managers IP (SIPSM) (*) - The SIPSM IP address of the OpenScape Voice where the SIP messages are sent too (e.g. REGISTER)

NOTE: If you don’t manually prefill the IP Address, it will be calculated automatically.

•

OpenScape Voice signaling FQDN name (SIPSM) - SIP signaling manager FQDN. The value must be part of the OSV domain i.e. osv.<Domain Name>.

This value is automatically generated for OSEE deployments or when left empty in RA solution.

NOTE: Both FQDN and DNS SRV entries should be filled if "Enable FQDN support on OSV" on the General tab is set to 'yes'

•

OpenScape Voice signaling DNS SRV name (SIPSM) - SIP signaling manager DNS SRV. The value must be part of the OSV domain i.e. osv.<Domain Name>.

This value is automatically generated for OSEE deployments or when left empty in RA solution.

NOTE: Both FQDN and DNS SRV entries should be filled if "Enable FQDN support on OSV" on the General tab is set to 'yes'

•

OpenScape Voice MTLS FQDN name (SIPSM) - SIP MTLS signaling manager FQDN. The value must be part of the OSV domain i.e. osv.<Domain Name>;.

This value is automatically generated for OSEE deployments or when left empty in RA solution.

NOTE: Both FQDN and DNS SRV entries should be filled if "Enable FQDN support on OSV" on the General tab is set to 'yes'.

•

OpenScape Voice MTLS DNS SRV name (SIPSM) - SIP MTLS signaling manager DNS SRV. The value be part of the OSV domain i.e. osv.<Domain Name>.

This value is automatically generated for OSEE deployments or when left empty in RA solution.

NOTE: Both FQDN and DNS SRV entries should be filled if "Enable FQDN support on OSV" on the General tab is set to 'yes'.

•

OpenScape Voice MTLS IP - This field is mandatory if the TLS protocol is selected as SIP transport protocol! This field is only mandatory if you do NOT generate a node.cfg via WebCDC and TLS protocol is selected. When you generate a node.cfg with WebCDC, then this field is filled in automatically.

•

OpenScape Voice billing IP - The OSV Billing IP address of the OSV server.

NOTE: If you don't manually prefill the IP address, it will be calculated automatically

•

OpenScape Voice cluster interconnect IP (Xchannel) - The OSV Cluster Interconnect IP address of the OSV server.

NOTE: If you don't manually prefill the IP address, it will be calculated automatically

•

OpenScape Voice CSTA IP - The OSV CSTA IP address of the OSV server.

NOTE: If you don't manually prefill the IP address, it will be calculated automatically.

•

OpenScape Voice LSM IP - The OSV LSM IP address of the OSV server.

NOTE: If you don't manually prefill the IP address, it will be calculated automatically.

•

OpenScape Voice MGCP/NCS IP - The OSV MGCP/NCS IP address of the OSV server.

NOTE: If you don't manually prefill the IP address, it will be calculated automatically.

•

Administration Network ID (*) - This field is mandatory if WebCDC needs to generate a node.cfg or when an Integrated Simplex OSV is used in solution.

•

Administration Netmask (*) - This field is mandatory if WebCDC needs to generate a node.cfg or when an Integrated Simplex OSV is used in solution.

•

Administration Default Gateway (*) - This field is mandatory if WebCDC needs to generate a node.cfg or when an Integrated Simplex OSV is used in solution.

•

Administration Start IP address -

–

The start IP address needs to be different than the Network ID. Normally the network ID is not used as IP address.

–

When the Start IP address is filled in, then WebCDC uses this start IP address.

–

If the field is empty, then WebCDC takes automatically the Network ID + 2 as Start IP address.

–

This field is mandatory if WebCDC needs to generate a node.cfg or when an Integrated Simplex OSV is used in solution.

•

Signaling Network ID (*) - Signaling Network ID (subnet)

•

Signaling Netmask (*) - Signaling Netmask

•

Signaling Default Gateway (*) - Signaling Default Gateway

•

Signaling Start IP Address -

–

The start IP address needs to be different than the Network ID. Normally the network ID is not used as IP address.

–

When the Start IP address is filled in, then WebCDC uses this start IP address.

–

If the field is empty, then WebCDC takes automatically the Network ID + 2 as Start IP address.

–

This field is mandatory if WebCDC needs to generate a node.cfg or when an Integrated Simplex OSV is used in solution.

•

Billing Network ID (*) -

•

Billing Netmask (*) -

•

Billing Default Gateway (*) -

•

Billing Start IP address -

•

Cluster Interconnect Network ID - This field is mandatory if WebCDC needs to generate a node.cfg

•

Cluster Interconnect Netmask - This field is mandatory if WebCDC needs to generate a node.cfg

•

Cluster Interconnect Default Gateway - This field is mandatory if WebCDC needs to generate a node.cfg

•

Cluster Interconnect Start IP address - This field is mandatory if WebCDC needs to generate a node.cfg

NOTE: A second block of data (identical to the above) will be displayed for Node 2 when OpenScape Voice Type is set to Standard Duplex.

Buttons on this tab:

•

Auto fill OSV Subnets - Fills in the IP address information based upon pre-set assignments and information provided in the Subnet field.

OpenScape Solution Set V10, Customer Data Collection with WebCDC V1, Planning Guide, Issue 2, ID: A31003-S11A0-P100-2-76A9

© 07/2024 Mitel Networks Corporation. - All rights reserved.
Mitel and the Mitel logo are trademarks of Mitel Networks Corporation. Unify and associated marks are trademarks of Unify Software and Solutions GmbH&Co. KG. All other trademarks herein are the property of their respective owners.