Multiple MiVoice Office 250 PBXs can be networked together to allow calls to be routed from one node to another. This allows calls to be handled by devices (agent, extensions, voicemail etc) on other nodes to where the call originated from and allows calls to be made through trunks on remote nodes using ARS.
There are two reasons why node configuration needs to be entered into the MCS website:
Each SIP device connected to the PBX has a specific node that they are programmed against and they connect to. Due to this, the MCS needs to now about these nodes and what their connection details are.
For example, when using a Mitel Phone Manager Softphone, a SIP connection would need to be made to the specific node that it has been programmed on. If connecting from the internal LAN network, the internal IP address of the node would be required. If connecting from a remote location, the external NAT IP address would be required.
The system will automatically import the node configuration during a device import but not all of the information can be retrieved this way and needs to be manually configured.
For more information on Softphone & 6900 SIP configuration, please refer to the Softphone/6900 Support section.
If Mitel Communication Service has been connected to multiple MiVoice Office 250 systems using a CT Gateway but has no Multi-Node license then one of the nodes needs to be selected as the 'Default' node. This node will be the one that MCS will accept Phone Manager connections from and provide IP SMDR and Agent Hot Desking services to.
To access the node configuration section, browse to the '' -> Site Settings -> Phone Systems -> PBX section. Scroll down to the Nodes section under Devices. If MCS is already connected to the PBX network then the Nodes section should already be pre-populated.
The following settings can be configured against each node:
Node ID: The unique node number for this PBX node as programmed on the telephone system in Database Programming
Description: In the Description field enter a user friendly name to identify this node.
Local IP Address: Set the Local IP address to be the internal LAN IP address of this node.
Local SIP port: Set the Local SIP port that will be used by the Softphone to use, by default this is 5060. This should match the configuration within Mitel Database Programming.
NAT IP Address: Set the NAT IP address to be the external IP address of this node. This will be used when the Softphone connects from a remote location.
NAT SIP port: Set the Nat SIP port that will be used by the Softphone to use on when connecting from a remote location.
Extension Programming Password: If there is an extension programming password configured on the node, it needs to be configured here so that the MCS can perform operations such as changing the Caller ID on an extension.
Encryption Password: This password is used when querying SIP Authorization Credentials from the telephone system for use with 6900 phones and Phone Manager Softphones. The password configured here must match the App Suite Encryption password configured on the node. For more information, please refer to the Encryption Password section.
Is default: The Is Default setting sets what the primary node connection is.This is to configure what extensions that Phone Manager clients can connect to when the system does not have a multi-node license. If a Phone Manager client tries to connect to an extension on a node other than the one that has the Default setting then the connection will be refused. With a multi-node license Phone Manager clients can be associated with any extension on any node. See the Multi-Node Scenarios section for more details.
Voicemail DID: An external DID number to access the Voicemail Retrieval application on the telephone system. This is used by Phone Manager Mobile.
Auto Attendant: An external DID number to access the auto attendant on the telephone system. This is used by Phone Manager Mobile
Wait time: The amount of time after a call is connected before any DTMF digits are dialed.