Copyright 2010-2017 Obihai Technology, Inc.
97
To let phone user change the
CallParkRingEnable
option from the User Preferences GUI on the phone, add
the
cpr
option in any one of the
GUI Menus
::
PerferencesMenu
n
(
n
= 1
–
6). The default on-screen label for
this option is Call Park Ring and the use can set the value to either Enable or Disable.
Notes:
-
The call park ring will not start in any of the following situations:
o
Phone is ringing
o
Phone is off-hook, speakerphone is on, or headset is on
-
Regardless of the duration setting, the call park ring will stop when any of the following happens:
o
No more calls parked in any of the monitored parking orbits
o
Phone starts ringing
o
Phone goes off-hook, or the speakerphone or headset is turned on
-
If a new call is parked while the call park ring is playing, the duration timer restarts so it can potentially ring for
a full duration for the newly added call
Tips: When call park ring is playing, an easy way to stop it (until a new call is parked) is by taking the phone off-hook or
turning on the speakerphone or headset momentarily.
Shared Line and Shared Call Appearances (SCA)
(SIP/SP only.) A Shared Line is a service account or extension that is installed on a group of phones, such that if a
sharing phone is using that extension, other sharing phones will be notified. There can be multiple simultaneous calls
on a shared line. The maximum allowed simultaneous calls on a shared line should be a fix number. Each call on a
shared line is called a Shared Call Appearance (SCA). If your phone has a shared line configured as one of the services, it
should have as many Call Keys defined on the phones that are bound to that service. SCAs of a shared line are ordered
with an index 1
–
n
as SCA1, SCA2, SCA3, ... SCA
n
, where
n
is the maximum number of calls permitted for that line. On
the OBi1000, the SCAs are assigned sequentially in ascending order according to the VLK index of the corresponding Call
Key bound to the shared line. For example, suppose a shared line with 4 SCAs is configured on a phone with VLK1, VLK3,
VLK7, and VLK8 assigned as the 4 Call Keys bound to that line, then the calls hosted on VLK1, VLK3, VLK7, and VLK8 are
SCA1, SCA2, SCA3, and SCA4, respectively.
There are two common implementations of SCA, namely, the Call-Info Method and the SLA/BLA (dialog) method. Use
the parameter
ITSP Profile
–
SIP
–
Feature Configuration
::
X_ShareLineMethod
to select which method to use. It can
be one of the following choices:
-
call-info
: This is the method used by BroadSoft. The phone subscribes to the
call-info
event package with
the proxy server to receive notification of share call appearance state updates. This method also uses the line-seize
event package for seizing a SCA before making a call
-
dialog;sla
: This is based on the Bridged Line Appearance draft (draft-anil-sipping-bla-02). The phone
accepts subscription to the
dialog;sla
event package from the state-agent, and also subscribes back the same with the
state-agent. The phone and state agent then exchange notifications of share call appearance state updates.
-
dialog;ma
: This is similar to the
dialog;sla
method, and is based on a more current version of the same
draft (draft-anil-sipping-bla-04). The name of the event package name is changed to
dialog;ma
.
To designate an SP service as a shared line, enable the option
SPn Service
–
Share line Features
::
X_ShareLine
. The
SPn
Service
–
Calling Features
::
MaxSessions
parameter should be set the value of the maximum number of call
appearances allowed on the shared line. You must also have the same number Call Appearance feature keys defined to
bind to this SP service. A Call Appearance key bound to a shared line behaves similarly to one that is bound to a private