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) Meaning Term (TIA) MAA/ MLA Private line type The Multiple Address Appearance feature, also commonly known as "Multiple Line Appearance", provides the served user 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. MAA/ Keyset 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 manipulate calls on the affected telephones. MLA/ MSA 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. 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 14 Administrative Options 16 General Keyset Options 16 FPK line key programming 19 Limitations 22 References 22 Abbreviations 22 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. Line OpenStage 2 OpenStage 1 Primary appearance Secondary appearance OpenStage 3 Secondary appearance 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 OpenStage Phone Line 2 Line 1 Primary appearance Secondary appearance Line 3 Secondary appearance OpenStage Phone Line 2 Line 1 Primary appearance Secondary appearance 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 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 configured 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 ...