Summary of the content on the page No. 1
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
Summary of the content on the page No. 2
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 Open- Stage@Asterisk. The Telecommunication Industry Association (TIA) has defined terms for VoIP telephony features [1] which slightly differ from the Siemens Enter- prise Communications (SEN) wording. This has historical reasons. As SEN uses the terms consistently in
Summary of the content on the page No. 3
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 syno- nym for MAA Multi Address Appearance on OpenStage 00.00.2007 I 3
Summary of the content on the page No. 4
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
Summary of the content on the page No. 5
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
Summary of the content on the page No. 6
Line 1 Primary appearance Line 2 OpenStage Secondary appearance Phone Line 3 Secondary appearance 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
Summary of the content on the page No. 7
Functional Overview Motivation A telephone is normally associated with a directory number, or in general, with SIP: an AoR. This num- ber 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
Summary of the content on the page No. 8
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 inter- actions. This document will outline these differences. Even if only one line key is configured, the phone changes into line presentation mode. The line pres- entatio
Summary of the content on the page No. 9
Line Presentation Tabs User address appearance OpenStage Idle Screen for MAA The idle screen contains the addi- tional line management row. For navigation between the tabs, the phone mode key or the left arrow key on the TouchGuide can be used. The lines are represented by the FPKs on the right hand side starting with the primary line key on top. Line Overview The line overview tab shows the current status of the managed lines. The icon on the left indicates the status (
Summary of the content on the page No. 10
Making Calls with Multiple Lines Incoming Call Incoming calls are notified as known from a single user phone. Additional information about the af- fected line is shown in the incoming call popup and the line FPK LED. The user can pick up the call using the standard mechanism; additionally, the line key can be used to pick up the call by a single press. Please note that two key presses are needed in case the key is configured to ‘Preselect mode’ (for details, please refer to [3]).
Summary of the content on the page No. 11
d. User dials the number. The administrator can configure the phone so that it selects the outgoing line automatically when the user initiates an outgoing call. The following options are available: 1. Idle line The phone will use the next available idle line, according to the configured order of prece- dence. For each line, a priority is defined. The phone will use this order to select the outgoing line. 2. Primary The phone will use the primary line to set up the outgoing call. If
Summary of the content on the page No. 12
Three-way conference 444<->101<->200 Conference View for 444 User 444 has set up a 3-way con- ference between 444, 101 and 200. User 444 is not able to set up any additional call Context View for 444 The phone offers no option to add an additional participant to the conference as the maxi- mum number of local confer- ence participants is exceeded. User 555 is not able to place a call. Context View for 555 The phone blocks any other call attempts from different users un
Summary of the content on the page No. 13
User Interface Examples The following examples give an impression about the powerful line/user handling of the OpenStage phone. Line Overview Table Called/Calling number Line status icon Line Overview Tab The line overview table gives a quick and easy overview about the status of the configured lines. On the right hand side, the other party is displayed. Call Options in the Context Menu Call Context Menu Call Context Menu The call context menu is always adapted t
Summary of the content on the page No. 14
Call Options in the Overview Menu Overview Context Menu Overview Context Menu The overview context menu offers a subset of the call context menu. The subset consists of the most com- monly used functions within a call and the view option to switch to the call view for this call. LED Status Overview The LED shows the current status of the represented line at any time. LED Explanation Off The line is in idle mode. Flashing Hold reminder is activated / incoming call
Summary of the content on the page No. 15
User Configuration Items The user can configure the phone behaviour relating to a line and the corresponding overview accord- ing to his personal needs. Line Configuration Menu The menu can be accessed using the Web Based Management (WBM) or the local user menu at the phone. The location is: User > Configuration > Keyset > Lines WPI (see [4]) tags are available for these settings, too. User Line Key Configuration The keyset line configuration can be done separately for each
Summary of the content on the page No. 16
Overview Configuration Menu The menu can be reached using the Web Based Management (WBM) or the local user menu at the phone. The location is: User > Configuration > Keyset > Overview Overview Configuration The overview screen can be config- ured by the user. Parameter Meaning Use FPK The phone will order the line entries in the overview table according to the order of order the corresponding FPKs. Add all lines All lines are added to the overview table. Ordering The icons
Summary of the content on the page No. 17
Administrative Options The MAA (Multiple Address Appearance) is a subset of the SEN proprietary MLA (Multiple Line Appear- ance). Therefore, some administrative settings are used in both scenarios. The descriptions given here are limited to the settings needed for MAA. Any deviating usage of the parameters will enable MLA, which is only supported by the SEN OpenScape Voice platform. There are two sets of options: A general set of options affecting all types of configured line keys.
Summary of the content on the page No. 18
The Originating line preference parameter determines which line will be used when the user goes off-hook or starts on-hook dialling. Remark: When a terminating call exists, the terminating line preference takes priority over the originat- ing line preference. The following preferences can be configured: idle line: An idle line is selected for originating calls. The selection is based on the hunt rank- ing parameter assigned to each line in the “Line key configuration” screen. If all
Summary of the content on the page No. 19
Preselect mode determines the phone’s behaviour when a call is active, and another call is ringing. If the parameter is set to "Single button", the user can accept the call a single press on the line key. If it is set to "Preselection", the user must first press the line key to select it and then press it a second time to accept the call. In both cases, the options for a ringing call are presented to the user: "Accept", "Reject", "Deflect". Preselect timer sets the timeout for an incomi
Summary of the content on the page No. 20
Line action mode: Determines the consequence for an established connection when the line key is pressed. Value range: "Hold", "Release" Default: "Hold" Show focus: Determines whether the line key LED blinks or is steady when it is in use. Value range: "Yes", "No" Default: "Yes" Reservation timer: Sets the period in seconds after which a line reservation is cancelled. If set to 0, the reservation timer is deactivated. Default: 60 Forward indication: Activates or deactivates the
