MiVoice MX-ONE

Optional Installations
Release 7.3
September 16, 2020
 Notice
The information contained in this document is believed to be accurate in all respects but is not warranted by Mitel Networks™
Corporation (MITEL®). The information is subject to change without notice and should not be construed in any way as a commit-
ment by Mitel or any of its affiliates or subsidiaries. Mitel and its affiliates and subsidiaries assume no responsibility for any errors
or omissions in this document. Revisions of this document or new editions of it may be issued to incorporate such changes.No
part of this document can be reproduced or transmitted in any form or by any means - electronic or mechanical - for any purpose
without written permission from Mitel Networks Corporation.

Trademarks
The trademarks, service marks, logos and graphics (collectively “Trademarks”) appearing on Mitel's Internet sites or in its publi-
cations are registered and unregistered trademarks of Mitel Networks Corporation (MNC) or its subsidiaries (collectively "Mitel")
or others. Use of the Trademarks is prohibited without the express consent from Mitel. Please contact our legal department at
[email protected] for additional information. For a list of the worldwide Mitel Networks Corporation registered trademarks, please
refer to the website: http://www.mitel.com/trademarks.

®,™ Trademark of Mitel Networks Corporation

© Copyright 2020, Mitel Networks Corporation
All rights reserved
 Contents

Chapter: 1 MiCollab Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

MiCollab Example Introduction . . . . . . . . . . . . . . . . . . . . . . . 1
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
OVA Deployment Installation . . . . . . . . . . . . . . . . . . . . . . . . 1
Configuration of MiCollab . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Menu: Service Link . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Menu: Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 3
Menu: Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Menu: Administration . . . . . . . . . . . . . . . . . . . . . . . . 4
Menu Application . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Option: Users and Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Option: MiCollab Client Service . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Option: Audio, Web and Video Conferencing . . . . . . . . . . . . . . . . 5
Option: NuPoint Web Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Test Access to AWV and NuPoint . . . . . . . . . . . . . . . . . . . . . . 8

Chapter: 2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Brief Description of Mitel Performance Analytics . . . . . . . . . . . . . 9
Supported Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter: 3 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter: 4 Mitel Performance Analytics SNMP integration with MiVoice MX-ONE 12

How to integrate with MiVoice MX-ONE . . . . . . . . . . . . . . . . . .12
Useful information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Chapter: 5 Co-existence with Similar Tools . . . . . . . . . . . . . . . . . . . . . 13

Chapter: 6 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter: 7 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Chapter: 8 Integration Description . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Direct SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Direct SIP Signaling Overview . . . . . . . . . . . . . . . . . . . . . . . .16
Direct SIP Supported Features . . . . . . . . . . . . . . . . . . . . . . . .16
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
MiVOICE MX-ONE Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 17
Skype for Business Server 2019 . . . . . . . . . . . . . . . . . . . . . . .17
Main Components . . . . . . . . . . . . . . . . . . . . . . . . . .18
Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Chapter: 9 Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . 18

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
MiVoice MX-ONE Installation . . . . . . . . . . . . . . . . . . . .18
Microsoft Infrastructure . . . . . . . . . . . . . . . . . . . . . . .18
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Direct SIP Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
MiVoice MX-ONE Direct SIP Setup - TCP . . . . . . . . . . . . . . . . . . . 20
Skype for Business Server 2019 Configuration -- TCP . . . . . . . . 21
Define PSTN Gateway in the Skype for Business Server 2019 Topology
Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Define a Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Define Voice Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Define Trunk Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Direct SIP with Security and Media Bypass Setup . . . . . . . . .28
MiVoice MX-ONE Direct SIP with Security and Media Bypass Setup 28
Import the Certificate to MX-ONE Service Node . . . . . . . . . . . . 29
Lync Configuration with Security and Media Bypass Setup . . . . 32
Define Dial Plan and Voice Policy . . . . . . . . . . . . . . . . . . . . . . . . 34
Define Trunk Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Load Balancing and Failover Setup . . . . . . . . . . . . . . . . .35
Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
DNS Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
MX-ONE Direct SIP with Load Balancing and Failover Setup - TCP 38
Lync Configuration with Load Balancing and Failover Setup – TCP 39
MX-ONE Direct SIP with Load Balancing and Failover Setup - TLS 39
Import the Certificate to MX-ONE Service Node . . . . . . . . . . . . 40
Lync Configuration with Load Balancing and Failover Setup – TLS 40

Chapter: 10 Integration Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Chapter: 11 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter: 12 Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter: 13 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Chapter: 14 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Chapter: 15 Setting up MX-ONE for GX Controller . . . . . . . . . . . . . . . . . . 43

Number Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Extension Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Common Service Profile 9: . . . . . . . . . . . . . . . . . . . . .44
Common Service Profile 11: . . . . . . . . . . . . . . . . . . . . .45
Least Cost Routing Data . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Route Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
ROCAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Route Category Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
RODAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Route Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
SIP ROUTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Chapter: 16 Setting up the GX Gateway . . . . . . . . . . . . . . . . . . . . . . . . 48

Logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Local Firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Session Board Controller (SBC) . . . . . . . . . . . . . . . . . . . . . . .52
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Local_users_ca . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
ISDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Primary Rate Interface . . . . . . . . . . . . . . . . . . . . . . . .60
Interop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
POTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
FXS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . .65
SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Registrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Interop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
 Misc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Codecs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Call Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Route Config . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Backup/Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

Chapter: 17 Setting up MX-ONE for an EX Controller . . . . . . . . . . . . . . . . . 77

Chapter: 18 Setting up EX Controller . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Local Firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
SBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Local_users_ca . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
ISDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
Primary Rate Interface . . . . . . . . . . . . . . . . . . . . . . . .89
Interop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
POTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
Config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
FXS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . .93
SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Registrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . .96
Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
Misc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
Codecs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
Call Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
Route Config . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Backup/Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Chapter: 19 Configure TLS on an EX/GX Controller . . . . . . . . . . . . . . . . . .102

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Creating TLS Certificate with SAN . . . . . . . . . . . . . . . . . . . . . 103
 Connecting CA to the MX-ONE Server . . . . . . . . . . . . . . 103
Verifying the CA File . . . . . . . . . . . . . . . . . . . . . . . . 104
Generating the Unit Certificate with SAN . . . . . . . . . . . . 105
Copying the Files on PC . . . . . . . . . . . . . . . . . . . . . . 106
Configuring the EX/GX for TLS . . . . . . . . . . . . . . . . . . . . . . . 106
Login to the EX/GX Controller . . . . . . . . . . . . . . . . . . . 107
Installing Unit Certificates . . . . . . . . . . . . . . . . . . . . . 107
Configuring the Secure SIP ports . . . . . . . . . . . . . . . . . 108
Setting the TLS version, Cipher Suite, and Certificate Validation Level 108
Enabling TLS on the SBC Service . . . . . . . . . . . . . . . . . . 109
Enabling TLS between SIP Gateways and SBC . . . . . . . . . . 110
Enabling SRTP on EX/GX Controller . . . . . . . . . . . . . . . . 111
Enabling Certificate Validation . . . . . . . . . . . . . . . . . . 111

Chapter: 20 Known Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

Chapter: 21 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113

Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Chapter: 22 Solution Description . . . . . . . . . . . . . . . . . . . . . . . . . . . .114

MiVoice MX-ONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Microsoft Lync Server 2013 . . . . . . . . . . . . . . . . . . . . . . . . 114
Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Chapter: 23 Requirements and Setup . . . . . . . . . . . . . . . . . . . . . . . . .115

MIVOICE MX-ONE Requirements . . . . . . . . . . . . . . . . . . . . . 116
Microsoft Lync Server 2013 Requirements . . . . . . . . . . . . . . . . 116
Integration Setup - TCP . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
MiVoice MX-ONE Setup - TCP . . . . . . . . . . . . . . . . . . . 117
Microsoft Lync Server 2013 Setup – TCP . . . . . . . . . . . . . 117
Enable Lync Users for Remote Call Control . . . . . . . . . . . . . . . . 119

Chapter: 24 How to Verify the Setup . . . . . . . . . . . . . . . . . . . . . . . . . .120

Lync 2013 Client Features . . . . . . . . . . . . . . . . . . . . . . . . . 120
Make an Outgoing Call Using the Lync 2013 Client . . . . . . . . . . . 122
Answer an Incoming Call . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Transfer a Call Between Current Conversations (Monitored Transfer) . 122
Single Step Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Forward an Incoming Call . . . . . . . . . . . . . . . . . . . . . . . . . 126
Place Calls on Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Alternate Between Multiple Concurrent Calls . . . . . . . . . . . . . . 128
Answer a Second Call While Already in a Call (call waiting) . . . . . . . 128
Dial Dual-Tone Multi-Frequency (DTMF) Digits . . . . . . . . . . . . . 129
Presence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Chapter: 25 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132

Chapter: 26 Good to Know . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132

Chapter: 27 Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133

Chapter: 28 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134

Chapter: 29 Application Requirements . . . . . . . . . . . . . . . . . . . . . . . .134

Chapter: 30 Installation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135

Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Installing Release 11.0 on a Standalone Physical Server . . . . . . . . . 135
Installing Release 11.0 in a VMware Environment . . . . . . . . . . . . 135
Firewall Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
MSL Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
MBG Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Phone Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Issues Resolved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Upgrade Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Appendix - Config Script . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Appendix - mitel.cfg Settings . . . . . . . . . . . . . . . . . . . . . . . 141
 MICOLLAB EXAMPLE INTRODUCTION
CHAPTER 1 MICOLLAB INTEGRATION

MiCollab Integration
This topic discusses the MiCollab integration with MX-ONE. For information on the MiCollab integration
with MX-ONE see MiCollab Platform Integration Guide.

MiCollab Example Introduction

This document contains an example of basic installation and configuration of the MiCollab application
server for integration with MiVoice MX-ONE.

Prerequisites
• Configure MX-ONE for MiCollab integration (see MX-ONE integration chapter in MiCollab Customer
Documentation).
– Configure PBX group and members in MX-ONE to be used for AWV.
– Configure SIP trunk in MX-ONE using profile NuPoint (remember to use remote port=5058).
– Configure csta link in MX-ONE.

• Used numbers and IP address in the examples:

– Attendant number in MX-ONE: 09
– MX-ONE IP address: 192.168.222.100
– Internal number serie:4xxxx
– Internal number length: 5 digits
– NuPoint: Access number: 6001
– Lines to NuPoint VoiceMail: 15
– Lines for NuPoint MWI: 1
– Lines for outgoing calls from NuPoint: 4
– AWV Access number: 8003
– Number of ports AWV: 3
– SIP Port Extension numbers for AWV: 8004,8005,8006

OVA Deployment Installation

Do as follows:
Deploy the MiCollab .ova file:
1. Start the virtual machine.
2. Open the console interface.
3. Choose keyboard.
4. Restore from backup - no.

1
 CONFIGURATION OF MICOLLAB
CHAPTER 1 MICOLLAB INTEGRATION

5. Set Administrator's password (this is the same for both root and admin user).
6. Select Timezone - (e.g. CET).
7. Enter primary domain - (e.g. mydomian.com).
8. Enter system name - (e.g. micollab).

9. Select only eth0 - just now no WAN should be enabled.

10. Type the IP address of the server.

11. Type the netmask.

12. Do not configure IPv6.

13. Do not configure eth1.

14. Do not configure another local network adapter.
15. Type the default gateway for the server.

16. Type the IP address of the corporate DNS .

17. Select the corporate DNS for DNS resolution.
18. Wait for the configuration to be activated.

19. Enter ARID and IP address (Important use correct address) of the FMC and then select PBX type.
20. Login through the console interface as admin.
21. Select 9. Manage Trusted Networks.
22. Select 2. Add IPv4 trusted network.(e.g the internal corporate ip network segments).
23. Enter the subnetmask.
24. Enter the router to use for the trusted network - normally the same router as for the server.
25. Select Next, then Back to the menu.

26. Login to https://<fqdn>/server-manager with admin and password configured during installation.

Configuration of MiCollab
In the main window and from the left menu you administrate the configuration of the MiCollab, see
below.Complete all configurations before start using PM to deploy users.

2
 CONFIGURATION OF MICOLLAB
CHAPTER 1 MICOLLAB INTEGRATION

Figure 1.1: Main window

Menu: Service Link

• Select Service Link and then Status.
• If you have not entered your ARID (Service account id) during the initial installation then enter it now
together with the ip.address of the FMC.
NOTE: If you have not selected the PBX during the initial installation, go to ServiceLink/Install Applica-
tions/Install Applications - select the PBX type and Next.

Menu: Configuration
• Select and start the MiCollab Client Integration Wizard.
• Select MiCollab Language Settings and set the System Language and Other NuPoint UM Prompt.
• Select E-mail settings. If required, configure settings for outbound SMTP server and userid.

3
 CONFIGURATION OF MICOLLAB
CHAPTER 1 MICOLLAB INTEGRATION

Menu: Security
• Select Remote Access. If required, change Secure Shell Settings to allow SSH access for later diag-
nostics.

Menu: Administration
• Select System Users. For the account micollab api. select Reset password and enter a new password.
You will require this user account and password when configuring the MiCollab subsystem in PM.

Menu Application
Menu application options are discussed in this section.

Option: Users and Service

Select User and Services and then configure following options:
• Option: Network Element
a. Select Add.
b. Type =MiVoice MX-ONE
c. System Name= <my Mxone>
d. IP Address = 192.168.222.100
e. Call Forward Destination Number = 6001

• Option: User templates

– Select Add.
Create customer roles templates from available default templates. It’s done by selecting wanted
default template, creating a copy of it and save with a new name. Edit the created customer tem-
plates for Entry, Premium, Standard and Standard - Mobile.
– Entry
• Select TUI Passcode. TUI Passcode = Same as Primary Phone Extension (can only be used if
extension length is 4 digits or more). TUI Passcode = Use this value = 4-10 digits (if extension
length is less than 4 digits).
• Attendant Extension: 09
• Message Waiting #1 = DTMF to PBX

• Premium
– Password = Use this value = "Strong Password"
– Select TUI Passcode
– TUI Passcode = Same as Primary Phone Extension (can only be used if extension length is 4 digits
or more)
– TUI Passcode = Use this value = 4-10 digits (if extension is less than 4 digits)
– Attendant Extension: 09
– Message Waiting #1 = DTMF to PBX

• Standard

4
 CONFIGURATION OF MICOLLAB
CHAPTER 1 MICOLLAB INTEGRATION

– Password = Use this value = Enter a strong Password

– Select TUI Passcode
– TUI Passcode = Same as Primary Phone Extension (can only be used if extension length is 4 digits
or more)
– TUI Passcode = Use this value = 4-10 digits (if extension is less than 4 digits)
– Attendant Extension: 09
– Message Waiting #1 = DTMF to PBX

• Standard - Mobile
– Password = Use this value = Enter a strong Password
– Select TUI Passcode
– TUI Passcode = Same as Primary Phone Extension (can only be used if extension length is 4 digits
or more)
– TUI Passcode = Use this value = 4-10 digits (if extension is less than 4 digits)
– Attendant Extension: 09
– Message Waiting #1 = DTMF to PBX

Option: MiCollab Client Service

Select MiCollab Client Services and then Configure MiCollab Client Services. Configure following options.

PBX Nodes.
• Select the PBX Node and configure.
• Set length: 5 ( internal number length in the MiVoice MX-ONE).

Enterprise
• Select Enterprise and then Default Account Settings.
• Select appropriate Country from the drop-down list

Option: Audio, Web and Video Conferencing

Select Audi, WEB and VIDEO conferencing and configure following options.

Configure SIP Server

• Select Add and configure, MX-ONE SIP Server Configuration.
Extension first: 8004
Extension last: 8006
• SIP password: 8003 (if authorization code is set to 8003 in MX-ONE for the extensions 8004-8006)
• SIP Domain: mydomain.com (domain of MX-ONE)
• IP Address: 192.168.222.100
• SIP Port: 5060

Web Conferencing Settings

• Select and configure Web Conference Name.
• Web conferencing Name: micollab.mydomain.com

5
 CONFIGURATION OF MICOLLAB
CHAPTER 1 MICOLLAB INTEGRATION

System Options
Select and configure System Options:
• Platform - MiVoice MX-ONE
• Dial -in phone number 1: 8003 (Internal number to AVW)
• Dial - in Phone Number 1 Label: internal
• Dial-in Phone number 2: 8468003 (corporate number to AWV)
• Dial- in Phone number 2 Label: corporate
• Dial -in number 3 +4684428003 (Public number to AWV)
• Dial- In Phone number 3 Label: Public
• Webserver admin E-mail [email protected]
• Generate Alert E-mail system [email protected]
• Prompt for Access Code first: Enable checkbox
• Allow HD Video Resolutions: Enable checkbox
• Prompt to extend conference 5 minutes prior to its end time: Enable checkbox

Option: NuPoint Web Console

Select and NuPoint Web Console and configure following options

Offline Configuration
Select Offline configuration/Edit Offline configuration and Duplicate Active Configuration - yes
Then select and configure following items:
1. Network Elements/Add
a. Type = SIP GATEWAY
b. Name = Mxone
c. IP Address = 192.168.222.100
d. Number of Ports = 20
2. Dialers (Pagers) (for Request playback call feature in UCA client) and select:
a. Add a "dialer"
b. Number: Select Next Available
c. Enter a name - Dialer
d. Acces code: T
e. Hold Time : 20
f. Add
3. Line Groups/Add

a. Add a line group for Voicemail connection:

• Line Group Number = 1
• Name = VoiceMail
• Application = NuPoint Voice
• User Interface = NuPoint Voice
• Lines/Add
• Line Triplet - next Available

6
 CONFIGURATION OF MICOLLAB
CHAPTER 1 MICOLLAB INTEGRATION

• Number of lines = 15
• PBX = MX-ONE
• Mapping = 1 (0 must not be used, see Online help - “add at Line Group)
• "Save"
• Pilot Number = 6001
• Dialling Plan
• Length of extensions starting with...
• 4 = 5 digits
• Voicemail
• System Attendent's extension = 09
• Save
b. Add a line group for Message Waiting indication:
• Line Group Number = 2
• Name = MWI
• Application = DTMF to PBX Dialler
• User Interface = NuPoint Voice
• Lines/Add
• Line Triplet - next Available
• Number of lines = 1
• PBX = MX-ONE
• Mapping = 16
• Add
• Pilot number = 6001
• DTMF to PBX Dialler/DTMF to PBX Dialer
• Pre-DN On Dial String = 1
• Pre-DN Off Dial String = 0
• Save

c. Add a line group for Outgoing calls from NuPoint:

• Line Group Number = 3
• Name = Outgoing Dialler
• Application = Outbound (Pager) Dialer
• User Interface = NuPoint Voice
• Lines/Add
• Line Triplet - next Available
• Number of lines = 4
• PBX = MX-ONE
• Mapping = 17
• Add
• Pilot number = 6001
• Save
• Dialling Plan
• Length of extensions starting with...

7
 TEST ACCESS TO AWV AND NUPOINT
CHAPTER 1 MICOLLAB INTEGRATION

• 4 = 5 digits
• Select the Dialer(Pagers) created in step b) by selecting the checkbox
• Save

4. Select Commit Changes and Exit and then Activate.

Active Configuration/Line Groups

• Select Active Configuration/Line groups and then Edit line group for Voicemail (Linegroup 1)
• Check that Prompt Language 1 is set to default (Do not change this).

Class of service Feature COS/14. MAS

• Select Class of Service/Feature COS and then Edit FCOS number 14 (MAS)
• Enable checkbox for:
– 051 Do not switch language for outside callers
– 218 Passcode NOT needed on direct calls
– 263 Store Caller Line Id as a phone or mailbox number
– 264 Play outside caller user interface (with FCOS bit 280)
– 280 Enable CLI Outside caller interface (with FCOS bit 264)

Test Access to AWV and NuPoint

• Call Voice Mail (access number 6001). Get Welcome message.
• Call to AWV (access number 8003). Get prompt to enter conference code.

8
 BRIEF DESCRIPTION OF MITEL PERFORMANCE ANALYTICS
CHAPTER 2 INTRODUCTION

Mitel Performance Analytics

SNMP integration with MiVoice
MX-ONE
Introduction

Brief Description of Mitel Performance Analytics

The Mitel Performance Analytics (MPA 2.1, former MarWatch) monitoring system provides fault and
performance management for multiple enterprise VoIP systems and associated network infrastructure,
both LAN and WAN. MPA supports monitoring and remote access, both for private networks, such as
enterprise LANs and MPLS VPNs, and for public network or Internet-reachable devices, such as access
routers.
MPA can monitor any SNMP device regarding alarms and general status.
MPA is a product from Martello Technologies.

Supported Scenarios
For an MX-ONE system with a single Service Node, the MPA shall of course be connected to that Service
Node.
The MPA can be connected in a couple of different ways to a multi-server MX-ONE system.
The primary multi-server scenario is that each Service Node server is connected to a MPA probe.

9
 SUPPORTED SCENARIOS
CHAPTER 2 INTRODUCTION

Figure 2.1: Primary scenario, direct connection to all MX-ONE servers in a 4-server MiVoice
MX-ONE system

Another possibility is that one Service Node can act as a proxy for several other Service Nodes (and other
entities), in which case only the proxy Service Node will be connected to the MPA probe.
The second scenario is not recommended, since it has certain resiliency problems, due to the fact that
the monitoring function will be fully dependent on the proxy, so if the proxy goes down, the status of the
other nodes will not be reported.
You can also have a mix of the primary and secondary scenarios.

10
 SUPPORTED SCENARIOS
CHAPTER 2 PREREQUISITES

Figure 2.2: Secondary scenario, connection by proxy, connection only to one MX-ONE
Service Node

Prerequisites
MPA consists of a number of web services running on either a cloud-hosted computing platform or
on-premises computing platform. There are several components to MPA. The remote ‘Probe’ installed in
non-Internet accessible networks maintains databases of status and events, and provides a web portal
with access security. Additionally, MPA has a Remote Access Service that provides a secure
“cross-connect” for remote access to the customer network.
MPA 2.1 or later version shall be used.
The MiVoice MX-ONE system(s) shall be up and running on Linux (SLES), either on a cloud-hosted
computing platform or on-premises computing platform. Appropriate MIB shall be active.

11
 HOW TO INTEGRATE WITH MIVOICE MX-ONE
CHAPTER 2 MITEL PERFORMANCE ANALYTICS SNMP INTEGRATION WITH MIVOICE MX-ONE

Mitel Performance Analytics SNMP integra-

tion with MiVoice MX-ONE

How to integrate with MiVoice MX-ONE

Do as follows:
1. As root open the file /etc/snmp/snmpd.conf.
2. Set the correct syslocation and syscontact to reflect where the server is located and who manages it.
3. Update the rocommunity setting to allow the Martello Marprobe to perform snmp-queries towards the
MX-ONE.
4. Update the trapsink setting to point towards the Martello Marprobe. This should be done in all
MX-ONE servers that the Martello MPA system should monitor.
5. After saving the changes you need to restart the snmpd daemon for the changes to take effect.

(The Martello MPA probe has been assigned IP-address 192.168.157.128. To limit the access the
“rocommunity” setting can be set to only allow access from a certain subnet or even a single IP-address).

Useful information
• Please see /usr/share/doc/packages/net-snmp/EXAMPLE.conffor a more complete example and
snmpd.conf(5).
• Writing is disabled by default for security reasons. If you would like to enable it, uncomment the rwcom-
munity line and change the community name to something nominally secure (keeping in mind that this
is transmitted in clear text).
NOTE: do not use '< > in strings for syslocation or syscontact.
NOTE: If you define the following here you will not be able to change them with:

snmpset syslocation (Optional) Server Room on Floor 7.

syscontact Sysadmin ([email protected]).
They include all MIBs and can use considerable resources. See snmpd.conf(5) for information on setting
up groups and limiting MIBs.
rocommunity public 127.0.0.1
rocommunity public 192.168.157.0/24
rwcommunity mysecret 127.0.0.1

MX-ONE alarm traps use the agentx protocol:

master agentx
AgentXSocket tcp:localhost:705

12
 USEFUL INFORMATION
CHAPTER 2 CO-EXISTENCE WITH SIMILAR TOOLS

MX-ONE alarm traps can trigger snmptrapd to sent mail and textmessages rapcommunity:
Default trap sink community to use trapcommunity private
trap2sink: A SNMPv2c trap receiver
trap2sink 192.168.157.128

Co-existence with Similar Tools

There are other tools for fault and performance management, for example the Manager System Perfor-
mance application, that can also be connected to the MiVoice MX-ONE system, as long as different IP
addresses are used compared to MPAs.
However, there should be no need to have several such tools, so that is not recommended.

References
For further reading regarding MPA and its features and configuration options, please see MPA System
Guide, Release 2.1 or later.

13
 GENERAL
CHAPTER 3 INTRODUCTION

Integration of MiVoice MX-ONE

and Skype for Business Server
2019, Quick Setup Guide
Introduction
The MiVoice MX-ONE communication system is based on an open software and hardware environment
that uses standard servers with a Linux SUSE operating system. This open standards approach enables
Mitel to offer our customers the choice of integrating MiVoice MX-ONE latest Microsoft UC products. We
have worked with Microsoft to ensure that this possibility is workable.
MiVoice MX-ONE 5.0 is the first communications system (IP-PBX) to be fully Unified Communications
Open Interoperability Program (UCOIP) qualified with Skype for Business Server 2019. The integration
of MX-ONE with Microsoft products is a complete Direct SIP Integration, including security and media
bypass, enabling customers to have both MX-ONE 5.0/6.x and Microsoft Lync 2019 co-exist in the same
infrastructure and thereby derive the benefits from the best of both worlds. MX-ONE integrates with Micro-
soft UC solutions directly via a SIP connection to reduce the overall cost and complexity of the combined
solution.
Refer to Microsoft's TechNet site for "Infrastructure Qualified for Microsoft Lync" for more information
about the Microsoft Unified Communications Open Interoperability Program. http://technet.micro-
soft.com/en-us/lync/gg131938

General
Integration of MiVoice MX-ONE with Skype for Business Server 2019 is supported as a complementary
solution providing end-user services, such as instant messaging and conferencing.
Microsoft Partner Program has certified the integration between MX-ONE communications system
running the MX-ONE Service Node software 5.0 SP4 and Skype for Business Server 2019 through a
Direct SIP connection. Also, later versions of MX-ONE can be integrated with Skype for Business Server
2019.

Scope
This guide describes the basic integration between MiVoice MX-ONE and Skype for Business Server
2019. The following sections describe the solution integration that has been certified through the Microsoft
Partner Program and covers only the Direct SIP Integration. For more information about how this integra-

14
 DIRECT SIP
CHAPTER 3 INTEGRATION DESCRIPTION

tion is set up and functions, refer to the relevant CPI documentation for MX-ONE, or go to the Microsoft
UC product websites.
We recommend that you check the latest products documentation.

Integration Description
The integration of MiVoice MX-ONE and Skype for Business Server 2019 described in this guide is
achieved via a Direct SIP that is specified by Microsoft. It means that a SIP trunk is used to connect
MX-ONE and Skype for Business Server 2019 (Mediation Server). The SIP trunk connection between the
systems can be deployed with or without encryption. MX-ONE supports TLS for signaling and SRTP for
media encryption when connected with Mediation Server.

This guide covers only the components that are required in the integration between MX-ONE 5.0 SP4 or
a later version, and Skype for Business Server 2019 via Direct SIP to offer the functionality required by
the Microsoft UC Open Interoperability Program for enterprise telephony services and infrastructure.
At least the following Skype for Business Server 2019 components are required to support this integration:
• Server Infrastructure
– Microsoft infrastructure (Domain Controller, Active Directory, DNS and so on)
– Skype for Business Server 2019 Standard or Enterprise Edition
– Microsoft Mediation Server

• Client
– Microsoft Lync 2019

Direct SIP
In Direct SIP Integration, referred to as Enterprise Voice by Microsoft Lync 2019, users will have dedi-
cated phone numbers that differ from those used in the MX-ONE.

15
 DIRECT SIP SIGNALING OVERVIEW
CHAPTER 3 INTEGRATION DESCRIPTION

This enables the Microsoft Lync 2019 client to make and receive external calls through a PC. The calls
are routed from the Skype for Business Server 2019 by the SIP trunk to the MX-ONE and further to the
PSTN and vice-versa. MX-ONE and Skype for Business Server 2019 will behave as networked PBXs, as
typically is the case with all external trunks in the MX-ONE.

Direct SIP Signaling Overview

MiVoice MX-ONE supports SIP/TCP or SIP/TLS as the SIP transport mechanism when connected with
Mediation Server.
The MX-ONE ports used for such connections are:
• SIP/TCP: 5060
• SIP/TLS: 5061

In addition to this, MX-ONE also supports media encryption (SRTP) when connected with Microsoft Lync
2019 Server when TLS is used. The media encryption is done between MX-ONE media gateway unit
(MGU) and Microsoft Mediation Server or between MX-ONE media gateway unit (MGU) and Microsoft
Lync client when Media Bypass is configured in Microsoft Lync 2019 Server.

Direct SIP Supported Features

During the certification process, the following Microsoft Lync features were validated with MX-ONE
Service Node software 5.0 SP4.
• Basic Call services between MX-ONE and Lync end-points over SIP trunks:
– Anonymous user calls
– Caller ID on both ends
– Decline call
– Call forwarding and simultaneously ring feature
– Inbound and outbound calls

• Media bypass (also known as direct media between MX-ONE and Microsoft Lync clients). Encryption
(TLS and SRTP) is required for this functionality.
– Inbound call from MX-ONE user device to Microsoft Lync client
– Outbound call from Microsoft Lync client to MX-ONE user device
– Outbound call: Call Forward All (CFA) to another Microsoft Lync client

16
 SKYPE FOR BUSINESS SERVER 2019
CHAPTER 3 INTEGRATION DESCRIPTION

– Outbound call from Microsoft Lync to another Lync user; with bypass enabled and CFA enabled

• Outbound call: PBX CFB (Call Forward on Busy) to another Microsoft Lync user
– Outbound call from Microsoft Lync to another Lync user; with bypass enabled and CFB enabled
• Conference
• Failover (to secondary Mediation Server - Lync gateway)
• Security (support for TLS/SRTP encryption)

Prerequisites
For proper integration between MiVoice MX-ONE and Skype for Business Server using Direct SIP, there
are some prerequisites on both sides that must be fulfilled.

MiVOICE MX-ONE Requirements

On the MiVoice MX-ONE side, at least one MX-ONE Service Node and one Media Gateway are required
to interwork with Skype for Business Server 2019.

Main Components
At least, the following MX-ONE components are required:
• MX-ONE communications system
– MX-ONE Service Node
• 5.0 SP4 or a later version
• Supported media gateways with the latest firmware compatible with 5.0 SP4, or a later version, which
can be:
– MX-ONE Classic - 7U 19-inch chassis, MGU board, or
– MX-ONE Lite - 3U 19-inch chassis, using MGU board
– MX-ONE Slim – 1U 19-inch chassis, using MGU board

• Terminals
– All current MX-ONE terminal types are supported with this integration: SIP, H.323, analog, digital,
DECT, and mobile extension

Licenses
The MX-ONE licenses needed for this integration are:
• SIP trunk licenses–note that the quantity of licenses depend on how the system is deployed).
• Encryption licenses are required if encryption (TLS/SRTP) is used.

Always check with your Mitel partner that your system has the required licenses, before beginning the
integration deployment.

Skype for Business Server 2019

A Microsoft environment needs to be in place in the customer site. Note that Microsoft Lync is not part of
the MX-ONE offering. It is important that expertise of Microsoft-competent engineers are available for

17
 INSTALLATION
CHAPTER 3 INSTALLATION AND CONFIGURATION

installation and integration according to the MX-ONE configuration guidelines for the interface between
the systems.

Main Components
The main Microsoft components that are required to interconnect with MiVoice MX-ONE are Skype for
Business Server 2019, Mediation Server, and Lync clients. The Lync requirements are described in the
Microsoft Lync Serve documentation. See the chapter References at the end of this guide.
NOTE: In Mitel´s lab validation, a single Skype for Business Server Standard Edition with a co-located
Mediation Server was used. For testing load balancing and failover, two stand-alone Mediation
Servers were added to the topology.

Licenses
Microsoft licenses needed for this integration are described as they are beyond the scope of this guide.
Contact Microsoft or a qualified Microsoft partner to obtain the proper license requirements for each
component of the Skype for Business Server solution.

Installation and Configuration

Installation

MiVoice MX-ONE Installation

Ensure that MX-ONE Service Node software 5.0 SP4 or a later version is installed in the customer envi-
ronment. The system installation is not covered in this guide and must be performed by a qualified Mitel
certified partner before the start of the integration work begins.
For Mitel MX-ONE installation, check the appropriate CPI documentation.

Microsoft Infrastructure
Ensure that Microsoft infrastructure and Skype for Business Server are installed in the customer environ-
ment by a qualified engineer.
For Microsoft infrastructure and Skype for Business Server requirements, check the appropriate Microsoft
documentation.

18
 CONFIGURATION
CHAPTER 3 INSTALLATION AND CONFIGURATION

Configuration
The following information was used in Mitel’s laboratory setup during the validation of the solution. The
setup may change depending of the customer specific needs.
NOTE: Fully Qualified Domain Name (FQDN) needs to be properly specified in the Domain Name System
(DNS).
• MX-ONE 5.0 SP4 (or a later version)
– Domain: lab.moon.galaxy Note that MX-ONE is part of a sub-domain
– IP address: 192.168.222.10
FQDN: mx-one-lync.lab.moon.galaxy
• Microsoft Domain Controller, Active Directory, Certification Authority, and DNS Server
– Domain: moon.galaxy
– IP address: 192.168.222.2
FQDN: lync-infra.moon.galaxy
• Skype for Business Server Standard Edition and Mediation pool
– Domain: moon.galaxy
– IP address: 192.168.222.3
FQDN: lync-2019-se.moon.galaxy
NOTE: Mitel recommends that complex scenarios be validated in the partner labs before customer deploy-
ment.

Direct SIP Setup

A SIP trunk must be configured in MX-ONE and the access code for this route (a trunk towards Skype for
business).
MX-ONE uses ports TCP 5060 and TLS 5061 to be interconnected with Skype for Business Server 2019.
NOTE: MX-ONE 5.0 SP4 (or a later version) works with predefined SIP profiles for certain SIP service
providers. if used, the profile file will help you in configuring the right data for the type selected. Each
profile file may contain a number of profiles. The profile will preconfigure settings such as "-register",
"-trusted", and so on according to the requirements of telephony provider.
MX-ONE 5.0 SP4 (or a later version) has predefined SIP trunk profiles to be used with Microsoft Lync
2019. One of the following trunk profiles needs to be selected during the MX-ONE SIP trunk configuration.
• Lync_TCP
TCP is used as transport protocol; the listening port is 5068.
• Lync_TLS_SRTP. TCP is used as transport protocol; the listening port is 5067. SRTP is used to
encrypt the media; it uses RTP/SAVP.
The following setup uses Lync_TCP where TCP is the transport protocol. In this case, the remote port is
expected to be listening on port 5068.
To ensure a good interoperability between MiVoice MX-ONE and Skype for Business Server 2019, the
SIP trunk profiles defined to Lync are “Forced Gateway”, at this guarantees the same behavior for all
types of calls passing through MX-ONE and towards Skype for Business Server 2019.

19
 CONFIGURATION
CHAPTER 3 INSTALLATION AND CONFIGURATION

MiVoice MX-ONE Direct SIP Setup - TCP

The following figure shows the Direct SIP Configuration used in this guide.

The following setup needs to be done in MX-ONE for configuring Direct SIP. Note that only SIP Route
definitions are shown.
1. Use the following command to view more details regarding the SIP Profile Lync_TCP:
sip_route -print -profile Lync_TCP
2. Define SIP Route category:
ROCAI:ROU=99,SEL=7110000000000010,SIG=0111110000A0,TRAF=03151515,TRM=4,
SERV=3100000001,BCAP=001100;
3. Define SIP Route data:
RODAI:ROU=99,TYPE=TL66,VARC=00000000,VARI=00000000,VARO=00000000;
4. Define SIP trunk data specific:
sip_route -set -route 1 -profile Lync_TLS_SRTP -uristring0 "sip:[email protected]" -re-
moteport 5067 -accept REMOTE_IP -match "mxoneskype.skypebusi-
ness.com,10.211.62.165,skype.skypebusiness.com,10.211.62.175" -codecs PCMA,PCMU -protocol
tls -service PRIVATE;
5. Verify your configuration:
sip_route -print –route 99 –short
6. Define the SIP Route equipment initiate; for example:
ROEQI:ROU=99,TRU=1-1&&1-30;
7. Define external destination SIP Route data:
RODDI:ROU=99,DEST=99,ADC=0005000000000250000001010000,SRT=3;

20
 CONFIGURATION
CHAPTER 3 INSTALLATION AND CONFIGURATION

Skype for Business Server 2019 Configuration -- TCP

To finalize the configuration between MX-ONE and Skype for Business Server 2019, do the following:
1. Enable TCP port for the Mediation pool (disabled by default).

Define PSTN Gateway in the Skype for Business Server 2019 Topology Builder
1. Open Skype for Business Server 2019, Topology Builder, and define a PSTN gateway to be used
between Lync and MX-ONE.
2. To define the PSTN gateway, expand Shared Components, right-click PSTN gatewaysoption.

21
 CONFIGURATION
CHAPTER 3 INSTALLATION AND CONFIGURATION

3. Click New IP/PSTN Gateway. The dialog box opens the Gateway FQDN or IP Address. Specify the
MX-ONE IP Address or FQDN and click Next.

4. Define the IP address: in this example, the default is retained. Click Next.

22
 CONFIGURATION
CHAPTER 3 INSTALLATION AND CONFIGURATION

5. Define the root trunk:

• Trunk name: FQDN (MX-ONE FQDN)
• Listening port for IP/PSTN gateway: 5060 (MX-ONE SIP TCP port)
• SIP Transport Protocol: TCP
• Associated Mediation Server: lync-2019-se.moon.galaxy
• Associated Mediation Server port: 5068 (default)
6. Click Next.

7. Publish the Topology.

Define a Dial Plan

The Dial Plan configuration is required to allow Microsoft Lync users to dial to MX-ONE terminals and
PSTN.

23
 CONFIGURATION
CHAPTER 3 INSTALLATION AND CONFIGURATION

To define it, execute the following:

1. Open the Skype for Business Server Control Panel.
2. Click Voice Routing and choose Dial Plan.

3. Define Normalization rules that fits your organization needs. A rule for Lync users to dial to MX- ONE
terminals and another to dial to PSTN (ensure that MX-ONE is connected to PSTN) are required. If
needed, contact Microsoft for the appropriate setup for your requirement.
Figure 3.1: New Normalization Rule, five digits example

4. Commit the changes.

Define Voice Policy

A voice policy is required to enable Microsoft Lync users to dial out via the Direct SIP connection using
MX-ONE. Lync client users need to be assigned for this policy.
To Create the Voice Policy, do the following:
1. Click Voice Routing and choose Voice Policy.
2. Click New and choose the type of policy that is applicable for your company setup, site policy or user
policy.
3. Enter a Name and a Description for the voice policy.

24
 CONFIGURATION
CHAPTER 3 INSTALLATION AND CONFIGURATION

4. Associate a new PSTN for the policy and click New.

5. Enter a Name and a Description for the New PSTN Usage Record

6. Click New to associate a route with this PSTN usage record.

7. Enter a Name and a Description for the new Route.
8. Associate the MX-ONE gateway that you created earlier with the new Route. To do this, click Add in
Associated Gateways.

25
 CONFIGURATION
CHAPTER 3 INSTALLATION AND CONFIGURATION

9. In Select Gateway, select the MX-ONE gateway created previously.

10. Click OK for all the queries to retain the configurations made.

11. Commit all changes.

26
 CONFIGURATION
CHAPTER 3 INSTALLATION AND CONFIGURATION

Define Trunk Configuration

To assign the MX-ONE gateway to a site or pool trunk, follow these steps:
1. Click Voice Routing and then click Trunk Configuration.
2. Click New and choose the type of trunk that is applicable for your company setup, site trunk, or pool
trunk.

3. Select the Encryption support level. In this case, it is Not supported.

4. Commit all changes to complete the setup.

27
 CONFIGURATION
CHAPTER 3 INSTALLATION AND CONFIGURATION

Conclusion
Now the setup is complete, assign users to the Policy created previously and test the integration by
making calls between the systems.
See the topic Enable users for Enterprise Voice in Skype for business Server at the following link:
http://technet.microsoft.com/en-us/library/gg413011.aspx

Direct SIP with Security and Media Bypass Setup

The following figure shows the Direct SIP with security and Media Bypass configuration used in this guide.

MiVoice MX-ONE Direct SIP with Security and Media Bypass Setup
The following setup needs to be done in MX-ONE in order to configure Direct SIP with security (encryp-
tion). Note that only Route definitions are shown.
NOTE: MX-ONE FQDN needs to be properly defined in the DNS Server.

When using security, the appropriate certificate must be installed in MX-ONE in addition to the encryption
licenses. Check Certificate Management on MX-ONE CPI documentation for more details regarding
certificates.
NOTE: TLS/SRTP security is required for Media bypass functionality. It means that the proper encryptions
licenses must be loaded in the MX-ONE system.
1. Use the following command to view more details regarding the SIP Profile Lync_TLS_SRTP:
sip_route -print -profile Lync_TLS_SRTP
2. Define SIP Route category:
ROCAI:ROU=98,SEL=7110000000000010,SIG=0111110000A0,TRAF=03151515,TRM=4,
SERV=3100000001,BCAP=001100;
3. Define SIP Route data:
RODA I:ROU=98,TYPE=TL66,VARC=00000000,VARI=00000000, VARO=00000000;

28
 CONFIGURATION
CHAPTER 3 INSTALLATION AND CONFIGURATION

4. Define SIP trunk data specific:

sip_route -set -route 1 -profile Lync_TLS_SRTP -uristring0 "sip:[email protected]" -re-
moteport 5067 -accept REMOTE_IP -match "mxoneskype.skypebusi-
ness.com,10.211.62.165,skype.skypebusiness.com,10.211.62.175" -codecs PCMA,PCMU -protocol
tls -service PRIVATE;
5. Verify your configuration:
sip_route -print –route 98 -short
6. Define the SIP Route equipment initiate: ROEQI:ROU=98,TRU=1-1;
7. Define external destination SIP Route data:
RODDI:ROU=98,DEST=98,ADC=0005000000000250000001010000,SRT=3;

Import the Certificate to MX-ONE Service Node

Import the server certificate mx-one-certificate.pfx to MX-ONE Service Node.
1. Install the certificate in the MX-ONE Service Node 1.
2. Run the mxone_certificate as root and press Enter button. The following screen appears.

3. Select certificate and click OK. The following screen appears.

29
 CONFIGURATION
CHAPTER 3 INSTALLATION AND CONFIGURATION

4. Select import and click OK. The following screen appears.

5. Click OK. The following screen appears to select a file or directory where the signed certificate is
stored.

30
 CONFIGURATION
CHAPTER 3 INSTALLATION AND CONFIGURATION

6. Specify the path where the forMXONE.pfx certificate is stored as shown in the following screen.

7. Click OK to store the imported certificate. Next, you install the certificate that you have imported and
click OK.

31
 CONFIGURATION
CHAPTER 3 INSTALLATION AND CONFIGURATION

8. Enable the TLS in MX-ONE > Manage TLS in MX-ONE -> Configure MX-ONE to use TLS. Refer to
the 132/154 31-ANF 901 14 document for more detail.
9. Enable Media Encryption in the route:
media_encryption_enable -type route
media_encryption_enable -type extension
media_encryption_enable -type intermgw
media_encryption_print

Lync Configuration with Security and Media Bypass Setup

You must do the following to finalize the configuration between Mitel MX-ONE and Skype for Business
Server 2019 the following needs to be done:
Define PSTN Gateway in the Skype for Business Server 2019 Topology Builder
1. Open the Skype for Business Server 2019, Topology Builder, and define a PSTN gateway be used
between Lync and MX-ONE.

2. To define the PSTN gateway, expand Shared Components and right-click the PSTN gateway.

3. Click New IP/PSTN Gateway. The Define the PSTN Gateway FQDN dialog box appears.

32
 CONFIGURATION
CHAPTER 3 INSTALLATION AND CONFIGURATION

4. Enter the FQDN or the IP address: specify the MX-ONE IP Address or FQDN and click Next.
5. Define the IP address: in this example, the default is retained. Click Next.

6. Define the root trunk:

33
 CONFIGURATION
CHAPTER 3 INSTALLATION AND CONFIGURATION

• Trunk name: FQDN (MX-ONE FQDN)

• Listening port for IP/PSTN gateway: 5061 (MX-ONE SIP TCP port)
• SIP Transport Protocol: TCP
• Associated Mediation Server: lync-2019-se.moon.galaxy
• Associated Mediation Server port: 5067 (default)
7. Click Next.

8. Publish the Topology

Define Dial Plan and Voice Policy

Define the Dial Plan and the Voice Policy as explained previously in this section.

34
 CONFIGURATION
CHAPTER 3 INSTALLATION AND CONFIGURATION

Define Trunk Configuration

To assign the MX-ONE gateway to a site or a pool trunk, and follow these steps:
1. Click Voice Routing, and then click Trunk Configuration.
2. Click New and choose the type of trunk that is applicable for your company setup, site trunk, or pool
trunk.
3. Select Enable media bypass.

4. Keep the default Encryption support level, which in this case is Required.

Now that the setup is concluded, assign users with the policy created previously and test the integration
making calls between the systems.

Load Balancing and Failover Setup

35
 CONFIGURATION
CHAPTER 3 INSTALLATION AND CONFIGURATION

Load Balancing
Mitel MX-ONE 5.0 and later versions support load balancing setup when connected with more than one
Mediation Server. In such scenario, the Microsoft DNS Load Balancing functionality can be used.
MX-ONE 5.0 and later versions support DNS SRV and multiple A-record query where a list with multiple
entries can be used. When properly configured, MX-ONE will attempt to send an INVITE to the entries in
the list until the call is successful. No answer or 503 Service Unavailable from one entry will trigger
MX-ONE to try the next entry.
For more details, see MX-ONE SIP Route command description in CPI or sip_route –help, parameter
remote port.

Failover
The failover feature also uses the Microsoft DNS Load Balancing functionality. When integrating MX-
ONE and Mediation Server, the same configuration is valid for both failover and load balancing.
In a scenario, where two Mediation servers are used and if one of the servers is unavailable, then the first
call will be attempted to set up to the first server, but it will be redirected after a few seconds and
answered; and all subsequent calls will be redirected and answered in the second Mediation Server.
The reason it takes some seconds before getting an answer from the second server, is that after the
INVITE is sent to the first server, the system waits four seconds for an answer, and if no answer is
received, the host is grey-listed for 32 seconds and an INVITE is sent to the second server after this.
For additional details, see the MX-ONE SIP Route command description in CPI or sip_route – help,
parameter remote port.
The following is a description of the setup that was verified in Mitel´s lab.

For this scenario, two standalone Mediation servers are used. In the MX-ONE side, only one MX-ONE
Service Node is used, and it is configured with the Mediation Pool entry.

36
 CONFIGURATION
CHAPTER 3 INSTALLATION AND CONFIGURATION

DNS Setup
Microsoft DNS needs to be configured to support Round Robin as described in the TechNet article
“Configure DNS for Load Balancing”. Follow the link and see the item “To enable round robin for Windows
Server”.
http://technet.microsoft.com/en-us/library/gg398251.aspx
The following figure shows the setup when Round Robin option is enabled.

DNS Multiple A record setup – Mediation Servers

To set up DNS Host (A) records for the two Mediation servers, the following must be configured. In the
DNS Manager Tool, create the entries as shown in the following table.
NOTE: For more information about creating the DNS Host A records, refer to http://technet.micro-
soft.com/en-us/library/gg398593.

FQDN TYPE IP ADDRESS

med.moon.galaxy Host (A) 192.168.222.7

med.moon.galaxy Host (A) 192.168.222.8

To test your configuration, use the command ping to check the setup.

37
 CONFIGURATION
CHAPTER 3 INSTALLATION AND CONFIGURATION

MX-ONE Direct SIP with Load Balancing and Failover Setup - TCP
The following setup needs to be done in MX-ONE for configuring Direct SIP with load balancing and
failover setup. Note that only Route definitions are shown.
NOTE: MX-ONE FQDN needs to be properly defined in the DNS Server.
1. Use the following command to view more details regarding the Profile Lync_TCP:
sip_route -print -profile Lync_TCP
2. Define SIP Route category:
RO-
CAI:ROU=97,SEL=7110000000000010,SIG=0111110000A0,TRAF=03151515,TRM=4,SERV=3100
0000 01,BCAP=00110;
3. Define SIP Route data:
RODAI:ROU=97,TYPE=TL66,VARC=00000000,VARI=00000000, VARO=00000000;
4. Define SIP trunk data specific:
sip_route -set -route 1 -profile Lync_TLS_SRTP -uristring0 "sip:[email protected]" -re-
moteport 5067 -accept REMOTE_IP -match "mxoneskype.skypebusi-
ness.com,10.211.62.165,skype.skypebusiness.com,10.211.62.175" -codecs PCMA,PCMU -protocol
tls -service PRIVATE;
5. Verify the configuration:
sip_route -print –route 97 -short
6. Define the SIP Route equipment initiate:
ROEQI:ROU=97,TRU=1-1;
7. Define external destination SIP Route data:

38
 CONFIGURATION
CHAPTER 3 INSTALLATION AND CONFIGURATION

RODDI:ROU=97,DEST=97,ADC=0005000000000250000001010000,SRT=3;

Lync Configuration with Load Balancing and Failover Setup – TCP

Define a Mediation poll in the Skype for Business Server 2019 Topology Builder.
In the test validation, a Mediation poll named meds.moon.galaxy was created with two standalone Medi-
ation servers.
Mediation Pool FQDN=meds.moon.galaxy Mediation Server 1 FQDN= med-1.moon.galaxy Mediation
Server 2 FQDN= med-2.moon.galaxy

To set up the PSTN gateways, refer the Skype for Business Server 2019 configuration - TCP.
Execute calls between MX-ONE and Microsoft Lync and check that the calls are distributed between the
systems.

MX-ONE Direct SIP with Load Balancing and Failover Setup - TLS
The following setup needs to be done in MX-ONE in order to configure Direct SIP with load balancing and
failover setup, please note that only Route definitions are showed.
NOTE: MX-ONE FQDN needs to be properly defined in the DNS Server.
1. Use the following command to check more details regarding SIP Profile Lync_TLS sip_route -print
-profile Lync_TLS
2. Define SIP Route category:
ROCAI:ROU=96,SEL=7110000000000010,SIG=0111110000A0,TRAF=03151515,TRM=4,
SERV=3100000001,BCAP=00110;
3. Define SIP Route data:
RODAI: ROU=96,TYPE=TL66,VARC=00000000,VARI=00000000, VARO=00000000;
4. Define SIP trunk data specific:

39
 CONFIGURATION
CHAPTER 3 INTEGRATION NOTES

sip_route -set -route 1 -profile Lync_TLS_SRTP -uristring0 "sip:[email protected]" -re-

moteport 5067 -accept REMOTE_IP -match "mxoneskype.skypebusi-
ness.com,10.211.62.165,skype.skypebusiness.com,10.211.62.175" -codecs PCMA,PCMU -protocol
tls -service PRIVATE;
5. Verify your configuration:
sip_route -print –route 96 -short
6. Define the SIP Route equipment initiate:
ROEQI:ROU=96,TRU=1-1;
7. Define external destination SIP Route data:
RODDI: ROU=96,DEST=96,ADC=0005000000000250000001010000,SRT=3;

Import the Certificate to MX-ONE Service Node

Import the server certificate mx-one-certificate.pfx to MX-ONE Service Node. On the access Server, for
example, MX-ONE Service Node 1 runs the following command:
1. Install the certificate in the MX-ONE Service Node 1: mxone_certificate, and select the certificate
mx-one-certificate.pfx
2. Enable Media Encryption in the route: media_encryption_enable –type route

Lync Configuration with Load Balancing and Failover Setup – TLS

Define a Mediation poll in the Skype for Business Server 2019 Topology Builder.
In the test validation, a Mediation poll named meds.moon.galaxy was created with two standalone Medi-
ation servers.
Mediation Pool FQDN=meds.moon.galaxy Mediation Server 1 FQDN= med-1.moon.galaxy Mediation
Server 2 FQDN= med-2.moon.galaxy
To set up the PSTN gateways, refer the Lync configuration with security and Media Bypass setup section.
Execute calls between MX-ONE and Microsoft Lync and check that the calls are distributed between the
systems.

Integration Notes
The latest software and firmware versions of MX-ONE components must be used.
NOTE: Mitel recommends that complex scenarios shall be validated in the partner labs before to customer
deployment.

40
 CONFIGURATION
CHAPTER 3 REFERENCES

References
Always check the latest documentation. The links below are the ones available for reference. Mitel CPI
Documentation – Mitel MX-ONE 5.0 SP4 or a later version.
Skype for Business Server Deploying Enterprise Voice
Enable Users for Enterprise Voice

Revision History

DOCUMENT VERSION COMMENTT DATE

A First release 2015-11-19
B Minor corrections 2014-03-28
C Updated with Mitel template 2015-06-08
D Updated in 4.2.3.7, 2015-10-27
cert_install_local replaced by
mxone_certificate. MX-ONE
version information also
corrected.
D3 Spelling correction 2017-04-05
D4 2013 old screens replaced with 2019-04-24
2015 screens
D5 Server 2015 is changed to 2019-09-10
server 2019

41
CHAPTER 4 INTRODUCTION

Installation and Configuration

Guide for GX and EX Controller
Introduction
This document describes a typical scenario for a branch office with survivability and local presence.
It contains both the GX and the EX gateways.
Figure 4.1: EX and GX Controller Gateways

NOTE: The EX gateway can only be used as a stand-alone system.

Prerequisites
When planning the number series in the branch office following must be considered:

42
 NUMBER ANALYSIS
CHAPTER 4 SETTING UP MX-ONE FOR GX CONTROLLER

• The extension range must be coherent and matching the local DID number series (if local presence is
used).
• MX-ONE SW must be at least version 7.0.
• The firmware level of the EX-Controller and GX-Gateway shall be at least Dgw 42.3.1032-MT with
profile S100-MT-D2000-45 for GX-Gateway and STNL-MT-D2000-65 for EX-Controller.
Other considerations/restrictions:
• A SIP outbound proxy address must be assigned in the startup.cfg file, that is, the SIP outbound proxy
address is the local address of the EX-Controller / GX-Gateway.

Setting up MX-ONE for GX Controller

Number Analysis
Number Analysis Data

Type of Series Number Series

Extension Number Series 10000 - 31999

33200 - 49999
67000 - 67999
External Destination Code 068
081 – 088
321
331
81 - 88
LCR Access Code 00

Call Discrimination Data

Type of Series Number Series

External/Internal Number CDCAT Customer

Number Analysis Data

43
 EXTENSION DATA
CHAPTER 4 SETTING UP MX-ONE FOR GX CONTROLLER

Extension Data
Figure 4.2: Directory Number Profile

MDSH>

Common Service Profile 9:

Cust: 0
Traf : 0103151515
Serv: 111100011001000000000100000300
Cdiv: 111000111010000
Roc: 000001
Npres: 0011000
Offered Time: 0
Forced DisconnectTime: 0
CnnLog: 0
Csp Name: Standard

44
 LEAST COST ROUTING DATA
CHAPTER 4 SETTING UP MX-ONE FOR GX CONTROLLER

Common Service Profile 11:

Cust: 0
Traf : 0103151515
Serv: 111130011001000000000100000300
Cdiv: 111000111010000
Roc: 000001
Npres: 0011000
Offered Time: 0
Forced DisconnectTime: 0
CnnLog: 0
Csp Name: Intrusion

Least Cost Routing Data

Least Cost Destination Data
Table 4.1: External Number Table

Entry TRC PRE Conf

00013443111 8 N
00031325 8 N
00040598 8 N
00084226 7 N
000856867 7 N

END
Least Cost Destination Data
Table 4.2: Number Length Table (Sheet 1 of 2)

Entry TRC PRE CONF MIN MAX ACF

001 0 N 6 18 Y
002 0 N 6 18 Y
003 0 N 6 18 Y
004 0 N 6 18 Y
005 0 N 6 18 Y
006 0 N 6 18 Y

45
 LEAST COST ROUTING DATA
CHAPTER 4 SETTING UP MX-ONE FOR GX CONTROLLER

Table 4.2: Number Length Table (Continued) (Sheet 2 of 2)

Entry TRC PRE CONF MIN MAX ACF

007 0 N 6 18 Y
008 0 N 6 18 Y
009 0 N 6 18 Y

Least Cost Destination Data

Table 4.3: Number Table

Entry TRC PRE ACCT FRCT TOLL CBCS BTON TNS OSA

5 0 1 1111111 0
1111111
1
5 0 2 1111111 0
1111111
1
5 0 3 1111111 0
1111111
1
4 0 4 1111111 0
1111111
1

END
Least Cost Destination Data
Table 4.4: Fictitious Destination Table

FRCT TZONE PRE

1 1 081
2 1 083
3 1 085
4 1 088

END

46
 ROUTE DATA
CHAPTER 4 SETTING UP MX-ONE FOR GX CONTROLLER

Route Data

ROCAP
Route Category Data
Figure 4.3: Route Category Data

RODAP
Route Data

Table 4.5: Route Data

ROU Type VARC VARI VARO Filter

81 TL66 H'00000000 H'0000000 H'00000000 NO

0
83 TL66 H'00000000 H'0000000 H'00000000 NO
0
211 TL66 H'00000000 H'0000000 H'00000000 NO
0

SIP ROUTE
One SIP route to each branch node is specified.
Route 81 towards BO#1 (Linköping)
route : 81
protocol = tcp
profile = Default
service = PUBLIC
uristring0 = sip:[email protected]
fromuri0 = sip:[email protected]

47
 ROUTE DATA
CHAPTER 4 SETTING UP THE GX GATEWAY

remoteport = 5070
accept = TRUNK_INFO
match = user=trunk
register = NO_REG
Route 83 towards BO#2 (Göteborg)
route : 83
protocol = tcp
profile = Default
service = PUBLIC
uristring0 = sip:[email protected]
fromuri0 = sip:[email protected]
remoteport = 5070
accept = TRUNK_INFO
match = user=trunk
register = NO_REG
Route 211 towards BO#3 (Malmö)
route : 211
protocol = udp
profile = MXONE-tieline
service = PRIVATE_SERVICES
uristring0 = sip:[email protected];tgrp=BO3
fromuri0 = sip:[email protected];tgrp=BO3
accept = ALL
register = SET_BY_PROFILE
trusted = TRUST_BY_PROFILE
NOTE: BO#3 is only reached by SIP trunks as it is an EX controller system running an own instance of
MX-ONE.

Setting up the GX Gateway

This section describes how to setup BO#1 (Linköping).
Setting up BO#2 (Göteborg) is similar, only numbering information and own IP-address is changed.

48
 LOGON
CHAPTER 4 SETTING UP THE GX GATEWAY

Logon
This section describes how to setup BO#1.
Factory Reset the EX Controller and plug in the network cable to the ETH1 port on EX Controller (If DHCP
is running in the network).
NOTE: If DHCP is not running into the network then, plug in the network cable to the ETH2 port on EX
Controller and use the default IP address of 192.168.0.10 to open the EX Controller Interface.
Figure 4.4: Login page

This section describes how to setup BO#1.

1. Factory Reset the EX Controller and plug in the network cable to the ETH1 port on EX Controller (If
DHCP is running in the network)
– User name/password: public /
– User name/password: admin/administrator

2. Plug in the analog phone in the FXS port 1 of the EX Controller and dial *#*0 to know the IP address
of the EX Controller assigned by using DHCP server.
3. Log into the EX Controller by using the above-mentioned IP address and navigate as described below
to configure.

Network Settings

Host
1. Select Network > Host and keep the default configuration interface as mentioned below.
Figure 4.5: Host settings - 1

Figure 4.6: Host settings - 2

2. Change to Static IP-address and enter default Gateway (GW).

49
 NETWORK SETTINGS
CHAPTER 4 SETTING UP THE GX GATEWAY

Figure 4.7: Changing static IP address

3. Change to static DNS server and enter IP-address or FQDN to DNS server.
Figure 4.8: Changing static DNS server

4. Change to static SNTP server, enter time server data.

Figure 4.9: Changing to static SNTP server

5. Set the Static Time Zone.

Valid options are:
– Pacific Time (Canada and US): PST8PDT7,M3.2.0/02:00:00,M11.1.0/02:00:00
– Mountain Time (Canada and US): MST7MDT6,M3.2.0/02:00:00,M11.1.0/02:00:00
– Central Time (Canada and US): CST6CDT5,M3.2.0/02:00:00,M11.1.0/02:00:00
– Eastern Time (Canada and US): EST5EDT4,M3.2.0/02:00:00,M11.1.0/02:00:00
– Atlantic Time (Canada): AST4ADT3,M3.2.0/02:00:00,M11.1.0/02:00:00

50
 INTERFACES
CHAPTER 4 SETTING UP THE GX GATEWAY

– GMT Standard Time: GMT0DMT-1,M3.5.0/01:00:00,M10.5.0/02:00:00

– W. Europe Standard Time: WEST-1DWEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00
– China Standard Time: CST-8
– Tokyo Standard Time: TST-9
– Central Australia Standard Time: CAUST-9:30DCAUST-10:30,M10.5.0/02:00:00,M3.5.0/02:00:00
– Australia Eastern Standard Time: AUSEST-10AUSDST-11,M10.5.0/02:00:00,M3.5.0/02:00:00
– UTC (Coordinated Universal Time): UTC0
Figure 4.10: Setting static time zone

6. Leave all other items as it is and click Apply when finished.

Interfaces
1. Go to Network > Interface.
Figure 4.11: Interface

2. Change Uplink to IpStatic (IPv4 Static) and enter the static IP-address and Static Default Gateway.
Figure 4.12: Changing Uplink to IpStatic

3. Leave all other items as it is and click Apply when ready.

NOTE: When the IP-address is changed the connection is lost and a new logon must be done with
the new IP-address.

Local Firewalls
1. Go to Network > Local Firewall.
Figure 4.13: Local firewalls

2. If local firewall security is needed change default policy to Drop.

51
 SESSION BOARD CONTROLLER (SBC)
CHAPTER 4 SETTING UP THE GX GATEWAY

Figure 4.14: Changing default policy

3. Enter the networks for which traffic can enter from.

Figure 4.15: Enter network traffic

4. Click Save or Save and Apply when ready.

Session Board Controller (SBC)

Configuration
1. Go to SBC > Configuration. The following Call Agents are present.
Figure 4.16: Call agent - 1

Figure 4.17: Call agent - 2

52
 SESSION BOARD CONTROLLER (SBC)
CHAPTER 4 SETTING UP THE GX GATEWAY

Figure 4.18: Call agent - 3

2. Insert A-Number prefix and B-number prefix. These numbers are to be added in front of the numbers
in when the GW is in survivable mode, that is, the call is routed to PSTN and thus needs to be prefixed.
3. Enter the number range that is allowed in the branch in the PATTERN parameter. For example,
111[0-9][0-9]$ means that the allowed number range in this branch is 11100 – 11199.
Figure 4.19: Parameters screen

4. Configure each call agent (ca).

5. Click to enter specific data for each call agent.

Local_users_ca
• Enter the IP-address of MX-ONE to the DOMAIN variable.
• Enter the number range that is allowed in the branch in the PATTERN parameter. For example,
111[0-9][0-9]$ means that the allowed number range in this branch is 11100 – 11199.
• Insert A-Number prefix and B-number prefix. These numbers are to be added in front of the numbers
in when the GW is in survivable mode, that is, the call is routed to PSTN and thus needs to be prefixed.

53
 SESSION BOARD CONTROLLER (SBC)
CHAPTER 4 SETTING UP THE GX GATEWAY

Figure 4.20: Configure Call Agent screen

Figure 4.21: Call Agent Rulesets screen

Ruleset MX-ONE_build_RURI survivability (ACTIVE ONLY IN SURVIVAL MODE)

PATTERN=111[0-9][0-9]$
The pattern for the internal range of numbers, in this example the internal range would be 11100 – 11199
Calls to this number range stay always local (do not send to the PSTN in survival mode)
DOMAIN=192.168.17.44
The IP of the headquarter (the main PBX), in this case 192.168.17.44
Ruleset: MX_ONE_Appearance_Prefix (ACTIVE ONLY IN SURVIVAL MODE)
NEW: APP_PREFIX=SCA-

54
 SESSION BOARD CONTROLLER (SBC)
CHAPTER 4 SETTING UP THE GX GATEWAY

This is the prefix for the usernames connected with shared appearance. In this example we have two:
“SCA-“ and “EDN-“
Ruleset: MX-ONE_Remove_Outbound_Appearance (ACTIVE ONLY IN SURVIVAL MODE)
PATTERN=111[0-9][0-9]$
This rule will remove any prefix used for Shared Call Appearance. The pattern for the internal range of
numbers, in this example the internal range would be 11100 – 11199
Ruleset: MX-ONE_outbound_A_Number_prefix (ACTIVE ONLY IN SURVIVAL MODE)
PATTERN=111[0-9][0-9]
This defines the local numbers.
A_PRFX=013443
This is the prefix for the local numbers used on outgoing calls to the PSTN (in this example we received
a number block 013443xxxxx from the PSTN provider and add the prefix on outgoing calls, so that the
calling party number sent to the PSTN is correct)
PSTN_PREFIX=00
Dial this prefix to break out to the PSTN. Here we have configured the “00” (not to be mixed up with the
“00” for international calls!)
Ruleset: MX-ONE_outbound_B_Number_prefix (ACTIVE ONLY IN SURVIVAL MODE)
This ruleset applies to calls to numbers defined in BNUMBER and will add B_PRFX to the called party
number.
BNUMBER=67[0-9][0-9]$
Applies to calls to the specific range of extensions,
B_PRFX=08568
This is the prefix for the Called Party Number. In this case it was build like: National Prefix (08) + Main
part of the HQ’s local number: (568), in case somebody dials an extension in the HQ
Ruleset: MX-ONE_outbound_B_Number_Override (ACTIVE ONLY IN SURVIVAL MODE)
This ruleset applies to calls to numbers defined in BNUMBER and will use the BOVERRIDE as Called
Party Number.
BNUMBER=330[0-9][0-9]$
Applies to calls to the specific range
BOVERRIDE=0856867000
Calls to extensions like BNUMBER will be sent to BOVERRIDE, in this example they will be sent to
0856867000
Ruleset: MX-ONE_local_reg_users_with_survivability
(Builds the registration cache for survivability purpose)
EXT_DIGIT_LENGTH=5

55
 SESSION BOARD CONTROLLER (SBC)
CHAPTER 4 SETTING UP THE GX GATEWAY

The length of the internal numbers, in this case set to “5”, for numbers like “00001 – 99999”
1. Click Save when done.

Trunk _ Lines _ca

• Enter the IP-address of MX-ONE to the DOMAIN variable (in two places).
• Enter the number range that is allowed in the branch in the PATTERN parameter. For example,
111[0-9][0-9]$ means that the allowed number range in this branch is 11100 – 11199.
• Insert a main extension number in MAIN_EXT parameter, this is could be the local answering position
when dialling a vacant number, and so on.
• Enter the PSTN_PREFIX and STRIPNDIGTS, this is used to remove the public access code when
dialling PSTN calls in survivable mode.
Figure 4.22: Trunk_Lines_ca

Figure 4.23: Trunk_Lines_ca Parameters

56
 SESSION BOARD CONTROLLER (SBC)
CHAPTER 4 SETTING UP THE GX GATEWAY

Ruleset: MX-One_remove_prefix
PSTN_PREFIX=00
This is the prefix used to dial out to the PSTN
Ruleset: MX-One_trunk_lines_to_reception_survivability
An incoming call in survival mode will be sent to MAIN_EXT destination if not reachable
MAIN_EXT=11104
This will receive the incoming call in case the original destination is not reachable (not defined or not regis-
tered)
PATTERN=111[0-9][0-9]$
The pattern for the internal range of numbers, in this example the internal range would be 11100 – 11199
DOMAIN=192.168.17.44
The IP of the headquarter (the main PBX), in this case 192.168.17.44
Ruleset: MX-One_Set_RURI_User_Type_Parameter
Set RURI User Type Parameter
USER_TYPE=trunk
1. Click Save when done.

MX-ONE_Lim1
1. Enter the IP-address of the MX-ONE in the Peer Host field.
Figure 4.24: Peer Host field

2. Enter the IP-address of the GW in the RURI_HOST parameter.

57
 SESSION BOARD CONTROLLER (SBC)
CHAPTER 4 SETTING UP THE GX GATEWAY

Figure 4.25: RURI_HOST Parameter

Ruleset: rewrite_RURI_host
Customize RURI host
RURI_HOST= 192.168.17.81. This is the local IP address.
3. When all the changes for call agents are done, a yellow field is shown indicating that configuration has
been modified.
4. Click Save when ready.

MX-ONE_TRUNK
1. Enter the IP-address of the MX-ONE in the Peer Host field.
Figure 4.26: MX-ONE Trunk

Figure 4.27: MX-ONE_TRUNK Parameters

58
 ISDN
CHAPTER 4 SETTING UP THE GX GATEWAY

2. When all the changes for call agents are done, a yellow field is shown indicating that configuration has
been modified.
3. Click Save when ready.

Figure 4.28: Configuration Modified

4. If the indication is not removed there are some error in the configuration.
5. Double check changes described above and correct them.

ISDN
Figure 4.29: ISDN tab

If ISDN trunks are used, press Start Sensing. The system automatically detects certain parameters, for
example, number of channels.

59
 ISDN
CHAPTER 4 SETTING UP THE GX GATEWAY

Primary Rate Interface

Figure 4.30: Primary Rate Interface

1. When sensing is done for several markets, specific parameters can be changed.

60
 ISDN
CHAPTER 4 SETTING UP THE GX GATEWAY

Figure 4.31: Interface Configuration

61
 ISDN
CHAPTER 4 SETTING UP THE GX GATEWAY

62
 ISDN
CHAPTER 4 SETTING UP THE GX GATEWAY

2. Click Apply and restart requested service when done.

Interop
Figure 4.32: Interop

1. You can change other parameters dependent on market.

Figure 4.33: Interop Configuration screen

2. Click Apply and restart requested service when done.

63
 ISDN
CHAPTER 4 SETTING UP THE GX GATEWAY

Services
Figure 4.34: Services

1. Change other parameters dependent on market.

Figure 4.35: Services Configuration screen

2. Click Apply and restart requested service when done.

64
 POTS
CHAPTER 4 SETTING UP THE GX GATEWAY

POTS

Config
Figure 4.36: Config

1. Set market specific data for Caller Id handling.

Figure 4.37: General Configuration screen

2. Click Apply when done and restart service.

FXS Configuration
Figure 4.38: FXS Configuration

1. Set analog phone specific data according to market.

Figure 4.39: FXS Configuration screen

65
 SIP
CHAPTER 4 SETTING UP THE GX GATEWAY

Figure 4.40: Country Customisation screen

2. Click Apply when done and restart service.

SIP

Gateways
Following gateways and port numbers are pre-defined.
Figure 4.41: Gateways

NOTE:A SIP route must be defined in MX-ONE to handle traffic to and from the ‘trunks_MX-ONE’
gateway.
Figure 4.42: trunks_mx-one

66
 SIP
CHAPTER 4 SETTING UP THE GX GATEWAY

Servers
Figure 4.43: Servers

1. Enter IP-address to MX-ONE in both Registrar Host and Proxy Host fields.
Figure 4.44: Default Servers

2. Change trunk_lines_gw to Yes in the drop-down list for Gateway Specific.

Figure 4.45: trunk_lines_gw

3. Enter IP-address of MX-ONE in the Proxy Host field.

4. Enter IP-address of the gateway in the Outbound Proxy Host field.
Figure 4.46: Outbound Proxy Host field

5. Enter the IP-address of the gateway as Alternate Destination for MX1_analog_ext.

6. Enter the IP-address of MX-ONE as Alternate Destination for trunks_mx-one.

67
 SIP
CHAPTER 4 SETTING UP THE GX GATEWAY

Figure 4.47: Alternate Destination for trunks_mx-one

7. Click Apply when done and restart service.

Registrations
Figure 4.48: Registrations

1. Enter the extension numbers for the analog extensions.

Figure 4.49: Endpoints Registration screen

2. Click Apply or Apply and Refresh when done.

68
 SIP
CHAPTER 4 SETTING UP THE GX GATEWAY

Authentication
Figure 4.50: Authentication

1. If password is required press for any item.

Figure 4.51: Authentication Screen

2. Indicate for which Endpoint and Criteria the changes are to apply.
3. Enter the Auth Code, in the Password field.
4. In the Validate Realm field, select Disable.

69
 SIP
CHAPTER 4 SETTING UP THE GX GATEWAY

Figure 4.52: Validate Realm field

5. Click Apply or Apply and Refresh Registration when done and restart service. The result after
‘Registration’ and ‘Authentication’ should be like as follows:
Figure 4.53: Endpoints Registration Status

Transport
Figure 4.54: Transport

1. Enable UDP if required.

Figure 4.55: Protocol Configuration screen

2. Click Apply when done and restart service.

Interop
Figure 4.56: Interop

1. Select trunk in the SIP URI User Parameter Value field.

2. This is used in the ‘match’ parameter for the SIP route in MX-ONE.

70
 SIP
CHAPTER 4 SETTING UP THE GX GATEWAY

Figure 4.57: SIP URI User Parameter Value field

3. Click Apply or when done and restart service.

Misc
Figure 4.58: Misc

1. Enter the IP-address of MX-ONE in the SIP Domain Override field for trunk_lines_gw.
Figure 4.59: Gateway Configuration field

2. Click Apply when done and restart service.

71
 MEDIA
CHAPTER 4 SETTING UP THE GX GATEWAY

Media

Codecs
Figure 4.60: Codecs

1. Change Codecs according to preference.

Figure 4.61: Changing Codecs

2. Click Apply when done and restart service.

72
 CALL ROUTER
CHAPTER 4 SETTING UP THE GX GATEWAY

Call Router

Route Config
Figure 4.62: Route Config

1. Click for index 1. This is used if the received B-number contains a full number. That is, more digits

than the pure DID numbers.

Figure 4.63: Routes screen

2. In the Transformations field add a name for a transformation rule.

Figure 4.64: Transformations field

3. Click Save.

4. Click in the first Call Property Transformation and enter the same name as above.

5. Use Called E164 for both Criteria Based On and Transformation Applies To fields.

73
 CALL ROUTER
CHAPTER 4 SETTING UP THE GX GATEWAY

Figure 4.65: Configure Transformation 1 Screen

6. Click Save or Save and Insert Rule.

7. Click in the second Call Property Transformation and enter the same name as above.

8. The ‘Criteria Rule’ in this case is 443 (111..)$ and the transformation rule is ‘\1. This means that if a
B-number is received containing 44311104, then the 3 first digits (443) are removed before the call is
sent to MX-ONE for further processing. (111..)$ means that the number can only be 5 digits starting
with 111.
Figure 4.66: Configure Transformation Rule 1 screen

9. Click Save or Save and Insert Rule. Now, the ‘Call Property Transformations’ looks like this as shown
below.
Figure 4.67: Transformations screen

74
 MANAGEMENT
CHAPTER 4 SETTING UP THE GX GATEWAY

10. Click Save if the yellow indication on top of the page is ON.

Management

Backup/Restore
1. Click Activate .......
Figure 4.68: Image Configuration screen

2. Click Apply and Backup Now.

75
 MANAGEMENT
CHAPTER 4 SETTING UP THE GX GATEWAY

File
Figure 4.69: Internal files screen

Find the previously made backup image

76
 LOGON
CHAPTER 4 SETTING UP MX-ONE FOR AN EX CONTROLLER

Figure 4.70: Backup image

Setting up MX-ONE for an EX Controller

The setting up of MX-ONE is not described in this document since it does not differ from an ordinary
MX-ONE setup.

Setting up EX Controller

Logon
This section describes how to setup BO#1.
Factory Reset the EX Controller and plug in the network cable to the ETH1 port on EX Controller (If DHCP
is running in the network).
NOTE: If DHCP is not running into the network then, plug in the network cable to the ETH2 port on EX
Controller and use the default IP address of 192.168.0.10 to open the EX Controller Interface.

77
 NETWORK SETTINGS
CHAPTER 4 SETTING UP EX CONTROLLER

Figure 4.71: Logon screen

This section describes how to setup BO#1.

1. Factory Reset the EX Controller and plug in the network cable to the ETH1 port on EX Controller (If
DHCP is running in the network).
– User name/password: public /
– User name/password: admin/administrator

2. Plug in the analog phone in the FXS port 1 of the EX Controller and dial *#*0 to know the IP address
of the EX Controller assigned by using DHCP server.
3. Log into the EX Controller by using the above-mentioned IP address and navigate as described below
to configure.

Network Settings

Host
1. Select Network > Host and keep the default configuration interface as mentioned below.
Figure 4.72: Host screen

Figure 4.73: Automatic Configuration Interface

2. Change to Static IP-address and enter default Gateway (GW).

78
 NETWORK SETTINGS
CHAPTER 4 SETTING UP EX CONTROLLER

Figure 4.74: Default Gateway Configuration

3. Change to static DNS server and enter IP-address or FQDN to DNS server.
Figure 4.75: DNS Configuration screen

4. Change to static SNTP server and enter time server data.

Figure 4.76: SNTP Configuration

5. Set the Static Time Zone. Valid options are:

– Pacific Time (Canada and US): PST8PDT7,M3.2.0/02:00:00,M11.1.0/02:00:00
– Mountain Time (Canada and US): MST7MDT6,M3.2.0/02:00:00,M11.1.0/02:00:00
– Central Time (Canada and US): CST6CDT5,M3.2.0/02:00:00,M11.1.0/02:00:00
– Eastern Time (Canada and US): EST5EDT4,M3.2.0/02:00:00,M11.1.0/02:00:00
– Atlantic Time (Canada): AST4ADT3,M3.2.0/02:00:00,M11.1.0/02:00:00
– GMT Standard Time: GMT0DMT-1,M3.5.0/01:00:00,M10.5.0/02:00:00

79
 INTERFACES
CHAPTER 4 SETTING UP EX CONTROLLER

– W. Europe Standard Time: WEST-1DWEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00

– China Standard Time: CST-8
– Tokyo Standard Time: TST-9
– Central Australia Standard Time: CAUST-9:30DCAUST-10:30,M10.5.0/02:00:00,M3.5.0/02:00:00
– Australia Eastern Standard Time: AUSEST-10AUSDST-11,M10.5.0/02:00:00,M3.5.0/02:00:00
– UTC (Coordinated Universal Time): UTC0
Figure 4.77: Time Configuration screen

6. Leave all other items as it is and click Apply when finished.

Interfaces
1. Go to Network > Interface.
Figure 4.78: Interfaces screen

2. Change Uplink to IpStatic (IPv4 Static) and enter the static IP-address and Static Default Gateway.

Figure 4.79: Network Interface Configuration

3. Leave all other items as it is and click Apply when ready.

Local Firewalls
1. Go to Network > Local Firewall.
Figure 4.80: Local Firewall screen

2. If local firewall security is needed, change default policy to Drop.

80
 SBC
CHAPTER 4 SETTING UP EX CONTROLLER

Figure 4.81: Local Firewall Configuration screen

3. Enter the networks for which traffic can enter from.

Figure 4.82: Local Firewall Rules screen

4. Click Save or Save and Apply when ready.

SBC

Configuration
1. Go to SBC > Configuration. The following Call Agents are present.
Figure 4.83: SBC Configuration screen

Figure 4.84: Call Agent Configuration screen

81
 SBC
CHAPTER 4 SETTING UP EX CONTROLLER

2. Insert A-Number prefix and B-number prefix. These numbers are to be added in front of the numbers
when the GW is in survivable mode. That is, the call is routed to PSTN and thus needs to be prefixed.
3. Enter the number range that is allowed in the branch in the PATTERN parameter. For example,
321[0-9][0-9]$ means that the allowed number range in this branch is 32100 – 32199.
Figure 4.85: Routing Rulesets screen

4. Configure each call agent (ca).

5. Click to enter specific data for each call agent.

Local_users_ca
• Enter the IP-address of MX-ONE to the DOMAIN variable.
• Enter the number range that is allowed in the branch in the PATTERN parameter. For example,
321[0-9][0-9]$ means that the allowed number range in this branch is 32100 – 32199.
• Insert A-Number prefix and B-number prefix. These numbers are to be added in front of the numbers
when the GW is in survivable mode. That is, the call is routed to PSTN and thus needs to be prefixed.

82
 SBC
CHAPTER 4 SETTING UP EX CONTROLLER

Figure 4.86: Configure Call Agent screen

Figure 4.87: Call Agent Rulesets

Ruleset MX-One_build_RURI survivability (ACTIVE ONLY IN SURVIVAL MODE)

PATTERN=111[0-9][0-9]$
The pattern for the internal range of numbers, in this example the internal range would be 11100 – 11199
Calls to this number range stay always local (would not send to the PSTN in survival mode)
DOMAIN=192.168.17.94
The IP-address of the MX-ONE instance running on the VM, in this case 192.168.17.94
Ruleset: MX_One_Appearance_Prefix (ACTIVE ONLY IN SURVIVAL MODE)
NEW: APP_PREFIX=SCA-
This is the prefix for the usernames connected with shared appearance. In this example, you have two:
“SCA-“ and “EDN-“

83
 SBC
CHAPTER 4 SETTING UP EX CONTROLLER

Ruleset: MX-One_Remove_Outbound_Appearance (ACTIVE ONLY IN SURVIVAL MODE)

PATTERN=321[0-9][0-9]$
This rule removes any prefix used for Shared Call Appearance. The pattern for the internal range of
numbers, in this example the internal range would be 32100 – 32199
Ruleset: MX-One_outbound_A_Number_prefix (ACTIVE ONLY IN SURVIVAL MODE)
PATTERN=321[0-9][0-9]
This defines the local numbers.
A_PRFX=040598
This is the prefix for the local numbers used on outgoing calls to the PSTN (in this example, received a
number block 013443xxxxx from the PSTN provider and add the prefix on outgoing calls, so that the
calling party number sent to the PSTN is correct)
PSTN_PREFIX=00
Dial this prefix to break out to the PSTN. Here, you need to configure the “00” (not to be mixed up with
the “00” for international calls!)
Ruleset: MX-One_outbound_B_Number_prefix (ACTIVE ONLY IN SURVIVAL MODE)
This ruleset applies to calls to numbers defined in BNUMBER and will add B_PRFX to the called party
number.
BNUMBER=67[0-9][0-9]$
Applies to calls to the specific range of extensions,
B_PRFX=08568
This is the prefix for the Called Party Number. In this case, it was build like: National Prefix (08) + Main
part of the HQ’s local number: (568), in case somebody dials an extension in the HQ.
Ruleset: MX-One_outbound_B_Number_Override (ACTIVE ONLY IN SURVIVAL MODE)
This ruleset applies to calls to numbers defined in BNUMBER and will use the BOVERRIDE as Called
Party Number.
BNUMBER=440[0-9][0-9]$
Applies to calls to the specific range
BOVERRIDE=0856867000
Calls to extensions like BNUMBER will be sent to BOVERRIDE, in this example they will be sent to
0856867000
Ruleset: MX-One_local_reg_users_with_survivability
(Builds the registration cache for survivability purpose)
EXT_DIGIT_LENGTH=5
The length of the internal numbers, in this case set to “5”, for numbers like “00001 – 99999”
1. Click Save when done.

Trunk_Lines_ca
• Enter the IP-address of MX-ONE to the DOMAIN variable (in two places).

84
 SBC
CHAPTER 4 SETTING UP EX CONTROLLER

• Enter the number range that is allowed in the branch in the PATTERN parameter. For example,
321[0-9][0-9]$ means that the allowed number range in this branch is 32100 – 32199.
• Insert a main extension number in MAIN_EXT parameter, this is could be the local answering position
when dialling a vacant number, and so on.
• Enter the PSTN_PREFIX and STRIPNDIGTS, this is used to remove the public access code when
dialling PSTN calls in survivable mode.
Figure 4.88: Configure Call Agent screen

Figure 4.89: Call Agent Rulesets

Ruleset: MX-One_remove_prefix
PSTN_PREFIX=00
This is the prefix used to dial out to the PSTN
Ruleset: MX-One_trunk_lines_to_reception_survivability
An incoming call in survival mode will be sent to MAIN_EXT destination if not reachable
MAIN_EXT=11104
This will receive the incoming call in case the original destination is not reachable (not defined or not regis-
tered)
PATTERN=321[0-9][0-9]$
The pattern for the internal range of numbers, in this example the internal range would be 32100 – 32199

85
 SBC
CHAPTER 4 SETTING UP EX CONTROLLER

DOMAIN=192.168.17.94
The IP of the headquarter (the main PBX), in this case 192.168.17.94
Ruleset: MX-One_Set_RURI_User_Type_Parameter
Set RURI User Type Parameter
USER_TYPE=trunk
1. Click Save when done.

MX-ONE_Lim1
1. Enter the IP-address of the MX-ONE in the Peer Host field.
Figure 4.90: Peer Host field

2. Enter the IP-address of the GW in the RURI_HOST parameter.

Figure 4.91: RURI_HOST parameter

Ruleset: rewrite_RURI_host
Customize RURI host

86
 ISDN
CHAPTER 4 SETTING UP EX CONTROLLER

RURI_HOST= 192.168.17.85. This is the local IP address.

1. Click Save when ready.

MX-ONE_TRUNK
1. Enter the IP-address of the MX-ONE in the Peer Host field.
Figure 4.92: Call Agent Parameters

Figure 4.93: Call Agent Rulesets

2. When all the changes for call agents are done, a yellow field is shown indicating that configuration has
been modified.
3. Click Save when ready.
Figure 4.94: Configuration Modified screen

4. If the indication is not removed there are some error in the configuration.
5. Double check changes described above and correct them.

ISDN
Figure 4.95: ISDN Screen

87
 ISDN
CHAPTER 4 SETTING UP EX CONTROLLER

If ISDN trunks are used the first action to do is to click Start Sensing. The system automatically detects
certain parameters, for example, number of channels.

88
 ISDN
CHAPTER 4 SETTING UP EX CONTROLLER

Primary Rate Interface

Figure 4.96: Primary Rate Interface screen

1. When sensing is done for several markets, specific parameters can be changed.

89
 ISDN
CHAPTER 4 SETTING UP EX CONTROLLER

90
 ISDN
CHAPTER 4 SETTING UP EX CONTROLLER

91
 ISDN
CHAPTER 4 SETTING UP EX CONTROLLER

1. Click Apply and restart requested service when done.

Interop
Figure 4.97: Interop screen

1. You can change other parameters dependent on market.

Figure 4.98: Interop Configuration screen

2. Click Apply and restart requested service when done.

Services
Figure 4.99: ISDN Services screen

1. Change other parameters dependent on market.

Figure 4.100: Services Configuration screen

2. Click Apply and restart requested service when done.

92
 POTS
CHAPTER 4 SETTING UP EX CONTROLLER

POTS

Config
Figure 4.101: Config screen

1. Set market specific data for Caller Id handling.

Figure 4.102: General Configuration screen

2. Click Apply when done and restart service.

FXS Configuration
Figure 4.103: POTS FXS Configuration screen

1. Set analog phone specific data according to market.

Figure 4.104: FXS Configuration screen

Figure 4.105: Country Customisation screen

2. Click Apply when done and restart service.

SIP

Gateways
Following gateways and port numbers are pre-defined.

93
 SIP
CHAPTER 4 SETTING UP EX CONTROLLER

Figure 4.106: Gateways screen

NOTE:A SIP route must be defined in MX-ONE to handle traffic to and from the ‘trunks_MX-ONE’
gateway.
Figure 4.107: Gateway Configuration screen

Servers
Figure 4.108: Servers screen

1. Enter IP-address to MX-ONE in both Registrar Host and Proxy Host fields.
Figure 4.109: Default Servers screen

2. Change trunk_lines_gw to Yes in the drop-down list for Gateway Specific.

Figure 4.110: Registrar Servers screen

3. Enter IP-address of MX-ONE in the Proxy Host field.

4. Enter IP-address of the gateway in the Outbound Proxy Host.
Figure 4.111: Proxy Servers screen

5. Enter the IP-address of the gateway as Alternate Destination for MX1_analog_ext.

6. Enter the IP-address of MX-ONE as Alternate Destination for trunks_mx-one.

94
 SIP
CHAPTER 4 SETTING UP EX CONTROLLER

Figure 4.112: Keep Alive Destination screen

7. Click Apply when done and restart service.

Registrations
Figure 4.113: Registrations screen

1. Enter the extension numbers for the analog extensions.

Figure 4.114: Endpoints Registration screen

2. Click Apply or Apply and Refresh when done.

95
 SIP
CHAPTER 4 SETTING UP EX CONTROLLER

Authentication
Figure 4.115: SIP Authentication screen

1. If password is required, click for any item.

Figure 4.116: Authentication screen

2. Indicate for which Endpoint and Criteria changes are applicable.

3. Enter the Auth Code, in the Password field.
4. Disable Validate Realm.
Figure 4.117: Validate Realm screen

5. Click Apply or Apply and Refresh Registration when done and restart service. The result after
‘Registration’ and ‘Authentication’ should be like as follows.

96
 SIP
CHAPTER 4 SETTING UP EX CONTROLLER

Figure 4.118: Endpoints Registration screen

Transport
Figure 4.119: Transport screen

1. Enable UDP if required.

Figure 4.120: Protocol Configuration screen

2. Click Apply when done and restart service.

Misc
Figure 4.121: Misc screen

1. Enter the IP-address of MX-ONE in the SIP Domain Override filed for trunk_lines_gw.
Figure 4.122: Gateway Configuration screen

2. Click Apply when done and restart service.

97
 MEDIA
CHAPTER 4 SETTING UP EX CONTROLLER

Media

Codecs
Figure 4.123: Codecs screen

1. Change Codecs according to preference.

Figure 4.124: Changing Codecs

2. Click Apply when done and restart service.

98
 CALL ROUTER
CHAPTER 4 SETTING UP EX CONTROLLER

Call Router

Route Config
Figure 4.125: Route Config screen

1. Click for index 1. This is used if the received B-number contains a full number. That is, more digits

than the pure DID numbers.

Figure 4.126: Routes screen

2. In the Transformations field add a name for a transformation rule.

Figure 4.127: Configure Route screen

3. Click Save.

4. Click in the first Call Property Transformation and enter the same name as above.

5. Use Called E164 for both Criteria Based On and Transformation Applies To fields.

99
 CALL ROUTER
CHAPTER 4 SETTING UP EX CONTROLLER

Figure 4.128: Configure Transformation screen

6. Click Save or Save and Insert Rule.

7. Click in the second Call Property Transformation and enter the same name as above.

8. Use Called E.164 for both Criteria Based On and Transformation Applies To fields.

Figure 4.129: Configure Transformation screen 1

9. Click Save or Save and Insert Rule.

10. Click in the second Call Property Transformation, and enter the same name as above.

11. The Criteria Rule in this case is 443(111..)$ and the transformation rule is ‘\1.
12. This means that if a B-number is received containing 44311104, then the 3 first digits (443) are
removed before the call is sent to MX-ONE for further processing. (111..)$ means that the number
can only be 5 digits starting with 111.
Figure 4.130: Configure Transformation Rule 1

13. Click Save or Save and Insert Rule. Now, the ‘Call Property Transformations’ looks like this as shown
below.

100
 MANAGEMENT
CHAPTER 4 SETTING UP EX CONTROLLER

Figure 4.131: Transformations screen

14. Click Save if the yellow indication on top of the page is ON.

Management
Figure 4.132: Management screen

Backup/Restore
1. Click the Activate unsecure script transfers through web browser link.
Figure 4.133: Image Configuration screen

2. Click Apply and Backup Now.

File
Figure 4.134: File screen

101
 PREREQUISITES
CHAPTER 4 CONFIGURE TLS ON AN EX/GX CONTROLLER

Figure 4.135: Internal files screen

1. Find the previously made backup image.

Figure 4.136: Backup image

2. Download and store on a secure place.

Configure TLS on an EX/GX Controller

This section describes how to configure TLS on an EX/GX controller with a typical scenario for a branch
office with survivability and local presence. TLS ensures secure communication between the MX-ONE
system and the EX and GX controller.

Prerequisites
Before you configure the TLS on the controller, ensure that the following requirements are met:
• The EX/GX controller setup is complete without TLS before you configure TLS on the controller. See
the previous chapters in this document for the setup information.

102
 CREATING TLS CERTIFICATE WITH SAN
CHAPTER 4 CONFIGURE TLS ON AN EX/GX CONTROLLER

• The EX/GX controller setup is fully loaded and the virtual machine on which MX-ONE has been setup
is switched on.
• The FXS extensions are registered. You can view the registration status in the path SIP > Registra-
tions.
• The FXS extensions need to be in the SBC registration cache. You can view in the path SBC > Regis-
tration.
• The TLS certificate authority is generated and is available in the path
/etc/opt/eri_sn/certs/root with:
– Certificate authority file: /etc/opt/eri_sn/certs/root/CA.pem
– Private key: /etc/opt/eri_sn/certs/root/private_key.pem

Creating TLS Certificate with SAN

This section describes how to create a TLS certificate with Subject Alternative Name (SAN). SAN exten-
sion of the certificate specifies additional host names so that more than one host can use the same copy
of a single certificate. This is required because the traffic between FXS ports and the SBC uses the loop-
back 127.0.0.1 address.

Connecting CA to the MX-ONE Server

To connect Certificate Authority (CA) to the MX-ONE server:
1. Log into the SSH client, such as Putty.
2. Connect to the MX-ONE server using the administrator credentials:

103
 CREATING TLS CERTIFICATE WITH SAN
CHAPTER 4 CONFIGURE TLS ON AN EX/GX CONTROLLER

MX-ONE Server - SSH

Verifying the CA File

Using the command line, verify that the certificate authority file is valid and contains the required Issuer:
openssl x509 -in /etc/opt/eri_sn/certs/root/CA.pem -text| grep Issuer
Issuer: CN=MXOneEnterpriseCA, C=SG, O=Root Certificate, OU=MX-ONE/emailAd-
[email protected]

104
 CREATING TLS CERTIFICATE WITH SAN
CHAPTER 4 CONFIGURE TLS ON AN EX/GX CONTROLLER

Generating the Unit Certificate with SAN

For the TLS to be enabled on different interfaces you must generate a unit certificate with SAN. For
example:
• Uplink: 10.211.162.127
• LAN1: 192.168.0.10 (default IP)
• Loopback: 127.0.0.1 (IP to connect FXS and PSTN ports to the internal SBC)

The certificate must be generated on the MX-ONE server using the following procedure:
1. Create a directory for the unit certificates.
mkdir -p /etc/opt/eri_sn/certs/units
cd /etc/opt/eri_sn/certs/units
2. Create a configuration file for the uplink (10.211.162.127.cnf) to provide SAN options. Replace the
uplink IP (10.211.162.127) with the IP address of the EX and GX controller.
cat << EOF > 10.211.162.127.cnf
[req]
distinguished_name = req_distinguished_name
req_extensions = v3_req
prompt = no

[req_distinguished_name]
CN = 10.211.162.127

[v3_req]
basicConstraints = CA:false
keyUsage = digitalSignature, keyEncipherment, dataEncipherment
extendedKeyUsage = serverAuth, clientAuth
subjectAltName = @alt_names

[alt_names]
DNS.1 = 192.168.0.10
DNS.2 = 127.0.0.1
DNS.3 = 10.211.162.127
IP.1 = 192.168.0.10
IP.2 = 127.0.0.1
IP.3 = 10.211.162.127
EOF
3. Generate a Private Key for the EX and GX controller unit. The first command will generate a key with
password, the second one will convert the key so it requires no password (required by the following
steps):
openssl genrsa -aes256 -out 10.211.162.127.key.protected 2048
openssl rsa -in 10.211.162.127.key.protected -out 10.211.162.127.key
4. Generate a CSR for the Unit.
openssl req -new -key 10.211.162.127.key -out 10.211.162.127.csr -sha256
-config 10.211.162.127.cnf
5. Verify the CSR:
openssl req -text -noout -verify -in 10.211.162.127.csr
6. Sign the CSR and generate a new certificate:

105
 CONFIGURING THE EX/GX FOR TLS
CHAPTER 4 CONFIGURE TLS ON AN EX/GX CONTROLLER

openssl x509 -req -sha256 -days 3652 -in 10.211.162.127.csr -CA

../root/CA.pem -CAkey ../root/private_key.pem -CAserial ../root/CA.srl
-CAcreateserial -out 10.211.162.127.crt -extfile 10.211.162.127.cnf
-extensions v3_req
7. Verify the uplink certificate (10.211.162.127.crt):
openssl x509 -in 10.211.162.127.crt -text
8. Create the uplink .pem file.
cat 10.211.162.127.crt 10.211.162.127.key > 10.211.162.127.pem
9. Generate a Private Key for the EX and GX controller unit. The first command will generate a key with
password, the second one will convert the key so it requires no password (required by the following
steps):
openssl genrsa -aes256 -out 10.211.162.127.key.protected 2048
openssl rsa -in 10.211.162.127.key.protected -out 10.211.162.127.key
10. Generate a CSR for the Unit.
openssl req -new -key 10.211.162.127.key -out 10.211.162.127.csr -sha256
-config 10.211.162.127.cnf
11. Verify the CSR:
openssl req -text -noout -verify -in 10.211.162.127.csr
12. Sign the CSR and generate a new certificate:
openssl x509 -req -sha256 -days 3652 -in 10.211.162.127.csr -CA
../root/CA.pem -CAkey ../root/private_key.pem -CAserial ../root/CA.srl
-CAcreateserial -out 10.211.162.127.crt -extfile 10.211.162.127.cnf
-extensions v3_req
13. Verify the uplink certificate (10.211.162.127.crt):
openssl x509 -in 10.211.162.127.crt -text
14. Create the uplink .pem file.
cat 10.211.162.127.crt 10.211.162.127.key > 10.211.162.127.pem

Copying the Files on PC

Using a file transfer software, copy the following files from the MX-ONE to your PC:
• Unit Certificate: /etc/opt/eri_sn/certs/units/10.211.162.127.pem
• Root Certificate: /etc/opt/eri_sn/certs/root/CA.pem

Configuring the EX/GX for TLS

The procedures described in this section shows how to configure TLS in an EX/GX controller to establish
a secure connection with MX-ONE system.

106
 CONFIGURING THE EX/GX FOR TLS
CHAPTER 4 CONFIGURE TLS ON AN EX/GX CONTROLLER

Login to the EX/GX Controller

Open a Web browser, log in to the EX/GX controller by using the default IP address or the previously
configured uplink IP address. You can either log in as a public user (with no password) or an administrator
using default credentials.

Installing Unit Certificates

1. In the EX/GX controller user interface, navigate to Management > Certificates.

2. Under Certificate Import Through Web browser.

a. Choose Host and click Choose.
b. Select the appropriate file (.pem file) on your PC and then click Import.

3. Under Certificate Import Through Web browser.

a. Choose Other and click Choose.
b. Select the appropriate file (.pem file) on your PC and then click Import.

107
 CONFIGURING THE EX/GX FOR TLS
CHAPTER 4 CONFIGURE TLS ON AN EX/GX CONTROLLER

4. Verify that the certificates have been installed:

5. Restart required services and log in to the EX/GX controller user interface again.

Configuring the Secure SIP ports

By default, the EX/GX controllers only listen to the non-secure SIP ports.
1. Navigate to SIP > Gateways in the EX/GX controller interface.

2. For each SIP Gateway, add a secure port (Port +1).

3. Click Apply and restart the services.

Setting the TLS version, Cipher Suite, and Certificate Validation Level
For SIP gateways on the EX/GX to communicate with the SBC service, configure the TLS version to 1.2
and the Cipher Suite to CS3.
NOTE: It is recommended to disable the certificate validation until the setup is complete.
1. Navigate to Management > Configuration Scripts and click Execute.
2. Select Activate unsecure script transfers and execution through web browser.
3. In Execute inline script, copy and paste the following:

108
 CONFIGURING THE EX/GX FOR TLS
CHAPTER 4 CONFIGURE TLS ON AN EX/GX CONTROLLER

SipEp.TransportTlsVersion=TLSv1_2
SipEp.TransportTlsCipherSuite=CS3
SipEp.InteropTlsCertificateValidation=NoValidation
Sbc.CertificateValidation=NoValidation
Scm.RestartRequiredServices

4. Click Execute. It takes approximately 30 seconds for the services to restart.

Enabling TLS on the SBC Service

To enable TLS on SBC:
1. Navigate to SBC > Configuration.

2. In Call Agent Configuration, edit trunk_lines_ca by clicking on the Edit icon next to it.

3. Set Force Transport as Tls and click Save.

4. Repeat the above steps for local_users_ca and MX-ONE_LIM1 call agents.

109
 CONFIGURING THE EX/GX FOR TLS
CHAPTER 4 CONFIGURE TLS ON AN EX/GX CONTROLLER

5. In Signaling Interface Configuration, edit loop_sand uplink_sand set Allowed Transports to

TlsOnly and Tls Mode to Both and click Apply.

6. Restart the required services. It takes about 30 seconds for the SBC service to restart.
7. Clear cache registration by navigating to SBC > Registration.

Enabling TLS between SIP Gateways and SBC

To enable TLS between SIP Gateways and SBC:
1. Navigate to SIP > Transport.

2. Configure the general configuration details as shown in the above figure and click Apply.
3. Restart the required services. It takes about 30 seconds for the service to restart.

4. Navigate to SIP > Registrations.

5. Validate if endpoints are registered the agent MX1_analog_ext.

110
 CONFIGURING THE EX/GX FOR TLS
CHAPTER 4 KNOWN LIMITATIONS

6. Navigate to SBC > Registration, validate all endpoints are registered using TLS.

7. Test a call between endpoints. For example 32100 to 32101.

Enabling SRTP on EX/GX Controller

To enable SRTP on the EX/GX controller:
1. Navigate to Media > Security.
2. Under Select Endpoint, choose Secure.
3. Select Mode as, Secure.
4. Select Key Management Protocol as, SDES.
5. Select Encryption as, AES_CM_128.
6. Select Yes for the T.38 setting.

Enabling Certificate Validation

After the EX/GX controller with TLS setup is complete, you can enable certificate validation:
1. Navigate to Management > Configuration Scripts > Execute and select Activate unsecure script
transfers and execution through web browser.
2. In Execute Inline Script, copy and paste the following:
SipEp.InteropTlsCertificateValidation=HostName
bc.CertificateValidation=HostName
Sbc.ResetRegistrationCache
Scm.RestartRequiredServices
3. Click Execute.
4. Navigate SIP > Registrations.

5. Validate that the endpoints are registered to call agent MX1_analog_ext.

Known Limitations
Below are some known limitations when using the EX-Controller or GX-Gateway:

111
 CONFIGURING THE EX/GX FOR TLS
CHAPTER 4 KNOWN LIMITATIONS

• When MX-ONE is installed as a virtual machine in the EX-Controller, Provisioning Manger is not
allowed to be installed.
• When EX-Controller is used in a multi-server configuration the EX-controller can never be the master
server.
• Maximum 5 servers can exist in a multi-server configuration, where at least one of the servers is an
EX-controller.
• When deploying a MX-ONE as a virtual machine the maximum amount of RAM is 7168 Mbytes.

112
 SCOPE
CHAPTER 5 INTRODUCTION

Integration of MiVoice MX-ONE

with Microsoft® Lync Server™
2013 – Remote Call Control
Introduction
MiVoice MX-ONE, a complete IP-based communications system, has evolved from a voice centric
system into a true multimedia communication system that can route and provide services to media
sessions like video, instant messaging etc. It is the core component of the MX-ONE solution, which
provides the necessary applications to offer true mobility and Unified Communications and Collaboration
(UCC). MX-ONE (TS) is based on an open software and hardware environment, using standard servers
with a LINUX SUSE operating system. MX-ONE Service Node focuses on enhanced SIP implementa-
tions to target our strategy regarding openness, cloud computing and video support. An example of
MX-ONE openness is the fact that it can interwork with third party UC products using standards-based
protocols, such as SIP and CSTA III (XML).
As part of this standards-based approach and in order to offer our customers a choice, we have worked
together with Microsoft to ensure that MX-ONE can be integrated with the latest Microsoft Unified
Communications products. MX-ONE is fully certified by the Microsoft Partner Program since Version 4.1
with Lync Server 2010 (Direct SIP integration) as well as MX-ONE 5.0 SP3 HF2 with Lync 2013 (Direct
SIP integration) in order to ensure that customers have seamless experiences with setup, support, and
use of MX-ONE with Microsoft Unified Communications software.
In MX-ONE 5.0 SP1, TR-87 support for CSTA III (Computer Supported Telecommunications Applications
Version 3) was added to allow a third party application to control an MX-ONE device via CSTA and SIP
messages. This service can be used, for example, to connect MX-ONE and Microsoft Lync Server via a
function called Remote Call Control.
Mitel has performed an internal integration validation between MX-ONE 6.0 and Lync Server 2013 via
Remote Call Control, where several tests were executed to assure the compatibility between the prod-
ucts.

Scope
The intent of this guide is to describe the setup tasks to integrate MiVoice MX-ONE and Microsoft Lync
Server 2013 for Remote Call Control.
For more details regarding components of this integration, we refer to the relevant MX-ONE CPI docu-
mentation or, please, go to the Microsoft Lync Server 2013 product website.

113
 MIVOICE MX-ONE
CHAPTER 5 SOLUTION DESCRIPTION

Note! Always check the latest products documentation.

Solution Description
Integration of MX-ONE 6.0 with Microsoft Lync Server 2013 for Remote Call Control as a complementary
solution, provides users enabled for remote call control to use Lync 2013 client to control calls on their
MX-ONE phones.

MiVoice MX-ONE
MiVoice MX-ONE has a built-in CSTA III server that is an interface that other applications can use to
remotely control a phone. Examples of operations that can be performed with CSTA Phase III are: make
call, answer call, dial a number and terminate a call.
MX-ONE 6.0 supports CSTA method that is based on European Computer Manufacturers Association
(ECMA) Technical Report-87 (TR-87), called Using CSTA for SIP Phone User Agents (uaCSTA).
MX-ONE implements a subset of the capabilities and methods proposed in TR-87 specification.
In TR-87 (Using CSTA for SIP Phone User Agents (uaCSTA)):
SIP is used to establish a CSTA application session
CSTA service request and response messages are transported over SIP
CSTA monitor is started and CSTA events are transported over SIP

Microsoft Lync Server 2013

Microsoft Lync Server 2013 offers Remote Call Control (RCC) support that allows users to remotely
control phones connected to a call manager, such as MX-ONE. It gives Lync 2013 client users the ability
to make or receive calls on their fixed or mobile phone instead of a computer.

Integration
CSTA III (XML) is required to provide the integration between MX-ONE and Lync Server for Remote Call
Control as shown in the figure below.
The telephony feature commands are sent from the Lync 2013 client through the Microsoft Lync Server
2013 to the internal MX-ONE CSTA server as CSTA III messages over SIP, so called user agent CSTA
(uaCSTA). The internal MX-ONE CSTA server analyzes the requests and maps them to the corre-
sponding CSTA commands towards MX-ONE, which will then carry out the requests.

114
 INTEGRATION
CHAPTER 5 REQUIREMENTS AND SETUP

RCC user

r
ve
I II o 8 7) SI P
TA R - MX-ONE
C S P (T device
SI

CSTA III over SIP (TR-87)

Lync Server
2013 – MiVoice MX-ONE 6.0
Standard
Edition

Figure 1 - Integration via Remote Call Control (RCC) between MX-ONE and Lync Server 2013
With Microsoft Lync Server 2013 integration, it is possible from Lync 2013 client (Remote Call Control
Only) to manage calls and talk using any fixed and remote extensions within the MX-ONE.
The features that a Lync 2013 client can manage when integrate with MX-ONE using RCC are:
Make an outgoing call
Answer an incoming call
Transfer a call to another user (monitored transfer with current conversations)
Single step transfer
Forward an incoming call to an internal number (internal and private network extensions)
Forward an incoming call to an external number
Redirect an incoming call
Place calls on hold
Alternate (toggle) between multiple concurrent calls
Answer a second call while already in a call.
Dial dual-tone multi-frequency (DTMF) digits

Requirements and Setup

MX-ONE and Microsoft Lync needs to be configured in different sip domains. Mitel recommendation is
that MX-ONE is a sub-domain of the Lync domain.
For example, Lync runs on the domain: domain.com and MX-ONE runs on the domain:
mx-one.domain.com.

115
 MIVOICE MX-ONE REQUIREMENTS
CHAPTER 5 REQUIREMENTS AND SETUP

MIVOICE MX-ONE Requirements

Software and licenses required for Microsoft Remote Call Control integration:
MiVoice MX-ONE Service Node 6.0 or later
MX-ONE licenses for:
CSTA III

Note! Multi terminal extensions cannot be monitored via CSTA and therefore it does not work
in the Remote Call Control scenario.

Microsoft Lync Server 2013 Requirements

The Microsoft infrastructure (AD, DNS, CA, etc) needs to be in place, including all licenses required.
This guide does not cover the Lync Server 2013 installation. Our recommendation is that the Microsoft
infrastructure shall be installed by a trained Microsoft engineer.
Before to start Microsoft Lync Server 2013 for RCC setup, read the following document:
Microsoft Lync Server 2013, Deploying Remote Call Control
http://technet.microsoft.com/en-us/library/gg558664.aspx

Note! This Microsoft documentation is used in conjunction with this guide.

MX-ONE was validated with Microsoft Lync 2013 Remote Call Control with only one Lync Front End
server.
Microsoft Lync 2013 requires load balancer when more than one Front End is used. Please note that this
setup was not validated with MX-ONE.

Note! The latest Lync Client (Lync 2013 update: April 2014) needs to be installed in the end
user computers, please see that article below.

http://support.microsoft.com/kb/2880474

Integration Setup - TCP

The setup used in this guide is based on the following scenario:
One Microsoft Lync Server - Standard Edition connected with one MiVoice MX-ONE 6.0.

116
 INTEGRATION SETUP - TCP
CHAPTER 5 REQUIREMENTS AND SETUP

Alice user Bob user

27001 27010 27002

CSTA III PSTN / PLMN

(TR87 uaCSTA) ISDN or SIP Route
or SIP operator

Lync Server
MiVoice MX-ONE 6.0
IP: 192.168 .222 .197
IP: 192.168.222.156
FQDN: lync-enter.domain .com
FQDN: mx-one -156.mx-one.domain .com

Figure 2 - Integration setup

Note! Mitel recommends that complex scenarios shall be validated in the partner labs prior to
customer deployment.

MiVoice MX-ONE Setup - TCP

The following shall be configured:
CSTA server needs to be initiated
Creating CSTA Server

CSTA III Setting:

csta--initiate--lim1 --csta-serv00000010

For more about CSTA III, see MX-ONE CPI documentation.

Microsoft Lync Server 2013 Setup – TCP

The following setup is based in the Microsoft Lync Server 2013 documentation, Deploying Remote Call
Control, for more about commands syntaxes check:
http://technet.microsoft.com/en-us/library/gg558664.aspx
The following shall be configured:
Configure a Static Route for Remote Call Control
Configure a Trusted Application Entry for Remote Call Control
Configure Static Route for Remote Call Control
The following commands shall be executed in the Lync Server Management Shell to configure Remote
Call Control.

Route for Remote Call ControlSetup, port 5060 (TCP):

$TCPRoute= New-CsStaticRoute-TCPRoute-Destination 192.168.222.156 -Port 5062
-MatchUrimx-one.domain.com

117
 INTEGRATION SETUP - TCP
CHAPTER 5 REQUIREMENTS AND SETUP

Set-CsStaticRoutingConfiguration-Route @{Add=$TCPRoute} -Identity Global

To verify the setup use the command:
Get-CsStaticRoutingConfiguration

Configure a Trusted Application Pool Entry for Remote Call Control

To create a Trusted Application Pool use the command:

New-CsTrustedApplicationpool-Identity 192.168.222.156 -Registrar lync-enter.domain.com –Site 1
–TreatAsAuthenticated$True –ThrottleAsServer$True
To verify the setup use the command:
Get-CsTrustedApplicationpool

Configure a Trusted Application Entry for Remote Call Control

To setup the trusted application use the command::

New-CsTrustedApplication-ApplicationIDRCC -TrustedApplicationPoolFqdn192.168.222.156 -Port
5062 -EnableTcp
To verify the setup use the command:
Get-CsTrustedApplication

Publish the topology

To implement the changes in the Lync , publish the topology

Enable-CsTopology

Define a SIP/CSTA Gateway IP Address

In this example TCP is used, then the SIP/CSTA gateway IP address needs to be defined. Follow the
instruction in the session “Define a SIP/CSTA Gateway IP Address” from Microsoft documentation:
http://technet.microsoft.com/en-us/library/gg602125.aspx.
When the setup is done, the Topology Builder screen should be similar to figure below.

118
 ENABLE LYNC USERS FOR REMOTE CALL CONTROL
CHAPTER 5 REQUIREMENTS AND SETUP

Figure 3 - Lync Server 2013 Topology Builder

Enable Lync Users for Remote Call Control

Configure a user for remote call control by using Lync Server Control Panel.
Under Telephony, select Remote Call Control Only. Please, note that the option “Remote Call Control” is
not supported by MX-ONE.
The following needs to be configured under Line URI and Line Server URI.

Enable Lync Users for Remote Call Control:

Line URI:tel:phonenumber, exampletel:27000
Line Server URI:sip:tel@MatchUri, for example: sip:[email protected]

119
 LYNC 2013 CLIENT FEATURES
CHAPTER 5 HOW TO VERIFY THE SETUP

Figure 4 - RCC only new user configuration example

How to Verify the Setup

After completing the setup, the integration can be verified in the following way:

Lync 2013 Client Features

Using a Lync 2013 client sign-in a RCC user.
If the configuration was done properly the user will be signed in without any error, see the figure below.

120
 LYNC 2013 CLIENT FEATURES
CHAPTER 5 HOW TO VERIFY THE SETUP

If there is small icon in the lower right side of the Lync 2013 client, showing a phone with an error, check
the setup, because the CSTA monitoring could not be established.

Use the MiVoice MX-ONE command “csta -p --lim all --devices” to check the devices that are monitored.

121
 MAKE AN OUTGOING CALL USING THE LYNC 2013 CLIENT
CHAPTER 5 HOW TO VERIFY THE SETUP

In the use cases below two Lync clients were used and three MX-ONE extensions.
1. Alice.RCC controls the extension 27001, which is a SIP extension in MX-ONE.
2. Bob.RCC controls the extension 27010, which is a SIP extension in MX-ONE.

3. 27000 and 27002 are SIP extensions in MX-ONE.

4. 33350202 and 33350102 are the PSTN phones.

Make an Outgoing Call Using the Lync 2013 Client

From extension A use the Lync client (RCC) to dial extension B, pick up your handset as soon as you
hear the ring back tone, wait the extension B answer, check if there is speech.

Answer an Incoming Call

From another extension dial to RCC user, answer it and check if there is speech.

Transfer a Call Between Current Conversations (Monitored

Transfer)
In this scenario A (Alice.RCC - extension 27001) calls B (Bob.RCC - extension 27010), A puts B on hold
and then calls extension C (27002). After C answers, A transfers the call between B and C.
We assume you have answered a call with extension B (27010) from the Lync client (RCC

122
 TRANSFER A CALL BETWEEN CURRENT CONVERSATIONS (MONITORED TRANSFER)
CHAPTER 5 HOW TO VERIFY THE SETUP

Using the client, put extension B on hold and make a second call to extension C (27002), and wait until
the extension C answers.

Once speech is established, initiate the transfer of extension B (Bob RCC) using the Current Conversa-
tions option as shown below.

123
 SINGLE STEP TRANSFER
CHAPTER 5 HOW TO VERIFY THE SETUP

Then, check if the call is correctly transferred.

Then, check if the call is correctly transferred.

Single Step Transfer

In this scenario A (Alice.RCC - extension 27001) is talking with C (extension 27002), A transfer C directly
to extension B (Bob.RCC - extension 27010).
We assume you have answered a call with extension C (27002).

124
 SINGLE STEP TRANSFER
CHAPTER 5 HOW TO VERIFY THE SETUP

A does single-step transfer from extension C (27002) to B (Bob.RCC - extension 27010).

Then, check if the call is correctly transferred.

125
 FORWARD AN INCOMING CALL
CHAPTER 5 HOW TO VERIFY THE SETUP

Forward an Incoming Call

Select a predefined or a new number (internal, network extension or external) and click ok.

Check if Lync client is showing that the forwarding is on.

126
 PLACE CALLS ON HOLD
CHAPTER 5 HOW TO VERIFY THE SETUP

Place Calls on Hold

When in speech, press the hold button to hold a call.

Click on Resume Call to return to the call.

127
 ALTERNATE BETWEEN MULTIPLE CONCURRENT CALLS
CHAPTER 5 HOW TO VERIFY THE SETUP

Alternate Between Multiple Concurrent Calls

When connected with two calls, press the hold button to hold a call and click on Resume Call to return to

the first one.

Answer a Second Call While Already in a Call (call waiting)

When a second call is alerting, click on Accept Call to answer it.

128
 DIAL DUAL-TONE MULTI-FREQUENCY (DTMF) DIGITS
CHAPTER 5 HOW TO VERIFY THE SETUP

You can alternate between the calls.

Dial Dual-Tone Multi-Frequency (DTMF) Digits

In an established call, click on the keypad and enter DTMF digits.

Presence
In order to verify presence, establish a call using Lync client (RCC) as below.

129
 PRESENCE
CHAPTER 5 HOW TO VERIFY THE SETUP

From extension A use the Lync client (RCC) to dial extension B, pick up your handset as soon as you

hear the ring back tone, wait until the extension B answers, check if there is speech.

130
 PRESENCE
CHAPTER 5 HOW TO VERIFY THE SETUP

From another Lync client, for example Bob, RCC that is monitoring Alice RCC, check if the presence
status is now “In a Call”.

Disconnect the call from extension A (Alice RCC) and check if the Alice RCC presence status goes to
Available in the Bob RCC.

131
 PRESENCE
CHAPTER 5 LIMITATIONS

Limitations
The integration supports Lync 2013 clients configured with “Remote Call Control only” option. The option
“Remote Call Control” is not supported.
The secure transport mechanism using TLS is not supported in MX-ONE 6.x.
The features listed below are not supported in this integration, when initiated by the Lync client:
Do not disturb (it is not supported by Lync client)

Note! Although these features may not be possible from the client, they may be invoked
directly on the terminal instead.

Good to Know
MX-ONE and Lync Server cannot be part of the same domain.
Latest Lync client needs to be installed.
DNS needs to be properly configured.

132
 PRESENCE
CHAPTER 5 REVISION HISTORY

Conference can be invoked via Lync client using MX-ONE procedure (normally dialing 3). However, the
Lync client will merge all other screens with the first one and that will be presented until the last member
disconnects.

Revision History

Document Version Comment Date

Rev. A First release 2014-05-09
Rev. B Rebranding 2015-05-10
Rev. B1 Some further rebranding corrections done. 2016-03-17
Rev. B2 Minor changes done. 2016-10-10

133
CHAPTER 6 GENERAL

MiVoice Border Gateway MBG

General
This document describes how to configure a single standalone MiVoice Border Gateway (MBG) Release
11.0 server to support Mitel 6900/6800 SIP Terminals as Tele­worker devices for MX-ONE.
This document complements MX-ONE document “Mitel 6700i and 6800i SIP Terminals for MX-ONE” and
provides instructions how to setup MBG as an Ingate replacement. The principle used here is to configure
MBG to have secure communication on the outside towards the home worker terminals and unsecured
communication on the inside towards MX-ONE. The proposed solution has the same limitations as the
existing Ingate deployment.
Instructions in this document are specific to the above configuration and must NOT be used in
any other deployments. For example, MiCollab 7.1 with MBG and MiCollab clients with MX-ONE.

Application Requirements
You must meet the minimum software level requirements for each application listed below so that the
applications function correctly with this Release.

Application Recommended Software Comments

Level
Mitel Standard Linux (MSL) 11.0 Refer to the MBG Installation
and Maintenance Guide 11.0
located in the Doc Center on the
MiAccess Portal.
MX-ONE 6.3 MX-ONE version 6.0 SP2 HF3
was tested in the Kanata lab, so
this version, or later, could be
used, but 6.3 is recommended.
6900 5.0.0 Release 5.0 SIP extensions
68xxi 4.2.0.181 Release 4.2
Release 4.2 SP1
recommended.
MBG 11.0 Release 11.0 and up
recommended.

134
 LICENSING
CHAPTER 6 INSTALLATION NOTES

Installation Notes
The principle used here is to configure MBG to have secure communication on the outside towards the
home worker terminals and insecure communication on the inside towards MX-ONE.

Licensing
The only licensing required is a MiVoice Border Gateway base kit (physical or virtual) and Teleworker
licenses (1 per 68xxi device + a few floater licenses).

Installing Release 11.0 on a Standalone Physical Server

1. Install the latest Mitel Standard Linux 10.4 64 bits release software version.
2. Install Release 9.2 via MSL’s server-manager Blades panel after syncing with the Mitel Application
Management Center (AMC); or,
3. Obtain a copy of the latest MiVoice Border Gateway Rel 11.0 software and burn it onto a CD. After
inserting the CD in the CD-ROM/DVD-ROM drive, upgrade via MSL’s server-manager Blades panel.
NOTE: Your CD burning software must be capable of burning ISO images.

Installing Release 11.0 in a VMware Environment

Virtual deployment should deploy the latest released MBG 11.0 ova and then upgrade to the latest avail-
able blade of that stream.

Firewall Configuration
If MBG is deployed in a demilitarized zone, the following ports need to be opened (above ports needed
for communication with the AMC).

• TCP port 5061 between the Internet and MBG for SIP TLS
• TCP port 5060 between MBG and MX-ONE
• TCP port 22223 between the Internet and MBG for SIP XML
• TCP port 22222 between MBG and MX-ONE for SIP XML
• TCP port 4431 between the Internet and MBG for Configuration Server Access (Optional)
• TCP port 80 between MBG and the Configuration Server

• UDP port 20000-31000 between the Internet and MBG and between MBG and the LAN for voice
• TCP port 22 between LAN and MBG for secure shell access

135
 MSL CONFIGURATION
CHAPTER 6 INSTALLATION NOTES

• UDP port 53 between MBG and the LAN for DNS resolution to a Corporate DNS server
NOTE: Do not enable TCP port 5060 or UDP port 5060 between the Internet and MBG.

MSL Configuration
1. Configure your MSL server to use a Corporate DNS server that can resolve any FQDN associated
with MX-ONE.
2. Configure your MSL server to allow Remote Access for secure shell from a local network. This access
will be needed to run a special setup script.
3. Navigate to Remote Access under MSL Server Manager.

4. Select “Allow access only from trusted and remote management networks” to setup secure shell
access.
5. Select “Yes” for administrative command line access over secure shell.
6. Select “Yes” to allow secure shell access using standard passwords.

MBG Configuration
From a new installation of Release 11.0, access the MiVoice Border Gateway User Interface from MSL
server-manager and perform the following steps:
1. Go to System Configuration > Network Profile.
a. Select Profile and Apply.
2. Go to System Configuration > Settings.
a. Under SIP options, increase the Set-side registration expiry time to 360 from the default of 240.
b. Enable SIP support for TCP/TLS and TCP.
c. Change Codec support to Unrestricted.
d. Change Set-side RTP security to Require (to enforce SRTP between the phone and MBG).
NOTE: Optionally, you can disable support for all protocols under Minet Support.

3. Service Configuration > ICPs

a. Add your MX-ONE system as type MiVoice MX-ONE with SIP capabilities as UDP, TCP.
b. Configure MX-ONE support.
c. Check Link to the ICP and Enable.
d. Configure the XML listen port as 22223 and check TLS.
e. Configure the XML destination port as 22222 and uncheck TLS.
f. Configure the configuration server listen port as 4431 and check TLS.
g. Configure the configuration server port as 80 and uncheck TLS.
h. Configure the configuration server address.
NOTE: Only provide access to the configuration server if ALL the files in all the directories are
encrypted with anacrypt. If not, enter a bogus IP address to not expose the internal configura-
tion server to the Internet. The InGate solution has the same exposure.
i. Click Save.

136
 MBG CONFIGURATION
CHAPTER 6 INSTALLATION NOTES

4. Do not start MBG yet.

5. Setup MBG with mutual TLS for SIP using configuration script.
6. Connect to the system via ssh (ex: using putty) and login as root.
7. Run the configuration script specifying the MBG Public IP address (i.e the address the Teleworker
68xx phones will connect to) and the MBG local or LAN IP address.
Optionally, you can use the script to modify an existing mitel.cfg or use MBG as a TFTP server for the
phones.
To view all options available, run the configuration script without arguments.
[root@mysystem ~]# /usr/sbin/configure_68xx_mbg_support.sh
Example #1: MBG Public IP is 1.1.1.1 and MBG local IP is 192.168.100.10
[root@mysystem ~]# /usr/sbin/configure_68xx_mbg_support.sh --mbg_wan_ip ip_ad­dress --mb-
g_lan_ip ip_address --generate_certificate
[root@mysystem ~]# /usr/sbin/configure_68xx_mbg_support.sh --mbg_wan_ip 1.1.1.1 --mbg_lan_ip
192.168.100.10 --generate_certificate
mbg_wan_ip=1.1.1.1
mbg_lan_ip=192.168.100.10
configure_tftp=false
generate_certificate=true
force=false

creating /root/aastra_tftp, output files will be placed there.

configuring mbg certificate with ip address: 1.1.1.1
Generating a 2048 bit RSA private key
.............................................................................................................+++
.......................................................+++
writing new private key to '/root/aastra_tftp/mbg_mxone_key.pem'
-----
writing RSA key
details:
InsertCertificateIntoChain
Subject: /CN=1.1.1.1
Issuer: /CN=1.1.1.1

ReorderCertificateChain:: client certificate found:

Subject: /CN=1.1.1.1
Issuer : /CN=1.1.1.1
ReorderCertificateChain:: root CA certificate found:
Subject: /CN=1.1.1.1
Issuer : /CN=1.1.1.1

VerifyCertificateChain:: m_vrCerts.size()=1 rc=1

certificate and key files for set are /root/aastra_tftp/mbg_mxone_cert.pem and /root/aastra_tftp/mb-
g_mxone_key.pem
done.

137
 MBG CONFIGURATION
CHAPTER 6 INSTALLATION NOTES

Example #2:MBG Public IP is 1.1.1.1, MBG local IP is 192.168.100.10, modify an existing mitel.cfg
(transferred to /root

[root@mysystem ~]# /usr/sbin/configure_68xx_mbg_support.sh --mbg_wan_ip 1.1.1.1 --mbg_lan_ip

192.168.100.10 --generate_certificate --modify_cfg_template mitel.cfg --ntp_server pool.ntp.org
--time_zone_name SE-Stockholm
mbg_wan_ip=1.1.1.1
mbg_lan_ip=192.168.100.10
configure_tftp=true
generate_certificate=true
force=false

will configure tftp directory /root/aastra_tftp to serve up config files

creating /root/aastra_tftp, output files will be placed there.
configuring mbg certificate with ip address: 1.1.1.1
Generating a 2048 bit RSA private key
..................................................................+++
..........+++
writing new private key to '/root/aastra_tftp/mbg_mxone_key.pem'
-----
writing RSA key
details:
InsertCertificateIntoChain
Subject: /CN=1.1.1.1
Issuer : /CN=1.1.1.1

ReorderCertificateChain:: client certificate found:

Subject: /CN=1.1.1.1
Issuer : /CN=1.1.1.1

ReorderCertificateChain:: root CA certificate found:

Subject: /CN=1.1.1.1
Issuer : /CN=1.1.1.1
VerifyCertificateChain:: m_vrCerts.size()=1 rc=1

certificate and key files for set are /root/aastra_tftp/mbg_mxone_cert.pem and /root/mitel_tftp/mb-
g_mxone_key.pem
creating mitel.cfg from template, configured with MBG's CN ip
sip proxy ip
sip proxy port
sip registrar ip
sip registrar port
sip outbound proxy
sip outbound proxy port
tftp server
sips trusted certificates
sips root and intermediate certificates
sips local certificate
sips private key
https validate certificates

138
 PHONE CONFIGURATION
CHAPTER 6 INSTALLATION NOTES

https user certificates

time server disabled
time server
time zone name
sip transport protocol
found URL's pointing to 22222, switching to https and port 22223
appending fixed URLs to config file
done.
8. Return to the MiVoice Border Gateway User Interface and click on Dashboard to Start MBG
9. Confirm that Teleworker 68xx phones have access to the public IP of MBG using the Teleworker
Network Analyzer tool.
10. Download the tool from Administration – File Transfer and install it on a Windows machine that has
network connectivity to the public IP of your system.
11. Launch the application and run a connect test against the public IP.
SIP TLS, Aastra MXL MX-ONE, Voice Traffic (begin) and (end) should return OK.
If any of the above return CLOSED or TIMED OUT, contact your firewall administrator.

Phone Configuration
1. Phone must be staged in the office.
2. Using WinSCP, copy the /root/aastra_tftp/mbg_mxone_cert.pem and /root/aastra_tftp/mbg_mxon-
e_key.pem to a special folder (ex: athome) on your configuration server.
3. Append the settings listed in “Appendix – mitel.cfg Settings” to your mitel.cfg file or used the modified
mitel.cfg also available under /root/aastra_tftp.
If needed, update all other files (ex: <model.cfg>) to use https/22223 instead of http/22222.

Limitations
A list of known limitations shared with the InGate solution.
1. Phones must be staged in the office.
2. Phone firmware must be done in the office as a phone firmware upgrade will remove the certificate
loaded.
3. Access to internal configuration server cannot be limited/controlled/blocked from the outside.
4. 68xxi must have access to a NTP server for certificate validation.
5. Corporate directory access must be setup with port forwarding on MSL (server-gateway configuration)
or the DMZ firewall.
6. If MX-ONE is setup to like lim1.mysystem.com, the MSL server must point to a Corporate DNS to
allow proper DNS resolution.

139
 KNOWN ISSUES
CHAPTER 6 INSTALLATION NOTES

Here is a list of known limitations with MBG

a. Single dedicated MBG.
b. MBG clustering and backup SIP registrar/proxy in the 68xxi configuration files.
c. Using FQDN instead of IP address in the 68xxi configuration files.

Known Issues
None.

Issues Resolved
Here is a list of issues resolved in 9.2.0.22 in conjunction with 68xx 4.2 SP1 firmware and workaround is
not longer required:
1. MN00609195 MBG 11.0: SIP 68xxi/MX-One/SRTP one way audio after “set side” session timer
re-invite (decrypt failure).
2. Conditions: Session timers are configured on TW 68xxi AND greater than 1310 (default in MX-ONE
sample is 1800).
3. Root Cause: 68xxi do NOT increment SDP version but changes SRTP keys in re-invite and MBG
falsely detects the SDP as a duplicate.
4. Workaround: Select a value less than 1200 for session timers in mitel.cfg for TW 68xxi.
5. MN00616730 MBG 11.0: SIP 68xxi/MX-One/SRTP one way audio after “ICP side” session timer
re-invite.
6. Conditions: Session timers are configured on LAN 68xxi AND greater than 1300 AND the codec list
is different between LAN and TW set but 1st selection is the same.
7. Root Cause: Still under investigation.

8. Workaround #1: Same codec selection list on TW 68xxi as LAN 68xxi (MX-ONE sample has G.722,
G711a, G.711u, G.729. Updates are used instead of re-invite.
9. Workaround #2: Disable session timers in mitel.cfg for LAN 68xxi or reduce the value to 1200 or less.

Upgrade Notes
Trials sites that have deployed based on earlier versions of this document, need to run the following
command on their system to ensure that all required files are part of a backup.
[root@mysystem ~]# db tug setprop config backuplist
/etc/tug/tug.ini.certifi­cates.ini,/etc/tug/tugcerts.ini,/etc/tug/ca-bundle.crt,/etc/tug/mbg_mxone.ini

Appendix - Config Script

[root@ ~]# /usr/sbin/configure_68xx_mbg_support.sh

140
 APPENDIX - MITEL.CFG SETTINGS
CHAPTER 6 INSTALLATION NOTES

mbg_wan_ip=
mbg_lan_ip=
configure_tftp=false
generate_certificate=false
force=false
----------
--mbg_lan_ip parameter must be specified
----------
Usage: /usr/sbin/configure_68xx_mbg_support.sh --mbg_wan_ip ip_address --mbg_lan_ip ip_address
[--tftp] [--generate_certificate] [--force] [--modify_cfg_tem­plate aastra_cfg_file_template] [--ntp_server
fqdn/ip] [--time_zone_name aastra_name_string]
--mbg_wan_ip - MBG public address
sets connect to this address and MBG certificate will contain this
--mbg_lan_ip - MBG private address
used for SIP udp and tcp communications with ICP
(udp and tcp are disabled on MBG's public address)
--tftp - configure this MBG to supply configuration files via tftp
--generate_certificate - create a certificate using the value supplied for 'mbg_wan_ip'
--force - override 'certificate already exists' check
--modify_cfg_template - If set, specified file will be modified.
Cfg settings dealing with certs/sip will be adjusted
--ntp_server - If set, specified fqdn will be used for ntp settings.
otherwise 'pool.ntp.org' will be used.
--time_zone_name - If set, specified time zone string will be used for ntp settings.
otherwise 'SE-Stockholm' will be used.

Appendix - mitel.cfg Settings

#------------------------------------------------------------------
# MiVoice Border Gateway (MBG) Teleworker features
# SIP TLS and SRTP between the phone and MBG
# HTTPS used for XML
#------------------------------------------------------------------

# MBG is the SIP proxy and registrar

sip proxy ip:MBGIP
sip proxy port:5061

141
 APPENDIX - MITEL.CFG SETTINGS
CHAPTER 6 INSTALLATION NOTES

sip registrar ip:MBGIP

sip registrar port:5061
sip outbound proxy:MBGIP
sip outbound proxy port:5061 #5061 or 0(which will attempt SRV and as fall back send to 5061 due to
TLS)

# Persistent SIP TLS (requires 'sip outbound proxy')

sips persistent tls:1
sip outbound support:1
sip transport protocol:4 #4-TLS

# Certificates/keys for sip-tls

sips trusted certificates: mbg_mxone_cert.pem
sips root and intermediate certificates: mbg_mxone_cert.pem
sips local certificate: mbg_mxone_cert.pem
sips private key: mbg_mxone_key.pem
https validate certificates: 1
https user certificates: mbg_mxone_cert.pem

# Voice Encryption (SRTP)

sip srtp mode:2

# OPTIONAL – Use MBG's TFTP server

#tftp server:MBGIP

#NTP server must be accessible from the home network

time server disabled: 0
Time server1:<NTP server>

# Action URI must use HTTPS to port 22223

action uri startup:https://$$PROXYURL$$:22223/Startup?user=$$SIPUSERNAME$$
services script: https://$$PROXYURL$$:22223/Services?user=$$SIPUSER­NAME$$&voicemailnr=
#------------------------------------------------------------------
NOTE: Similar changes may be required to <model>.cfg or <mac>.cfg files.

142
Main window 3
Primary scenario, direct connection to all MX-ONE servers in a 4-server MiVoice MX-ONE sys-
tem 10
Secondary scenario, connection by proxy, connection only to one MX-ONE Service Node 11
New Normalization Rule, five digits example 24
EX and GX Controller Gateways 42
Directory Number Profile 44
Route Category Data 47
Login page 49
Host settings - 1 49
Host settings - 2 49
Changing static IP address 50
Changing static DNS server 50
Changing to static SNTP server 50
Setting static time zone 51
Interface 51
Changing Uplink to IpStatic 51
Local firewalls 51
Changing default policy 52
Enter network traffic 52
Call agent - 1 52
Call agent - 2 52
Call agent - 3 53
Parameters screen 53
Configure Call Agent screen 54
Call Agent Rulesets screen 54
Trunk_Lines_ca 56
Trunk_Lines_ca Parameters 56
Peer Host field 57
RURI_HOST Parameter 58
MX-ONE Trunk 58
MX-ONE_TRUNK Parameters 58
Configuration Modified 59
ISDN tab 59
Primary Rate Interface 60
Interface Configuration 61
Interop 63
Interop Configuration screen 63
Services 64
Services Configuration screen 64
Config 65
General Configuration screen 65
FXS Configuration 65
FXS Configuration screen 65
Country Customisation screen 66
Gateways 66
trunks_mx-one 66
Servers 67
Default Servers 67
trunk_lines_gw 67
Outbound Proxy Host field 67
Alternate Destination for trunks_mx-one 68
Registrations 68
Endpoints Registration screen 68
Authentication 69
Authentication Screen 69
Validate Realm field 70
Endpoints Registration Status 70
Transport 70
Protocol Configuration screen 70
Interop 70
SIP URI User Parameter Value field 71
Misc 71
Gateway Configuration field 71
Codecs 72
Changing Codecs 72
Route Config 73
Routes screen 73
Transformations field 73
Configure Transformation 1 Screen 74
Configure Transformation Rule 1 screen 74
Transformations screen 74
Image Configuration screen 75
Internal files screen 76
Backup image 77
Logon screen 78
Host screen 78
Automatic Configuration Interface 78
Default Gateway Configuration 79
DNS Configuration screen 79
SNTP Configuration 79
Time Configuration screen 80
Interfaces screen 80
Network Interface Configuration 80
Local Firewall screen 80
Local Firewall Configuration screen 81
Local Firewall Rules screen 81
SBC Configuration screen 81
Call Agent Configuration screen 81
Routing Rulesets screen 82
Configure Call Agent screen 83
Call Agent Rulesets 83
Configure Call Agent screen 85
Call Agent Rulesets 85
Peer Host field 86
RURI_HOST parameter 86
Call Agent Parameters 87
Call Agent Rulesets 87
Configuration Modified screen 87
ISDN Screen 87
Primary Rate Interface screen 89
Interop screen 92
Interop Configuration screen 92
ISDN Services screen 92
Services Configuration screen 92
Config screen 93
General Configuration screen 93
POTS FXS Configuration screen 93
FXS Configuration screen 93
Country Customisation screen 93
Gateways screen 94
Gateway Configuration screen 94
Servers screen 94
Default Servers screen 94
Registrar Servers screen 94
Proxy Servers screen 94
Keep Alive Destination screen 95
Registrations screen 95
Endpoints Registration screen 95
SIP Authentication screen 96
Authentication screen 96
Validate Realm screen 96
Endpoints Registration screen 97
Transport screen 97
Protocol Configuration screen 97
Misc screen 97
Gateway Configuration screen 97
Codecs screen 98
Changing Codecs 98
Route Config screen 99
Routes screen 99
Configure Route screen 99
Configure Transformation screen 100
Configure Transformation screen 1 100
Configure Transformation Rule 1 100
Transformations screen 101
Management screen 101
Image Configuration screen 101
File screen 101
Internal files screen 102
Backup image 102