PBX Nodes Tab
The PBX Nodes tab provides a table for the PBX nodes you have added to the Enterprise.
- IP Address: Indicates the IP address for the PBX server.
- Description: Indicates the description that you provide for the PBX node.
- Version: ( MiVoice Business only): Indicates the software version the PBX is currently running.
- Extension Length: Specifies the number of digits used for extensions on the PBX node.
- Voice Mail Number: Specifies the voice mail extension for NuPoint UM on the PBX node.
- Last Sync: Specifies the date of the last PBX node synchronization.
- Sync Status: Specifies the status of the last PBX node synchronization. Results include In Progress, Success, Success with Info and Failure. You can view synchronization details from the PBX Node Details page.
CSTA settings
-
Port: Type the port MiCollab Client uses for MiVoice MX-One or MiVoice 5000. This setting should remain at default. If the PBX port number changes, the PBX administrator needs to inform you so you can modify this setting.
-
MiVoice MX-One : Default value is 8882.
-
MiVoice 5000 : Default value is 3211. In rare instances, there may be multiple ports for the MiVoice 5000. Type the port numbers, up to three, separated by a semi-colon.
Note:If you change the Feature Access Code on UCA, you need to restart the client.
-
-
Extended checking of the phone device: Default is Off. Turn on only when directed by support.
-
Print PDU: MiVoice 5000 only. Default is Off. Turn on only when directed by support.
-
Number of log files: MiVoice 5000 only. Type the number of log files to store. Default value is 10.
-
Maximum file size: MiVoice 5000 only. Type the maximum log file size. Default value is 3 MB.
-
Protocol file: MiVoice 5000 only. Type the name of the file used for the trace. Default is pdutrace.
-
XML trace active: MiVoice MX-One only.
-
Use phone number block: Type the device range to handle devices only in this range. For MiVoice 5000 the range is 2001 to 3001
Group Call Pickup Feature Access Code: This option is visible to both PBX types, MX-One and MiVoice 5000. This option helps to store the feature access code which is provisioned in MX-One for Group Call Pickup in the UCA database.
Note: If the Group Call Pickup Feature Access Code (FAC) is changed in the administrator portal, then no notification is sent to the clients. Clients will need to re-login to get the updated FAC details.
-
Sort the information in the table.
-
Select one or more entries in the table.
-
Click the Add Node link to add a PBX node.
-
Click the PBX node link in the IP Address column to edit the PBX node.
-
Delete a PBX node.
To delete a PBX node:-
Select the node you want to delete from the PBX node list.
-
Click the Delete Node link. A dialog box appears prompting you to confirm the deletion.
-
Click OK to delete the node, or click Cancel to cancel the deletion.
-
-
Synchronize specified PBX nodes.
To synchronize one or more nodes:-
Select the nodes you want to synchronize.
-
Click the Synchronize link. A dialog box appears prompting you to confirm the synchronization.
-
Click OK to start the synchronization, or click Cancel to cancel the synchronization.
Note: The Synchronize link only appears when the PBX Node Synchronizer has been enabled on the Synchronization tab. The Synchronize link does not apply to multi-node Mitel MiVoice Office 250 sites that are configured for synchronization with a CT Gateway. For this type of configuration, all of the nodes can be synchronized using the Sync Now button on the Synchronization tab. -
-
Click
to open the PBX Administration Tool .
Using the PBX administrator's Web window, you can complete configuration, maintenance, and diagnostic tasks for the PBX node, without logging out of the Unified Communications administrator interface. Close the PBX administrator's Web window when you have finished updates to the PBX node.
-
Click
to complete a Line Monitor Cache refresh (MiVoice Business only).
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. -
Refresh the information on the page.