System Release 8.

DIMETRA™
Dimetra IP Scalable (DIPS)
Dimetra IP Compact (DIPC)/Scalable Dimetra IP (SDIP)

OBJECT CALL

March 2014

*MN000436A01*
MN000436A01-A

© 2014 Motorola Solutions, Inc. All rights reserved

Copyrights
The Motorola products described in this document may include copyrighted Motorola computer programs. Laws in
the United States and other countries preserve for Motorola certain exclusive rights for copyrighted computer
programs. Accordingly, any copyrighted Motorola computer programs contained in the Motorola products described
in this document may not be copied or reproduced in any manner without the express written permission of Motorola.
© 2014 Motorola Solutions, Inc. All Rights Reserved
No part of this document may be reproduced, transmitted, stored in a retrieval system, or translated into any language
or computer language, in any form or by any means, without the prior written permission of Motorola Solutions, Inc.
Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication,
estoppel or otherwise, any license under the copyrights, patents or patent applications of Motorola, except for the
normal non-exclusive, royalty-free license to use that arises by operation of law in the sale of a product.

Disclaimer
Please note that certain features, facilities, and capabilities described in this document may not be applicable to or
licensed for use on a particular system, or may be dependent upon the characteristics of a particular mobile subscriber
unit or configuration of certain parameters. Please refer to your Motorola contact for further information.

Trademarks
MOTOROLA, MOTO, MOTOROLA SOLUTIONS, and the Stylized M Logo are trademarks or registered
trademarks of Motorola Trademark Holdings, LLC and are used under license. All other trademarks are the property
of their respective owners.

European Union (EU) Waste of Electrical and Electronic Equipment (WEEE)

directive

The European Union's WEEE directive requires that products sold into EU countries must have the crossed out
trash bin label on the product (or the package in some cases).
As defined by the WEEE directive, this cross-out trash bin label means that customers and end-users in EU countries
should not dispose of electronic and electrical equipment or accessories in household waste.
Customers or end-users in EU countries should contact their local equipment supplier representative or service centre
for information about the waste collection system in their country.

MN000436A01-A | March 2014 | Send Feedback

CMM Labeling and Disclosure Table
The People’s Republic of China requires that our products comply with China Management Methods (CMM)
environmental regulations. (China Management Methods refers to the Regulation Management Methods for
Controlling Pollution by Electronic Information Products.) Two items are used to demonstrate compliance; the Label
and the Disclosure Table.
The label is placed in a customer visible position on the product. The first of the following examples means that the
product contains no hazardous substances; the second means that the product contains hazardous substances, and has
an Environmental Friendly Use Period (EFUP) of fifty years.

The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxic and Hazardous
Substances (T&HS) contained in the Electronic Information Product (EIP) will not leak or mutate causing
environmental pollution, or bodily injury from the use of the EIP.
The Disclosure Table, printed in simplified Chinese, is included with each customer order. An example of a
Disclosure Table (in Chinese) follows:

MN000436A01-A | March 2014 | Send Feedback

Service Information
Government Technical Support (GTS), EA Solutions Support Centre
The Government Technical Support (GTS), EA Solutions Support Centre provides a remote Technical Support
Service to help customers resolve technical issues and quickly restore networks and systems. This team of highly
skilled professionals is available to customers with current service agreements in place that include the Technical
Support Service. The EA GTS technical experts may be accessed through the EMEA Integrated Call Center either
electronically or using the telephone numbers listed below. If you are unsure whether your current service agreement
entitles you to benefit from this service, or if you would like more information about the Technical Support Service,
contact your local customer support or account manager for further information.

Contact Details
Email: essc@[Link]

Table 1: List of Telephone Numbers

Country In Country Number to Dial

AUSTRIA 01206091087
DENMARK 043682114
FRANCE 0157323434
GERMANY 06950070204
ITALY 0291483230
LITHUANIA 880 030 828
NETHERLANDS 0202061404
NORWAY 24159815
PORTUGAL 0217616160
RUSSIA 810 800 228 41044
(Alternative 810 800 120 1011)
SAUDI ARABIA 800 844 5345
SOUTH AFRICA 0800981900
SPAIN 0912754787
UNITED KINGDOM 02030 277499
All Other Countries +44 2030 277499

European Systems Component Centre (ESCC)

The European Systems Component Centre provides a repair service for infrastructure equipment. Customers requiring
repair service should contact the Customer Information Desk to obtain a Return Material Authorization number. The
equipment should then be shipped to the following address unless advised otherwise.
Motorola GmbH, European Systems Component Centre, Am Borsigturm 130,13507 Berlin, Germany

Contact Details
• E-Mail: [Link]@[Link]

MN000436A01-A | March 2014 | Send Feedback

8 | Service Information

• Telephone: +49 (0) 30 66861404

• Telefax: +49 (0) 30 66861426
• Monday – Friday 08:00 am to 06:00 pm (CET)

Parts Identification and Ordering

Request for help in identification of non-referenced spare parts should be directed to the Customer Care Organization
of Motorola’s local area representation. Orders for replacement parts, kits, and assemblies should be placed directly
on Motorola’s local distribution organization or through the Extranet site Motorola Online at https://
[Link].

Updated Versions of Manuals

Verify the current version of the manual at our Extranet site, Motorola Online: https://
[Link].

Your Input
Send questions and comments regarding user documentation to documentation@[Link]
We welcome your feedback on this and other Motorola manuals. To take a short, confidential survey on Motorola
Customer Documentation, go to [Link] or scan the following QR code with your mobile
device to access the survey.

Send Feedback | March 2014 | MN000436A01-A

Document History
Edition Description Date
MN000436A01–A Initial Version Mar. 2014

MN000436A01-A | March 2014 | Send Feedback

 Contents | 11

Contents
Copyrights........................................................................................................................................ 3
CMM Labeling and Disclosure Table............................................................................................5
Service Information......................................................................................................................... 7
Document History............................................................................................................................ 9
List of Figures................................................................................................................................ 13
List of Tables.................................................................................................................................. 15
List of Processes............................................................................................................................. 17
List of Procedures.......................................................................................................................... 19
About Object Call.......................................................................................................................... 21
What Is Covered In This Manual?...................................................................................................................... 21
Helpful Background Information........................................................................................................................ 21
Related Information.............................................................................................................................................21
Icon Conventions.................................................................................................................................................22
Style Conventions................................................................................................................................................22

Chapter 1: Feature Overview................................................................................25

Object Call Feature Introduction.........................................................................................................................25
Object Call Terminology.....................................................................................................................................27
Object Group Numbering....................................................................................................................................28
Numbering Scheme Overview................................................................................................................ 28
Talkgroup/Multigroup Creation Overview............................................................................................. 29
Talkgroup/Multigroup Deletion/Deactivation Overview........................................................................30
Object Group Attachment Request......................................................................................................................30
Temporary Object Call........................................................................................................................................31
Object Group Call............................................................................................................................................... 32

Chapter 2: Configuration and Optimization....................................................... 33

Object Call Feature Initial Configuration............................................................................................................33
Opening the UCM Main Window....................................................................................................................... 33
Defining Object Call Parameter Values and Activating the Feature...................................................................35
Modifying Object Call Feature Parameter Values.............................................................................................. 37
Object Group Subject Configuration...................................................................................................................39
Creating an Object Group Subject ..........................................................................................................40
Modifying Parameter Values for an Object Group Subject.................................................................... 44
Deleting an Object Group Subject...........................................................................................................47
Object Group Instance Configuration................................................................................................................. 47
Creating an Object Group Instance......................................................................................................... 48
Modifying Parameter Values for an Object Group Instance...................................................................51
Deleting an Object Group Instance......................................................................................................... 53

Chapter 3: Troubleshooting.................................................................................. 55
Object Call Monitoring....................................................................................................................................... 55
Rejected Object Calls.......................................................................................................................................... 55
User Configuration Manager Object Call Troubleshooting................................................................................ 56
12 | Contents
 List of Figures | 13

List of Figures
Figure 1: Airport Workgroups Servicing a Flight .......................................................................... 26
Figure 2: Windows Explorer .......................................................................................................... 34
Figure 3: UCM Main Window ....................................................................................................... 34
Figure 4: Object Group Definition – Basic Tab ............................................................................. 35
Figure 5: Object Group Definition – Configuration Tab ................................................................36
Figure 6: Object Group Definition – Basic Tab ............................................................................. 38
Figure 7: Object Group Definition – Configuration Tab ................................................................38
Figure 8: Object Group Subject – Basic Tab ..................................................................................41
Figure 9: Object Group Subject – Basic Tab ..................................................................................41
Figure 10: Object Group Subject – Configuration Tab .................................................................. 42
Figure 11: Object Group Subject – Configuration Tab .................................................................. 43
Figure 12: Object Group Subject – Basic Tab ................................................................................44
Figure 13: Object Group Subject – Basic Tab ................................................................................45
Figure 14: Object Group Subject – Configuration Tab .................................................................. 46
Figure 15: Object Group Subject – Configuration Tab .................................................................. 46
Figure 16: Object Group Instance – Basic Tab ...............................................................................48
Figure 17: Object Group Instance – Basic Tab ...............................................................................49
Figure 18: Object Group Instance – Configuration Tab ................................................................. 50
Figure 19: Object Group Instance – Configuration Tab ................................................................. 50
Figure 20: Object Group Instance – Basic Tab ...............................................................................51
Figure 21: Object Group Instance – Basic Tab ...............................................................................52
Figure 22: Object Group Instance – Configuration Tab ................................................................. 52
Figure 23: Object Group Instance – Configuration Tab ................................................................. 53
14 | List of Figures
 List of Tables | 15

List of Tables
Table 1: List of Telephone Numbers ................................................................................................ 7
Table 2: Airport Workgroups Servicing a Flight – Figure Explanation ......................................... 26
Table 3: Object Call Feature Terms and Definitions ......................................................................27
Table 4: Object Call Results ........................................................................................................... 55
Table 5: Object Call Feature – UCM Troubleshooting .................................................................. 56
16 | List of Tables
List of Processes
Object Call Feature Initial Configuration ....................................................................................... 33

MN000436A01-A | March 2014 | Send Feedback

List of Procedures
Opening the UCM Main Window .................................................................................................. 33
Defining Object Call Parameter Values and Activating the Feature .............................................. 35
Modifying Object Call Feature Parameter Values ..........................................................................37
Creating an Object Group Subject .................................................................................................. 40
Modifying Parameter Values for an Object Group Subject ............................................................44
Deleting an Object Group Subject .................................................................................................. 47
Creating an Object Group Instance .................................................................................................48
Modifying Parameter Values for an Object Group Instance .......................................................... 51
Deleting an Object Group Instance .................................................................................................53

MN000436A01-A | March 2014 | Send Feedback

About Object Call
This document provides detailed information about the Object Call feature. The objective is to provide users with a
detailed description of this feature, its operation and configuration.

What Is Covered In This Manual?

This document covers the following chapters:
• Feature Overview on page 25. Provides a description of the Object Call feature, its usage operation in the radio
system.
• Configuration and Optimization on page 33. Presents the procedures for the configuration of the Object Call
feature objects in User Configuration Manager application.
• Troubleshooting on page 55. Provides troubleshooting information of the Object Call feature errors that may
appear during its configuration.

Helpful Background Information

Motorola offers various courses designed to assist in learning about the system. For information, go to http://
[Link]/training to view the current course offerings and technology paths.

Related Information
In addition to the information in the table below, see the Related Information Guide.

Related Information Description

Glossary The glossary provides a list of abbreviations, acronyms and terms used in the
Dimetra IP system documentation.
Documentation Overview The document provides a list of all documents delivered with your Dimetra
IP system. Its primary purpose is to help you to find the information you are
looking for.
System Overview This manual provides basic radio system concepts, call processing basics,
and an introduction to the various components and processes associated with
the Dimetra IP system. The manual provides the background needed to
comprehend the theory of operation and it provides equipment/subsystem
functional descriptions. It also describes the role of the numerous network
management software applications used for managing the system.
Barring of Incoming Calls/ This manual provides detailed description of the Barring of Incoming Calls/
Barring of Outgoing Calls Barring of Outgoing Calls (BIC/BOC) feature, as well as information on how
(BIC/BOC) to enable and initially configure the feature and troubleshoot problems.
User Configuration This manual describes the User Configuration Manager (UCM) which is a
Manager Windows based, Private Radio Network Management (PRNM) Suite
application. The UCM is used in the configuration of the system. It is also
Table continued…

MN000436A01-A | March 2014 | Send Feedback

22 | About Object Call

Related Information Description

the tool used to modify configuration parameters. To configure a system,
both the UCM and the Zone Configuration Manager (ZCM) are needed.
UCS Synchronization Tool This manual describes the User Configuration Server (UCS) Synchronization
Manual Tool, which provides automated intercluster configuration of some of the
UCS objects that require to be registered in all clusters in a multicluster
system.
Backup and Restore This volume describes the system backup and restoration procedures and
Including FRU/FRE their impact on the services as well as pre and post-restoration checks. The
volume also describes how to perform FRU/FRE procedures.

Icon Conventions
The documentation set is designed to give the reader more visual clues. The following graphic icons are used
throughout the documentation set. These icons and their associated meanings are described below.
Danger: The signal word DANGER with the associated safety icon implies information that, if
disregarded, will result in death or serious injury.
Warning: The signal word WARNING with the associated safety icon implies information that, if
disregarded, could result in death or serious injury, or serious product damage.
Caution: The signal word CAUTION with the associated safety icon implies information that, if
disregarded, may result in minor or moderate injury, or serious product damage.
Caution: The signal word CAUTION may be used without the safety icon to state potential damage or
injury that is not related to the product.
Important: IMPORTANT statements contain information that is crucial to the discussion at hand, but is
not CAUTION or WARNING. There is no warning level associated with the IMPORTANT statement.

Note: NOTE contains information more important than the surrounding text, such as exceptions or
preconditions. They also refer the reader elsewhere for additional information, remind the reader how to
complete an action (when it is not part of the current procedure, for instance), or tell the reader where
something is located on the screen. There is no warning level associated with a note.
Suggestion: SUGGESTION implies a recommendation or tip from Motorola that does not require to be
followed, but might be helpful. There is no warning level associated with SUGGESTION.

Style Conventions
The following style conventions are used:

Convention Description
Bold This typeface is used for names of, for instance, windows, buttons, and labels when
these names appear on the screen (example: the Alarms Browser window). When
it is clear that we are referring to, for instance, a button, the name is used alone
(example: Click OK).
Monospacing font in This typeface is used for words to be typed in exactly as they are shown in the text
bold (example: In the Address field, type [Link]
Table continued…

Send Feedback | March 2014 | MN000436A01-A

 About Object Call | 23

Convention Description
Monospacing font This typeface is used for messages, prompts, and other text displayed on the
computer screen (example: A new trap destination has been
added).
<Monospacing font in This typeface is used with angle brackets for words to be substituted by a specific
bold Italic> member of the group that the words represent (example: <router number>).
Note: In sequences to be typed in, the angle brackets are omitted to
avoid confusion as to whether the angle brackets are to be included in
the text to be typed.

CAPITAL LETTERS This typeface is used for keyboard keys (example: Press Y, and then press
ENTER).
Italic This typeface is used citations. This can be the name of a document or a phrase
from another document (example: Dimetra IP System Overview).
→ An → (arrow pointing right) is used for indicating the menu or tab structure in
instructions on how to select a certain menu item (example: File → Save) or a
certain sub-tab.

MN000436A01-A | March 2014 | Send Feedback

Chapter

1
Feature Overview
This chapter provides an overview of the Object Call feature and its operation. The feature is licensed, and it must be
activated for its operation to take effect. For licensing details, refer to the Backup and Restore Including FRU/FRE
volume.

Object Call Feature Introduction

The Object Call feature in a radio system allows radio users to communicate with each other using talkgroups that are
not programmed in the radio. A user on a radio terminal has the possibility to call an object or attach to groups related
to the object. It is also possible to create a group call towards a talkgroup to which the radio is not attached.
The feature is applicable in an organization with a dynamic usage of a high number of talkgroups where it is not
possible to pre-program all the necessary talkgroups in the radios. The users can instead call an object and be
connected to the necessary talkgroup(s).
An example may be an airport system, where different functions carried out at the airport are linked to flights (that is
objects), resulting in a flight-oriented communication system. When an airplane is arriving at an airport gate, different
resources are necessary to service this flight, and for communication purposes these resources are grouped following
a structure of flights and functional groups. The following could be formed:
• one talkgroup per flight number,
• one talkgroup per workgroup/function such as catering, cleaning, ground service, gate service,
• one talkgroup per workgroup/function around a specific plane identified by the flight number.
When radio users move from one task to the next (identified by a new flight number), the radio user must call a new
object and get attached to new talkgroups.
Another example could be a railway company where it may be preferred to have a talkgroup per route and per tour.
When the radio user moves from one route/tour to the next, then he or she may attach to the new talkgroups.
Talkgroups defined for the use of the Object Call feature are called Object Groups.
An Object Group is defined based on a two-dimensional structure. The dimensions are called Subject and Instance.
Following the example of an airport environment, the flight number is the Subject, and each workgroup serving this
flight is an Instance. In such scenario, a user has the possibility of communicating with the following objects dialing a
specific number. If we have flight number 123, and workgroups like: 03: Catering, 04: Baggage, then a radio user
can dial and communicate with the following resources:
• 12303 – identifies a catering group on flight 123;
• 12300 – identifies all workgroups on flight 123 (00 is the Instance wildcard);
• 00004 – identifies the baggage group for all flights (000 is the Subject wildcard).
Therefore, the Object Call feature provides the possibility of addressing all workgroups working on a flight, persons
working within a particular function on a specific flight or all persons connected to a specific function in the airport
(in the example above – the baggage workgroup). For more details, on how the dialed numbers are formed see Object
Group Numbering on page 28 and its subsections.
The following figure presents an example of the Object Call operation.

MN000436A01-A | March 2014 | Send Feedback

26 | Feature Overview

Figure 1: Airport Workgroups Servicing a Flight

8 234

7
1

6 123

Table 2: Airport Workgroups Servicing a Flight – Figure Explanation

Annotation Description
1 Flight no. 123 serviced by workgroups marked in gray.
2 Flight no. 234 serviced by workgroups marked in orange.
3 Catering workgroup servicing flight no. 123, and flight no. 234 that has departed.
4 Baggage workgroup servicing flight no. 123.
5 Petrol workgroup servicing flight no. 123, and flight no. 234 that has departed.
6 Ground Service workgroup servicing flight no. 123.
7 Gate Service workgroup servicing flight no. 123, and flight no. 234 that has departed.
8 Airfield Operations workgroup servicing flight no. 123, and flight no. 234 that has
departed.

The Object Call feature makes use of the Object Group Call (see Object Group Call on page 32), and consists of an
Object Group Attachment Request, and a Temporary Object Call.

Send Feedback | March 2014 | MN000436A01-A

 Feature Overview | 27

An Object Group Attachment Request is a call initiated towards the Object in which the radio user can request
talkgroup attachment to an Object Group. Such request makes it possible to attach talkgroups/multigroups which are
not statically programmed in the radio (see Object Group Attachment Request on page 30).
A Temporary Object Call is a possibility to do a free-dialing group call towards an Object Group. By making a
Temporary Object Call it is possible to communicate with a talkgroup without attaching to the talkgroup (see
Temporary Object Call on page 31).

Object Call Terminology

Table 3: Object Call Feature Terms and Definitions

Term Description
Object Used to determine a subject, a task, a mission, or a workgroup identified by a
talkgroup number. The object is addressed in the radio system with an ID.
The following are examples of an object:
• a bus line
• a specific tour on a bus line
• a flight
• a workgroup
• a specific workgroup working on a determined flight
The number that identifies an object is composed of two dimensions:
• Subject – could represent bus lines or flight numbers.
• Instance – could represent workgroup or tours.

Object Groups Indicates a talkgroup which can be dynamically provisioned in the radio or it
can be called from a radio which does not have the talkgroup programmed in
the radio. Object Groups in the radio system are identified by a talkgroup ID
(referred to as the Group Short Subscriber Identity – GSSI).
Object Groups are defined based on a two-dimensional structure consisting
of Subjects and Instances, and of the Object Group prefix (OGp). The
following are examples:
• <OGp><Subject><Instance>
• <OGp><Subject><Instance wildcard>
• <OGp><Subject wildcard><Instance>
The Object Group <OGp><Subject><Instance wildcard> is
defined as a multigroup consisting of all Object Groups related to the same
Subject.
For more information, refer to the Object Group Numbering on page 28.
Object Number Indicates a number which is used to identify an object in the radio system.
An <object number> is one of the following:
• <Subject><Instance>
• <Subject><Instance wildcard>
• <Subject wildcard><Instance>

Object Group Attachment Indicates a radio user request for dynamic provisioning and afterwards
Request attachment to Object Groups. Such request makes it possible to attach
Table continued…

MN000436A01-A | March 2014 | Send Feedback

28 | Feature Overview

Term Description
talkgroups/multigroups which are not statically provisioned in the radio. See
Object Group Attachment Request on page 30 for more details.
Object Group Call Indicates a group call or a multigroup call towards an Object Group. See
Object Group Call on page 32 for more details.
Temporary Object Call Indicates a type of Object Call, where the user initiates a group call towards
an Object Group that may not be programmed in the radio prior to the call.
Note: It is only possible to make Temporary Object Calls towards
talkgroups which are classified as Object Groups.

See Temporary Object Call on page 31 for more details.

Object Group Numbering

An Object Group identifies a talkgroup that can be dynamically configured in the radio, or it can be called from a
radio that does not have the talkgroup programmed. An Object Group in the radio system is identified by a talkgroup
ID, referred to as the Group Short Subscriber Identity (GSSI).
When a radio user wants to deliver a message to a specific talkgroup, he or she dials a determined number. Therefore,
for the use of the Object Call feature specific numbering rules have been defined for the called Object Group (see
Numbering Scheme Overview on page 28 for more details). The Object Group number consists of a two-
dimensional structure. The dimensions are the Subject and the Instance. For example, in an airport environment such
structure gives the possibility to distinguish between different groups working with the same subject.
A Subject could represent a flight number or a bus line.
An Instance could represent specific workgroups or tours.
The combination of the Subject and Instance are:
• <Subject><Instance> – a number identifying a specific subject and instance.
• <Subject><Instance wildcard> – a number identifying all instances of a specific subject.
• <Subject wildcard><Instance> – a number identifying a specific instance across all subjects.
An example could be an airport environment, where several workgroups need to communicate with each other and
are necessary to prepare a flight. In this case, the flight number is the Subject, and each workgroup serving this flight
is an Instance. If the following flights (Subjects) and workgroups (Instances) are identified, then the call variations
provided below are possible:
• Flight No. 123
• Flight No. 234
• 01: Baggage
• 02: Catering
• 03: Cleaning
The object number 12301 identifies the baggage group on flight number 123.
The object number 23400 identifies all workgroups on flight 234, where 00 is the Instance wildcard.
The object number 00003 identifies the cleaning group where 000 is the Subject wildcard.

Numbering Scheme Overview

When a radio user makes a call related to an Object Call, the dialed number consists of the following:

Send Feedback | March 2014 | MN000436A01-A

 Feature Overview | 29

• A prefix indicating if a call is an object group attachment request or a temporary object call request; 1–2 digits
when feature is activated;
• An Object Number consisting of the following:
• Subject (1–5 digits),
• Instance (1–5 digits).
The maximum number of digits of a dialed number is 8.
In case the number of digits is 8, then the prefix could be of the following: 01, 02...10,11,12,13.
In case the number of digits is less than 8, then the prefix could be of the following: 01..99.
Note: Prefixes, Subjects, and Instances have a fixed number length and are configured in the User
Configuration Manager (UCM) application on the Object Group Definition object.

The prefixes mentioned above identify what type of an object call has been initiated by the user. The following two
are distinguished:
• Object Group prefix <OGp> – used to determine an Object Group Attachment Request. It is displayed on the
radio when the group is programmed in the radio and the radio affiliates to the talkgroup. In addition, it is also
shown in the Talkgroup list.
• Temporary Object Call prefix <TOCp> – used to determine a Temporary Object Call. It does not require the
called talkgroups to be provisioned in the radio.
Note: Prefix <OGp> and <TOCp> is configured in UCM on the Object Group Definition object.

In this way the prefixes, and Object Numbers (Subjects and Instances) configured in UCM, determine the following
Object Groups:
• <OGp><Subject><Instance>
• <OGp><Subject><Instance wildcard>
• <OGp><Subject wildcard><Instance>
The following Short Subscriber Identities (SSI) cannot be used as Individual Short Subscriber Identity (ISSI) and
Group Short Subscriber Identity (GSSI):
• <TOCp><Subject><Instance>
• <TOCp><Subject><Instance wildcard>
• <TOCp><Subject wildcard><Instance>
The result of calls made towards the object group numbers is presented in Table 4: Object Call Results on page 55.

Talkgroup/Multigroup Creation Overview

Talkgroups and multigroups related to the Object Call are created when the Object Group Subject and Object Group
Instance are configured in UCM. Configuring these objects in UCM results in generation of talkgroups and
multigroups visible on the Talkgroup and Multigroup object search list. However, this generation is executed only
when the Subjects and Instances have been created and activated in UCM.
Activation of the Subjects is done on the Object Group Subject – Basic tab, by setting the Subject Activated
parameter to Yes.
Activation of the Instances is done on the Object Group Instance – Basic tab, by setting the Instance Activated
parameter to Yes.
For each activated in this way Subject and each activated Instance, a set of talkgroups is created based on the OGp,
Subject, and Instance configured in UCM. Every combination of the OGp, Subject, and Instance is created, and the
talkgroups have the same properties as specified for the Subject. The talkgroup is immediately enabled.
The alias for talkgroups is a combination of the alias for the Subject and the alias for the Instance following the rules
below:

MN000436A01-A | March 2014 | Send Feedback

30 | Feature Overview

• Alias for <OGp><Subject><Instance> is <Subject alias>&<Instance alias>.

When a new Instance is created and activated, the result is that a new talkgroup is automatically created for each
Subject. The multigroup for each Subject is updated accordingly.
For each activated Subject a multigroup is created based on the OGp, Subject and Instance wildcard. The multigroup
includes all the Object Groups including the same Subject, and has the same properties as specified for the Subject.
The alias for the multigroup is as follows:
• Alias for <OGp><Subject><Instance wildcard> is <Subject alias>&0.
All created multigroups are visible in the Multigroup search list, but they are only editable from the Object Group
Definition and Object Group Subject objects in UCM.
For each activated Instance a talkgroup is created based on OGp, Subject wildcard and Instance. All talkgroups are
visible in the Talkgroup search list, but they are only editable from the Object Group Definition and Object Group
Instance objects in UCM.
The alias for the talkgroup <OGp><Subject wildcard><Instance> is 0&<Instance alias>.
Note: During creation of the Subjects and Instances, the only difference in configuration is the Interrupt
or Wait Mode parameter. It is only valid for the Object Group Subject, and takes effect only for the
multigroup <OGp><Subject><Instance wildcard>.

Talkgroup/Multigroup Deletion/Deactivation Overview

Talkgroups and multigroups related to the Object Call can be removed from the system using the UCM application.
Removal is done by performing the deletion, or deactivation of the Object Group Subject/Object Group Instance.
Object Groups (talkgroups and multigroups) can be deleted by:
• deactivation of an Object Group Subject or
• deactivation of an Object Group Instance.
The Object Groups are easily recreated by activating an Object Group Subject or an Object Group Instance. Using the
possibility to activate and deactivate Object Group Subjects and Object Group Instances makes it possible to limit the
number of talkgroups. Deactivation of an Object Group Subject is done on the Object Group Subject – Basic tab, by
setting the Subject Activated parameter to No. The same procedure is available for the Object Group Instance
(Instance Activated parameter must be set to No).
Object Groups (talkgroups and multigroups) can be permanently deleted by:
• deletion of an Object Group Subject (see Deleting an Object Group Subject on page 47),
• deletion of an Object Group Instance (see Deleting an Object Group Instance on page 53).
When a Subject is deactivated or deleted, all the talkgroups including the Subject and the multigroup for the Subject
are deleted.
When an Instance is deactivated or deleted, the result is that talkgroups including this Instance are deleted for each
Subject. The multigroup for each Subject is updated.

Object Group Attachment Request

In the Object Call feature, radio users may request talkgroup attachment to Object Groups they are not a member of.
This is possible due to the Object Group Attachment Request which allows to attach talkgroups/multigroups that are
not statically programmed in the radio. Such request is initiated when a radio user makes a call towards the
determined Object Group by dialing the <OGp><Subject><Instance> and pressing the push-to-talk button. The prefix
(OGp) along with the length of digits of the Subject and Instance are configured in UCM on the Object Group
Definition object. The object numbers (Subject and Instance) are configured on the Object Group Subject, and Object
Group Instance objects.

Send Feedback | March 2014 | MN000436A01-A

 Feature Overview | 31

For example, if a user dials 512301, where

• 5 – indicates the Object Group Attachment Request configured in UCM,
• 123 – indicates the flight number,
• 01 – indicates a baggage workgroup,
then the attachment will be made to the talkgroup used to determine the baggage group on flight number 123.
It is not possible to perform on Object Group Attachment Request towards Object Groups containing a wildcard, such
calls are rejected.
When an Object Group Attachment Request is made, the Switching and Management Infrastructure (SwMI) based on
the called Object Group dynamically provisions a set of talkgroups/multigroups in the radio.
In detail, the SwMI performs the following when such request is initiated:
• checks if the user is allowed to call the object (for details see the Barring of Incoming Calls/Barring of Outgoing
Calls (BIC/BOC) manual),
• removes previously provisioned object groups from the radio,
• dynamically provisions the following groups in the radio:
• <OGp><Subject><Instance> – as the selected group and in the scan list.
• <OGp><Subject wildcard><Instance> in the scan list of a radio.
• <OGp><Subject><Instance wildcard> in the scan list of a radio.
When Object Groups are provisioned in the radio, the radio user can remain on the automatically selected Object
Group or switch the talkgroup or make a telephone call or a private call while the dynamically provisioned talkgroups
remain in the scan list of a radio.
The Object Group Attachment Request is reported on the Multi-Computer Aided Dispatch Interface (MultiCADI) and
Air Traffic Information Access (ATIA) Log Viewer applications as a private call request and termination.

Temporary Object Call

A Temporary Object Call is a type of an Object Call where a user can perform a free-dialing group call towards an
Object Group. By making a Temporary Object Call it is possible to communicate with a talkgroup without attaching
to the talkgroup.
A Temporary Object Call is only possible towards a talkgroup classified as Object Groups.
The Temporary Object Call processing is initiated when a user dials the <TOCp><Object Number> and presses the
push-to-talk button, where the <Object Number> can be as follows:
• <Subject><Instance>
• <Subject><Instance wildcard>
• <Subject wildcard><Instance>
When the Temporary Object Call is made by a user, the SwMI performs the following:
• checks if the user is allowed to make group calls,
• checks if the user is allowed to call the object (for details see the Barring of Incoming Calls/Barring of Outgoing
Calls (BIC/BOC) manual).
As a result, if a group call has not yet been established for the called Object Group, then a group call is set by the
SwMI, and the calling radio user is able to deliver the message.
If a group call is already established, the radio user – as determined by the audio interrupt rules - either joins the
group as a listener or interrupts the current speaker. As soon as no one is transmitting, the user can deliver the
message.

MN000436A01-A | March 2014 | Send Feedback

32 | Feature Overview

The radio participates in the group call until the call is terminated or the radio user presses the OnHook/OffHook/
EndCall button (dependent on the radio model).
As the radio is not attached to the talkgroup the radio user will not be involved in any succeeding group call on this
talkgroup.
The Temporary Object Call is reported on the Multi-Computer Aided Dispatch Interface (MultiCADI) and Air Traffic
Information Access (ATIA) Log Viewer applications as a group call.

Object Group Call

An Object Group Call designates any group call on an object group initiated by a radio or by a console. The radio user
or a console is able to participate in a group call on any of the provisioned talkgroups/multigroups.
Initiation and termination of Object Group Calls is reported on the Multi-Computer Aided Dispatch Interface
(MultiCADI) and Air Traffic Information Access (ATIA) Log Viewer applications as a group call based on the
talkgroup/multigroup number.
Note: A successful Object Group call towards an Object Group <OGp><Subject wildcard><Instance>
mainly depends on the requested Sites defined for the Instance. Only radios which fulfill the following can
receive calls:
• radios having the talkgroup <OGp><Subject wildcard><Instance> as the selected talkgroup,
• radios scanning the talkgroup on the requested Sites.
Radios only scanning the talkgroup on other sites may not receive the call.

Send Feedback | March 2014 | MN000436A01-A

Chapter

2
Configuration and Optimization
The following topics provide configuration information for the Object Call feature using the User Configuration
Manager application.

Object Call Feature Initial Configuration

Note:
• Configuration of the Object Call feature is only possible if a license has been purchased and is enabled,
otherwise the related object groups are grayed out. The feature must be activated for its operation to
take effect.
• The system also allows you to create the Object Group Subjects, and Object Group Instances before
activating the Object Call feature. However, the configuration will take effect only when the feature is
activated (the Activated parameter on the Object Group Definition – Basic Tab must be set to Yes).
In such case, it is suggested to check that the parameters previously defined for the Object Groups are
the ones that are necessary for your system before creating the Subjects and Instances.
Process:
1 Start the User Configuration Manager (UCM) application. See Opening the UCM Main Window on page 33.
2 Set the parameter values of the Object Call, and activate the Object Call feature. See Defining Object Call
Parameter Values and Activating the Feature on page 35.
Note: One Object Group Definition record is created during initial system configuration, therefore
default parameter values have been already defined. If you want to change the initially defined values,
see Modifying Object Call Feature Parameter Values on page 37, as edition can only be done when
no Subjects nor Instances have been created.
3 Make sure you have the Home Zone Maps configured in the User Configuration Manager, as they must be created
and submitted before creating an Object Group Subject, and Object Group Instance. For details on Home Zone
Mapping configuration, refer to the User Configuration Manager manual.
4 Start the UCS Synchronization Tool (UST), and synchronize the Object Group Definition object across all clusters
for your system. See the UCS Synchronization Tool manual.
5 Create the Object Group Subject object. See Creating an Object Group Subject on page 40.
6 Create the Object Group Instance object. See Creating an Object Group Instance on page 48.

Opening the UCM Main Window

Procedure:
1 Double-click the Motorola Private Radio Network Management (PRNM) Suite Application Launcher icon on the
desktop.
The Windows Explorer window appears.

MN000436A01-A | March 2014 | Send Feedback

34 | Configuration and Optimization

Figure 2: Windows Explorer

Note: In a multicluster system, you are only able to see the cluster that you have logged in to.

2 Double-click User Configuration Manager.

The UCM main window appears.

Figure 3: UCM Main Window

Send Feedback | March 2014 | MN000436A01-A

 Configuration and Optimization | 35

Defining Object Call Parameter Values and Activating the Feature

The Object Call feature is activated using the UCM application, on the Object Group Definition object. Activate the
feature to communicate with talkgroups/multigroups that are not necessarily pre-programed in your radio. Activation
is possible if a dedicated license feature has been purchased and is enabled in the system, otherwise the object is
grayed out.
One default Object Group Definition record is created during initial system configuration with default values, which
can be modified (see Modifying Object Call Feature Parameter Values on page 37) at any time unless the Object
Group Subject/Instance have been previously configured.
Note: Object Group Definition record cannot be added nor deleted.

Prerequisites: You have launched the User Configuration Manager (UCM) application on the NM Client PC.
Procedure:
1 In UCM, select the Subscribers → Object Group Definition object.
In the contents pane of the UCM one object group record is available — Object Group Parameters. This record
is created by default during the initial system configuration.
2 Right-click the created Object Group Parameters record, and from the pop-up window select Open.
The Object Group Definition configuration window appears.

Figure 4: Object Group Definition – Basic Tab

3 Select the Configuration tab of the Object Group Definition configuration window.
The Configuration tab window appears.

MN000436A01-A | March 2014 | Send Feedback

36 | Configuration and Optimization

Figure 5: Object Group Definition – Configuration Tab

4 In the Length of Prefix field, enter the number of digits used for prefixes of the object group attachment request
or a temporary object call request. The available range is 1– 2 digits, when the feature is enabled (not necessarily
activated).
5 In the Object Group Prefix field, enter the value of the Object Group (<OGp>). The value ranges are as follows,
when the Object Call feature is enabled (not necessarily activated):
• If the Length of Prefix is 1, select <OGp> from the range 1–9.
• If the Length of Prefix is 2, and the total number of digits is less than 8 (Length of Prefix + Length of Subject
+ Length of Instance), select <OGp> from the range 01–99.
• If the Length of Prefix is 2, and the total number of digits is 8, select <OGp> from the range 01–13.
Note: The Object Group Prefix must have a different value than the Temporary Object Call Prefix.

6 In the Temporary Object Call Prefix field, enter the value of the Temporary Object Call. The value ranges are as
follows, when the Object Call feature is enabled (not necessarily activated):
• If the Length of Prefix is 1, select <TOCp> from the range 1–9.
• If the Length of Prefix is 2, and the total number of digits is less than 8 (Length of Prefix + Length of Subject
+ Length of Instance), select <TOCp> from the range 01–99.
• If the Length of Prefix is 2, and the total number of digits is 8, select <TOCp> from the range 01–13.
Note: The Object Group Prefix must have a different value than the Temporary Object Call Prefix.

7 In the Length of Subject field, enter the total number of digits used for the Subject ID. The value ranges are 1–5;
the default value is 4 after initial system configuration.
Note: The sum of the Length of Subject and Length of Instance must be less than or equal to 6,
otherwise an error appears.

8 In the Length of Instance field, enter the total number of digits used for the Instance ID. The value ranges are 1–
5; the default value is 2 after the initial system configuration.

Send Feedback | March 2014 | MN000436A01-A

 Configuration and Optimization | 37

Note: The sum of the Length of Subject and Length of Instance must be less than or equal to 6,
otherwise an error appears.

9 Click Apply.
Parameter values have been set, and configuration information has been saved.
10 Select the Basic tab, and for the Activated parameter select Yes.
Note:
• The Object Call feature can be activated only if a dedicated license has been purchased and is
enabled. For licensing details, refer to the Backup and Restore Including FRU/FRE volume. Once
the feature is enabled and activated, its operation takes effect.
• Additionally, you may change the values of parameters on the Configuration tab until no Subjects
or Instances have been created, and regardless whether the feature is activated/deactivated. Default
values are configured during the initial system configuration. When the Subjects and Instances have
been configured, the parameter fields for the Object Group Definition are grayed out.
11 Click Apply.
Information has been saved and the Object Call Feature has been activated.

Post requisites:
Important: Before creating an Object Group Subject or an Object Group Instance, the Object Group
Definition must be synchronized across all clusters in the system. For synchronization details, see the UCS
Synchronization Tool manual.

Modifying Object Call Feature Parameter Values

Note:
Modification of the Object Call feature parameters is only possible if a dedicated license has been
purchased and is enabled in the system, otherwise the object is grayed out.
Modification of an Object Group Definition parameter is possible regardless whether the feature is
activated or deactivated. However, the feature must be activated for the applied modification to take effect.
Prerequisites: You have launched the User Configuration Manager (UCM) application on the NM Client PC.
Procedure:
1 In UCM, select Subscribers → Object Group Definition, and right-click the initially created record (Object
Group Parameters) and choose the Open menu item.
The Object Group Definition configuration window appears.

MN000436A01-A | March 2014 | Send Feedback

38 | Configuration and Optimization

Figure 6: Object Group Definition – Basic Tab

Note: One default record of the Object Group Definition is created during initial system configuration.
No additional record can be created nor deleted, only modification of the parameter values is possible
on the Configuration tab, regardless whether the feature is activated/deactivated.

2 Select the Configuration tab of the Object Group Definition configuration window.
The Configuration tab window appears.

Figure 7: Object Group Definition – Configuration Tab

Send Feedback | March 2014 | MN000436A01-A

 Configuration and Optimization | 39

Note: Parameter values of the Object Group Definition object can be modified only if no Subjects and
Instances have been configured in the system (Object Group Subject/Instance objects). Otherwise, the
parameters are grayed out.

3 In the Length of Prefix field, enter the number of digits used for prefixes of the object group attachment request
or a temporary object call request. The available range is 1– 2 digits, when the feature is enabled (not necessarily
activated).
4 In the Object Group Prefix field, enter the value of the Object Group (<OGp>). The value ranges are as follows,
when the Object Call feature is enabled (not necessarily activated):
• If the Length of Prefix is 1, select <OGp> from the range 1–9.
• If the Length of Prefix is 2, and the total number of digits is less than 8 (Length of Prefix + Length of Subject
+ Length of Instance), select <OGp> from the range 01–99.
• If the Length of Prefix is 2, and the total number of digits is 8, select <OGp> from the range 01–13.
Note: The Object Group Prefix must have a different value than the Temporary Object Call Prefix.

5 In the Temporary Object Call Prefix field, enter the value of the Temporary Object Call. The value ranges are as
follows, when the Object Call feature is enabled (not necessarily activated):
• If the Length of Prefix is 1, select <TOCp> from the range 1–9.
• If the Length of Prefix is 2, and the total number of digits is less than 8 (Length of Prefix + Length of Subject
+ Length of Instance), select <TOCp> from the range 01–99.
• If the Length of Prefix is 2, and the total number of digits is 8, select <TOCp> from the range 01–13.
Note: The Object Group Prefix must have a different value than the Temporary Object Call Prefix.

6 In the Length of Subject field, enter the total number of digits used for the Subject ID. The value ranges are 1–5;
the default value is 4 after initial system configuration.
Note: The sum of the Length of Subject and the Length of Instance must be less than or equal to 6,
otherwise an error appears.

7 In the Length of Instance field, enter the total number of digits used for the Instance ID. The value ranges are 1–
5; the default value is 2 after the initial system configuration.
Note: The sum of the Length of Subject and the Length of Instance must be less than or equal to 6,
otherwise an error appears.

8 Click Apply.
Information has been saved and the parameter values of the Object Groups have been modified according to your
needs.

Post requisites:
Important: Before creating an Object Group Subject or an Object Group Instance, the Object Group
Definition must be synchronized across all clusters in the system. For synchronization details see the UCS
Synchronization Tool manual.

Object Group Subject Configuration

The Object Group Subject identifies the part of the Object Group which represents for example a flight number or a
bus line. The Object Group Subject consists of all necessary information that a trunking system requires for a
talkgroup/multigroup on the system.
The following topics provide information on the configuration of the Object Group Subject using User Configuration
Manager application.

MN000436A01-A | March 2014 | Send Feedback

40 | Configuration and Optimization

Important: Before creating an Object Group Subject, the Object Group Definition must be synchronized
across all clusters in the system. For synchronization details, see the UCS Synchronization Tool manual.

Creating an Object Group Subject

Note:
Configuration of the Object Group Subject is only possible if a dedicated license has been purchased and is
enabled in the system, otherwise the object is grayed out. What is more, the feature must be activated for its
operation to take effect.
Creation of an Object Group Subject is possible at any time, regardless whether the Object Call feature is
activated or deactivated.
Prerequisites:
Important:
• Before creating an Object Group Subject, a Home Zone Map (HZM) must be created and submitted.
Make sure you have the Home Zone Maps configured. For details on Home Zone Mapping
configuration, refer to the User Configuration Manager manual.
When the Subject is created, it is validated against the Home Zone Map if the complete set of possible
talkgroups and their multigroup, created based on the Subject, is allocated within the same zone. In
case, a multigroup and its talkgroups is not allocated in the same zone, then the creation of that Object
Group Subject is rejected.
• Before creating an Object Group Subject, the Object Group Definition must be synchronized across all
clusters in the system. For synchronization details, see the UCS Synchronization Tool manual.
Procedure:
1 In UCM, select Subscribers → Object Group Definition → Object Group Subject, and right-click in the
contents pane and choose the New menu item.
The Object Group Subject configuration window appears.

Send Feedback | March 2014 | MN000436A01-A

 Configuration and Optimization | 41

Figure 8: Object Group Subject – Basic Tab

Figure 9: Object Group Subject – Basic Tab

2 In the Subject Alias field, enter a unique name that refers to a specific Object Group Subject defined on the
system. The name can consist of 1–8 characters; cannot start with SZ$ or ZC$ (case sensitive) and cannot use | @
_"'%$?&/\.
3 In the Subject ID field, enter a value from 1 – 99999 that refers to a specific object group defined on the system
related to the Object Call feature. The value of the Subject ID depends on the value entered in the Length of
Subject field set on the Object Group Definition – Configuration Tab. The following is applicable:
• 1 – 9 in case the Length of Subject = 1,

MN000436A01-A | March 2014 | Send Feedback

42 | Configuration and Optimization

• 1 – 99 in case the Length of Subject = 2,

• 1 – 999 in case the Length of Subject = 3,
• 1 – 9999 in case the Length of Subject = 4,
• 1 – 99999 in case the Length of Subject = 5.
Note:
The value ‘0’ (zero) is used as wildcard and cannot be specified as Subject ID.
Subject ID with a length less than the Length of Subject will automatically be preceded by ‘0’.
The value ‘0’ is used as wildcard, and the number of digits follows the same rules as listed above.
4 Select the Yes or No radio button for the Subject Activated field to allow/disallow the creation of the Object Call
related talkgroups in the system.
5 In the Security Group field, select the alias of the security group from a list of entries to which this record is
assigned by clicking the ... button to the right of the field.
6 Click Apply.
7 Select the Configuration tab.
The Configuration tab appears.

Figure 10: Object Group Subject – Configuration Tab

Send Feedback | March 2014 | MN000436A01-A

 Configuration and Optimization | 43

Figure 11: Object Group Subject – Configuration Tab

8 Select the profile information for the following:

• Console TG/MG Capabilities Profile Alias – mandatory field, default value TEMPLATE;
• TG/MG Capabilities Profile Alias – mandatory field;
• TG/MG Valid Sites Profile Alias – mandatory field.
Note: Default configuration parameters of these profiles are set up during initial system configuration.
If you want to create or modify the setup default profiles, refer to the User Configuration Manager
manual.
9 Select the Yes or No radio button for the Preempt Capable field to allow/disallow group calls initiated in this
talkgroup/multigroup to preempt lower priority calls both on voice and data channels. The default value is No.
10 In the Interrupt or Wait Mode field, select:
• Interrupt – enables a multigroup to interrupt talkgroup calls currently in conversation to include them in a
multigroup call, regardless if all talkgroup members are available.
• Wait – allows a talkgroup call in progress to end before a multigroup call begins, so the multigroup waits for
all talkgroup members to be available.
The default value is Wait.
Note: The Interrupt or Wait Mode parameter is only valid for the Object Group Subject, and takes
effect only for the multigroup <OGp><Subject><Instance wildcard>.

11 Select the Yes or No radio button for the Extended Band Channels Can Be Assigned field to allow/disallow
assigning the channels operating in the standard 380-400 MHz band and in the extended frequency band (410-430
MHz). The default value is No.
Note: This parameter is connected with the eTETRA (Enhanced TETRA – Support for dual band base
station) for which a license needs to be purchased.

12 Click Apply.
Parameter values of the Object Group Subject have been saved and the object is created.
Note: When the Object Group Subjects are created and activated, appropriate talkgroups/multigroups
related to Object Call are automatically created on the Talkgroup, and Multigroup object. These created
talkgroups/multigroups have the same properties as specified for this Subject with the following alias:
• For <OGp><Subject><Instance>,<Subject alias>&<Instance alias>.

MN000436A01-A | March 2014 | Send Feedback

44 | Configuration and Optimization

• For <OGp><Subject><Instance wildcard>, <Subject alias>&0.

Modifying Parameter Values for an Object Group Subject

Prerequisites: You have launched the User Configuration Manager (UCM) application on the NM Client PC.
When and where to use:
Note: You can change the parameter values of an Object Group Subject at any time, regardless whether the
Object Call feature is activated or deactivated. However, the feature must be activated for the applied
modification to take effect.
Procedure:
1 In UCM, select Subscribers → Object Group Definition → Object Group Subject. In the contents pane right-
click the record of which you want the parameters to be modified, and choose the Open menu item.
The Object Group Subject configuration window of that configuration record appears.

Figure 12: Object Group Subject – Basic Tab

Send Feedback | March 2014 | MN000436A01-A

 Configuration and Optimization | 45

Figure 13: Object Group Subject – Basic Tab

2 Modify the Subject Activated field as needed.

• Yes – activates the creation of Object call related talkgroups in the system.
• No – deletes the created Object Call related talkgroups, but not permanently. Permanent deletion is performed
by deleting a specific Object Group Subject record.
3 Click Apply.
Information has been saved.
4 Select the Configuration tab.
The Configuration tab appears.

MN000436A01-A | March 2014 | Send Feedback

46 | Configuration and Optimization

Figure 14: Object Group Subject – Configuration Tab

Figure 15: Object Group Subject – Configuration Tab

5 Modify the profile information for the following according to your needs:
• Console TG/MG Capabilities Profile Alias – mandatory field; default value TEMPLATE;
• TG/MG Capabilities Profile Alias – mandatory field;
• TG/MG Valid Sites Profile Alias – mandatory field.

Send Feedback | March 2014 | MN000436A01-A

 Configuration and Optimization | 47

Note: Default configuration parameters of these profiles are set up during initial system configuration.
If you want to create or modify the setup default profiles, refer to the User Configuration Manager
manual.
6 Modify the Preempt Capable field as needed.
•Yes – allows all group calls initiated in this talkgroup to preempt lower priority calls both on voice and data
channels.
• No – disables this capability.
7 Modify the Interrupt or Wait Mode field as needed.
•Interrupt – enables a multigroup to interrupt talkgroup calls currently in conversation to include them in a
multigroup call, regardless if all talkgroup members are available.
• Wait – allows a talkgroup call in progress to end before a multigroup call begins, so the multigroup waits for
all talkgroup members to be available.
8 Modify the Extended Band Channels Can be Assigned field as needed.
• Yes – allows for assigning the channels operating in the standard 380-400 MHz band and in the extended
frequency band (410-430 MHz).
• No – allows for assigning channels operating in the standard 380-400 MHz band only.
Note: This parameter is connected with the eTETRA (Enhanced TETRA – Support for dual band base
station) for which a license needs to be purchased.

9 Click Apply.
Parameter values of the Object Group Subject have been changed and information has been saved.

Deleting an Object Group Subject

Prerequisites: You have launched the User Configuration Manager (UCM) application on the NM Client PC.
When and where to use: Deleting an Object Group Subject may result in deleting the talkgroups from the system. If
the Object Group Subject is activated when the deletion is taking place, then the related talkgroups and multigroups
are deleted.
Note: Deletion of an Object Group Subject record is possible at any time, regardless whether the Object
Call feature is activated or deactivated.

Procedure:
1 In UCM, select Subscribers → Object Group Definition → Object Group Subject.
2 In the contents pane, right-click the record you want to delete, and choose Delete from the pop-up menu item.
The selected Object Group Subject record has been deleted. For an activated Subject, all talkgroups including
the Subject and the multigroup for the Subject have been deleted.

Object Group Instance Configuration

The Object Group Instance identifies the part of the Object Group which represents for example a certain workgroup
within a flight or a certain tour of a bus line.
The following topics provide information on the configuration of the Object Group Instance using User Configuration
Manager application.
Important: Before creating an Object Group Instance, the Object Group Definition must be synchronized
across all clusters in the system. For synchronization details, see the UCS Synchronization Tool manual.

MN000436A01-A | March 2014 | Send Feedback

48 | Configuration and Optimization

Creating an Object Group Instance

Note:
Configuration of the Object Group Instance is only possible if a dedicated licensed has been purchased and
is enabled in the system, otherwise the object is grayed out. What is more, the feature must be activated for
its operation to take effect.
Creation of an Object Group Instance is possible at any time, regardless whether the Object Call feature is
activated or deactivated.
Prerequisites:
Important: Before creating an Object Group Instance, the Object Group Definition must be synchronized
across all clusters in the system. For synchronization details, see the UCS Synchronization Tool manual.

Procedure:
1 In UCM, select Subscribers → Object Group Definition → Object Group Instance, and right-click in the
contents pane and choose the New menu item.
The Object Group Instance configuration window appears.

Figure 16: Object Group Instance – Basic Tab

Send Feedback | March 2014 | MN000436A01-A

 Configuration and Optimization | 49

Figure 17: Object Group Instance – Basic Tab

2 In the Instance Alias field, enter a unique name that refers to a specific Object Group Instance defined on the
system. The name can consist of 1–7 characters; cannot start with SZ$ or ZC$ (case sensitive) and cannot use | @
_"'%$?&/\.
3 In the Instance ID field, enter a value from 1 – 99999 that refers to a specific object group defined on the system
related to the Object Call feature. The value of the Instance ID depends on the value entered in the Length of
Instance field set on the Object Group Definition – Configuration Tab. The following is applicable:
• 1 – 9 in case the Length of Instance = 1,
• 1 – 99 in case the Length of Instance = 2,
• 1 – 999 in case the Length of Instance = 3,
• 1 – 9999 in case the Length of Instance = 4,
• 1 – 99999 in case the Length of Instance = 5.
Note:
The value ‘0’ (zero) is used as wildcard and cannot be specified as Instance ID.
Instance ID with a length less than the Length of Instance will automatically be preceded by ‘0’.
The value ‘0’ is used as wildcard, and the number of digits follows the same rules as listed above.
4 Select the Yes or No radio button for the Instance Activated field to allow/disallow the creation of Object Call
related talkgroups in the system.
5 In the Security Group field, select the alias of the security group from a list of entries to which this record is
assigned by clicking the ... button to the right of the field.
6 Click Apply.
7 Select the Configuration tab.

MN000436A01-A | March 2014 | Send Feedback

50 | Configuration and Optimization

Figure 18: Object Group Instance – Configuration Tab

Figure 19: Object Group Instance – Configuration Tab

8 Select the profile information for the following:

• Console TG/MG Capabilities Profile Alias – mandatory field, default value TEMPLATE;
• TG/MG Capabilities Profile Alias – mandatory field;
• TG/MG Valid Sites Profile Alias – mandatory field.
Note: Default configuration parameters of these profiles are set up during initial system configuration.
If you want to create or modify the setup default profiles, refer to the User Configuration Manager
manual.
9 Select the Yes or No radio button for the Preempt Capable field to allow/disallow group calls initiated in this
talkgroup/multigroup to preempt lower priority calls both on voice and data channels. The default value is No.

Send Feedback | March 2014 | MN000436A01-A

 Configuration and Optimization | 51

10 Select the Yes or No radio button for the Extended Band Channels Can be Assigned field. The default value is
No.
Note: This parameter is connected with the eTETRA (Enhanced TETRA – Support for dual band base
station) for which a license needs to be purchased.

11 Click Apply.
Parameter values of the Object Group Instance have been saved and the object is created.
Note: When the Object Group Instances are created and activated, appropriate talkgroups related to
Object Call are automatically created on the Talkgroup object. These created talkgroups have the same
properties as specified for this Instance with the following alias:
• For <OGp><Subject wildcard><Instance>, 0&<Instance alias>.

Modifying Parameter Values for an Object Group Instance

Prerequisites: You have launched the User Configuration Manager (UCM) application on the NM Client PC.
When and where to use:
Note: You can change the parameter values of an Object Group Instance at any time, regardless whether
the Object Call feature is activated or deactivated. However, the feature must be activated for the applied
modification to take effect.
Procedure:
1 In UCM, select Subscribers → Object Group Definition → Object Group Instance. In the contents pane right-
click the record of which you want the parameters to be modified, and choose the Open menu item.
The Object Group Instance configuration window of that configuration record appears.

Figure 20: Object Group Instance – Basic Tab

MN000436A01-A | March 2014 | Send Feedback

52 | Configuration and Optimization

Figure 21: Object Group Instance – Basic Tab

2 Modify the Instance Activated field as needed.

• Yes – activates the creation of the Object Call related talkgroups in the system.
• No – deletes the created Object Call related talkgroups, but not permanently. Permanent deletion is performed
by deleting a specific Object Group Instance record.
3 Click Apply.
Information has been saved.
4 Select the Configuration tab.

Figure 22: Object Group Instance – Configuration Tab

Send Feedback | March 2014 | MN000436A01-A

 Configuration and Optimization | 53

Figure 23: Object Group Instance – Configuration Tab

5 Modify the profile information for the following according to your needs:
• Console TG/MG Capabilities Profile Alias – mandatory field; default value TEMPLATE;
• TG/MG Capabilities Profile Alias – mandatory field;
• TG/MG Valid Sites Profile Alias – mandatory field.
Note: Default configuration parameters of these profiles are set up during initial system configuration.
If you want to create or modify the setup default profiles, refer to the User Configuration Manager
manual.
6 Modify the Preempt Capable field as needed.
•Yes – allows all group calls initiated in this talkgroup to preempt lower priority calls both on voice and data
channels.
• No – disables this capability.
7 Modify the Extended Band Channels Can be Assigned field as needed.
• Yes – allows for assigning the channels operating in the standard 380-400 MHz band and in the extended
frequency band (410-430 MHz).
• No – disables this functionality.
Note: This parameter is connected with the eTETRA (Enhanced TETRA – Support for dual band base
station) for which a license needs to be purchased.

8 Click Apply.
Parameter values of the Object Group Instance have been changed and information has been saved.

Deleting an Object Group Instance

Prerequisites: You have launched the User Configuration Manager (UCM) application on the NM Client PC.
When and where to use:
Deleting an Object Group Instance may result in deleting the talkgroups from the system. If the Object Group
Instance is activated when the deletion is taking place, then the related talkgroups including this Instance are deleted
for each Subject. The multigroup for each Subject is updated accordingly.

MN000436A01-A | March 2014 | Send Feedback

54 | Configuration and Optimization

Note: Deletion of an Object Group Instance is possible at any time, regardless whether the Object Call
feature is activated or deactivated.

Procedure:
1 In UCM, select Subscribers → Object Group Definition → Object Group Instance.
2 In the contents pane, right-click the record you want to delete, and choose Delete from the pop-up menu item.
The selected Object Group Instance has been deleted. For an activated Instance, talkgroups including this
Instance are deleted for each Subject. The multigroup for each Subject is updated accordingly.

Send Feedback | March 2014 | MN000436A01-A

Chapter

3
Troubleshooting
The following topics contain troubleshooting information and limitations for the Object Call feature.

Object Call Monitoring

The Object Call feature activity is monitored on the following applications:
• Multi-Computer Aided Dispatch Interface (MultiCADI),
• Air Traffic Information Access (ATIA) Log Viewer.
An Object Group Attachment Request is visible as a private call request and termination, and group affiliation.
An Object Group Call is visible as a group call.
Temporary Object Call is visible as a group call.

Rejected Object Calls

Dialing an object group number needs to follow a pre-defined numbering scheme, in order for the call to go through
(see Numbering Scheme Overview on page 28). Some combinations will always result in a call being rejected. The
following table presents different results of calls made towards the object group numbers:

Table 4: Object Call Results

Call Towards... Private Call Group Call

<OGp><Subject><Instance> Object Group Attachment Request Object Group Call
<OGp><Subject><Wildcard> Call Rejected Object Group Call
<OGp><Wildcard><Instance> Call Rejected Object Group Call
<OGp><Wildcard><Wildcard> Call Rejected Call Rejected
<TOCp><Subject><Instance> Object Group Call towards N/A
<OGp><Subject><Instance>
<TOCp><Subject><Wildcard> Object call towards the multigroup N/A
<OGp><Subject><Wildcard>
<TOCp><Wildcard><Instance> Object Group Call towards N/A
<OGp><Wildcard><Instance>
<TOCp><Wildcard><Wildcard> Call Rejected Call Rejected

MN000436A01-A | March 2014 | Send Feedback

56 | Troubleshooting

User Configuration Manager Object Call Troubleshooting

Table 5: Object Call Feature – UCM Troubleshooting

Problem Troubleshooting/Restriction Information

No configuration of the Object Call Configuration of the Object Call is only possible when a
feature can be performed. dedicated feature license is purchased, otherwise the related
Object Groups are grayed out in UCM, and no configuration
can be performed. The feature must be activated for its
operation to take effect.
The Object Group Definition cannot be Only one Object Group Definition record in UCM is available
created in UCM. – Object Group Parameters. It is created during the initial
configuration of the system, and cannot be deleted.
The Object Call related talkgroups are In order for the Object Call related talkgroups to be created, the
not created. following requirements must be fulfilled:
• Talkgroups are only created if the Object Call feature has
been activated. This is done by selecting the Object Group
Definition record, and in the Object Group Definition -
Basic tab set the Activated parameter to Yes.
• Talkgroups related to a specific Subject ID are only created
if the Subject is activated. To do so, select a specific Object
Group Subject record, and in the Object Group Subject
— Basic tab, set the Subject Activated parameter to Yes.
• Talkgroups related to a specific Instance are only created if
the Instance is activated. To do so, select a specific Object
Group Instance record, and in the Object Group Instance
— Basic tab, set the Instance Activated parameter to Yes.

A radio user cannot call an Object Each radio system allows to create a determined number of
Group, despite the created talkgroups talkgroups used in your system. This is limited by the Zone
with the Subject and Instance activated in Controller (ZC). Therefore, some calls may not go through
UCM. even though the Subjects and Instances have been configured
and activated in UCM. Radio users that try to attach to the
talkgroups will be rejected. When the maximum number of
talkgroups has been reached, a trap is sent to the Fault
Manager. The solution is to make sure with the operator that
the maximum number of talkgroups has not been exceeded, and
also check the alarms in the Fault Manager. If the number of
talkgroups/multigroups is exceeded, delete/deactivate them
using the UCM application (see Talkgroup/Multigroup
Deletion/Deactivation Overview on page 30 ).
When defining a new Object Group When an Object Group Subject is created, validation against
Subject an error message appears about the Home Zone Map is performed. Two possible reasons for
home zone mapping. rejecting the creation of the Object Group Subject are possible:
• Home Zone Map is not submitted. For this configuration,
refer to the User Configuration Manager manual.
• A multigroup and its talkgroups is not allocated in the same
zone. When the Subject is created, it is validated against the
Home Zone Map if the complete set of possible talkgroups
Table continued…

Send Feedback | March 2014 | MN000436A01-A

 Troubleshooting | 57

Problem Troubleshooting/Restriction Information

and their multigroup created based on the Subject is

allocated within the same zone. If that is not the case, the
Home Zone Map must be modified (see User Configuration
Manager manual), or the value ranges of the Object Group
Prefix, Length of Subject, Length of Instance defined on
the Object Group Definition – Configuration tab must be
changed (see Modifying Object Call Feature Parameter
Values on page 37).

The Object Call related talkgroups/ The reason for this situation, is the fact that created talkgroups
multigroups visible in the talkgroup/ and multigroups are editable only using the Object Group
multigroup search list on the Talkgroup/ Subject/Instance objects in UCM. They cannot be edited on the
Multigroup object in UCM are not Talkgroup and/or Multigroup object. The configuration
editable. parameters are grayed out.
If you want to edit, add, or delete created talkgroups/
multigroups for an Object Call, select a determined Object
Group Subject or Object Group Instance record, and
perform the necessary configuration actions.
See Talkgroup/Multigroup Creation Overview on page 29 for
more details.
When modifying the Console TG/MG The reason for this situation is the fact that the Patch parameter
Capabilities Profile Alias of an Object on a determined Console TG/MG Capabilities Profile is set to
Group Subject an error appears that an Yes in UCM. Therefore, the profile cannot be assigned to a
update of the profile due to a created multigroup. The default profile is TEMPLATE configured
patch cannot be executed. during initial system configuration.
The solution is to set the Patch parameter on the Console
TG/MG Capabilities Profile to No in UCM. See the User
Configuration Manager manual for Console TG/MG
Capabilities Profile configuration.
When defining the values on the Object The reason for such situation is the fact that ISSI and GSSIs
Group Definition — Configuration tab an that have already been defined in the system cannot be
error about ISSI and GSSI ranges determined in the value ranges set for the Object Call. When
appears. the following parameters on the Object Group Definition —
Configuration are set: Length of Prefix, Object Group Prefix,
Temporary Object Call Prefix, Length of Subject, and Length
of Instance, they are checked if no ISSIs or GSSIs are already
specified within the object group value range
<OGp><Subject value range><Instance value
range> and <TOCp><Subject value
range><Instance value range>. For example, if:
• Length of Prefix = 1
• Object Group Prefix = 7
• Temporary Object Call Prefix = 9
• Length of Subject = 4
• Length of Instance = 2
the ISSIs or GSSIs cannot be defined in the value range of
7000000–7999999 and 9000000–9999999.
The solution is to change the values for the Object Group, see
Modifying Object Call Feature Parameter Values on page 37,

MN000436A01-A | March 2014 | Send Feedback

58 | Troubleshooting

Problem Troubleshooting/Restriction Information

or deleting the records with the SSI mentioned in the error
message (the first SSI is included in the error message).

Send Feedback | March 2014 | MN000436A01-A