Download  Print this page

Siemens Multi Address Appearance (MAA) On OpenStage Technical Paper

On openstage phone
Hide thumbs

Advertisement

Quick Links

Technical Paper
Multi Address Appearance (MAA)
On OpenStage
Issue 1.0
Siemens Enterprise Communications GmbH & Co KG
Munich, 07/26/2010
Germany
Siemens Enterprise Communications
www.siemens-enterprise.com

Advertisement

loading

  Summary of Contents for Siemens Multi Address Appearance (MAA) On OpenStage

  • Page 1 Technical Paper Multi Address Appearance (MAA) On OpenStage Issue 1.0 Siemens Enterprise Communications GmbH & Co KG Munich, 07/26/2010 Germany Siemens Enterprise Communications www.siemens-enterprise.com...
  • Page 2: Disclaimer

    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.
  • Page 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 synonym for MAA Multi Address Appearance on OpenStage 00.00.2007 I 3...
  • Page 4: Table Of Contents

    Contents Disclaimer Disambiguation Contents Scope Functional Overview Motivation User Experience Basic Representation Making Calls with multiple lines LED Status Overview User Configuration Items Administrative Options General Keyset Options FPK line key programming Limitations References Abbreviations Multi Address Appearance on OpenStage 00.00.2007 I 4...
  • Page 5: Scope

    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;...
  • Page 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).
  • Page 7: Functional Overview

    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.
  • Page 8: User Experience

    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.
  • Page 9 Line Presentation Tabs User address appearance OpenStage Idle Screen for MAA. The idle screen contains the additional line management row. Navigation between the different tabs can be done using the phone application button or the left arrow key on the TouchGuide. The lines are represented by the FPK keys on the right hand side starting with the primary line key on top.
  • Page 10: Making Calls With Multiple Lines

    Making Calls with multiple lines Incoming call Incoming calls are notified as known from a single user phone. Additional information about the affected 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.
  • Page 11 The phone can be configured by the administrator to select automatically the outgoing line, if the user initiates an outgoing call. Idle line The phone will use the next available idle line. Lines are configured with a priority order. The phone will use the order to use the next free line.
  • Page 12 Tree way conference 444<->101<->200 Conference View for 444: User 444 has set up a 3 way conference between 444, 101 and 200. User 444 is not able to setup any additional call Context view for 444: The phone offers no option to add an additional participant to the conference as the maximum number of local...
  • Page 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.
  • Page 14: Led Status Overview

    Overview Context Menu Overview Context Menu: The overview context menu offers a subset of the call context menu. The subset consist of the most used functions within a call and the view option to switch the call view of this call.
  • Page 15 User Line Key Configuration The keyset line configuration can be done for every line. Each line has an own tab with the same parameters. Parameter Meaning Ring delay (seconds) Number of seconds until the phone will play the ringing tone for an incoming call.
  • Page 16: Administrative Options

    Administrative Options The MAA is a subset of the SEN proprietary MLA. Therefore the administrative settings are used in both scenarios. The explained configuration parameters are reduced to the MAA needed settings. A deviating usage of the parameter will enable the MLA, which is only supported by the SEN OpenScape Voice platform.
  • Page 17 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 originating line preference. The following preferences can be configured: "idle line": An idle line is selected.
  • Page 18 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.
  • Page 19: Fpk Line Key Programming

    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"...
  • Page 20 Every keyset must necessarily have a line key for the primary line. To configure the key of the primary line, set Primary line to "true". Only one single line can be the primary line. Enabling the primary line option will disable a possibly previous configured primary line. If Ring on/off is checked, the line will ring when an incoming call occurs, and a popup will appear on the display.
  • Page 21 Ring delay: Time interval in seconds after which the line starts ringing on an incoming call. Default: 0 Selection order: Priority assigned to the line for the selection of an outgoing line. Default: 0 Address: Address/phone number which has a corresponding entry on the SIP server/registrar. Realm: Domain wherein user id and password are valid.
  • Page 22: Limitations

    [1] TIA-811-A: Performance and Interoperability Requirements for Voice-over-IP (VoIP) Feature Telephones (http://www.tiaonline.org/standards/technology/voip/documents/TIA-811-A-final-for- global.pdf) [2] Session Initiation Protocol (SIP)-Specific Event Notification (RFC 3261) [3] OpenStage Admin Guide (http://wiki.siemens- enterprise.com/images/1/1b/Administration_Manual_OpenStage_OpenScape_Voice.pdf) [4] WPI Guide (http://wiki.siemens- enterprise.com/images/c/c7/OpenStage_Provisioning_Interface_Developer%27s_Guide.pdf) Abbreviations Address of Record Multiple Address Appearance...
  • Page 23 Siemens Enterprise Communications is owned by a Hofmannstr. 51 joint venture of The Gores Group and Siemens AG. The joint venture also encompasses Enterasys Networks, which 81359 Munich, Germany provides network infrastructure and security systems, delivering a perfect basis for joint communications solutions.

This manual is also suitable for:

Multi address appearanceMaa