Cisco Linksys SPA9000 - Manual (Page 112)

4-22
Linksys SPA9000 Administrator Guide
Document Version 3.01
Chapter 4 Configuring SPA9000 Features
Managing Call Forwarding
For example, on Line 1, you can define one hunt group with the virtual extension 50300 for Sales, and
another with extension 50400 for Customer Support. In this example, Line 1 has the main number of
14083331000. The <Contact List> in this example looks like the following:
14083331000:aa|50300:5001,5002,hunt=next;10;1|50400:5003,5004,5005,hunt=random;15;0
In this example, when an external caller calls 14083331000, the AA answers and prompts the caller to
enter a target extension. If the caller enters 50300, the AA blind transfers to the 50300 hunt group, which
consists of two stations. If the caller enters 50400, the AA blind transfers to the 50400 hunt group, which
consists of three stations.
Note In this example, only 14083331000 is assigned by the ITSP. The two hunt group extensions are virtual
and can be selected by the SPA9000 administrator.
Using Shared Line Appearance
Shared line appearance (SLA) allows multiple stations to share an extension number and manage a call
as a group. One of the most interesting features of SLA is that when the active station places the call on
a shared line key on hold, the call can be resumed from any of the sharing client stations simply by
pressing the corresponding line key from another station.
To configure a group of client stations to share the same extension, perform the following:
• Select one of the extensions on the client station to configure the share line. As a convention,
Linksys recommends always reserving EXT 1 on the client station as the primary and private
extension of the designated user. Any shared extension should be configured on EXT 2–4.
• On the selected EXT, set <Shared Ext> to yes and the <Shared User ID> to the user-id being shared.
Set up the rest of the account information just like the primary EXT on the same station (<User ID>,
<Password>, <Proxy>, and so on).
• Assign one or more line key buttons on the client station to the shared extension. Set <Shared Line>
of the line key to “yes”.
It may be more convenient to think of a shared line appearance as a physical line key on the client station.
Sharing line appearance is just like sharing line keys across multiple client stations: if a shared line key
is being used by one of the stations in the group, the other members in the group cannot use the line key
until it is released. All the stations sharing the line key, however, can monitor the status of the line key,
which includes such information as the following:
• Is the line key free?
• Is the line key ringing?
• Who is using the line key, and to whom is the user talking?
When there is an incoming call to the shared extension, the SPA9000 alerts all the sharing client stations.
If a client station happened to have both share and private line keys assigned to the shared extension, a
shared line key is chosen first to receive the call before any private line keys.
SPA9000 acts as the state agent (sa) to support SLA. Client stations send NOTIFY (with the dialog event
package and dialog-info+xml message body) to SPA9000 to inform any changes to a shared line key.
The SPA9000 relays the state to all the rest of the sharing client stations with a similar NOTIFY. All the
NOTIFY messages are unsolicited to eliminate the burden of maintaining subscription dialogs. The state
of the dialog-info XML is set to “partial” to indicate this is the state change pertaining to one line key
only.