MiVoice Office Application Suite - Technical Manual
Network Configuration
 

Network Configuration

The MCS requires a 100Mb/1Gb LAN connection that has access to the telephone system. Phone Manager clients will also need access to the MCS over the network. If the server is installed into a Microsoft Active Directory environment then it should be added to the domain, ideally before the MCS software is configured.

Custom Active Directory Group Policies can adversely affect the system and they should be tested before going live.

To enable users to easily access the server with the website role a valid DNS entry should be created that can then be used when browsing to the server, for example http://communicationserver.

The sections below provide information on all ports used by the system that may need to be opened on server or network based firewalls. Which ports will depend on the features and system configuration.

For information on configuring remote connections through an MBG, please refer to the Engineering Guidelines.

 

MiVoice Office Application - Host Server

Incoming Ports

The following ports need to be opened on the firewall of the server running the MiVoice Office Application Suite:

Application Description Source Port
Website access Browser access to the MiVO App Suite website for Configuration, Reporting, Recording Access etc. Browser Access HTTP 80, HTTPS 443
Phone Manager Desktop CTI Event Link Phone Manager Desktop TCP 2001
Client Sessions Phone Manager Desktop TCP 8187, 8186
Client Personal Wallboard Sessions Phone Manager Desktop TCP 8200, 8204
Broadcast location service Phone Manager Desktop UDP 8184
Phone Manager Mobile Client Sessions Phone Manager Mobile TCP 8185
Audio Phone Manager Mobile TCP 8190
SIP Audio MiVoice Office 250 UDP 20000-20500
SIP Proxy MiVoice Office 250 TCP 8196
MiVoice Office Call Recorder MiVoice Office 250 SIP (RAC Call Recording) MiVoice Office 250 UDP 5060
MiVoice Office 250 Audio (RAC Call Recording) MiVoice Office 250 UDP 12000-12100
Live Streaming Browser Access TCP 8201
Integration Services Call Recorder Client and Phone Manager Desktop TCP 8188
6900 Handset Service Server Connections & 6900 Handset Requests 6900 Series Handsets

HTTPS 8202, HTTP 8203

6900 Handset Multicast DNS 6900 Series Handsets UDP 5353
6900 Handset Requests 6900 Series Handsets TFTP 69
6900 Handset Directory Requests (LDAP) 6900 Series Handsets TCP 8205
6900 Syslog 6900 Series Handsets UDP 514
Windows Time Server Windows Time Server UDP 123

MiVoice Office Real-Time
Wallboard / Dashboard

Data Link from client browser or from Amazon Fire TV application. Browser Access and Amazon Fire TV

TCP 8200, 8204

       

Outgoing Ports

MiVoice Office Application Suite makes outgoing connections to the ports listed in the table below. The local port used by the server when making these request will be random.

Application Description Target Port
Licensing License update and activation requests to the licensing server. https://service.xarios.com HTTPS 443
Phone Manager Mobile SIP Audio MiVoice Office 250 UDP 20000-20500
Push Notification Service https://fcm.googleapis.com/fcm/send
sb://mcs-default.servicebus.windows.net
TCP 5228, 5229, 5230, HTTPS 443
CTI Link CTI Link to Phone System

MiVoice Office 250 / CT Gateway

TCP 4000
MiVoice Office Call Recorder MiVoice Office 250 SIP (RAC Call Recording) MiVoice Office 250 UDP 5060
MiVoice Office 250 Audio (RAC Call Recording) MiVoice Office 250 UDP 12000-12100
6900 Handset Service Outgoing post to handsets 6900 Series Handsets HTTP 80

 

Internal Use Ports

The following ports are used by internal services on the MiVoice Office Application. Traffic on these ports will not leave the server.

Port/Protocol
TCP 8183
TCP 8189
TCP 8191
TCP 8197
       
During the installation rules will be added to the in-built Windows Firewall for ports used by the MCS services. When using the Record-A-Call or SIP/RTP recording, the IP address of the PBX (Base server, PEC & PS1) may need to be added to the firewall allowed list to allow traffic into the MCS.

 

Phone Manager Desktop Client

The table below outlines the network connections made by Phone Manager Desktop clients.

Description Target/Source Port
CTI Link MiVO App Suite Server TCP 2001
Client Sessions MiVO App Suite Server TCP 8187*, 8186*
Client Personal Wallboard Sessions MiVO App Suite Server TCP 8200, 8204
Integration Services MiVO App Suite Server TCP 8188*
Broadcast location service MiVO App Suite Server UDP 8184*
SIP Audio (Only required if using the integrated softphone client) MiVoice Office 250 UDP 20000-20500
SIP Connection (Only required if using the integrated softphone client) MiVoice Office 250 TCP/UDP 5060
The SIP Audio/Connection ports are the default ports only and may have been updated on the MiVoice Office 250.
During Phone Manager Desktop client installation, rules for communication will automatically be added to the Windows Firewall on the client computer.
Ports marked with a * also apply to the Call Recorder Client.

 

Phone Manager Mobile Client

The table below outlines the network connections made by Phone Manager Mobile clients.

Description Target/Source Port
Client Sessions MiVO App Suite Server TCP 8185
Audio MiVO App Suite Server TCP 8190

 

6900 Handsets

The table below outlines the network connections made by 6900 handsets.

Description Target/Source Port
Configuration Server Link MiVO App Suite Server HTTPS 8202
HTTP 8203
TFTP MiVO App Suite Server TFTP 69
Multicast DNS MiVO App Suite Server UDP 5353
LDAP MiVO App Suite Server TCP 8205
Time Server Network or Internet Time Server UDP 123
Syslog MiVO App Suite Server UDP 514
SIP Audio MiVoice Office 250

UDP 6004-6603(HX)
UDP 6604-7039(PEC)

SIP Connection MiVoice Office 250 TCP/UDP 5060