Siemens MG-2D User Manual
Technical Paper
Multi Address Appearance (MAA)
On OpenStage
Issue 1.0
Siemens Enterprise Communications GmbH & Co KG
Munich, 07/26/2010
Germany
Communication for the open minded
Siemens Enterprise Communications
www.siemens-enterprise.com/open
Disclaimer
This document contains information on multiple address appearance on OpenStage
phone. It raises no claims to completeness.
Disambiguation
This document describes Multiple Address Appearance (MAA) for OpenStage@Asterisk. The Telecommunication Industry Association (TIA) has defined
terms for VoIP telephony features [1] which slightly differ from the Siemens Enterprise Communications (SEN) wording. This has historical reasons. As SEN uses the
terms consistently in every kind of documentation, this document will also use the
SEN wording. The following terms are affected:
¾ Multiple Address Appearance (MAA)
¾ Multiple Line Appearance (MLA)
¾ Multiple Station Appearance (MSA)
The following table gives an overview about the differences:
Term
(SEN)
MAA/
MLA
Private
line
type
Meaning Term
(TIA)
The Multiple Address Appearance feature, also commonly
known as "Multiple Line Appearance", provides the served user
MAA/
Keyset
with multiple addresses appearing on a single telephone. The
served user has the ability to originate, receive and otherwise
control calls on each of these address appearances. These address appearances behave independently of each other.
MSA
Shared
line
type
Multiple Station Appearance provides the ability for the same
address (e.g. telephone number, DNS name, URL) to appear on
multiple telephones. Users at each telephone may be provided
with the ability to make, answer, share and otherwise manipu-
MLA/
MSA
late calls on the affected telephones.
The main difference is the usage of the term “Multiple Line Appearance”; SEN uses
MLA for MSA too, whereas TIA uses MLA together with MAA.
Multi Address Appearance on OpenStage 00.00.2007 I 2
MAA denotes Multiline Appearance with private lines only.
MSA denotes Multiline Appearance with shared lines.
This document uses MLA as a synonym for MSA. Keyset is a synonym for MAA
Multi Address Appearance on OpenStage 00.00.2007 I 3
Contents
Disclaimer 2
Disambiguation 2
Contents 4
Scope 5
Functional Overview 7
Motivation 7
User Experience 8
Basic Representation 8
Making Calls with multiple lines 10
LED Status Overview 14
User Configuration Items 15
Administrative Options 17
General Keyset Options 17
FPK line key programming 20
Limitations 23
References 23
Abbreviations 23
Multi Address Appearance on OpenStage 00.00.2007 I 4
Scope
This document specifies the Multiple Address Appearance (MAA) interface between an OpenStage SIP
phone and a SIP based communication server like Asterisk and describes the configuration.
A line is identified by an AoR resp. SIP URI and typically corresponds to a user. A line can appear on one
or multiple clients; in SIP terms, Multiple Line Appearance (MLA) means that each client registers as a
contact for the AoR concerned. A line that appears on multiple clients is known as a shared line. The
representation of a line on a given client is known as an appearance. The appearance at that client
which is normally used by the user associated with the line is known as the primary appearance, and
appearances at other clients are known as secondary appearances. Figure 1 shows an example of a
shared line with multiple appearances.
OpenStage 1
Primary appearance
OpenStage 2
Line
Secon dary app earan c e
OpenStage 3
Secon dary app earan c e
Figure 1: A shared line with multiple line appearances
A given client that is configured as a keyset can support multiple lines, also called Multiple Address
Appearance (MAA). The client will have a single appearance for each line it supports. From the client’s
point of view, a primary appearance of a line is known as a primary line and a secondary appearance of
a line is known as a secondary line. At present, the following restrictions apply for OpenStage SIP
phones:
¾ Each client must have one and only one primary line;
¾ A client must not have more than one appearance of the same line.
Figure 2 shows an example for an OpenStage phone with three addresses configured. Line 1 is the
primary line, all other lines are secondary lines.
Multi Address Appearance on OpenStage 00.00.2007 I 5
Line 1
Primary appearance
OpenStage
Phone
Secon dary app earan c e
Line 2
Line 3
Secon dary app earan c e
Figure 2: A phone with multiple address appearance
A client configured as a keyset need not have any secondary lines; in that case, it has only a single line
(the primary line). A client can be configured with a private line that is not shared, i.e., the line has only
a single appearance. For the purposes of this specification, the fact that a client is configured with
more than one line or is configured with a single line that is a shared line makes the client a keyset, as
opposed to an ordinary single user phone.
NOTE
1. A client could be configured with only a single line, that line being a private line. A client con-
figured in this way would not make use of any of the special keyset signalling capabilities defined in this specification. However, the client's the user interface and parts of the configuration may differ from a single line non-keyset device.
2. The Asterisk communication system does not support the OpenStage shared multiline signal-
ling features, and SEN will not provide any support to this proprietary protocol enhancement.
Therefore, only the configuration of private lines is taken into account, and this document is
restricted to MAA only.
Multi Address Appearance on OpenStage 00.00.2007 I 6
Functional Overview
Motivation
A telephone is normally associated with a directory number, or in general, with SIP: an AoR. This number is used for placing calls to this telephone and for displaying the telephone's, resp. user's identity
when placing calls to another party. This number is also used when more than one call appearance is
supported due to additional features, like call waiting.
A keyset is a telephone that is associated with more than one number - this allows a given telephone to
act on behalf of different phone numbers, or users. Just like with traditional telephony systems, people
sometimes refer to lines instead of numbers, hence keyset phones are also referred to as multiline
phones. The main line, i.e. the line/directory number for the user associated with a given physical telephone, is called primary line, whereas all other lines that can be handled on other phones are called
secondary lines. Call Log and MWI are working for the primary line only and not for secondary lines.
Sharing of lines is possible, but, as mentioned before, this is not in the focus of this document.
At any given time, one telephone can handle only one call appearance for connecting to the handset,
and the same applies to keyset / multiline telephones. Also for keyset telephones, features like call
waiting can increase the number of call appearances that can be handled, but on a keyset telephone,
these appearances may refer to different lines / numbers / users. The programmable feature keys are
used for handling the lines and their respective call appearances, supported by the associated LEDs
reflecting the line/call status. The number of lines that can be configured depends on the phone model.
This feature can be used for the following use cases, amongst others:
¾ Address multiple users at one phone
¾ Enhanced Call Hold Scenarios
¾ Allow more than two incoming calls at one phone
This feature can not be used for the following use cases, amongst others:
¾ MLA. If the line is configured at more than one phone, incoming calls are sent to the last reg-
istered device.
¾ Line status observation. If the same line is configured at more than one phone, the line status
is not presented at these phones.
Depending on the selected system, a specific set of additional features for handling call appearances is
available (e.g. placing calls on hold).
Similar features are named Bridged Line Appearance (BLA) and Shared Call Appearance (SCA).
Multi Address Appearance on OpenStage 00.00.2007 I 7
User Experience
MAA is automatically activated if the phone has line keys configured, thus the phone works as MAA
phone ‘out of the box’. Line key administration is done by the administrator; the user has no influence
on these settings. Depending on the settings, the phone will react slightly different in basic user interactions. This document will outline these differences.
Even if only one line key is configured, the phone changes into line presentation mode. The line presentation mode helps the user to keep track of the different line statuses. On an OpenStage 60/80
phone, up to 30 lines can be configured, whereas OpenStage 15/20/40 phones are limited to 18 lines.
Basic Representation
If an OpenStage phone is configured as MAA phone, the basic appearance is changed. A new line is
introduced into the idle screen; it is represented in line overview mode. The “My Phone” tab shows the
status of the primary line, while the “Overview” tab displays the current statuses of all lines/users managed on the phone. If a line is used, an additional tab is provided for this line.
A single user line is always represented by an FPK. The FPK label corresponds to the line overview entry
and the line overview tab name; the FPK LED status corresponds to the icon displayed in the line overview tab.
The user can change between the different tabs using the phone home key or the ‘left arrow’ key.
Multiple address representation is adapted to the availability of phone resources. Although the phone
is able to manage phone calls for many users, it still has only one audio input and output device, storage for only one call log, and only one MWI button/LED.
Therefore, one line is privileged. This line, called primary line, is bound to the local call log and to the
MWI. In idle state, the primary line has a line overview screen of its own called “My Phone”. It contains
information about missed calls and messages waiting. On each MAA phone, one and only one primary
line must be defined. All other user lines are secondary lines; they are treated equally among each
other.
The example pictures used in this document are all using the same configuration:
Label Number Line Type
User 204 204 Primary line
User 333 333 Secondary line
User 444 444 Secondary line
User 555 555 Secondary line
MWI and call log are used for user 204, which is the primary line
Multi Address Appearance on OpenStage 00.00.2007 I 8
Loading...