Siemens | Multi Address Appearance (MAA) On OpenStage | Multi Address Appearance (MAA) On OpenStage

Multi Address Appearance (MAA) On OpenStage
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
MSA
Shared
line
type
Meaning
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.
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.
Term
(TIA)
MAA/
Keyset
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.
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
Disambiguation
Contents
2
2
4
Scope
5
Functional Overview
Motivation
7
7
User Experience
Basic Representation
Making Calls with multiple lines
LED Status Overview
User Configuration Items
8
8
10
14
15
Administrative Options
General Keyset Options
FPK line key programming
17
17
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
Line
OpenStage 2
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
Line 1
Primary appearance
OpenStage
Phone
Line 2
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.
2.
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.
The Asterisk communication system does not support the OpenStage shared multiline signalling 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 registered 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
User 204
User 333
User 444
User 555
Number
204
333
444
555
Line Type
Primary line
Secondary line
Secondary line
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
cLine Presentation Tabs
dUser address appearance
OpenStage Idle Screen for MAA
The idle screen contains the additional 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 (e.g. idle, hold, talk). The line
label is displayed on the right hand
side of the icon.
Line Management Navigation
The user has two possibilities to
navigate between the tabs in the line
tab navigation:´
¾ Press the phone mode key to
toggle between the different
tabs
Line Tab Navigation
¾ Press the ‘left’ error key to
navigate between the different tabs.
The OpenStage 40 does not have a
home mode key. Therefore, the left
arrow key must be used for navigation.
Multi Address Appearance on OpenStage
00.00.2007 I
9
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. Please note that two key presses are needed in case the key is configured to ‘Preselect mode’
(for details, please refer to [3]).
LED flashing
Incoming Call notification
Line name presentation
Incoming Call Presentation:
The phone notifies the user depending on the administrative setting for
this line. The line may ring, as known
from a standard single user phone.
Additionally, the incoming call popup
shows the line name. The line FPK
LED is flashing.
The phone’s behaviour for multiple incoming calls depends on the administrative setting. See
‘Terminating line preference’ for seizing lines.
Making calls
In a single user scenario, the phone will always use the configured user number to make an outgoing
call. In a multi user scenario, the phone must know which call number should be used, as the appropriate line must be seized. Line seizure can be done manually or automatically. The phone’s behaviour
depends on the administrative configuration. See ‘Originating line preference’ for more details.
Use cases for manual line seizure:
1.
2.
3.
Standard procedure
a. User picks up the handset.
b. Phone asks to select the outgoing line.
c. User presses the line key.
d. Outgoing call popup is shown.
e. User dials the number.
Line key seizure
a. User presses the line key.
b. Outgoing call popup is shown.
c. User dials the number.
Using Line Overview
a. User goes to line overview tab.
b. User selects one line for the outgoing call by pressing the ‘OK’ button or the context
menu.
c. Outgoing call popup is shown.
Multi Address Appearance on OpenStage
00.00.2007 I
10
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.
2.
3.
4.
Idle line
The phone will use the next available idle line, according to the configured order of precedence. For each line, a priority is defined. The phone will use this order to select the outgoing
line.
Primary
The phone will use the primary line to set up the outgoing call. If the primary line is blocked,
the phone will show a reminder popup stating that no outgoing line is available.
last
The phone will use that line which had been used for the previous in- or outgoing call. If this
line is already in use, the phone will show a reminder popup stating that no outgoing line is
available.
none
This setting is used to enable manual seizure. The user is asked to select the outgoing line.
Dialing the Last Dialed Number
The last dialed number is displayed in the outgoing call popup. The number shown in this popup is
always the number that has been dialed last number from the primary line. Calls made with secondary
lines are not recorded in the call log and not presented as last dialed number.
Call Forwarding
Call forwarding can only be activated for the primary line. If call forwarding shall be performed for
secondary lines, a central switch feature must be activated. This can be done via the stimulus feature
key.
Putting a Line on Hold
An existing call can be put on hold. In addition to the standard mechanism, the line key can be used to
put the call for this line on hold, if the administrator has set the ‘Line action mode ’ parameter accordingly. A flashing LED is indicating the held call. If the line key is pressed again, the held call will be
retrieved.
Remark: The call status per line is also displayed on the line overview screen.
Warning: As opposed to a single user phone, the held call is not shown on the phone screen. This
might confuse a user which is accustomed to the behaviour of a single user phone.
In a MAA scenario, a held call releases the phone’s audio resources so it can be used to make calls from
other lines. Therefore, the phone switches back to idle screen when the user puts a call on hold. The
flashing line led and the line overview are the only indications that a call is on hold. The phone will not
remind the user after some time that a call is still on hold; this feature is for single user phones only.
Resource Handling
The phone has local resources for two concurrent calls. If the resources are exhausted, no further call
can be set up, and the phone will deny any further requests. Here is an example for a three way conference.
Multi Address Appearance on OpenStage
00.00.2007 I
11
Three-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 set
up 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 conference 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
until the resources are available
again.
Multi Address Appearance on OpenStage
00.00.2007 I
12
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
Multi Address Appearance on OpenStage
Call Context Menu
The call context menu is always
adapted to the current call status of a
used line. It is in line with the menu
of a single user telephone and presents a set of options available for the
current user/line.
00.00.2007 I
13
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 commonly 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
Multi Address Appearance on OpenStage
Explanation
Off
The line is in idle mode.
Flashing
Hold reminder is activated /
incoming call on the line.
Flickering
Outgoing call on the line.
Fast blinking
Line is in ringing.
Blinking
Call forward is activated.
Illuminated
The line is busy.
00.00.2007 I
14
User Configuration Items
The user can configure the phone behaviour relating to a line and the corresponding overview according 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 individual
line. Each line has a tab of its own in
which the parameters are set.
Parameter
Ring delay
(seconds)
Allow in
overview
Address
Primary line
Ring on/off
Selection order
Hot/warm line
Hot/warm
destination
Meaning
Number of seconds until the phone will play the ringing tone for an incoming call.
If checked, the line will be shown in the overview table.
AoR resp. call number for this line (not configurable by the user).
Line status (not configurable by the user).
If checked, a ringer tone is played for incoming calls on this line (not configurable
by the user).
Used for outgoing calls if idle lines are selected automatically (not configurable by
the user).
Not used in this context.
Not used in this context.
Multi Address Appearance on OpenStage
00.00.2007 I
15
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 configured by the user.
Parameter
Use FPK
order
Add all lines
Ordering
icons
Meaning
The phone will order the line entries in the overview table according to the order of
the corresponding FPKs.
All lines are added to the overview table.
The icons can be used to order the line entries suitable to the user’s needs.
Multi Address Appearance on OpenStage
00.00.2007 I
16
Administrative Options
The MAA (Multiple Address Appearance) is a subset of the SEN proprietary MLA (Multiple Line Appearance). 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. These options are used
when at least one FPK is configured as (primary) line key.
¾
A set of options per line key. These options specify the behaviour of individual line keys. Thus,
each line key can have different settings.
General Keyset Options
WBM Configuration:
Admin > System > Features -> Keyset operation
General Keyset Options
The options can be set via WBM,
WPI und local phone menu.
The following are common for all keyset lines. The Rollover ring setting will be used when a call is
active and an incoming call arrives on a different line.
¾
no ring: The phone will not ring on the incoming call.
¾
"alert ring": A 3 seconds burst of the configured ring tone is activated on the incoming call.
¾
"alert beep": A beep tone is played on the incoming call, instead of a ring tone. The tone is
added to the audio of the call, so if a handset is used, the tone will sound from the handset.
¾
"standard ring": The default ring tone is activated on the incoming call.
LED on registration determines whether the line LEDs will be lit for a few seconds if they have been
registered successfully with the SIP server on phone startup.
Multi Address Appearance on OpenStage
00.00.2007 I
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 the originating 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 ranking parameter assigned to each line in the “Line key configuration” screen. If all available lines
are used, a popup is shown indicating that no further line is available.
¾
primary: The designated primary line / main DN is selected for originating calls. If the primary
line is already used, a popup is shown indicating that no further line is available, even if other
lines are configured and idle. In this case, the user has to manually select the line for the outgoing call.
¾
last: The line selected for originating calls is the line that has been used for the last call (originating or terminating). If the last line is already in use, a popup is shown indicating that no
further line is available, even if other lines are configured and idle. In this case, the user has to
manually select the line for the outgoing call.
¾
none: To originate a call, the user manually selects a line by pressing its line key. Manual line
selection overrides automatic line preferences.
The Terminating line preference parameter decides which terminating line, i. e. line with an incoming call, is selected for call accepting when the user goes off-hook.
The following preferences can be configured:
¾
ringing line: The line in the alerting or audible ringing state is automatically selected when
the user goes off-hook. If multiple lines are alerting or ringing, that line which has been alerting the longest is selected.
¾
ringing PLP: The line in alerting or audible ringing state is automatically selected when the
user goes off-hook. However, if the prime line is alerting, it is given priority.
¾
incoming: The earliest line to start audible ringing is selected, or else the earliest alerting
(ringing suppression ignored) line is selected.
¾
incoming PLP: The earliest line to start audible ringing is selected, or else the earliest alerting
(ringing suppression ignored) line is selected. However, if the prime line is alerting, it is given
priority.
¾
none: To answer a call, the user manually selects a line by pressing its line key before going
off-hook, or by pressing the speaker key. Manual line selection overrides automatic line preferences.
Line action mode determines the consequence for an established connection when the line key is
pressed. If "hold" is selected, the call currently active is set to hold as soon as the corresponding line
key is activated. The user has two options: 1) to reconnect to the remote phone by pressing the line
key again, or 2) to initiate another call from a newly selected line. If "release" is selected, the previously
established call is ended.
If Show Focus is checked, the LED of a line key flutters when the line is in use. If not checked, the line
key is lit steadily when the line is in use.
The Reservation timer sets the period after which the reservation of a line is cancelled. A line is automatically reserved for the keyset whenever the user has selected a line for an outgoing call and hears a
dial tone. If set to 0, the reservation timer is deactivated.
Forward indication activates or deactivates the indication of station forwarding, i. e. the forwarding
function of OpenScape Voice. If Forward indication is activated and station forwarding is active for the
corresponding line, the LED of the line key blinks.
Multi Address Appearance on OpenStage
00.00.2007 I
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. In both cases, the options for a ringing call are presented to the user: "Accept", "Reject",
"Deflect".
Preselect timer sets the timeout for an incoming call. After the timeout has expired, the call is
no longer available.
With firmware V2, call bridging is available. When Bridging enabled is activated, the user may join into
an existing call on a shared line by pressing the corresponding line key. On key press, the OpenScape
Voice builds a server based conference from the existing call parties and the user. If the call has already
been in a server based conference, the user is added to this conference.
Remark: This is a shared line only feature and not relevant for the MAA scenario.
Line Preview
The line preview settings are related to a specific FPK function. This FPK function enables the preview
mode, which allows the user to preview a line before using it. When preview mode is active, the line
keys behave similar to when the keyset configuration is set to preselection for line keys. On pressing
the line key, the call activity on the corresponding line is shown. Unlike with a preselected line, there
will be no change to the phone’s current line connections. The LED indicates whether line preview is
active or not.
The information shown to the user depends on the ring/alert configuration for the line in question. If
the line is configured to alert only, the preview will only show the state of the call, not the identity of
the call party. If the line is configured to ring, the identity of the call party will be revealed.
The preview mode can be configured as temporary or as permanent. If System > Features > Keyset
operation > Preview mode is disabled, preview mode will end when the user uses the previewed line,
or a new call is started in any other way, or if the focus is changed away from call view. If the parameter is enabled, preview mode remains active until the user cancels it by pressing the key again.
The Preview timer parameter determines the time span during which the line preview will remain on
the screen.
A dedicated line preview FPK can be administrated.
The menu can be accessed using the Web Based Management (WBM) or the local user menu at the
phone. The location is:
System > Features > Program keys > Preview
Data required
¾
Rollover ring: Determines if a ring tone will signal an incoming call while a call is active.
Value range: "No ring", "Alert beep", "Alert ring"
Default: "Alert beep"
¾
LED on registration: Determines if line LEDs will signal SIP registration. Value range: "Yes",
"No"
Default: "Yes"
¾
Originating line preference: Selects the line to be used for outgoing calls. Value range: "Idle
line", "Primary", "Last", "None"
Default: "Idle line"
¾
Terminating line preference: Determines which line with an incoming call shall be selected
for answering.
Value range: "Ringing line", "Incoming", "Incoming PLP", "Ringing PLP", "None"
Default: "Idle line"
Multi Address Appearance on OpenStage
00.00.2007 I
19
¾
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 indication of station forwarding.
Value range: "Yes", "No"
Default: "No"
¾
Preselect mode: Determines whether an incoming call is accepted by a single press on the
corresponding line key or a double press is needed.
Value range: "Single button", "Preselection"
Default: "Single button"
¾
Preselect timer: Sets the timeout in seconds for accepting an incoming call.
¾
Bridging enabled (V2): When set to "Yes", the user is allowed to join a call on a shared line.
For this purpose, a server based conference is established. Not relevant for MAA.
FPK line key programming
For configuration via WBM, invoke System > Features > Program keys and select line in the pulldown
menu of the key you want to configure. Next, press Edit....
FPK programming: Line key
options per FPK.
Remark: It is recommended to configure primary lines only on keys 1 to 6, or 1 to 5, if a shift key is
needed. This ensures that the lines are still accessible when the user migrates to a different phone with
fewer keys via an optional mobility feature.
A line corresponds to a SIP address of record (AoR), which can have a form similar to an Email address,
or can be a phone number. It is defined by the Address parameter. For registration of the line, a corresponding entry must exist on the SIP server resp. the SIP registrar server.
A label can be assigned to the line key by setting its Key label.
Multi Address Appearance on OpenStage
00.00.2007 I
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. If the option is not checked, the incoming call will be indicated only by the blinking of the
key’s LED. If it is desired that the line ring with a delay, the time interval in seconds can be configured
by Ring delay.
When the user lifts the handset in order to initiate a call, the line to be used is determined by selection
rules. To each line, a priority is assigned by the Selection order parameter. A line with the rank 1 is the
first line to be considered for use. If more than one line have the same rank, the selection is made
according to the key number. Note that Selection order is a mandatory setting; it is also relevant to the
Terminating line preference, as well as to other functions.
The Address (Address of Record) parameter is the phone number resp. SIP name corresponding to the
entry in the SIP registrar at which the line is to be registered. The phone will register each line with
‘Address@Registrar’.
Remark: For the configuration of line keys, the use of the WPI (Workpoint Interface) is recommended.
For operating the WPI, please refer to the WPI developer’s guide [4]. Alternatively, the web interface or
the local menu can be used. Note that the creation of a new line key and the configuration of some
parameters can not be accomplished by the phone’s local menu.
Generally, it is advisable to restrict the user’s possibilities to modify line keys. This can be achieved
solely by the WPI. For further instructions, see the WPI developer’s guide.
The Realm, a protection domain used for authenticated access to the SIP server, works as a name
space. Any combination of user id and password is meaningful only within the realm it is assigned to. If
the realm is not set by admin, the phone will set it automatically after the first successful registration.
The other parameters necessary for authenticated access are User Identifier and Password. For all
three parameters, there must be corresponding entries on the SIP server.
The Shared type parameter determines whether the line is a shared line, i. e. shared with other endpoints, or a private line, i .e. available exclusively for this endpoint. A line that is configured as primary
line on one phone can be configured as secondary line on other phones. The MAA environment is
restricted to private lines. Therefore the option must be set to ‘private’ in this case.
When Allow in overview is set to "Yes", the line can be visible in the line overview on the phone’s
display.
With firmware V2, hot/warm line functionality is available. If a line is configured as hot line, the number indicated in Hot warm destination is dialled immediately when the user goes off-hook. This number is configured in the user menu under Configuration > Keyset > Lines > Hot/warm destination. To
create a hot line, Hot warm action must be set to "hot line". If set to "Warm phone", the specified destination number is dialled after a delay which is defined in System > Features > Configuration > Initial digit timer (seconds). During the delay period, it is possible for the user to dial a different number
which will be used instead of the hot/warm line destination. In addition, the user will be provided with
a dial tone during the delay period. With the setting "No action", the line key will not have hot line or
warm line functionality. As the hotline/warmline function is used in special scenarios only, it is generally recommended not to use this option in MAA environments.
Data required
¾
Key label <n>: Set the label of the line key with the key number <n>.
Default: "Line"
¾
Primary line: Determines whether the line is the primary line.
Value range: "Yes", "No"
Default: "No"
Multi Address Appearance on OpenStage
00.00.2007 I
21
¾
Ring on/off: Determines whether the line rings on an incoming call.
Value range: "On", "Off"
Default: "On"
¾
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.
¾
User Identifier: User name for authentication with the SIP server.
¾
Password: Password for authentication with the SIP server.
¾
Shared type: Determines whether the line is a shared line (shared by multiple endpoints) or a
private line (only available for this endpoint).
Value range: "shared", "private", "unknown".
Default: "shared"
¾
Hot/Warm line type: Determines whether the line is a hot line or a warm line.
Value range: „hot line“, „warm line“
¾
Hot/Warm line destination: Number to be dialled when the phone is in hotline or warmline
mode.
¾
Allow in Overview: Determines whether the line appears in the phone’s line overview.
Value range: "Yes", "No"
Default: "Yes"
¾
Hot warm action (V2): Determines if the line is a regular line, a hot line, or a warm line.
Value range: "No action", "hot line", "warm line"
¾
Hot warm destination (V2): The destination to be dialled from the hot/warm line when the
user goes off-hook.
Remark: A new line key can only be added by use of the WBM or, preferably, using the WPI [4]. Once
a line key exists, it can also be configured by the local menu.
Multi Address Appearance on OpenStage
00.00.2007 I
22
Limitations
When OpenStage is configured as a keyset device with multiple lines, then uaCSTA services can only be
applied to the primary line of the OpenStage device, and secondary lines cannot be controlled using
the uaCSTA interface.
When invoking call related services (e.g. AnswerCall) and physical devices services (e.g. SetMicrophoneMute), it is the OpenStage device which decides which call or speaker the service request is applied
to.
References
[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-forglobal.pdf)
[2] Session Initiation Protocol (SIP)-Specific Event Notification (RFC 3261)
[3] OpenStage Admin Guide (http://wiki.siemensenterprise.com/images/1/1b/Administration_Manual_OpenStage_OpenScape_Voice.pdf)
[4] WPI Guide (http://wiki.siemensenterprise.com/images/c/c7/OpenStage_Provisioning_Interface_Developer%27s_Guide.pdf)
Abbreviations
AoR
MAA
MSA
MLA
SIP
UA
MWI
BLA
SCA
Address of Record
Multiple Address Appearance
Multiple Station Appearance
Multiple Line Appearance
Session Initiation Protocol
User Agent
Message Waiting Indication
Bridged Line Appearance
Shared Call Appearance
Multi Address Appearance on OpenStage
00.00.2007 I
23
About Siemens Enterprise Communications:
Siemens Enterprise Communications is a premier provider of end-to-end enterprise communications solutions that use
open, standards-based architectures to unify communications and business applications for a seamless collaboration
experience. This award-winning "Open Communications" approach enables organizations to improve productivity and
reduce costs through easy-to-deploy solutions that work within existing IT environments, delivering operational
efficiencies. It is the foundation for the company's OpenPath commitment that enables customers to mitigate risk and
cost-effectively adopt unified communications. This promise is underwritten through our OpenScale service portfolio,
which includes international, managed and outsource capability. Siemens Enterprise Communications is owned by a
joint venture of The Gores Group and Siemens AG. The joint venture also encompasses Enterasys Networks, which
provides network infrastructure and security systems, delivering a perfect basis for joint communications solutions.
©Siemens Enterprise
Communications GmbH & Co. KG
For more information about Siemens Enterprise Communications or Enterasys, please visit
www.siemens-enterprise.com/open or www.enterasys.com
Status 04/2010
Communication for the open minded
Siemens Enterprise Communications
www.siemens-enterprise.com/open
Siemens Enterprise
Communications GmbH & Co. KG
is a Trademark Licensee of Siemens AG
Hofmannstr. 51
81359 Munich, Germany
The information provided in this brochure contains merely
general descriptions or characteristics of performance
which in case of actual use do not always apply as described
or which may change as a result of further development
of the products. An obligation to provide the respective
characteristics shall only exist if expressly agreed in the
terms of contract. Availability and technical specifications are subject to change without notice. OpenScape,
OpenStage and HiPath are registered trademarks of
Siemens Enterprise Communications GmbH & Co. KG.
All other company, brand, product and service names are
trademarks or registered trademarks of their respective
holders.
Printed in Germany.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising