Page 91 / 286 Scroll up to view Page 86 - 90
Configuring Phone Lines and Calling Routing Behavior
Managing Inbound Calls with the Contact List
SPA9000 Voice System Administration Guide
89
4
Table 1
DID-to-Extension Mapping Example
Be aware of the following factors:
Direct Inward Dialing requires network support for SIP trunking DID.
It is important that the DID number format match exactly the format of the
number signaled in the SIP trunk.
Please check with your Service Provider to confirm the availability of this
feature and the correct DID number format, before proceeding with this
configuration.
SYNTAX:
<DIDn1>:+<Extn1>|<DIDn2>:+<Extn2>|<DIDn3>:+<Extn3>|<DIDn4>:+
<Extn4>|<DIDn5>:
+<Extn5>|<DIDn6>:+<Extn6>|<DIDn7>:+<Extn7>|<DIDn8>:+<Extn8>|
<DIDn9>:+<Extn9>|
<DIDn10>:+<Extn10>|<DIDn11>:+<Extn11>|<DIDn12>:+<Extn12>|<DI
Dn13>:+<Extn13>|
<DIDn14>:+<Extn14>|<DIDn15>:+<Extn15>|<DIDn16>:+<Extn16>|<de
fault_route>
DID number
Extension number
User
408-555-5550
aa
Auto Attendant
408-555-5551
101
User 1
408-555-5552
102
User 2
408-555-5553
103
User 3
408-555-5554
104
User 4
408-555-5650
500
Support (hunt) group
Downloaded from
www.Manualslib.com
manuals search engine
Page 92 / 286
Configuring Phone Lines and Calling Routing Behavior
Managing Inbound Calls with the Contact List
SPA9000 Voice System Administration Guide
90
4
EXAMPLE
:
4085555550:aa|4085555551:+101|4085555552:+102|4085555553:+10
3|4085555554:+104|4085555650:+500|
Enter a plus (+) or a minus (-) before the extension number to achieve the
desired results for caller ID and call routing:
+ <Extn1>
The extension will be alerted when there is an incoming call to
the DID number, and the DID number will be used as the local user-ID in
outbound SIP requests, along with the display-name of the extension.
- <Extn1>
The extension will not be alerted when there is an incoming call
to the DID number. However, the DID number will be used as the local user-
ID in outbound SIP requests, along with the display-name of the extension.
DIDn#: DID number, matching the format of the number signaled in the SIP
trunk
Extn#:
Target extension number or
a
for Auto Attendant
Default route: The default route (extension, hunt group or Auto Attendant) to be
used in case the incoming target number does not match any of the DID
numbers in the contact list with the format described in the sections above.
Call forwarding: Optionally, add call forward information to the Contact List to
specify how unanswered calls are handled.
It is useful to add call forward information to ensure that calls are answered
when the designated phone is unstaffed, as may be the case during lunch time
or after hours. In this case, if the call is not answered within a specified time, the
call is routed to another phone or to the Auto Attendant.
SYNTAX:
<DIDn1>:+<Extn1>,cfwd=<target>|<DIDn2>:+<Extn2>,cfwd=<targ
et>|<DIDn3>:+<Extn3>,cfwd=<target>
EXAMPLE:
4085555550:aa|4085555551:+101,cfwd=aa|4085555552:+102|4085
555553:+103|4085555554:+104|4085555650:+500|
Downloaded from
www.Manualslib.com
manuals search engine
Page 93 / 286
Configuring Phone Lines and Calling Routing Behavior
Managing Inbound Calls with the Contact List
SPA9000 Voice System Administration Guide
91
4
Entering a Contact List Rule
Use the following procedure to enter a contact list rule.
STEP 1
Connect to the SPA9000 administration web server, and choose Admin access
with Advanced settings.
STEP 2
Click
Voice tab > Line
N
, where
N
represents the line interface number.
STEP 3
Scroll down to the
Subscriber Information
section.
SPA9000 Voice > Line: Subscriber Information
STEP 4
Enter the desired rules in the
Contact List
field. For more information, see
“Example
Contact List Rules,” on page 86
and
“Entering a Contact List Rule,” on page 91
.
NOTE
The maximum length of the <Contact List> parameter is 383 characters.
STEP 5
If you included a call forward rule, modify the
Cfwd No Ans Delay
parameter to
specify the number of seconds that elapse before a call is considered to be
unanswered.
STEP 6
Click
Submit All Changes
. The SPA9000 reboots.
STEP 7
To verify your progress, make an inbound call and verify that the call is handled as
you intended.
Downloaded from
www.Manualslib.com
manuals search engine
Page 94 / 286
Configuring Phone Lines and Calling Routing Behavior
Managing Inbound Calls with Hunt Groups
SPA9000 Voice System Administration Guide
92
4
Managing Inbound Calls with Hunt Groups
A Hunt Group is a group of client stations that are treated as one extension for the
purpose of managing inbound calls. The client stations in the hunt group can be
alerted simultaneously or sequentially. The first client station to pick up the call
establishes a private connection to the caller.
NOTE
Compare a Shared Line Appearance to a Hunt Group. A Hunt Group may ring
several stations simultaneously, but only one station can answer and manage the
call. A Shared Line Appearance also rings multiple lines simultaneously but allows
multiple stations to share and manage the call. For more information, see
“Managing
Inbound Calls with Shared Line Appearances,” on page 98
.
There are two types of hunt rules:
Global Hunt Rule:
The hunt rule applies to all line interfaces. Enter this type
of hunt rule on the Voice tab > SIP page > PBX Parameter section, Hunt
Groups field.
Line-Specific (Contact List) Hunt Rule:
The hunt rule applies to a
particular line interface. Enter this type of hunt rule on the Voice tab > Line
N
page > Subscriber Information section > Contact List field. For example, if
you enter this rule on the Line 1 page, it applies only to the calls that are
received on Line 1.
The syntax for the two types of rules varies, as described later in this section. If
you define a hunt group both in the Contact List and on the SIP page > PBX
Parameters section, the call forward parameter from the Contact List is ignored;
instead, the call forward parameter defined on the SIP page > PBX Parameter
section is used.
Downloaded from
www.Manualslib.com
manuals search engine
Page 95 / 286
Configuring Phone Lines and Calling Routing Behavior
Managing Inbound Calls with Hunt Groups
SPA9000 Voice System Administration Guide
93
4
Syntax for Hunt Rules
Global Hunt Rule
(SIP page > PBX Parameters section > Hunt Groups field)
SYNTAX:
extension:[name=”
name”
,]
station
[,
station
[,
station
[…]]],hunt=
hrule
[,cfwd=
target
]
Line-Specific Hunt Rule
(Line
N
page > Subscriber Information section > Contact List field)
SYNTAX:
station
[,
station
[,
station
[…]]],hunt=
hrule;
[,cfwd=
target
]
Parameters
extension
: An extension number for the hunt group
name
: A name for the hunt group, which will appear in the Corporate
Directory
station:
The extension numbers; the wildcard symbols ? and * can be
used to represent one or more characters
hunt=hrule:
The hunt order, ring interval, and maximum duration, in the
following format:
hunt=algo;interval;max
-
algo:
The hunt order.
re:
Restart. Hunting starts at the beginning of the list. If the first station
does not answer within the specified
interval
(see below), the hunt
proceeds through the stations in sequential order.
ne:
Next. The system determines the station that was chosen in the
previous hunt, and hunting starts with the next station in the list. If that
station does not answer within the specified
interval
(see below), the
hunt proceeds through the stations in sequential order.
ra:
Random order. The system randomly chooses a station from the list. If
the selected station does not answer within the specified
interval
(see
below), the hunt proceeds randomly through the unchosen stations until
each station is tried.
al:
All. The system rings all the stations at the same time.
-
interval:
The number of seconds to wait for one station to answer,
before choosing another station. If interval is *, the hunt is stopped at the
first station that starts ringing, and rings the station until it answers, or the
caller hangs up, or the station's ringer times out.
Downloaded from
www.Manualslib.com
manuals search engine

Rate

3.5 / 5 based on 2 votes.

Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top