# Network Elements

## Purpose

The Network Elements form manages all elements within a network. Use this form to

- view, define, and manage the basic attributes of network elements, such as name, IP address, type, data-sharing status, and zones.

- specify the elements that you want to start sharing system data with and set the scope All Network Elements, All Cluster Members, All 3300 ICPs, Network Group Members, Admin Group Members, Resilient Pair, Member Hosts, Hospitality Gateway and Guest Room Host, Hospitality Gateway and Suite Host, or None. of the sharing.

- specify elements that you want to synchronize data with and select the forms and data records that you want to synchronize.

- sort, modify, and delete network elements belonging to a data-sharing network or cluster.

- create network elements for SIP trunks by creating a network element for the local switch, a network element for each SIP peer, gateway or Service provider, and creating a network element for the Outbound Proxy, if one exists in the network (see Program SIP Trunks).

Use this form when performing the following tasks:

- System Data Synchronization Programming Overview

- Synchronizing Data

- Add Elements to Network Elements form

For more information:

- About System Data Synchronization

- About the SDS Forms

## Conditions

- Each network element must have a unique IP address or FQDN. Otherwise, the SDS synchronization fails.

- The local network element record is automatically created during system software installation, and cannot be deleted.

- A cluster must be created (defined) in the Cluster Elements form before you can assign elements to it. See Voice Clustering Programming Overview for instructions on how to set up clusters.

- ICP/PBX Networking entries are added automatically by configuring MiVoice Business/3300 ICP Network Element entries with unique PBX Numbers/CEIDs in the Network Elements form. Conversely, ICP/PBX Networking entries are not automatically deleted by the Network Element form. Deletion of ICP/PBX Networking entries must be performed in ICP/PBX Networking form.

NOTE: A network element is automatically displayed here each time a new gateway trunk profile is added.

- Following a software upgrade (or downgrade), clear your browser cache to remove any stale data that could otherwise prevent you from initiating an SDS synchronization. A grayed-out Sync button is an indication that the cache needs clearing.

## Field Descriptions

Parameter | Description | Default Value
Name | Enter a unique name of up to nine characters for the network element. Other rules for names: can start with either an upper or lower-case letter; all other letters can be upper or lower case. non-alpha characters are allowed. spaces are NOT allowed (because it affects SIP trunking). This naming convention must be followed if MiVoice Enterprise Manager will be used to manage the network element. The name displays in read-only format in the system name field in the local element's System Options form. NOTES The name must be identical to the element name entered in Enterprise Manager. Otherwise, attempts by Enterprise Manager to program resilient data on the secondary controller will fail. The name must also be identical to the name of the networked voice mail server (if programmed) in the VM Network Servers form; otherwise, you will be unable to add or edit extension mailboxes. Avoid using spaces in the names you assign as they cause problems for certain SIP-related maintenance commands. | Blank
Type | Select the network element type (for example, 3300 ICP) from the drop-down list. 3300 ICP (includes MiVoice Business for ISS and proprietary Mitel hardware platforms running 3300 ICP or MiVoice Business call-processing software) SX-2000 Microlight SX-2000 Redundant Outbound Proxy Other (includes SIP Peers) MSL Server MSL Server (MiCollab) Directory Server Application Server Enterprise Manager SIP DECT Manager NOTES Some network element types, such as Directory Servers, do not support data sharing. MSL Server-type network elements do not support multiple clusters. For example, Open Integration Gateway. The MSL Server (MiCollab) option is used for MiVoice Business Express (MiVB-X) and MiCollab. | 3300 ICP
FQDN or IP Address | Defines the Fully Qualified Domain Name (FQDN) or IP Address (IPv4 or IPv6) of the network element. This field is disabled for the local network element. In SDS shared networks that contain cluster nodes on a release earlier than MiVoice Business Release 9.0, continue using IPv4 addresses. If you use FQDN, then in the Controller Registry form, enter fqdn in the IP Local Address (ipv4/fqdn) field. Use either FQDN or IP address for SIP devices, depending upon the SIP Service Provider's specification. IMPORTANT: If you change the IP address of a network element, make sure that you back up the database. If you do not back up the database after the IP address is changed, the restore fails. NOTES To use the System Data Synchronization (SDS) feature, you must use IPv4 addresses until all the nodes on the network support FQDNs. To change the local system's IP address, host or domain name, use the Server Manager application (Not applicable to Container-based MiVoice Business (cMiVB)). Configure the external LDAP with the FQDN (instead of the IP address) if the IDS LDAP network element exists with the same IP address. If the FQDN or IP Address field is greyed out, you need to access the form - Controller Registry to update Registry key ( of IP local Address (Iipv4/fqdn) from fqdn to ipv4 and reboot | Blank
Data Sharing | System-generated field. Identifies the current data-sharing state of each network element listed. This field displays each network element's data-sharing status and scope as follows:
---- | indicates that the field is not applicable to local element
NO | indicates that the element is not sharing with local element in any scope
YES* | indicates that the element is a member of a cluster but is sharing only at the network level (that is, sharing has not been initiated at the cluster level).
YES | indicates that the element is sharing data within either a network or cluster scope, or both.
NOTE: Data Sharing is always disabled for network elements that do not support SDS, such as Directory Servers. | True/False
Local | Displays "True" if the selected network element is local. Displays "False" if the selected network element is not the local element. This field should only display "True" for the element you are logged in to. NOTE: The local PBX for each network element is assigned in the ICP/PBX Networking form. |
Version | If the local element is sharing data with a remote element, this field displays the remote element's software version. The version number is cleared if you disable SDS on either element, or disable data sharing between the elements. | Blank
Zone | The zone specified for the IP voice media stream originating or terminating at the selected 3300 ICP/MiVoice Business system. It defaults to 1. The zone range is 1-999. See Bandwidth Management - Programming for conditions and dependencies on zone assignments in a mixed-release network. | 1
ARID | System-generated field. Shows the element's Application Record ID as obtained from the Mitel Application Management Center (AMC). |
SIP Peer | To add a network element for a SIP trunk, select "Other" as the Type, select this check box, and then fill in the related SIP Peer Specific fields that are displayed. NOTE: The Zone for the SIP Peer is assigned in this form. | Blank
3300/SX-2000 Properties NOTE: Field header grouping identifies properties that apply only to 3300 ICP/MiVoice Business or SX-2000 systems.
Member Of Cluster | Enabled if the selected network element is a member of the cluster, and indicates the cluster name. This field is not enabled if the selected network element is not a member of the cluster. | Blank
Member Of Cluster (cluster) | Enabled if the selected network element is a member of the cluster, and indicates the cluster name. This field is not enabled if the selected network element is not a member of the cluster. | Blank
PBX Number/Cluster Element ID | Enter a unique (within the form) PBX Number /Cluster Element ID in the range 1 to 999. The PBX Number/Cluster Element ID links the Network Element with its corresponding ICP/PBX Networking entry. If the element is a member of a local cluster, the ID also links the element with its corresponding Cluster Element entry. For cluster elements the CEID Index number associates a CEID digit string in the Cluster Elements form with remote directory numbers in the Remote Directory Numbers form. If you enter a CEID index, you must enter a corresponding CEID digit string before you can commit the form. Before you can delete a CEID index, you must delete all references to remote telephone directory entries that are associated with that CEID index. NOTES In a clustered, a redirect, or a resilient environment the PBX Number in the ICP/PBX Networking form must match the CEID Index Number. Entry of a unique PBX Number/Cluster Element ID is mandatory for IP Trunking, XNET, and cluster elements, but not enforced by the system in the Network Element form in MCD Release 5.0. Enforcement will come in a future release. In the meantime, a message box will display each time the form is opened (unless you use the check box to stop it) as a reminder to enter unique numbers/IDs. Changes to the ICP/PBX number for cluster elements must be made in the Network Elements form. Furthermore, the changes must be made from a member of the same cluster where all members are sharing with each other and running MCD 5.0. For non-clustered elements with unique PBX numbers, you are advised to make any numbering changes in the Network Elements form since the form is shared with other 3300 ICP/MiVoice Business systems in the same SDS community. If the PBX number is duplicated, then you should change the PBX number in the Network Element form first, and then in the ICP/PBX Networking form of each 3300 ICP/MiVoice Business system in the cluster. The ICP/PBX Networking form is not shared by SDS and so must be manually updated. For more recommendations, see Tips on Assigning and Changing PBX Numbers. The PBX Number / Cluster Element ID can only be changed from a 3300 ICP/MiVoice Business system that is a member of the same cluster. | Blank
Primary Node Id (PNI) | The Primary Node ID is used to route calls to other non-cluster elements in the network. You can only modify the local element PNI in this form. You cannot modify the PNI of an element belongs to a cluster. Enter a value of up to seven digits in length. This value also appears in the ARS Node Identities form in the primary Directory Number (DN) field. A PNI cannot appear as a directory number or as an ARS string on any of the systems in the network. Use the "Locate Number" maintenance command to determine if the PNI is a number that is already used on any of the other elements in the network. | Blank
Outbound Proxy Specific NOTE: In the fields below, the default is blank. The default is blank in cases where DNS is used to determine the transport and port parameters. Otherwise, you should set the appropriate values. The common SIP UDP/TCP port is 5060, and the common SIP TLS port is 5061.
Outbound Proxy Transport | The list of transport parameters used in the SIP URI: UDP/TCP/TLS. | Default (UDP)
Outbound Proxy Transport Type | The list of transport parameters used in the SIP URI: UDP/TCP/TLS. | Default (UDP)
Outbound Proxy Port | Enter the port number of the Service Provider or the gateway. | Blank
SIP Peer Specific
SIP Peer Transport | The list of transport parameters used in the SIP URI: UDP/TCP/TLS. Use TLS if you require encryption between 3300 ICP/MiVoice Business devices in the same network. TLS is not supported across firewalls. | Default (UDP)
SIP Peer Port | Enter the port number of the SIP Peer. | 0
External SIP Proxy FQDN or IP Address | Enter the IP address (IPv4 or IPv6) or the Fully Qualified Domain Name (FQDN) of the SIP proxy server of the peer network. Do not fill in this field if an External SIP Proxy is not in use. | Blank
External SIP Proxy Transport | The list of transport parameters used in the SIP URI: UDP/TCP/TLS. | Default (UDP)
External SIP Proxy Port | Enter the port number of the proxy. | 0
SIP Registrar FQDN or IP Address | Enter the IP address (IPv4 or IPv6) or the Fully Qualified Domain Name (FQDN) of the SIP registrar of the peer network. Do not fill in this field if a SIP Registrar is not in use. | Blank
SIP Registrar Transport | The list of transport parameters used in the SIP URI: UDP/TCP/TLS. | Default (UDP)
SIP Registrar Port | Enter the port number of the SIP Peer. | 0
SIP Peer Status | Defines SIP peer status, which can be Auto-Detect/Normal, Disabled, or Always Active. Auto-Detect/Normal periodically sends OPTIONS messages to test to see if the link to the remote SIP Peer is alive. When the link is detected to have gone away the SIP Module marks the link out-of-service and periodically sends OPTIONS messages to restore service. Setting the Always Active option causes the SIP Module to assume that the link is available unless you choose another option. Use the Disabled option to temporarily disable a trunk connection |
SIP DECT Manager Specific |
Secure AXI Port | Port number assigned to the secure Application XML Interface (AXI) interface of the SIP DECT Manager network element. The valid range of values is from 0 through 65535. | 12622
Server Type | SIP DECT deployment configuration type: OpenMobility Manager (OMM) or MultiOpenMobility Manager (MOM). | OMM
Secondary SIP-DECT Manager FQDN or IP Address | FQDN or IP Address of a secondary SIP DECT Manager, if programmed. |
Username | Username for the administrative account configured in the SIP DECT Manager. | O
Password | Password for the administrative account configured in the SIP DECT Manager. |
Confirm Password | Password confirmation field. |
Auto-create on subscription | Enable/disable unbound subscription of SIP DECT phones (see OM DECT Phone Sharing and Provisioning Guide in the Document Center for more information). | True
Secure SIP Transport Protocol | Defines the transport protocol field in the SIP DECT manager's System. The drop-down list consists of - UDP, TCP, UDP and TCP, TLS, and Persistent TLS. | UDP