You can add new PBX nodes and edit existing PBX nodes on the PBX Node Details page.
NOTE: The fields on the PBX Node Details page vary between MiVoice Business, MiVoice Office 250, MiVoice 5000, MiVoice MX-ONE, and MiVoice Office 400 PBX nodes. Some fields are PBX-specific and do not appear if they are not required for the PBX.
NOTE: Some configuration fields are disabled if MiCollab Client is running in MiCollab-integrated mode. MiVoice 5000, MiVoice MX-ONE, and MiVoice Office 400 are only supported in MiCollab integrated mode. Refer to the MiCollab Administrator Help for more information.
If you are configuring multiple MiVoice Office 250 nodes, click here to review information about using a CT Gateway.
For multiple MiVoice Office 250 nodes, you can streamline the synchronization process by configuring synchronization between the Unified Communications server and a single CT Gateway supporting the multi-node configuration.
After you configure the CT Gateway for synchronization, you do not need to complete synchronizations for each PBX node. When the MiCollab Client Service synchronizes with the CT Gateway, the required data for all of the associated PBX nodes is updated on the Unified Communications server.
Add each PBX node in the multi-node configuration to the MiCollab Client Service (Adding and Editing PBX Nodes).
Add the CT Gateway as the final PBX node in the configuration (Adding and Editing PBX Nodes).
Configure PBX Node synchronization (Synchronization tab).
Remember the following guidelines when configuring a CT Gateway for multiple MiVoice Office 250 nodes:
You cannot synchronize individual PBX nodes. However you can synchronize all nodes using the Sync Now button on the Synchronization tab.
All PBX-node level settings, including Voice mail server and Voice mail public number, should be configured for the actual PBX node, and not the CT Gateway node.
Each node's Session Manager must have a DB Programming account with a password that matches the password set for the single CT Gateway node.
The CT Gateway must be running software version 4.4.01 or higher.
All nodes configured on the CT Gateway must be communicating (up and working) so that the PBX synchronizer will synchronize all of the accounts. If one or more of the MiVoice Office 250 nodes are not communicating with the CT Gateway, the node will not be synchronized as indicated by the message that is generated under the PBX Nodes tab.
All nodes connected to the CT Gateway must be using OAI protocol version 10.0 or later (MiVoice Office 250 v3.2 or later). Node connections to the CT Gateway that are not running protocol version 10.0 or later must be removed from the CT Gateway, or the nodes must be upgraded to v3.2 or later.
It is recommended that all duplicate extensions between nodes be removed before installing the CT Gateway. If this is not done, one of the accounts with the duplicate extension information will be deleted during the synchronization.
NOTE: You are not required to configure the resilient node.
Description: (Required) Type a name for the PBX node. By default, this field is blank. The Description field is limited to 1-64 characters in length, and must contain alpha-numeric characters (dashes and spaces included).
Hostname: (MiVoice Business Only - Required) Type the IP address or hostname for the MiVoice Business PBX node in this field. By default, this field is blank.
NOTE:
The values for the following read-only fields apply to MiVoice Business PBXs only
and are generated after the MiCollab Client Service
synchronizes with the PBX.
• Version: Indicates the software version that
the MiVoice Business
PBX is currently running.
• Handoff
feature code: Indicates
the feature code programmed for the Handoff feature on the MiVoice Business PBX.
As a prerequisite, the MiVoice Business
Feature Code for Handoff must be programmed. If this feature
is added to an existing server, the PBX need to be synchronized
with MiCollab Client
before the feature can be used.
Internal IP address/hostname: (MiVoice Business only - Required) Type the internal IP address or hostname for the Mitel MiVoice Business PBX node in this field. If your PBX configuration includes an expanded Processing Server (PS1), type the IP address of the base server in this field and type the IP address of the PS1 in the OAI IP address/hostname field.
External IP address/hostname: (Mitel MiVoice Business/Mitel MiVoice Office 250 Only - Optional) Type the external IP address or hostname for the PBX node. This field applies to remote MiCollab Client softphones in teleworker mode. The External IP Address/Hostname provides a communication path between remote users and the PBX. By default, this field is blank.
Extension length: (Required) Extension length is the maximum length that can be configured for a PBX DN. The DN extension can range from 1 to the maximum extension length. Select the number of digits used for internal extensions on the PBX. Options include 3-7 digits. By default, this field is set to 4.
Registration code:(MiVoice Business
Only-Required) Type the registration code as configured
on the MiVoice Business
PBX. The valid length is 1-10 digits, and valid characters
include 0-9, *, and #.
The registration code corresponds to the Set Registration Access
Code or Set Replacement Access Code, programmed in the MiVoice Business System
Administration Tool (Systems Options Assignment form). These
codes, typically 3 characters in length, can be a maximum
of 10 characters long. A single Set Registration and Set Replacement
Access Code applies to all IP devices on the system. Set Registration
and Set Replacement Access Codes make up the first part of
an IP device Personal Identification Number (PIN). The second
part of the PIN is the IP device extension. For example, if
an IP device has a PIN of 9991000, 999 is the Set Registration/Replacement
Access Code and 1000 is the extension number.
The registration code can be one to 10 characters in length,
and can include digits 0-9, *, and #. By default, this field
is blank.
Dialing prefix: (Optional)
Type the number that the user dials to obtain an outside line
on the system. The dialing prefix is inserted automatically
when the user makes a call from the History view, or from
an imported contact. The dialing prefix can be 1-32 digits
in length, and can include digits 0-9. By default, this field
is blank.
The dialing prefix is not inserted by MiCollab Client
when the number dialed starts with the ‘-‘ character (a hyphen).
For example, if the number dialed by the MiCollab Client
client is -4809619000, then the number dialed by the PBX is
4809619000 (without the hyphen). If the number dialed by the
MiCollab Client
client is 4809619000, then the number dialed by the PBX is
94809619000, where 9 has been defined as the PBX node outgoing
prefix.
Voice mail server: (Specific to NuPoint voice mail only - Optional. If an embedded voice mail is in use, then do not enter it.) Type the IP address or hostname for the node’s voice mail server. The voice mail server configured here serves all accounts assigned to this node. If this field is left blank, all accounts assigned to this node will use the voice mail server configured on the Enterprise tab. If required, you can configure a different voice mail server on a user's account, which will override the voice mail server you configure here and on the Enterprise tab. The voice mail server can be 1-128 characters in length.
Voice mail number: (Required) Type the voice
mail extension for NuPoint UM. If required, you can configure
a different voice mail extension on a user's
account, which will override the extension you configure
here. The voice mail number can be 1-32 digits in length,
and can include digits 0-9. By default, this field is blank.
If MiCollab Client is running in integrated mode and you change
the voice mail number, it is applied to all MiCollab
Client accounts on the PBX. If MiCollab Client is running
in co-located mode, it is just applied to new accounts (see
following option).
Apply voice mail number to all accounts: (Optional) This option is only present when MiCollab Client is running in co-located mode. It allows you to quickly change the Voice mail number for all accounts on the node configured for the same voice mail number. After you change the Voice mail number, select this option, and then click Save. All accounts that were configured for the previous Voice mail number are updated to the new Voice mail number.
Voice mail public number: (Optional) Type the voice mail public number for NuPoint UM. If required, you can configure a different voice mail public number on a user's account, which will override the voice mail public number you configure here. The voice mail public number can be 1-32 digits in length, and can include digits 0-9. By default, this field is blank.
No answer timer: (Optional) Type an amount of time, in seconds, slightly less than the amount of time that will elapse before an incoming unanswered call is directed to voice mail. This setting is used by MiCollab Client for call forwarding. The No answer timer can be 0-60 seconds in length. By default, this field is set to 16 seconds.
Username: (MiVoice Business only
- Required) Type the username of the preconfigured
account on the PBX node that will be used by the MiVoice Business directory
synchronizer. The username field can be 1-64 characters in
length. By default, this field is blank.
To configure an MiVoice Business
PBX node synchronizer, an administrator user account must
exist on each MiVoice Business
node (User Authentication Profiles in the MiVoice Business
System Administration Tool). This account must have System
Access enabled. The MiVoice Business
user name and password must be specified in the properties
of each switch that will be synchronized.
NOTE: For security reasons, you can create an administrator user account that has System Access enabled, with No Access as the assigned Access Type using the System Administrator Policies form.
Password: (MiVoice Business only - Required) Type the password of the preconfigured account on the PBX node that will be used by the PBX node synchronizer. This is the password for the MiXML connection to the node. The password can be 1-64 characters in length. By default, this field is blank.
Internal OAI IP address/hostname: (Mitel MiVoice Office 250 Only) This field is only required when the Mitel MiVoice Business PBX node includes an expanded Processing Server (PS-1). Type the internal IP address of the PS-1 in this field. Type the IP address of the base server in the Internal IP address/hostname field.
External OAI IP address/hostname: (Mitel MiVoice Office 250 Only -Optional) This field is only required when the Mitel MiVoice Business PBX node includes an expanded Processing Server (PS-1). Type the External IP address of the PS-1 in this field. This field applies to remote MiCollab Client SIP softphones in teleworker mode. The External IP Address/Hostname provides a communication path between remote users and the PBX. By default, this field is blank.
OAI port (Mitel MiVoice Office 250 Only - Required): Type the port number used for the OAI connection to the MiVoice Business node. The range for this field is 1-65,535. By default, this field is 4000.
OAI password: (Mitel MiVoice Office 250 Only - Optional) Type the password of the preconfigured account on the PBX node that will be used by the PBX node synchronizer. This is the password for the OAI connection to the node. The password can be 1-64 characters in length. By default, this field is blank.
IP/Digital Telephone Database Programming Password: (Mitel MiVoice Office 250 Only – Optional) Type the password required by Administrator phones, when programming the Mitel MiVoice Business system through the phone. The password can consist of up to eight numeric characters. By default, this field is blank. In Mitel MiVoice Business Database Programming, this field is located under System\Phone-Related Information\IP/Digital Telephone Database Programming Password\Edit Password.
Language: (Optional) Select a language from the list if you want to override the Enterprise language settings for the PBX. You can configure the language parameter on the Enterprise, PBX, or account level. The Enterprise language field sets the default language for all accounts on the Enterprise. The PBX language setting overrides the Enterprise setting, and the account setting overrides the PBX setting. The user's language setting determines which language the Welcome E-mail Message is generated in for that user.
Reload Dialed Digits Processing Template Files: Select the dialed digits processing logic to be used when a MiCollab Client user enters a phone number from the client. Once the dialed digit processing files are modified, clicking on this button will reload the files into the MiCollab Client system. This will update the processing logic for all PBXs across all enterprises on that MiCollab Client Service.
NOTE: The dialed digits processing logic should not be modified unless instructed to do so by Mitel support personnel. Since this affects the very way numbers are dialed from MiCollab Client, incorrect processing may render useless large parts of the system.
This area of the PBX Node Details page includes fields for specifying plus dialing settings.
NOTE: Starting with MiCollab Client 5.1, some of the dialed digit processing happens locally within MiCollab Client clients. Due to this, if some dialing settings are changed in the server-manager, all clients within that enterprise (or for that PBX) should be restarted. Following are the settings affected by this:
The plus dialing settings include:
NOTE: It is important that sites using E.164 (plus dialing) settings set up ARS on the PBXs to strip the Toll Digit for local calls.
NOTE: The Plus Dialing Settings on the PBX Node tab override those on the Enterprise tab.
NOTE: starting with + and strips the (0) from the digit string before processing the dialed digit string for insertion of the international access code and the long distance code. This change addresses the needs of European customers who have numbers such as +44(0)<number> in their contacts. The (0) in the number is optional, based on the location from which the user is calling the number. For example, if the number +44(0)6665544 is dialed from the MiCollab Client client by a user in the United States SA, then the number dialed by MiCollab Client is 011446665544 where 011 is the international access code and 44 is the country code of the United Kingdom. If the same number is dialed from the MiCollab Client client by a user within the United Kingdom, then the number dialed by MiCollab Client is 006665544, where 0 is the dialing prefix, the dialing prefix, and also the long distance code defined for the PBX node under the Plus Dialing settings.
CLID Translation: This field is only applicable to 3300 type PBX. This field should be set to a list of comma separated digits (such as 0, 00). The MiCollab Client Service will them remove these leading digits from incoming numbers before generating call records and call history information.
At most, one digit string (the first one that is applicable) will be applied to any given number. For example, suppose the incoming number is 001143476276 and the CLID translation is specified as 00, 11. The MiCollab Client Service will translate that number into 1143476276, due to the fact that the first CLID translation string (00) matched the leading digits of the incoming number. The fact that the next CLID translation string (11) matches the now leading digits of the incoming number is inconsequential because the CLID translation has already been done once.
NOTE: This feature is only applicable to 3300 type PBX.
NOTE: Whitespaces in the field are ignored.
NOTE: If the field is empty, then the CLID translation settings at the enterprise level will take effect. If the enterprise level CLID translation string is empty as well, then no translation is done.
These default settings are used on the Dynamic Status page in the desktop client.
Forward my calls to:
Use PBX Default (default)
Voice Mail
NOTE: The Under these conditions option is available only if Forward my calls to is set to Voice Mail.
Under these conditions:
Busy (default)
No Answer
Busy and No Answer
These default settings are used on the Dynamic Status page in the desktop client.
When I am on the phone:
Use PBX Default (default)
Voice Mail
If I do not answer:
Use PBX Default (default)
Voice Mail
For MiVoice Business PBX nodes, schedule Line Monitor Cache refreshes.
During a Line Monitor Cache refresh, the MiCollab Client Service requests updated information for the MiVoice Business phone lines configured for MiCollab Client. On average, the refresh takes one second per single-line set and two seconds per three or four-line set.
NOTE: System Performance. During a line monitor cache refresh, clients are taken offline temporarily, and then automatically returned to service with the new line configuration. Schedule line monitor cache refreshes during low traffic periods. No server reboot is required.
To schedule line monitor cache refreshes:
Select a day or days of the week to perform the refresh.
Select an hour, minute, and AM/PM interval to perform the refresh.
For MiVoice Office 250 PBX nodes, skip to the next step.
Select the checkbox Disable MX-ONE Statuses to disable the additional MX-ONE Statuses and diversion profile integration for all users under the selected PBX node. The default status In the Office will be selected for all users having an additional MX-ONE status.
Deselect the checkbox Disable MX-ONE Statuses to enable the additional MX-ONE Statuses and diversion profile integration for all users under the selected PBX node.
NOTE: You will receive a confirmation box when the settings are saved or created. Click Ok to proceed with the settings.
Click Refresh to view the current status of the operation:
NONE
FAILED
SUCCESS
Enabling In Progress
Disabling In Progress
Click Create to create the PBX node.
Click Save to save the updated information for the PBX node.
Click Cancel to return to the PBX Node tab without making changes.
You are returned to the PBX Nodes tab.
After you add a PBX node, configure the PBX node synchronizer, and perform a synchronization, you can view read-only synchronization details for the last synchronization completed.
Click Synchronization Details to expand the page. Details include:
Reload Dialed Digits Processing Template Files
Once the dialed digit processing files are modified, clicking on Reload Dialed Digits Processing Template Files button will reload the files into the MiCollab Client system. This will update the processing logic for all PBXs across all enterprises on that MiCollab Client Service.
NOTE: The dialed digits processing logic should not be modified unless instructed to do so by Mitel support personnel. Since this affects the very way numbers are dialed from MiCollab Client, incorrect processing may render useless large parts of the system.
Related Topics: