Miralix Online System requirements 7.3
- 1 PC requirements
- 2 Miralix Softphone
- 3 Softphone: Securing good quality of a Softphone conversation and headlines that should be considered
- 4 Firewall- Miralix Softphone
- 5 Firewall- AudioCodes and Polycom phones
- 6 AudioCodes and Polycom SIP telephones
- 7 Headset Support
- 8 Miralix Go (Mobil App)
- 9 Sending SMS
- 10 ContactCenter agents with OT CSTA (3. part telephone)
- 11 Calendar requirements
- 12 Miralix Dataimport with repeated import
- 13 Miralix DataImport- Azure Active Directory
- 14 Miralix Dataimport once
- 15 Process lookup in Miralix Online
- 16 Miralix OfficeTeam Wallboard for PowerPoint
- 17 Voice over IP
- 18 Update .NET with Windows Update
- 19 Remote access for support
PC requirements
Minimum PC requirements for clients |
Windows 8.x, Windows 10, Windows 11 |
Min. Core i3-6100 processor or equivalent. |
4 GB RAM |
Microsoft .NET 6.0 Desktop Runtime + ASP.NET Core Runtime 64bit og 32bit |
NIC card with IP address + IP connection to the Internet |
Latest Windows updates |
Screen resolution on min. 1280x1024 |
Miralix AutoUpdate Service is installed on client PC together with Miralix Client applications, which automatically updates client software, unless otherwise agreed before installation. |
The above are minimum requirements if the PC is used for resource-intensive tasks, it may be necessary with stronger CPU and more RAM to ensure good sound quality |
Encryption |
All traffic between Miralix clients and Miralix services are encrypted via Advanced Encryption Standard (AES). For more information, see the Miralix ISAE 3000 statement |
Antivirus |
Miralix clients can contact the Miralix Director to get the server address and domain information, so clients can automatically fill these at login. The Miralix Director service is an alternative for DNS TXT records, that Miralix is hosting. Clients communicate with the Miralix Director on port 443, on the following DNS records: miralixdirector.miralix.online and miralixdirector.miralixonline.com
The following Miralix folders as well as subfolders must be omitted in file scans: ”\AppData\local\Miralix” and ”\AppData\roaming\Miralix”. E.g.: ”C:\Users\WINUSER\AppData\Local\Miralix” and ”C:\Users\WINUSER\AppData\Roaming\Miralix”
NB: The directory can vary depending on the drive used for Miralix applications |
Firewall rules for Miralix Miralix Desktop, Miralix OfficeOperator and Miralix Greenbox Editor | |
Miralix Server IP adress | IP: |
Outbound traffic ports (from Miralix Desktop / OfficeOperator / Greenbox Editor to Miralix Server) | Proxy: TCP port 3001-3027 Autodiscover: TCP port 443
|
Miralix Softphone
Network requirements |
|
Wireless Lan | Use of Miralix Desktop or Miralix officeOperator with Softphone on PC’s connected via Wireless Lan is not recomended |
Citrix | Use of Miralix Desktop or Miralix officeOperator with Softphone on Citrix is not supported |
Softphone: Securing good quality of a Softphone conversation and headlines that should be considered
Firewall- Miralix Softphone
Miralix Desktop or OfficeOperator with Softphone. | |
Miralix Server IP adresses | IP range (to ensure redundancy) 213.83.165.128/25 |
Outbound traffic ports (from Miralix Desktop / Softphone to Miralix Server) (Green arrow) | SIP: TCP, 5011-5037
RTP: TCP, 10000-63999 RTP: UDP 10000-63999 |
Incoming traffic ports (from Miralix Server to Miralix Desktop / Softphone) (Blue arrow) | SIP: TCP, 5070
RTP: TCP, 26000-26999 |
Inbound and outbound traffic ports between Miralix Server and Miralix Desktop (Red arrow) | Proxy: TCP, 3001-3027 |
Firewall- AudioCodes and Polycom phones
Miralix Desktop or OfficeOperator with Softphone. | |
Miralix Server IP adresses | IP range (to ensure redundancy) 213.83.165.128/25 |
Outbound traffic ports (from AudioCodes phone to Miralix Server) | SIP: TCP, 5061 (TLS) RTP: UDP, 4000-4099 |
Incoming traffic ports (from Miralix Server to AudioCodes phone ) | SIP: TCP, 5070 RTP: TCP, 26000-26999 |
Inbound and outbound traffic ports between Miralix Server and AudioCodes phone | Proxy: TCP, 3001-3027 |
Miralix Desktop or OfficeOperator with Polycom phone (to be completed by Miralix during commissioning) | |
Miralix Server IP adresses | IP range (to ensure redundancy) 213.83.165.128/25 |
Outbound traffic ports (from Polycom phone to Miralix Server) | SIP: UDP, 5011-5068 RTP: UDP, 10000-63999 |
Incoming traffic ports (from Miralix Server to polycom phone) | SIP: UDP, 5060 RTP: UDP, 49200-49250 |
Inbound and outbound traffic ports between Miralix Server and Miralix Desktop | Proxy: TCP, 3001-3027 |
Miralix Desktop or OfficeOperator with Poly Edge phone (to be completed by Miralix during commissioning) | |
Miralix Server IP adresses | IP range (to ensure redundancy) 213.83.165.128/25 |
Outbound traffic ports (from Poly edge phone to Miralix Server) | SIP: TCP, 5011-5037 RTP: UDP, 10000-63999 |
Incoming traffic ports (from Miralix Server to poly Edge phone) | SIP: TCP, 5060 RTP: UDP, 49200-49250 |
Inbound and outbound traffic ports between Miralix Server and Miralix Desktop | Proxy: TCP, 3001-3027 |
AudioCodes and Polycom SIP telephones
AudioCodes telephones | |
DHCP | The AudioCodes telephones needs an Ip address from DHCP, but may not receive any information via Scope option 43, 66/67, 160 because the telephones must connect to Miralix OnLine via AudioCodes Redirect Server on port 443. |
Switche | If AudioCodes telephones are connected via POE, the switches must support this according to manufactures description |
Polycom phones | |
If Polycom telephones are used, these must be connected to the MPLS network, which is set up by Telenor | |
Switche | If Polycom telephones are to be connected via POE, it is important that switches support this, cf. the manufacturer's description |
Headset Support
Miralix supports headsets from the following manufacturer
Manufacturer | Note |
Jabra | Requires installation of Jabra direct on client PC’s and latest software updates |
Plantronics | Requires installation of Plantronics HUB on client PC’s and latest software updates |
Sennheiser | Requires installation of Epos Connect/HeadSetup Pro on Client PC’s and latest software updates |
NB! Headsets connected to PC and/or headset base via Bluetooth is not recommended. Speech quality cannot be guaranteed. Headset drivers (Jabra Direct, Plantronics Hub, Epos Connect/HeadSetup Pro) must be installed for satisfied operation during calls. Polycom and AudioCodes telephones does not support all headset models, especially if calls are to be answered on the headset (via EHS). Please contact your headset provider for more information.
Miralix Go (Mobil App)
Platform | Version | Screen resolution |
Google Android | Miralix supports the same Android versions supported by Google – Version 10, 11, 12 and 13. Miralix will debug on the same Android versions that Google maintains – Version 10, 11, 12 and 13. | Min. 1136 X 640 pixel |
Apple iPhone iOS | Miralix supports the two latest major IOS versions from Apple – Version 15 and 16. Miralix will debug on the same IOS version that Apple maintains – Version 16. | Min. 1136 X 640 pixel |
NB! Troubleshooting scenarios may require updating the OS on the device.
Firewall |
Firewall must be open for outgoing HTTPS traffic |
Sending SMS
Sending SMS from Miralix OfficeOperator and Miralix Desktop can be done by:
Miralix Texty Service
Telenor Statusplan v2 (Telenor Statusplan)
If Miralix Texty Service is used, SMS will be sent by Miralix’ central server.
NB! Max. 2500 or 10000 per month, depending on which license is associated.
Sending of SMS can only be guaranteed to Danish numbers. Sending of SMS to foreign
mobile numbers are dependent on Telenor Denmark's interconnect agreements with foreign operators.
ContactCenter agents with OT CSTA (3. part telephone)
Contact-Center with OT CSTA | Unsupported extension facilities |
ContactCenter with OT CSTA means that OfficeTeam controls call control to Miralix OfficeOperator and Miralix Desktop instead of the PBX. If the ContactCenter is used with a PBX, agent’s phones may not use facilities such as call forwarding, as OfficeTeam is unable to “see” that the phone is forwarded, and calls will not be diverted or serviced by Miralix OfficeOperator or Miralix Desktop. See the list “Unsupported extension facilities” next to this section. | Call forwarding of agents extension to another extension or Voicemail. Call forwarding on busy and no answer are also not supported. |
Break in where agent is involved | |
Activation where agent is involved | |
NB! Call diversion to an agent must be made to a personal queue in OfficeTeam - not directly to the agent extension/telephone. | |
NB! If mobile phones are used as agent phones, then 4G and call forwarding may be disabled on the mobile phone. Other wise there is a risk that calls to the Contact Center will be lost because the calls end up in the mobile voicemail. | |
OT CSTA line types for OfficeTeam Contact-Center | |
SIP Trunk from Miralix SIP Gateway | |
SIP Trunk from Telenor | |
SIP Trunk from TDC | |
SIP trunk from GlobalConnect (Supertel) | |
SIP Trunk from Audiocodes Session Border Controller (for other SIP trunk providers) | |
NB! In order for calls to be processed correctly and number display to work, it is required that a CLIP SA agreement has been signed with the telecommunications provider, on all external lines. but can be omitted in some cases. If more SIP Trunks are to be connected to the Contact Center, this must be reported to Miralix before installation, as this will require additional hardware configuration. | |
Calendar requirements
Platform | Miralix synchronizing | Server | Permissions |
Microsoft Exchange | Via Exchange Web Services Åben port 443 | Exchange Server 2010 Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online | Reviewer rights are required for all the mailboxes where Miralix sync is desired, this may. configured with PS cmdlet Add-MailboxFolderPermission -identity "$($Mailbox.Name):\Kalender" -AccessRights Reviewer -User miralixsync |
Exchange Impersonation | With Exchange impersonation (Exchange Server 2010, 2013, 2016, 2019, Online) it is possible to run Miralix CalendarSyncService from version 2.5.1.0 without setting calendar rights in the Exchange server. New-ManagementRoleAssignment -Name "ApplicationImpersonation Role for Miralix Sync" -Role ApplicationImpersonation -User MiralixSync@maildom.tld | ||
Google Apps for Work | Via Calendar API Open port 443 | Add API-Client access in Google Apps for Work to the Miralix Calendar application | |
Microsoft Graph API |
|
| Domain The user "Miralix" must be created on Microsoft Office 365, with access to Exchange |
Miralix Dataimport with repeated import
Server requirements for Data Import server |
Windows Server 2016 through Windows Server 2019. Miralix Dataimport does not need “own” server, but can be installed on an existing server |
Microsoft .NET 6.0 Runtime + ASP.NET Core Runtime 64bit |
20GB free hard disk space |
4GB RAM available for the Miralix Data Import Service |
Network card with IP address + IP connection to the Internet |
Latest Windows updates |
TCP Port 3001-3027 must be open in the outbound firewall |
Remote system logins
NB! Miralix Dataimports witch connects remotely to Miralix Proxy service (Miralix server) needs to be approved for “Remote system login”
LDAP/LDAPS |
Miralix Dataimport uses LDAP to retrieve data from Active Directory via the standard ports: LDAP = port 389 LDAPS = port 636 |
Active Directory
Domain user must be a local administrator and a member of "domain users"
Contact Miralix if you want to import from other / more domains
Imports of users are performed through Organizational Units, Distribution Groups, or Security Groups
NB! Please note that data must be present and correctly entered in Active Directory, eg that telephone number is entered in the "Telephone number" field, if this field is used as "required" in Miralix Dataimport, otherwise data can not be used by Miralix programs. Be aware of the security risk of any import via the Internet, as LDAP does not support encryption. LDAPS can be used instead, which offers encryption. If Miralix Dataimport is installed on a local server, LDAP can be used well, as traffic between Miralix Dataimport and other Miralix services will be encrypted.
Encryption
All traffic between Miralix Dataimport and other Miralix services can be encrypted via the Advanced Encryption Standard (AES). For further information, please refer to the Miralix ISAE 3000 statement.
Multi Domains
Ability to import data from several different domains. Requires domain user creation on each domain for Miralix Dataimport.
File import
TXT and CSV file with separator and one of the following encodings: UTF-8, Ansi, Unicode
For file import, the file must be directly accessible on a drive from the server where Miralix Dataimport is installed
Miralix DataImport- Azure Active Directory
Server requirements for Data Import server |
Windows Server 2016 through Windows Server 2019. Miralix Dataimport does not need “own” server, but can be installed on an existing server |
Microsoft .NET 6.0 Runtime + ASP.NET Core Runtime 64bit |
20GB free hard disk space |
4GB RAM available for the Miralix Data Import Service |
Network card with IP address + IP connection to the Internet |
Latest Windows updates |
TCP Port 443 and 3001-3027 must be open in the outbound firewall |
Azure Active Directory
Account with permissions to add an App Registration, Grant permissions for App Registrations and add an Enterprise application to the tenant.
If import from another or more than one Azure tenant is required, contact Miralix.
Miralix DataImport uses Microsofts Graph API, to import user information, from members of Azure Groups.
NB! Be aware that data are present and correct applied into Azure Active Directory e.g., that the users telephone number is present in the Telephone number field, otherwise the data will not be suitable for Miralix Services.
Encryption
All traffic between Miralix DataImport and other Miralix services are encrypted via Advanced Encryption Standard (AES). For more information, see the Miralix ISAE 3000 statement.
Multi Domains
It is possible to import data from several domains/tenants. This requires an App Registrations on every tenant for Miralix DataImport.
It is possible for Miralix client applications to use the login type, Microsoft 365, if the Enterprise application is added and configured.
Azure Active Directory / Microsoft 365 login
Miralix Clients from version 6.1.x can use the login type Microsoft 365, if the user has been imported by Miralix DataImport from an Azure tenant.
Miralix Dataimport once
File import
TXT and CSV file with separator and one of the following encodings: UTF-8, Ansi, Unicode
The file must be directly accessible on a drive from the server where Miralix Dataimport is installed
Process lookup in Miralix Online
Process Lookup in Miralix Contact Center can be done in 2 ways:
Process activation can be executed from the Miralix Desktop client:
Like a URL lookup that launches an external application in a browser of the customer.
As a "Powershell command" or other 3rd party program that delivers information to another system at the customer.
2. Process activation can be executed from Miralix Contact Center via, for example, a "Powershell command" or other 3rd party program that looks up in another system at the customer or delivers information to another system:
Aktivering følger opkaldsflow i Miralix Kontaktcenter.
NB! It is a prerequisite that the customer's external system or database is accessible to Miralix Online without the installation of any kind of 3rd party security software or programs, eg VPN client on the server. Setup and firewall opening will be limited to Miralix's IP addresses.
Miralix OfficeTeam Wallboard for PowerPoint
Minimum requirements for Wallboard clients |
PC or terminal server session, 64bit Operative system |
Microsoft Office 2013, 2016 and 2019 32/64 bit |
Firewall and Antivirus |
TCP Port 3001-3027 outbound traffic must be open in Firewall
Following Miralix folder and sub folders must be excluded from file scanning ”\AppData\local\Miralix” og ”\AppData\roaming\Miralix”. Eks.: ”C:\Users\Miralix\AppData\Local\Miralix” og ”C:\Users\Miralix\AppData\Roaming\Miralix”
NB! The directory can vary depending on which drive is used for Miralix programs |
Voice over IP
QoS network requirements | |
Delay | To insure a acceptable voice quality, the one-way delay should not exceed 50 mS, and should be less than 25ms |
Packet loss | Packet loss should not exceed 0,1% |
RFC 1889 Jitter | To ensure a high voice quality, RFC1889 jitter should not exceed 6mS |
Delay variation jitter | Delay variation jitter should not exceed 50mS |
Update .NET with Windows Update
After installing .NET, it is possible to get continuous updates via Windows Update.
It is recommended to always use the latest release of .NET 6.0.
For more info see:
https://devblogs.microsoft.com/dotnet/server-operating-systems-auto-updates/#opting-in
https://devblogs.microsoft.com/dotnet/net-core-updates-coming-to-microsoft-update/#automatic-updates
Remote access for support
In order for Miralix to provide support on the installed applications, it is a requirement that TeamViewer is installed with access via Teamviewer's Server ID on servers that have Miralix services installed. Miralix installs TeamViewer clients. Further information can be found on Teamviewer's website: https://www.teamviewer.com/en/products/remotecontrol.aspx
Copyright © 2022 Miralix A/S