MiVoice MX-ONE

Route Data, RO - Operational Directions

Release 7.2
September 24, 2019
 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 2019, Mitel Networks Corporation
All rights reserved
 Contents

Chapter: 1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter: 2 Route Data, RO, Operational Directions . . . . . . . . . . . . . . . . . . 2

Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

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

Chapter: 4 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter: 5 Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Initiate a SIP Route . . . . . . . . . . . . . . . . . . . . . . . . . . 5
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Public SIP Route with Enterprise SBC . . . . . . . . . . . . . . . . . . . . . . 6
Initiate the Route . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Remove a Route . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
E1 - T1 Change . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Print the Route Categories . . . . . . . . . . . . . . . . . . . . .11
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Alter the Route Categories . . . . . . . . . . . . . . . . . . . . .11
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter: 6 Direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Initiate a Direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

49/154 31-ANF 901 14 Uen L 2019-10-18

 Overflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Remove a Direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Print the Direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Chapter: 7 External Destination and Alternative Routing . . . . . . . . . . . . . 20

Remove the Ordinary Route Choice to an External Destination . . . . .20
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Initiate the Ordinary Route Choice to an External Destination . . . . . .23
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
For H.323: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Initiate Alternative Route Choices to an External Destination . . . . . .24
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
For H.323: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Remove an Alternative Route Choice to an External Destination . . . .25
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Initiate Customer Route Choices to an External Destination . . . . . . .25
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Remove Customer Route Choices to an External Destination . . . . . .25
Print External Destination Data and Alternative Routing Data . . . . . .26

Chapter: 8 Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Initiate Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Order of selecting lines . . . . . . . . . . . . . . . . . . . . . . .27
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
H.323 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Remove Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Print Line Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Chapter: 9 Day and Night Service Positions . . . . . . . . . . . . . . . . . . . . . 32

49/154 31-ANF 901 14 Uen L 2019-10-18

 Initiate Day and Night Service Positions . . . . . . . . . . . . . . . . . .32
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Remove Day and Night Service Positions . . . . . . . . . . . . . . . . . .32
Alter Day and Night Service Positions . . . . . . . . . . . . . . . . . . . .32
Print Day and Night Service Positions . . . . . . . . . . . . . . . . . . . .32

Chapter: 10 Call Metering Equipment . . . . . . . . . . . . . . . . . . . . . . . . . 33

Initiation of Call Metering Equipment for External Line . . . . . . . . . .33
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Moving of Call Metering Equipment to Another External Line . . . . . .34
Removal of Call Metering Equipment for an External Line . . . . . . . .34
Printout of Call Metering Equipment Data . . . . . . . . . . . . . . . . .34

Chapter: 11 Central Answering Position in Network with ISDN/H.323 (or SIP Without Notifi-
cation) 35
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Initiate Central Answering Position in a Network . . . . . . . . . . . . .35
Remove a Central Answering Position from a Network . . . . . . . . . .35
Change the Central Answering Position in the Network . . . . . . . . . .36
Print a Central Answer Position in a Network . . . . . . . . . . . . . . .36

Chapter: 12 Customer-Centralized Operator in an ISDN/H.323 Network (or SIP Without Noti-

fication) 37
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Initiate a Customer-Centralized Operator in a Network . . . . . . . . . .37
Remove a Customer-Centralized Operator from a Network . . . . . . .38
Change the Customer-Centralized Operator in the Network . . . . . . .38
Print a Customer-Centralized Operator in a Network . . . . . . . . . . .38

Chapter: 13 Route Optimization (Path Replacement) . . . . . . . . . . . . . . . . 39

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Phase 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Phase 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

Chapter: 14 Customer-Dependent Rerouting Position . . . . . . . . . . . . . . . . 43

49/154 31-ANF 901 14 Uen L 2019-10-18

 Initiate a Customer-Dependent Rerouting Position . . . . . . . . . . . .43
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Remove a Customer-Dependent Rerouting Position . . . . . . . . . . .43
Alter a Customer-Dependent Rerouting Position . . . . . . . . . . . . .43
Print a Customer-Dependent Rerouting Position . . . . . . . . . . . . .43

Chapter: 15 Answering Position for Vacant Numbers . . . . . . . . . . . . . . . . 44

Initiate an Answering Position for Vacant Numbers . . . . . . . . . . . .44
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Remove an Answering Position for Vacant Numbers . . . . . . . . . . .44
Alter an Answering Position for Vacant Numbers . . . . . . . . . . . . .44
Print an Answering Position for Vacant Numbers . . . . . . . . . . . . .44

Chapter: 16 Rerouting Number for an Isolated LIM . . . . . . . . . . . . . . . . . 45

Initiate a Rerouting Number for an Isolated LIM . . . . . . . . . . . . . .45
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Remove the Rerouting Number for an Isolated LIM . . . . . . . . . . . .46
Alter the Rerouting Number for an Isolated LIM . . . . . . . . . . . . . .46
Print the Rerouting Number for an Isolated LIM . . . . . . . . . . . . . .46

Chapter: 17 Number Data for the Route . . . . . . . . . . . . . . . . . . . . . . . . 47

Initiate Number Data for the Route . . . . . . . . . . . . . . . . . . . . .47
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Examples: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Alter Number of Data for the Route . . . . . . . . . . . . . . . . . . . . .48
Remove Number Data for the Route . . . . . . . . . . . . . . . . . . . .48
Print Number Data for the Route . . . . . . . . . . . . . . . . . . . . . .48

Chapter: 18 Public exchange number per LIM . . . . . . . . . . . . . . . . . . . . . 49

Deletion of a Public Exchange Number Per LIM . . . . . . . . . . . . . .49
Printout of public exchange number per LIM . . . . . . . . . . . . . . .49

Chapter: 19 Prefixing of Received Calling Number . . . . . . . . . . . . . . . . . . 50

Initiate a Calling Number Prefix . . . . . . . . . . . . . . . . . . . . . . .50
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

49/154 31-ANF 901 14 Uen L 2019-10-18

 Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Alter the Prefixes of a Received Calling Number . . . . . . . . . . . . . .50
Remove the Prefixes of a Received Calling Number . . . . . . . . . . . .50
Print the Prefixes of a Received Calling Number . . . . . . . . . . . . . .51

Chapter: 20 Facilities Restriction Level/Travelling Class Mark . . . . . . . . . . . . 52

Initiate FRL on Outgoing Routes . . . . . . . . . . . . . . . . . . . . . . .52
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Remove FRL from an Outgoing Route . . . . . . . . . . . . . . . . . . . .54
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Alter FRL on an Outgoing Route . . . . . . . . . . . . . . . . . . . . . . .55
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Print FRL on Outgoing Routes . . . . . . . . . . . . . . . . . . . . . . . .55
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

Chapter: 21 Priority Disconnect of Trunk Calls . . . . . . . . . . . . . . . . . . . . 56

Initiate the Priority Disconnect Feature . . . . . . . . . . . . . . . . . . .56
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Remove the Priority Disconnect feature . . . . . . . . . . . . . . . . . .57
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Print Priority Disconnect Settings . . . . . . . . . . . . . . . . . . . . . .57
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

Chapter: 22 Priority Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Remove CSIU from an Outgoing Route . . . . . . . . . . . . . . . . . . .58
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
Alter CSIU for an Outgoing Route . . . . . . . . . . . . . . . . . . . . . .58
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
Print CSIU for Outgoing Routes . . . . . . . . . . . . . . . . . . . . . . .59
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

Chapter: 23 Fault Statistics on Digital External Lines . . . . . . . . . . . . . . . . . 60

49/154 31-ANF 901 14 Uen L 2019-10-18

 Change of Fault Counters by Zero Setting . . . . . . . . . . . . . . . . .60
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Printout of Fault Counter Data . . . . . . . . . . . . . . . . . . . . . . . .60
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Chapter: 24 Print the Vacant Numbers . . . . . . . . . . . . . . . . . . . . . . . . 61

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Chapter: 25 Print the Free Equipment Positions . . . . . . . . . . . . . . . . . . . 62

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Chapter: 26 Print the Initiated Equipment Positions . . . . . . . . . . . . . . . . . 63

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Chapter: 27 Name on Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
Initiate Name on Route . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
Remove Name on Route . . . . . . . . . . . . . . . . . . . . . . . . . . .64
Print Name on Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

Chapter: 28 SIP Route Configuration When Using webRTC Client/Gateway . . . . 65

Chapter: 29 Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

49/154 31-ANF 901 14 Uen L 2019-10-18

CHAPTER 1 GENERAL

General
For more information about administration of routes, see the operational directions for ADMINISTRATION
OF ROUTES. For more information on administration of number data, see the operational directions for
NUMBERING.

1
49/154 31-ANF 901 14 Uen L 2019-10-18
 FUNCTIONS
CHAPTER 2 ROUTE DATA, RO, OPERATIONAL DIRECTIONS

Route Data, RO, Operational Directions

Route Data, RO
1 General
For more information about administration of routes, see the operational directions for ADMINISTRATION
OF ROUTES. For more information on administration of number data, see the operational directions for
NUMBERING.

Functions
Traffic between an MX-ONE Telephony System and a public or inter-working exchange requires a line.
This line is initiated, or assigned, to a free equipment position in the system. A number of lines with the
same characteristics together forms a route. A number of routes leading to the same external destination
may be used to form a direction.
Routes can be initiated with different categories, such as signaling, service, and traffic characteristics, to
suit different types of external lines.
To each route or direction that permits outgoing traffic one or more external destinations shall be affiliated.
It is possible to initiate up to seven alternative route choices to one external destination.
A day service and a night service position can be initiated to each incoming route or line, that is, a common
answering position for the route or individual for the line during day service and night service, respectively.
An answering position for vacant numbers, to be used at incoming calls to vacant numbers, can also be
initiated for each route.
For restrictive route selection there is an Application System (AS) parameter which indicates if the restric-
tive category check is done for calls originated in the own exchange. This AS can be changed by the
command ASPAC, PARNUM=106.
If the customer group function is used in the PBX, different customers can be assigned their own route
choices. Furthermore, it is possible to assign each customer their own day and night switching positions
(customer-dependent rerouting positions).

Glossary
For a complete list of abbreviations and glossary, see the description for ACRONYMS, ABBREVIATIONS
AND GLOSSARY.

2
49/154 31-ANF 901 14 Uen L 2019-10-18
CHAPTER 3 PREREQUISITES

Prerequisites
Depending on what is to be done, number series of specific number types may have to be initiated.
Since many of the legacy trunk lines are regarded as optional functions, the relevant SW program(s)
TLPxx, must be manually loaded before initiating the trunk function.
See the operational directions ADMINISTRATOR USER’S GUIDE, the parameter description for UNIT in
TECHNICAL REFERENCE GUIDE, MML PARAMETERS, and the installation instruction INSTALLING
AND CONFIGURING MIVOICE MX-ONE, section Optional programs.

3
49/154 31-ANF 901 14 Uen L 2019-10-18
CHAPTER 4 PROCEDURE

Procedure
The following work-flow shall be used for route administration:
1. Initiate the route
2. Initiate route choices to the external destination
3. Initiate equipment positions as external lines for the route
4. Perform other activities
NOTE: IP additional information must be provided to completely initiate the route as an H.323 route. See
the operational directions for IP NETWORKING.

4
49/154 31-ANF 901 14 Uen L 2019-10-18
 ROUTE
CHAPTER 5 EXECUTION

Execution

Route

Initiate a SIP Route

General
The sip_route command defines the external SIP communication. This is followed by an ordinary route
setup.
In the delivery there are a number of SIP trunk profiles available,
The sip trunk profile is often part of a solution described in a solution document. This is the case for the
profiles MXONE-tie-line, AMCC, InAttend, Lync_*.
CPI does not contain solution documents for SIP trunk providers. However, the service Remote Extension
over SIP, explained in “Operational Directions, REMOTE EXTEN­SION OVER SIP”.
Use sip_route -print -profile get a complete list.
Print the selected profile to by sip_route -print -profile <PROFILE>. The printout has the following head-
ings:
• Profile include parameters
sip_route parameters with hinted values (parameter = value) that must be set for sip_route to be
executed.
Note: Additional parameters can be set, except for parameters in Profile exclude parameters.
• Profile exclude parameters
sip_route parameters with fixed values (parameter = value) or excluded parameters (parameter with no
value) which are set as Profile line protocol parameters instead. The mapping between the excluded
parameters and the more elaborate protocol parameters are listed in /etc/opt/eri_sn/sip_trunk_pro-
files/trunk_pro­file.template
• Profile line protocol parameters
Fixed SIP protocol related parameters. These parameters extends and replaces RODAI parameters. The
mapping between RODAI and these parameters are listed in /etc/opt/eri_sn/sip_trunk_profiles/trunk_pro-
file.template
For backward compatibility, the profile Default, allows ‘RODAI variables VARI,VARC,VARO not equal
zeroes’ to override these values. sip_route without -profile set is using profile Default.
• Profile route THH initiation commands
Recommended settings for the commands, ROCAI, RODAI, ROEQI and optionally RODDI commands.
The settings has been used in verification tests. There might be additional information in the profile file,
/etc/opt/eri_sn/sip_trunk_pro­files/<profile_repository>.conf

5
49/154 31-ANF 901 14 Uen L 2019-10-18
 ROUTE
CHAPTER 5 EXECUTION

Execution
Initiate the SIP route data towards the external network. Use the command sip_route.
1. sip_route -set [-profile XXX] -route Y -uristring0 “sip:?@<SIP reqURI>”,[other sip_route parameters
needed or required by the profile -Profile include parameters-]
2. ROCAI:ROU=Y, SIG={D11=A for SIP route}, other service parameters
3. If sip_route -profile is set (except for Default which is available for backward compatibility), then
VARI,VARC,VARO must have zeros as the profile parameters, -Profile line protocol parameters- is
the replacement for these settings.
RODAI:ROU=Y,TYPE=TL66,VARI=00000000,VARC=00000000,VARO=00000000;
4. TRU parameter defines which servers (lim) that shall be used for SIP signaling for this route and the
call capacity.ROEQI:ROU=Y,TRU=<lim>-<first sequence number>&&<lim> -<last sequence
number>
Example: Set route which limit the route to only use lim 3 for signaling with the max capacity of 60 con-
current calls.
ROEQI:ROU=Y,TRU=3-1&&3-60
5. Define access code that shall trigger this route
RODDI:ROU=Y,DEST=<dest-number>
NOTE: The sip_route command must be executed before the ROEQI command that ties equipment to
the route.
Also, see chapter Lines.

Public SIP Route with Enterprise SBC

General
The service provider may offer SIP trunk as part of a WAN corporate solution. If the public SIP trunk
access is part of this WAN network it can be accessed directly from MX-ONE.In this case no proxy needs
be configured in sip_route.
This description is referring to the case when a SIP trunk provider just offers an access over the Internet,
The customer must have an Internet service in order to setup a SIP trunk connection.
In order to protect MX-ONE and the corporate network, a firewall is needed. For SIP traffic a SIP aware
firewall is needed and is called Session Border Controller (SBC).

Execution
Example:
MX-ONE: 192.168.10.10
SBC:192.168.10.11
SIP trunk service provider access: trunkservice.com
For outbound settings:
sip_route -set -route 250 -protocol tcp -service PUBLIC -proxyip 192.168.10.11 -proxy­port 5060 -uris-
tring0 ‘sip:[email protected]’ -remoteport 5060
For inbound settings:

6
49/154 31-ANF 901 14 Uen L 2019-10-18
 ROUTE
CHAPTER 5 EXECUTION

sip_route -set -route 250 -accept FROM_DOMAIN -match ’trunkservice.com’

NOTE: The will match the host part of the SIP from header in the sip request arrived from trunkservice.com
via the defined proxy (SBC).
Also use the commands ROCAI and RODAI to set the basic route data, for example:
ROCAI:ROU=250,SEL=7110000000000010,SIG=0111110000A0,
TRAF=03151515,TRM=4,SERV=3100000001,BCAP=000100;
RODAI:ROU=250,TYPE=TL66,VARI=00000011,VARC=00001000, / VARO=00000900;
Finally associate the route to one or several MX-ONE server which will be used as SIP access point for
the SBC. for example:
ROEQI:ROU=250,TRU=1-1&&1-60;
The TRU value corresponds to lim 1, with capacity of 60 concurrent calls.

Initiate the Route

General
An arbitrary number of routes can be defined as call-metering routes, see the operational directions for
CHARGING. All call-metering routes can be reached by the PBX operator.
The bearer capability of a route can be set to SPEECH, 3.1-kHz audio, 64 kbps restricted digital, 64 kbps
unrestricted digital, 7-kHz audio (UDI-TA), or 16 kbps unrestricted digital. One or several of the capabili-
ties must be set in order to allow for outgoing telephony on the route. If setting of the bearer capability is
omitted for a route, the default value SPEECH and 3.1-kHz audio is assumed.
Execution
1. Initiate the route by first keying command ROCAI followed by command RODAI.
NOTE: Both of the commands must be keyed for the route to be completely initiated.
2. Key the commands ROCAP and RODAP to verify that the initiations were successful.

Remove a Route
Prerequisites
No lines shall be affiliated to the route. Neither shall there be any call origin group for PBX operators nor
external destination affiliated to the route. Any existing call-metering equipment must be removed first.
Also, no Least Cost Routing (LCR) data pointing to the route shall exist.
NOTE: The route can be utilized for common and individual abbreviated numbers.

7
49/154 31-ANF 901 14 Uen L 2019-10-18
 ROUTE
CHAPTER 5 EXECUTION

Execution

Measure/Question Observation/ Comment

1 Key the command ROEDP to -

verify that the route exists and
that no lines are affiliated to the
route.
2 Are there any lines affiliated to If NO, proceed to step 4.
the route?

8
49/154 31-ANF 901 14 Uen L 2019-10-18
 ROUTE
CHAPTER 5 EXECUTION

Measure/Question Observation/ Comment

3 Key the command ROEQE to See Remove Lines on page 29.
remove the lines.
4 Is the route a SIP route? -
5 Remove the route. Use the -
command sip_route
-remove.
6 Key the command RODDP to -
check if any external
destinations are affiliated to the
route.
7 Are there any external If NO, proceed to step 7.
destination affiliated to the
route?
8 Remove all external See Remove the Ordinary Route
destinations that are affiliated Choice to an External
to the route. Destination on page 19.
9 Key the command OPCTP to -
check if the route is part in any
call origin group.

9
49/154 31-ANF 901 14 Uen L 2019-10-18
 ROUTE
CHAPTER 5 EXECUTION

Measure/Question Observation/ Comment

8 Is the route part in any call If NO, proceed to step 12.

origin group?
9 Key the command OPCTR to See the operational directions
remove the route from a call for PBX OPERATOR TRAFFIC.
origin group.
10 Are there more call origin If YES, return to step 9.
groups to be removed from?
11 Key the command OPCTP to -
verify that the route is no longer
part in any call origin group.

10
49/154 31-ANF 901 14 Uen L 2019-10-18
 ROUTE
CHAPTER 5 EXECUTION

Measure/Question Observation/ Comment

12 Check if the route has individual See the operational directions
metering. If any type of for CHARGING.
metering exists save the
metering results on file.
13 Key the command ROUTE to -
remove the route.
14 Key the command ROCAP to -
verify the result.

E1 - T1 Change
If an E1 trunk line is to be reconfigured to a T1 trunk line or the other way round, it is necessary to restart
the used virtual board in the process. Use the board_restart command.

Print the Route Categories

General
Route categories initiated with command ROCAI are printed by keying command ROCAP. Route categories
initiated with command RODAI are printed by keying command RODAP.

Execution
Key the command ROCAP and RODAP to obtain printouts.

Alter the Route Categories

General
Route categories initiated with command ROCAI can be altered with command ROCAC. Route categories
initiated with command RODAI can be altered with command RODAI.
NOTE: All parameters must be stated in the RODAI command and not only the ones that are to be
changed.
When using command RODAI or when altering call-metering information or traffic direction with command
ROCAC, all external lines must be removed before keying the command.

11
49/154 31-ANF 901 14 Uen L 2019-10-18
 ROUTE
CHAPTER 5 EXECUTION

Execution

Measure/Question Observation/ Comment

1 Key the command ROCAP and -

RODAP to print out the current
route categories.
2 Shall any route categories If NO, proceed to step 5.
initiated with command RODAI
be altered?

12
49/154 31-ANF 901 14 Uen L 2019-10-18
 ROUTE
CHAPTER 5 EXECUTION

Measure/Question Observation/ Comment

3 Key the command ROEDP to -
print out the external lines
belonging to the route.
4 Block all boards with external NOTE: The command can lead
lines belonging to the route.Use spontaneous printouts. Proceed
the command block. to step 7.

5 Shall the route be altered to a If YES, return to step 3.

metering route?
6 Shall the traffic direction be If YES, return to step 3. If NO,
altered? proceed to step 13.
7 Key the command ROEQE to -
remove all lines belonging to
the route.
8 Key the command RODAI or -
ROCAC to alter the route
categories.

13
49/154 31-ANF 901 14 Uen L 2019-10-18
 ROUTE
CHAPTER 5 EXECUTION

Measure/Question Observation/ Comment

9 Will the route be a SIP route? -

10 Key the command sip_route -
to initiate the SIP route data.
11 Key the command ROEQI to -
re-initiate lines to the route.
12 Key the command RODAP and -
ROCAP to verify the result.
13 Key the command alarm to -
print (list) alarms in the alarm
log.
14 Key the command alarm to Proceed to STOP.
erase (reset) alarms in the
alarm log.
15 Key the command ROCAC to -
alter the route categories.

14
49/154 31-ANF 901 14 Uen L 2019-10-18
 ROUTE
CHAPTER 5 EXECUTION

Measure/Question Observation/ Comment

16 Key the command ROCAP to -

verify the result.

15
49/154 31-ANF 901 14 Uen L 2019-10-18
 INITIATE A DIRECTION
CHAPTER 6 DIRECTION

Direction

Initiate a Direction

General
Up to four routes with the same or different characteristics form a direction to a destination. See the figure
below.
Up to 100 directions are permitted.
Selection of a route within the direction depends on the authorization category of the calling party. For
example, one category can be allowed to use all routes, while another is allowed to use one route only.
The authorization categories can consist of different types of calling parties, such as a PBX operator or
normal extension. These categories have fixed positions in an authorization table. Other types of users
can be assigned one of the classes A, B, C, D, or E in the authorization table.
An H.323 route defined in a direction (RODII) must be previously initiated with a remote destination IP
address (RIANI). Since a direction could be formed by different types of routes, remote destination IP
address could not be assigned linked to the destination (RODDI).

Overflow
When all external lines within a route are busy or blocked, a call wishing to use the route tries to overflow
to another route within the direction. The overflow route must be of the same or lower authorization cate-
gory as the first route.
Overflow within the direction also depends on the order in which the routes were initiated in the direction
(RODII). For a call to overflow to another route, the overflow route must have been initiated after the first
tried route. A call can never overflow to a route that was initiated before the route that was first tried, even
if that earlier initiated route has a lower authorization category.

16
49/154 31-ANF 901 14 Uen L 2019-10-18
 INITIATE A DIRECTION
CHAPTER 6 DIRECTION

This means that special care has to be taken concerning the order of initiating routes in a direction.

Prerequisites
Routes must be initiated.

Execution
1. Key the command RODII to initiate the direction.
2. Key the command RODIP to verify that the initiation was successful.

17
49/154 31-ANF 901 14 Uen L 2019-10-18
 REMOVE A DIRECTION
CHAPTER 6 DIRECTION

Remove a Direction

Prerequisites
The direction must exist.

Execution

Measure/Question Observation/ Comment

1 Key the command RODDP to -

see the current external
destination route data.
2 Is the direction used as route If NO, proceed to step 5.
choice to any of the external
destinations?
3 Remove this route choice to the See 4.3.2 Remove the Ordinary
external destination. Route Choice to an External
Destination on page 17.

18
49/154 31-ANF 901 14 Uen L 2019-10-18
 PRINT THE DIRECTION
CHAPTER 6 DIRECTION

Measure/Question Observation/ Comment

4 Is the direction used to any If YES, return to step 3.

other external destination?
5 Key the command RODIE to -
remove the direction.

Print the Direction

General
RODIP provides a printout of the direction and its authorization tables (initiated with command RODII).

Execution
Key the command RODIP to obtain a printout.

19
49/154 31-ANF 901 14 Uen L 2019-10-18
 REMOVE THE ORDINARY ROUTE CHOICE TO AN EXTERNAL DESTINATION
CHAPTER 7 EXTERNAL DESTINATION AND ALTERNATIVE ROUTING

External Destination and Alternative Routing

Remove the Ordinary Route Choice to an External Destina-

tion

General
The ordinary route choice to an external destination can be removed without having to remove any alter-
native route choices to this destination. Any alternative route choices will be removed together with the
ordinary route choice.
Since Least Cost Routing (LCR) destinations might use the external destinations that are to be removed,
it is required to check existing LCR data and, if a match is found, rearrange the LCR data.

20
49/154 31-ANF 901 14 Uen L 2019-10-18
 REMOVE THE ORDINARY ROUTE CHOICE TO AN EXTERNAL DESTINATION
CHAPTER 7 EXTERNAL DESTINATION AND ALTERNATIVE ROUTING

Execution

Measure/Question Observation/ Comment

1 Key the command LCDDP to See the operational directions

verify that no LCR destination for LEAST COST ROUTING, LC.
points exist to the external
destination that shall be
removed. Repeat the procedure
for all FDT subtables if the
Time/Day function is used in the
LCR configuration.
2 Was the external destination to If NO, proceed to step 5.
remove found in any FDT table?
3 Key the command LCDDE for all See the operational directions
tables in LCR to remove data for LEAST COST ROUTING, LC.
which points to the external
destination.
4 Key the command LCDDP to -
verify the result.
5 Key the command LCLDP to See the operational directions
check if the external destination for LEAST COST ROUTING, LC.
to remove is defined as the
default external destination for
LCR.
6 Was the external destination If NO, proceed to step 9.
found to be the default external
destination for LCR?

21
49/154 31-ANF 901 14 Uen L 2019-10-18
 REMOVE THE ORDINARY ROUTE CHOICE TO AN EXTERNAL DESTINATION
CHAPTER 7 EXTERNAL DESTINATION AND ALTERNATIVE ROUTING

Measure/Question Observation/ Comment

7 Key the command LCLDI to See the operational directions

change default external for LEAST COST ROUTING, LC.
destination for LCR.
8 Key the command LCLDP to -
verify the result.
9 Key the command LCOPP to See the operational directions
verify that no OCPT subtable is for LEAST COST ROUTING, LC.
affiliated to the route.

Measure/Question Observation/ Comment

10 Is any OCPT subtable affiliated If NO, proceed to step 13.

to the route?

22
49/154 31-ANF 901 14 Uen L 2019-10-18
 INITIATE THE ORDINARY ROUTE CHOICE TO AN EXTERNAL DESTINATION
CHAPTER 7 EXTERNAL DESTINATION AND ALTERNATIVE ROUTING

Measure/Question Observation/ Comment

11 Key the command LCOPE to See the operational directions

remove the affiliation between for LEAST COST ROUTING, LC.
the route and the subtable.
12 Key the command LCOPP to -
verify the result.
13 Key the command RODDE to -
remove the ordinary route
(direction) choice to the
external destination(s).
14 Key the command RODDP to -
verify the result.

Initiate the Ordinary Route Choice to an External Destina-

tion

General
The way a call to an external destination finds the route to use is through a route access code. One route
access code is used for each external destination. One ordinary route choice, and up to seven alternative
route choices (= alternative routing), may be initiated to an external destination.
Note: When programming a route access code, a market dependent parameter controls whether the
access code must be defined in number analysis as an external destination (number type = ED). In most
markets the parameter is set to not check number analysis meaning any number can be programmed
even if it is not defined as an external destination.
The idea is to make it possible to use a single number within a series as the route access code, where
the number series itself is not an external destination in number analysis. This can be used when
migrating a user from one system to another as it removes the requirement to specify individual numbers
as route access codes. For example, a system has extensions 41xxx and some of the users will migrate
to another exchange due to an office relocation but will keep the same number. It is possible to configure
4 as a route access code to the other exchange. Then when the directory move should happen, the indi-
vidual numbers (e.g. 41002) only need to be changed in number analysis from number type extension to
number type external destination, with no need to program individual route access codes for each user.
If a private network configuration is not properly done, a call may be routed back to an already passed
exchange (using alternative routing). A call entering this kind of loop will eventually use all available lines
and cause network congestion. The return block function, loop avoidance, and transit counter prevent this
from happening in a private network.
These functions enable a maximum number of allowed transit PBXes for a call to pass in order to reach
an external destination to be defined. A call exceeding the maximum number of allowed transit PBXes will
be cleared down.

23
49/154 31-ANF 901 14 Uen L 2019-10-18
 INITIATE ALTERNATIVE ROUTE CHOICES TO AN EXTERNAL DESTINATION
CHAPTER 7 EXTERNAL DESTINATION AND ALTERNATIVE ROUTING

See also the command description for ROUTE DATA, command RODDI.

Prerequisites
The route or direction used to reach the external destination must be initiated.

For H.323:
• If parameter ROU is used, initiating the H.323 route data is a prerequisite, see the operational direc-
tions for IP NETWORKING, RI. If no remote IP address was provided when initiating the H.323-specific
route data, a remote IP address shall be stated now.
• If parameter DRN is used, no IP address may be stated now. Data of the routes associated to the
chosen direction must have been previously initiated including their own remote IP address, see the
operational directions for IP NETWORKING, RI.

Execution
1. Key the command RODDI to initiate an ordinary route choice to the external destination
2. Key the command RODDP and RODRP and verify that the initiation was successful.

Initiate Alternative Route Choices to an External Destina-

tion

General
Up to seven alternative route choices can be initiated to an external destination. When no free and select-
able lines are available in the ordinary route choice, the lines of the alternative route are used in order to
access the desired destination.
In case of IP networking, it is possible to define different alternative paths for the same H.323 route choice.
It is enough to provide different IP addresses for the different choices (alternative addressing).
See also the command description for ROUTE DATA, command RODDI.

Prerequisites
The ordinary route choice to the external destination must be initiated.

For H.323:
• If parameter ROU is used, initiating the H.323 route data is a prerequisite see the operational directions
for IP NETWORKING, RI. If no remote IP address was provided when initiating the H.323-specific
route data, a remote IP address shall be stated now.

24
49/154 31-ANF 901 14 Uen L 2019-10-18
 REMOVE AN ALTERNATIVE ROUTE CHOICE TO AN EXTERNAL DESTINATION
CHAPTER 7 EXTERNAL DESTINATION AND ALTERNATIVE ROUTING

• If parameter DRN is used, no IP address may be stated now. Data of the routes associated to the
chosen direction must have been previously initiated including their own remote IP address, see the
operational directions for IP NETWORKING, RI.

Execution
1. Key the command RODDI to initiate an alternative route choice to an external destination.
2. Key the command RODDP to verify that the initiation was successful.

Remove an Alternative Route Choice to an External Desti-

nation

Execution
1. Key the command RODDE to remove an alternative route choice to an external destination.
2. Key the command RODDP to verify that the removal was successful.

Initiate Customer Route Choices to an External Destination

General
Customers are permitted to have one or more of their own routes. It is also possible for customers to share
routes. Customers are allowed to have alternative route choices.

Prerequisites
The ordinary route choice to the external destination must be initiated.

Execution
1. Key the command RODDI to initiate a customer route choice to an external destination.
2. Key the command RODDP and verify that the initiation was successful.

Remove Customer Route Choices to an External Destina-

tion
1. Key the command RODDE to remove a customer route choice to an external destination.
2. Key the command RODDP to verify that the removal was successful.

25
49/154 31-ANF 901 14 Uen L 2019-10-18
 PRINT EXTERNAL DESTINATION DATA AND ALTERNATIVE ROUTING DATA
CHAPTER 7 EXTERNAL DESTINATION AND ALTERNATIVE ROUTING

Print External Destination Data and Alternative Routing

Data
Key the commands RODDP and RODRP to obtain printouts of the external destination data and the alterna-
tive routing data, respectively.

26
49/154 31-ANF 901 14 Uen L 2019-10-18
 INITIATE LINES
CHAPTER 8 LINES

Lines

Initiate Lines

General
The line initiation command only supports initiation of lines in one LIM at the time. The number of lines
supported by a LIM and the number of lines per LIM supported by a route are limited. However, a route
can stretch over a number of LIMs and thus consist of a larger number of trunk lines. For more information,
see the description for CAPACITIES.
For ISDN there is a software limitation for the number of ISDN boards (PRA, BRA, or both of them) per
LIM. The practical limitation is often lower, because of limitations in the number of time slots in a LIM, and
also depending on the type of magazine that is used for the board positions. There is also a limitation for
the maximum number of ISDN lines in a LIM, which corresponds to eight fully initiated PRAs. For more
information, see the description for CAPACITIES.

Prerequisites
The route must be initiated.

Order of selecting lines

Before initiating the lines, the order in which to initiate the lines must be considered. This is necessary as
it is the initiation order of the lines, together with the value of the parameter SEL in the command ROCAI,
that controls the selection of lines at an outgoing call.
For lines within a LIM the numbering of the lines are used to control the selection.
Three selection principles exist:
1. Even load, see Figure 1. This method means that the traffic load on the lines in a route is distributed
equally between the lines in the route within a LIM (or originator gateway when possible). The line
that is selected shall not be selected again until all other lines in the LIM (or originator gateway when
possible) have been selected. The own LIM (or originator gateway when possible) is always
searched first for a free line, using the principle described above. If no free line exists in the own
LIM, the next LIM is searched in the same way.
2. Sequential selection within the own LIM, see Figure 2. The principle for this method of selection is
that the search for a free line always starts with the route's line of the lowest order that is situated in
the own LIM (or originator gateway when possible).
When no free lines are available in the own LIM the search continues to the next LIM, which is searched
in the same way. The lines of a route in a LIM shall form a continuous chain, from the lowest order line
up to the highest order line. This chain is connected to the respective chain of the next LIM where the

27
49/154 31-ANF 901 14 Uen L 2019-10-18
 INITIATE LINES
CHAPTER 8 LINES

route is represented, and so on. Search for a free line always starts from the beginning of the own LIM
chain and continues to the line of the highest order in the last LIM.
3. Sequential selection within a route, see Figure 2. The principle for this method of selection is that the
search for a free line always starts with the route's first line (First line denotes the line of the lowest
order in a route, for example, TRU=5-1). What LIM a line is situated in is not considered at selection
(as in principle 1 and 2 above), so this must be considered at the initiation of the lines. All lines within
the route shall form one continuous chain, from the lowest order line up to the highest order line,
where search for a free line always starts from the beginning of the chain.
The principle for both-way routes shall be that the public or interworking exchange selects free lines
starting from the opposite end of the chain. In this way the risk for call collision is minimized.
When a sequence order for selecting lines within a route has been decided, the lines shall be initiated into
the system in the order they are to be selected at an outgoing call. The lines within a route can be divided
over a number of different LIMs. The order of selection between the LIMs is controlled by the order of
initiation.
The lines need not to be initiated in sequence within each LIM. By, for example, initiating the lines 24-1,
24-3, and 24-5 in LIM 24, it is possible afterwards to squeeze lines into the order of selecting lines.
Figure 8.1: Even Load

28
49/154 31-ANF 901 14 Uen L 2019-10-18
 INITIATE LINES
CHAPTER 8 LINES

Figure 8.2: Sequential Selection within Own LIM

29
49/154 31-ANF 901 14 Uen L 2019-10-18
 INITIATE LINES
CHAPTER 8 LINES

Figure 8.3: ITU-T Method 2 Line Selection

Execution
H.323
1. Key the command ROEQI to initiate the line.
If the initiated lines belong to an H.323 route:
– no EQU may be provided
– a remote IP address may be provided, but only if a remote IP address has been provided when
initiating the associated route.
2. Key the command ROEDP to verify the result.
See operational directions for IP NETWORKING, RI.

SIP
1. Key the command ROEQI to initiate the line.
If the initiated lines belong to an SIP route:
– no EQU may be provided

30
49/154 31-ANF 901 14 Uen L 2019-10-18
 REMOVE LINES
CHAPTER 8 LINES

– the command sip_route has to be entered prior to ROEQI

2. Key the command ROEDP to verify the result.
NOTE: Check if prefix data exists for the route, by using the ROAPP command. If prefix data exists, perform
the following step after initiating the lines. If lines are initiated in a LIM where no line individuals exists for
that route, the ROAPI command should be executed after ROEQI to update the prefix data for the route in
that LIM.

Remove Lines
Check if the line is digital and is included in the synchronization configuration. If this is the case, see the
operational directions for ADMINISTRATOR USER’S GUIDE.
1. Block the individual on the board to which the line is connected. Use command block -help.
2. Key the command ROEQE to remove the line.
3. Key the command ROEDP to verify that the removal was successful.

Print Line Data

Key the command ROEDP to obtain a printout.

31
49/154 31-ANF 901 14 Uen L 2019-10-18
 INITIATE DAY AND NIGHT SERVICE POSITIONS
CHAPTER 9 DAY AND NIGHT SERVICE POSITIONS

Day and Night Service Positions

Initiate Day and Night Service Positions

General
Internal day and night service position means that the answer positions that are affiliated to a route or line
shall be situated in the same exchange as the answering position.
NOTE: When the exchange uses customer number facility and the route is defined as DID route, only
customer group-dependent day and night service positions shall be stated.

Prerequisites
Route and lines must be initiated. Depending on whether an extension, PBX operator, or internal group
hunting group number is to be day or night service position, these must already be initiated.

Execution
1. Key the command RODNI to initiate day and night service positions.
2. Key the command RODNP to verify that the initiation was successful.

Remove Day and Night Service Positions

1. Key the command RODNE to remove day and night service positions.
2. Key the command RODNP to verify that the removal was successful.

Alter Day and Night Service Positions

Previously initiated day or night service positions are altered by keying command RODNI once again.
Key the command RODNP to verify that the change was successful.

Print Day and Night Service Positions

Key the command RODNP to obtain a printout.

32
49/154 31-ANF 901 14 Uen L 2019-10-18
 INITIATION OF CALL METERING EQUIPMENT FOR EXTERNAL LINE
CHAPTER 10 CALL METERING EQUIPMENT

Call Metering Equipment

Call metering information received from the public exchange can be available at outgoing calls both on
digital and analog routes.
On digital routes, this information is transmitted over the signalling channel, there is no need for external
call metering equipment.
On analog routes, the call metering information is transmitted as pulses where the frequency is either 50
Hz, 12 kHz or 16 kHz. To be able to detect these pulses, an external call metering equipment has to be
connected. This is either one or several daughter boards mounted on the TLU75 board, one or several
CDU boards (discontinued), or by using the TLU83/2 board that supports 12 kHz and 16 kHz metering.
The commands ROECP, ROECI and ROECE are only valid to use together with old CDU boards.

Initiation of Call Metering Equipment for External Line

General
Observe that the system does not verify that all lines within a call metering route are affiliated to the call
metering equipment, that is the system accepts the fact that lines lacking call metering equipment exist
despite the fact that the route is a call metering route.

Prerequisites
Route and line must be initiated. The call metering equipment and the line must be situated in the same
LIM.

Execution
1. Key the command ROCAP to verify that the route is categorized as call metering route.
2. Verify that the relevant function block TL can use the call metering equipment.
3. Connect a cable between the call metering equipment and the line.
NOTE: Parameter CDU will be found in the parameter description for the relevant TL function block,
that will be found under Route Data, RO.
4. Key the command ROECI to initiate the affiliation between the call metering equipment and the line.
5. Key the command ROECP to verify the result.

33
49/154 31-ANF 901 14 Uen L 2019-10-18
 MOVING OF CALL METERING EQUIPMENT TO ANOTHER EXTERNAL LINE
CHAPTER 10 CALL METERING EQUIPMENT

Moving of Call Metering Equipment to Another External

Line
1. Key the command ROECE to erase the call metering equipment from the previous line.
2. Move the connection cable to the new line.
3. Key the command ROECI to affiliate the call metering equipment to the new line.
4. Key the command ROECP to verify the result.

Removal of Call Metering Equipment for an External Line

1. Key the command ROECE to erase the affiliation between the call metering equipment and the line.
2. Remove the connection cable between the line and the call metering equipment.
3. Key the command ROECP to verify the result.

Printout of Call Metering Equipment Data

Key the command ROECP to obtain a printout of the equipment positions of the line and the call metering
equipment.

34
49/154 31-ANF 901 14 Uen L 2019-10-18
 GENERAL
CHAPTER 11 CENTRAL ANSWERING POSITION IN NETWORK WITH ISDN/H.323 (OR SIP WITHOUT NOTIFICATION)

Central Answering Position in Network with

ISDN/H.323 (or SIP Without Notification)

General
A central answering position in a network can only be initiated if the centralized operator function exists
in the exchange. The order of priority between the rerouting positions for a specific route are as follows:
1. Internal day service position
2. Central, external answering positions (up to three)
3. Internal night service position

Prerequisites
Routes and lines must be initiated. The rerouting position is accessed via a common abbreviated number.
The abbreviated number contains the external number of the rerouting position. The exchange numbers
of all exchanges in the private network must be initiated as external destinations.
Day or night service position for a specific external line must not be initiated, as it would always have
higher priority and could not be external.

Initiate Central Answering Position in a Network

1. Key ADCOI (command for a common abbreviated number) to initiate the number of the external
rerouting position.
2. Key the command RORNI to initiate the external rerouting position.
3. Key the command RORNP to verify the result.

Remove a Central Answering Position from a Network

1. Key the command RORNE to remove the central rerouting position.
If the last external rerouting position is to be removed, the route is released from the centralized operator
function.
2. Key the command RORNP to verify the result.
3. Key the command ADCOE to remove the number of the external rerouting position.

35
49/154 31-ANF 901 14 Uen L 2019-10-18
 CHANGE THE CENTRAL ANSWERING POSITION IN THE NETWORK
CHAPTER 11 CENTRAL ANSWERING POSITION IN NETWORK WITH ISDN/H.323 (OR SIP WITHOUT NOTIFICATION)

Change the Central Answering Position in the Network

1. Key the command RORNE to remove the previous external rerouting position.
2. Key ADCOE to remove the number of the previous external rerouting position.
3. Key ADCOI (command for a common abbreviated number) to initiate the number of the new external
rerouting position.
4. Key the command RORNI to initiate the new external rerouting position.
5. Key the command RORNP to verify the result.

Print a Central Answer Position in a Network

1. Key the command RORNP to obtain a printout of those central answer positions initiated for a specific
route.
2. Key the command ADCDP for a printout of the affiliation between the numbers of external answer posi-
tions and corresponding abbreviated numbers.

36
49/154 31-ANF 901 14 Uen L 2019-10-18
 GENERAL
CHAPTER 12 CUSTOMER-CENTRALIZED OPERATOR IN AN ISDN/H.323 NETWORK (OR SIP WITHOUT NOTIFICATION)

Customer-Centralized Operator in an
ISDN/H.323 Network (or SIP Without Notifica-
tion)

General
Rerouting calls to the customer-centralized operator is supported only in an ISDN/H.323/SIP network and
the incoming route shall have customer affiliation. Two customer-centralized operators can be specified
for each customer in an exchange.
The order of priority between the rerouting positions for a specific route is as follows:
1. Internal day service position
2. Customer-centralized operators (up to two)
3. Central, external answering positions
4. Internal night service position
NOTE: In a VPN scenario, the number of customer-centralized operators supported depends on the
number of USER INFO messages that can be sent in Service 2. If two USER INFO messages are allowed
in Service 2, then only one customer-centralized operator is supported. When more than two USER INFO
messages are allowed, both customer-centralized operator 1 and 2 are supported.

Prerequisites
Routes and lines must be initiated and the routes must have customer affiliation. The customer-central-
ized operator number is defined by a common abbreviated number. The abbreviated number contains the
external number of the customer-centralized operator.
Day or night service position for a specific external line must not be initiated, as it would always have
higher priority and could not be external.

Initiate a Customer-Centralized Operator in a Network

1. Key ADCOI (command for a common abbreviated number) to initiate the number of the
customer-centralized operator.
2. Key the command RORNI and state parameter CUST to initiate the customer-centralized operator.
3. Key the command RORNP and state parameter CUST to verify the result.

37
49/154 31-ANF 901 14 Uen L 2019-10-18
 REMOVE A CUSTOMER-CENTRALIZED OPERATOR FROM A NETWORK
CHAPTER 12 CUSTOMER-CENTRALIZED OPERATOR IN AN ISDN/H.323 NETWORK (OR SIP WITHOUT NOTIFICATION)

Remove a Customer-Centralized Operator from a Network

1. Key the command RORNE and state parameter CUST to remove the customer-centralized operator.
2. Key the command RORNP and state parameter CUST to verify the result.
3. Key the command ADCOE to remove the number of the customer-centralized operator.

Change the Customer-Centralized Operator in the Network

1. Key the command RORNE and state parameter CUST to remove the previous customer-centralized
operator.
2. Key ADCOE to remove the number of the previous customer-centralized operator.
3. Key ADCOI (command for a common abbreviated number) to initiate the number of the new
customer-centralized operator.
4. Key the command RORNI and state parameter CUST to initiate the new customer-centralized oper-
ator.
5. Key the command RORNP to verify the result.

Print a Customer-Centralized Operator in a Network

1. Key the command RORNP and state parameter CUST to obtain a printout of the customer-centralized
operators initiated for a specific customer.
2. Key the command ADCDP for a printout of the affiliation between the numbers of customer-centralized
operators and corresponding abbreviated numbers.

38
49/154 31-ANF 901 14 Uen L 2019-10-18
 GENERAL
CHAPTER 13 ROUTE OPTIMIZATION (PATH REPLACEMENT)

Route Optimization (Path Replacement)

General
Route optimization between exchanges can be executed when a direct route with free lines exists
between two exchanges, but when the original call is set up through another route passing a third
exchange.
Events that can lead to route optimization:
• Extending or transfer has occurred in a third exchange
• Alternative routing
• Conference terminated with two external parties remaining.
• Extending or transfer has occurred in a third exchange
Route optimization between the exchanges means that a call from exchange A that is answered by
exchange B and thereafter extended to exchange C shall utilize a direct route. In other words, the connec-
tion shall be set up directly between exchanges A and C. The route to exchange B is cleared down.

Phase 1
A connection is set up between exchanges A and B

Phase 2
Exchange B calls exchange C

39
49/154 31-ANF 901 14 Uen L 2019-10-18
 PHASE 3
CHAPTER 13 ROUTE OPTIMIZATION (PATH REPLACEMENT)

Phase 3
Exchange B extends the call to exchange C. A new connection is set up between exchanges A and C,
and the previous connection via exchange B is cleared down.

Prerequisites
• Direct route between the exchanges.
• The exchanges belong to the same network.
• The route optimization function has been opened with the help of AS parameters.
• Conference feature exists in the exchanges. The conference hardware is located in the Media
Gateway.
• The routes have been assigned categories for Common Channel Signaling (CCS).

40
49/154 31-ANF 901 14 Uen L 2019-10-18
 EXECUTION
CHAPTER 13 ROUTE OPTIMIZATION (PATH REPLACEMENT)

Execution

41
49/154 31-ANF 901 14 Uen L 2019-10-18
 EXECUTION
CHAPTER 13 ROUTE OPTIMIZATION (PATH REPLACEMENT)

Measure/Question Observation/ Comment

1 Key the command ASPAP to -

verify existing values fort he
following application system
parameters:
• Route optimization
permitted/not permitted
• Time delay for start of route
optimization (10 s recom-
mended)
• Time delay for start of route
optimization after alternative
routing. (60 s recommended)
- Limit value for number of
attempts after rejection (3
attempts recommended)
2 Are alteration(s) necessary? If NO, proceed to step 4.
3 Actual values of parameters are -
altered with command ASPAC.
4 Key the command ASPAP to -
verify the result.

The lines are initiated in accordance with route data without any particular affiliation to route optimization.

42
49/154 31-ANF 901 14 Uen L 2019-10-18
 INITIATE A CUSTOMER-DEPENDENT REROUTING POSITION
CHAPTER 14 CUSTOMER-DEPENDENT REROUTING POSITION

Customer-Dependent Rerouting Position

Initiate a Customer-Dependent Rerouting Position

General
This rerouting position is neither route nor line dependent. One rerouting position per customer for a day
switched PBX and one per night switched PBX can exist. When the exchange uses customer group
facility and the route is defined as DID route, only customer group dependent day and/or night service
positions shall be stated.

Prerequisites
Depending on whether an extension, a PBX operator, or an internal group hunting group number is to be
a day or night service position, these must be initiated.

Execution
1. Key the command ROCDI to initiate a customer-dependent rerouting position.
2. Key the command ROCDP to verify the result.

Remove a Customer-Dependent Rerouting Position

1. Key the command ROCDE to remove the day and night service position.
2. Key the command ROCDP to verify the result.

Alter a Customer-Dependent Rerouting Position

1. Key the command ROCDI to alter the day and night service position.
2. Key the command ROCDP to verify the result.

Print a Customer-Dependent Rerouting Position

Key the command ROCDP to obtain a printout.

43
49/154 31-ANF 901 14 Uen L 2019-10-18
 INITIATE AN ANSWERING POSITION FOR VACANT NUMBERS
CHAPTER 15 ANSWERING POSITION FOR VACANT NUMBERS

Answering Position for Vacant Numbers

Initiate an Answering Position for Vacant Numbers

General
Answering position for vacant numbers is used when an incoming external call to a vacant number is to
be rerouted to a common answering position. It is possible to define if B-answer signal shall be sent at
rerouting due to call to a vacant number, see the command ASPAC, PARNUM=146.

Prerequisites
The route must be initiated and defined for direct in-dialling traffic. Depending on whether an extension
or internal group hunting group number is to be an answering position for vacant numbers, these must
already be initiated.

Execution
1. Key the command ROVNI to initiate the answering position for vacant numbers.
2. Key the command ROVNP to verify the result.

Remove an Answering Position for Vacant Numbers

1. Key the command ROVNE to remove the answering position for vacant numbers.
2. Key the command ROVNP to verify the result.

Alter an Answering Position for Vacant Numbers

1. Key the command ROVNI to initiate the new answering position for vacant numbers.
2. Key the command ROVNP to verify the result.

Print an Answering Position for Vacant Numbers

Key the command ROVNP to obtain a printout.

44
49/154 31-ANF 901 14 Uen L 2019-10-18
 INITIATE A REROUTING NUMBER FOR AN ISOLATED LIM
CHAPTER 16 REROUTING NUMBER FOR AN ISOLATED LIM

Rerouting Number for an Isolated LIM

Initiate a Rerouting Number for an Isolated LIM

General
A rerouting number for calls, receiving congestion due to isolated LIM, can be initiated in each LIM when
the inter-LIM media connection is faulty. The initiated number is placed in front of the dialled number.
This feature makes it possible to call between a remote isolated LIM and the main part of the exchange
or between isolated LIMs when a fault has occurred in the inter-LIM media connection. By defining the
rerouting number as a route access code, the call can be routed either through the private or the public
network.
A suitable configuration for this feature can be a system with remote sites with several LIMs at each site.
If the remote site consists of three LIMs, the rerouting number can be a route access code to the second
LIM at the remote site.
This means that the exchange can cover up to a maximum of nine LIMs using alternative route selection,
because the exchange can handle up to seven alternatives to each destination. This means that to get
full accessibility (reach all extensions within the remote site) the following number of tie lines are needed.

LIMs Number of tie lines

2 1
3 3
4 6
5 10
6 15
7 21
8 28
9 36

The number of tie lines can be decreased to the cost of lower accessibility.

Prerequisites
The ordinary and alternative route to the external destination must be initiated.

45
49/154 31-ANF 901 14 Uen L 2019-10-18
 REMOVE THE REROUTING NUMBER FOR AN ISOLATED LIM
CHAPTER 16 REROUTING NUMBER FOR AN ISOLATED LIM

Execution
1. Key the command RORII to initiate the rerouting number for an isolated LIM.
2. Key the command RORIP to verify the result.

Remove the Rerouting Number for an Isolated LIM

1. Key the command RORIE to remove the rerouting number for an isolated LIM.
2. Key the command RORIP to verify the result.

Alter the Rerouting Number for an Isolated LIM

1. Key the command RORIE to remove the rerouting number for an isolated LIM.
2. Key the command RORII to initiate the new rerouting number for an isolated LIM.
3. Key the command RORIP to verify the result.

Print the Rerouting Number for an Isolated LIM

Key the command RORIP to obtain a printout.

46
49/154 31-ANF 901 14 Uen L 2019-10-18
 INITIATE NUMBER DATA FOR THE ROUTE
CHAPTER 17 NUMBER DATA FOR THE ROUTE

Number Data for the Route

Initiate Number Data for the Route

General
The following number data can be defined for incoming routes:
• Predigits (parameter PRE). Defined per incoming route, in cases where the public or interworking
exchange only can send a limited number of digits over the incoming route.
• Identity of the incoming route (parameter ROUDIR).
The following number data can be defined for outgoing routes:
• Terminating area code (parameter TERAC).
• TON, Type of called number (B-number). (D2 and D19 in parameter ADC.) Used instead of prefix digits
to indicate to the closest following exchange or network, the type of called public or private number (of
the call using this destination).
• Normally, D2 and D19 are set to the same value. But, if the route is used for MX-ONE Telephony
System VPN (Virtual Private Network without Intelligent Network) and the public network cannot
handle private TONs, the private TON shall be set in D2 (in order to have net services) and a public
TON shall be set in D19 (the TON to send to the public network that does not accept private TONs).

The following number data can be defined for incoming and outgoing routes:
• Exchange numbers of own exchange (parameters EXNOPU and EXNOPR). Used together with the
directory number to compose the complete identity of a party in a private or public network. This
complete identity is sent to the cooperating exchange at external calls.
For incoming routes it is the received TON of the calling number (A-number) that determine what
exchange numbers to use, when composing the complete calling identity to send to the cooperating
exchange. For outgoing routes it is the TON of the calling number (A-number) in own exchange that deter-
mine what exchange numbers to use (D3 and D4 in parameter ADC). Calls to a destination with calling
parties of a specific type of number, shall have a dedicated destination data record in the route choice
table (parameter DEST, command RODDI) where the TON of the calling party is set. This TON both regu-
lates what exchange numbers to use, and is sent to the cooperating exchange as TON of the calling party.
It is important to coordinate the setting of exchange numbers in the RONDI command (EXNOPU and
EXNOPR) with the setting of TON in the RODDI command (parameter ADC).
Eight different exchange numbers may be defined, each consisting of up to five digits. Each one of the
eight exchange numbers corresponds to a different Type of number (TON). The complete exchange iden-
tity is composed by adding the relevant exchange numbers to the directory number. What exchange
number(s) to add is determined by the TON of the call.

47
49/154 31-ANF 901 14 Uen L 2019-10-18
 ALTER NUMBER OF DATA FOR THE ROUTE
CHAPTER 17 NUMBER DATA FOR THE ROUTE

Examples:
• An International number (TON=1) is composed of: Country code + Trunk code + Local code + Directory
number, and can have a maximum length of 20 digits (5+5+5+5).
• A Local private number (TON=6) is composed of: Location code + Directory number, and can have a
maximum length of 10 digits.
• A Level 1 Regional number (TON=7) is composed of: Location code + Directory number, and can have
a maximum length of 10 digits.

Prerequisites
Routes must be initiated.
All external destinations must be initiated with the right type of number (TON) using command RODDI.

Execution
1. Key the command RONDI to initiate the number data for the route. To initiate many exchange
numbers for the public network for one route, RONDI must be repeated for each exchange number.
The same procedure applies to exchange numbers for the private network.
2. Key the command RONDP to verify that the initiation was successful.

Alter Number of Data for the Route

1. Key the command RONDI to alter the previously initiated number data.
2. Key the command RONDP to verify that the alteration was successful.
NOTE: Number data initiated with command RODDI cannot be altered by only use the command RODDI.
First, the previous number data must be removed with command RODDE, then command RODDI is used
to initiate the new number data

Remove Number Data for the Route

1. Key the command RONDE to remove the number data for the route.
2. Key the command RONDP to verify that the removal was successful.

Print Number Data for the Route

Key the command RONDP to obtain a printout of the number data for the route.

48
49/154 31-ANF 901 14 Uen L 2019-10-18
 DELETION OF A PUBLIC EXCHANGE NUMBER PER LIM
CHAPTER 18 PUBLIC EXCHANGE NUMBER PER LIM

Public exchange number per LIM

Deletion of a Public Exchange Number Per LIM

1. Initiated public exchange number per LIM can be removed by keying the command route_-
data_common -e.
2. Key the command route_data_common -p to verify the result.

Printout of public exchange number per LIM

Key the command route_data_common -p to obtain a printout.

49
49/154 31-ANF 901 14 Uen L 2019-10-18
 INITIATE A CALLING NUMBER PREFIX
CHAPTER 19 PREFIXING OF RECEIVED CALLING NUMBER

Prefixing of Received Calling Number

Initiate a Calling Number Prefix

General
It is possible to initiate prefixes to be used for calling numbers received on specific routes. The function
is only used in transit or gateway exchanges.
This functionality is required when the incoming calling number shall be transited to some kind of back-
bone network where identical calling numbers might be received from different exchanges. Here it is
necessary to use prefixes so that the backbone network can distinguish otherwise identical calling
numbers from each other. A unique calling number is necessary for billing and for further routing
purposes.
The prefixes are applicable for both public and private calling numbers.

Prerequisites
Routes must be initiated.

Execution
1. Key the command ROAPI to initiate calling number prefixes.
2. Key the command ROAPP to verify that the initiation was successful.

Alter the Prefixes of a Received Calling Number

1. Initiated prefixes are altered by keying command ROAPI once again.
2. Key the command ROAPP to verify that the change was successful.

Remove the Prefixes of a Received Calling Number

1. Key the command ROAPE to remove calling number prefixes.
2. Key the command ROAPP to verify that the removal was successful.

50
49/154 31-ANF 901 14 Uen L 2019-10-18
 PRINT THE PREFIXES OF A RECEIVED CALLING NUMBER
CHAPTER 19 PREFIXING OF RECEIVED CALLING NUMBER

Print the Prefixes of a Received Calling Number

Key the command ROAPP to obtain a printout of initiated calling number prefixes.

51
49/154 31-ANF 901 14 Uen L 2019-10-18
 INITIATE FRL ON OUTGOING ROUTES
CHAPTER 20 FACILITIES RESTRICTION LEVEL/TRAVELLING CLASS MARK

Facilities Restriction Level/Travelling Class

Mark

Initiate FRL on Outgoing Routes

General
The FRL/TCM feature makes it possible to selectively restrict use of the private network as well as over-
flow to the public network. Each calling party (for example, a voice or data extension or incoming route)
is assigned a Facilities Restriction Level (FRL) which is passed through the private network from one node
to another as the user's Travelling Class Mark (TCM). In addition, each route choice within a direction to
a given external destination in the private network is also assigned an FRL when initiated.
To be permitted to use a specific route choice, the FRL of the calling party must be higher or equal to the
FRL assigned to the route choice.
NOTE: FRL/TCM is not used for restriction purposes in the originating exchange, as opposed to Priority
routing. Apart from this, the two features are very much alike. See also the parameter description for
APPLICATION SYSTEM parameter PARNUM=106.
FRL/TCM is available for H.323 and ISDN.

52
49/154 31-ANF 901 14 Uen L 2019-10-18
 INITIATE FRL ON OUTGOING ROUTES
CHAPTER 20 FACILITIES RESTRICTION LEVEL/TRAVELLING CLASS MARK

Execution

Measure/Question Observation/ Comment

1 Key the commands EXCAP, See parameter --ext-roc in the

extension_profile-p and command
ROCAP to print the FRLs of the extension_profile -p.
calling parties.

53
49/154 31-ANF 901 14 Uen L 2019-10-18
 REMOVE FRL FROM AN OUTGOING ROUTE
CHAPTER 20 FACILITIES RESTRICTION LEVEL/TRAVELLING CLASS MARK

Measure/Question Observation/ Comment

2 Key the command RODIP to -
print out the existing directions.
3 Key the command RODII to set -
an FRL on an outgoing route
within a direction.
4 Are there any more outgoing -
routes to set FRL on?
5 Key the command RODIE to If YES, return to step 3.
remove the direction.
6 Key the command RODDP to -
print out existing external
destinations.
7 Key the command RODDI to Use the parameter DRN in
initiate the direction with command RODDI.
defined FRLs as route choice to
a destination.
7 Are there any more direction If YES, return to step 7.
with defined FRLs to initiate as
route choice to a destination?

Remove FRL from an Outgoing Route

General
Consider that the direction with FRL routes can be initiated as route choice to more than one external
destination. If this is the case, the influence on these other external destinations has to be taken care of.

Prerequisites
A direction must be initiated as route choice to an external destination.

Execution
1. Key the command RODDP to see if the direction with FRL routes is initiated as route choice to more
than one external destination.
2. Key the command RODDE to remove the direction as route choice to an external destination.
3. Key the command RODIE to remove the direction.

54
49/154 31-ANF 901 14 Uen L 2019-10-18
 ALTER FRL ON AN OUTGOING ROUTE
CHAPTER 20 FACILITIES RESTRICTION LEVEL/TRAVELLING CLASS MARK

4. Key the commands RODDP and RODIP to verify the result.

Alter FRL on an Outgoing Route

General
Consider that the direction with FRL routes can be initiated as route choice to more than one external
destination. If this is the case the influence on these other external destinations has to be taken care of.

Prerequisites
A direction must be initiated as route choice to an external destination.

Execution
1. Key the command RODDP to see if the direction with FRL routes is initiated as route choice to more
than one external destination.
2. Key the command RODIE to remove the previous FRL value.
3. Key the command RODII to set a new FRL value for the route in the direction.
4. Key the command RODIP to verify the result.

Print FRL on Outgoing Routes

Prerequisites
A direction must be initiated as route choice to an external destination.

Execution
1. Key the command RODDP to see which direction an external destination uses as route choice.
2. Key the command RODIP to print out the FRL values of the routes in the direction.

55
49/154 31-ANF 901 14 Uen L 2019-10-18
 INITIATE THE PRIORITY DISCONNECT FEATURE
CHAPTER 21 PRIORITY DISCONNECT OF TRUNK CALLS

Priority Disconnect of Trunk Calls

Initiate the Priority Disconnect Feature

General
The Priority Disconnect feature makes it possible to automatically let prioritized calls disconnect lower
priority calls in case of trunk resource congestion, and thus succeed despite a congestion situation. The
function will of course affect other calls, that will be forced to disconnect, and the users of those discon-
nected calls will experience it as a malfunction of the voice telephony, if not informed of the function.
Each call (primarily from voice extensions or incoming routes) is assigned a priority routing category
called FRL/TCM (see previous section), which will be interpreted as a Call Service Information (CSI), with
three levels; Emergency, Priority and Routine. In addition there are “Normal/Administrator calls”, without
CSI.
The call priority can be set either by CoS for the originator, or be assigned on per call basis, if that function
is activated by O&M personnel. The later option requires the AS parameter 74 to be appropriately set,
and also requires dedicated common abbreviated numbers to be initiated.
The CSI is used in a single node, but also passed through the private network (specific MFC tie-lines,
DPNSS, ISDN, H.323 or SIP) from one node to another. The CSI is conveyed as FRL/TCM values via
tie-lines.
When a call with CSI is attempted, and meets congestion, the CSI of the new call is checked towards the
CSI of an ongoing call, in order to determine if a Priority Disconnect can be done. A call with lowest priority
will be disconnected.
A call with CSI Emergency is allowed to do priority disconnect on all other trunk calls, except on other
Emergency class calls.
A call with CSI Priority is allowed to do Priority Disconnect on Priority, Routine and Normal calls.
A call with CSI Routine is allowed to do Priority Disconnect on other Routine and on Normal calls.
NOTE: The CSI is in this case used as a kind of “forced release” CoS, and not as a restriction to access
trunk resources, as the CSIU described below.

Execution
1. Key the command ASPAC parameter 74 to enable the Priority Disconnect function. There is also in
the same parameter an option to change the ring cadence for analog extensions, see the opera-
tional directions for APPLICATION SYSTEM PARAMETERS.
2. Key the command ASPAP to verify the change.
3. Initiate common abbreviated numbers that match the three CSI levels, if the dynamic CSI on per call
basis is wanted. For details, see operational directions for ABBREVIATED DIALLING.
## (H’BB) equals FRL/TCM value 7, and CSI Emergency. (Highest priority)

56
49/154 31-ANF 901 14 Uen L 2019-10-18
 REMOVE THE PRIORITY DISCONNECT FEATURE
CHAPTER 21 PRIORITY DISCONNECT OF TRUNK CALLS

*# (H’AB) equals FRL/TCM value 6, and CSI Priority.

** (H’AA) equals FRL/TCM value 5, and CSI Routine. (Lowest priority)

Remove the Priority Disconnect feature

General
As described for Initiate the Priority Disconnect feature.

Prerequisites
Priority Disconnect is enabled, but should be disabled/removed.

Execution
1. Key the command ASPAC parameter 74 to disable the Priority Disconnect function.
2. Key the command ASPAP to verify the removal.

Print Priority Disconnect Settings

Prerequisites
The Priority Disconnect feature is supported by the system, but may be either enabled or not.
Execution
1. Key the command ASPAP with parameter 74 to check the Priority Disconnect settings.

57
49/154 31-ANF 901 14 Uen L 2019-10-18
 REMOVE CSIU FROM AN OUTGOING ROUTE
CHAPTER 22 PRIORITY ROUTING

Priority Routing

Remove CSIU from an Outgoing Route

General
Consider that the direction with CSIU routes can be initiated as route choice to more than one external
destination. If this is the case the influence on these other external destinations has to be taken care of.

Prerequisites
A direction with CSIU routes must be initiated as route choice to an external destination.
Execution
1. Key the command RODDP to see if the direction with CSIU routes is initiated as route choice to more
than one external destination.
2. Key the command RODDE to remove the direction as route choice to an external destination.
3. Key the command RODIE to remove the direction.
4. Key the commands RODDP and RODIP to verify the result.

Alter CSIU for an Outgoing Route

General
Consider that the direction with CSIU routes can be initiated as route choice to more than one external
destination. If this is the case the influence on these other external destinations has to be taken care of.

Prerequisites
A direction with CSIU routes must be initiated as route choice to an external destination.
Execution
1. Key the command RODDP to see if the direction with CSIU routes is initiated as route choice to more
than one external destination.
2. Key the command RODIE to remove the previous CSIU value.
3. Key the command RODII to set a new CSIU value for the route in the direction.
4. Key the command RODIP to verify the result.

58
49/154 31-ANF 901 14 Uen L 2019-10-18
 PRINT CSIU FOR OUTGOING ROUTES
CHAPTER 22 PRIORITY ROUTING

Print CSIU for Outgoing Routes

Prerequisites
A direction with CSIU routes must be initiated as route choice to an external destination.

Execution
1. Key the command RODDP to see which direction an external destination uses as route choice.
2. Key the command RODIP to print out the CSIU values of the routes in the direction.

59
49/154 31-ANF 901 14 Uen L 2019-10-18
 CHANGE OF FAULT COUNTERS BY ZERO SETTING
CHAPTER 23 FAULT STATISTICS ON DIGITAL EXTERNAL LINES

Fault Statistics on Digital External Lines

Faults that occur during transmission on a digital external line board can be collected for statistical
purposes.
Only boards with the fault counter services can be used in this command, namely: TLU76(DPNSS/DASS
indexes /2 and /12 only) and TLU77(ISDN T1).

Change of Fault Counters by Zero Setting

General
Before starting a new fault collection of a digital board, all the fault counters on that board should be set
to zero. The zero setting time is stored as a reference.

Prerequisites
-

Execution
Key command ROFCC to reset the fault counters of a digital board.

Printout of Fault Counter Data

General
The behavior of a digital board can be verified by printing out its fault counters which are accumulated
from the last reset. The resetting time is also printed for reference.

Prerequisites
-

Execution
Key command ROFCP to print the fault counters of a digital board.

60
49/154 31-ANF 901 14 Uen L 2019-10-18
 GENERAL
CHAPTER 24 PRINT THE VACANT NUMBERS

Print the Vacant Numbers

General
Before initiating external destinations, a printout of all vacant numbers (of a specified number type and
within specified limits) can be obtained. Numbers that may be of interest are numbers initiated as
-numbertype = ed, ec, and pd (in the number_initate command).

Execution
Key the command vacant_number to obtain a printout of all vacant numbers of a specified number type.

61
49/154 31-ANF 901 14 Uen L 2019-10-18
 GENERAL
CHAPTER 25 PRINT THE FREE EQUIPMENT POSITIONS

Print the Free Equipment Positions

General
Before initiating external lines to a route, a list of available equipment positions for the required type of
line (TL type) should be printed out.

Prerequisites
The relevant TL type must exist in the system.

Execution
Key the command resource_status to obtain a printout of free equipment positions for a specific TL
type.

62
49/154 31-ANF 901 14 Uen L 2019-10-18
 GENERAL
CHAPTER 26 PRINT THE INITIATED EQUIPMENT POSITIONS

Print the Initiated Equipment Positions

General
The command resource_status can be used to find all TL boards in a LIM. The printout will show the
type of board that is initiated for each equipment position in the LIM. The printout can be reduced to only
show TL boards of a specific type.
The command resource_status can also be used to look at a specific equipment position, to find out
what external lines (and the routes they belong to) that are affiliated to that equipment position.
Execution
Key the command resource_status to obtain a printout of initiated equipment positions.

63
49/154 31-ANF 901 14 Uen L 2019-10-18
 GENERAL
CHAPTER 27 NAME ON ROUTE

Name on Route

General
-

Initiate Name on Route

1. Key the command name -i to initiate name on routes.
2. Key the command name -p to verify that the initiation was successful.

Remove Name on Route

1. Key the command name -e to remove name on routes.
2. Key the command name -p to verify that the initiation was successful.

Print Name on Route

Key the command name -p to obtain a printout.

64
49/154 31-ANF 901 14 Uen L 2019-10-18
CHAPTER 28 SIP ROUTE CONFIGURATION WHEN USING WEBRTC CLIENT/GATEWAY

SIP Route Configuration When Using

webRTC Client/Gateway
When setting up incoming SIP trunks you may limit access to the trunks by using incoming firewalls with
TLS or tunneling. You can, and must for security reasons, set up rules for authentication on the trunk inter-
face by using digest credentials (controlled by "401 Unauthorized" or "407 Proxy Authentication
Required").
A major security issue is the implementation of the web pages in the server. If web pages are executed
on the client side and there is no provision in the webRTC server whether the numbers presented on the
page are actually sent to the switch, the client computer can substitute the numbers presented and
thereby the client can call any number.
To verify that the number received in the MX-ONE switch is within specified range, a check must be
performed on the received B-number. Such a check will reduce the possibility of misuse of the trunk in
the incoming calls. To perform this check, it is recommended that you use the "ROCAI:TRAF" parameter
on the incoming route or trunk.
• By using TRAF D7D8 (Traffic connection class), it is possible to limit the devices to which the resulting
call can connect. The Traffic connection class limits the possibility of endpoints connecting to devices
that are forbidden even if endpoints can dial the numbers of such devices. For controlling the allowed
connections, Traffic connection class is used in a matrix, set by the command traffic_matrix -1.
This is an effective way of forbidding transit calls even after transport because, if the resulting connec-
tion is forbidden in the matrix, the call is dropped.
• TRAF D3D4 (TCD category NIGHT for incoming external lines) and TRAF D5D6 (TCD category DAY
for incoming external lines) check the dialed digits together with the number analyses data (TCD/ITK).
Based on this check, you can set tables to limit access to unwanted numbers for a route.
• By using TRAF D1D2 (Abbreviated number traffic Classes) together with RONDI:PRE or number_con-
version_initiate -route x -conversiontype 0 -pre abc, it is possible to lock or limit the
numbers dialed from an external line to a small fixed table within the common abbreviated number
table. The inserted number will be the first part of the common abbreviated number, and the table posi-
tion is determined by the digit received from the trunk. The translated abbreviated number can be any
nternal or external number. In addition, it is possible to add account codes for billing. If this method is
used only the numbers in the abbreviated table can be reached.
• A combination of all methods in ROCAI:TRAF can be used depending on circumstances.

65
49/154 31-ANF 901 14 Uen L 2019-10-18
CHAPTER 29 TERMINATION

Termination
If a route access code for external traffic is altered then the instance (person) responsible for the PBX is
to be informed.
If exchange data have been altered and no more commands are to be keyed a dump to backup media
shall be performed.

66
49/154 31-ANF 901 14 Uen L 2019-10-18
 © Copyright 2019, Mitel Networks Corporation. All Rights Reserved. The Mitel word and logo are trademarks of Mitel Networks
Corporation, including itself and subsidiaries and authorized entities. Any reference to third party trademarks are for reference only and Mitel
mitel.com makes no representation of ownership of these marks.