Service Providers
Polycom, Inc.
40
For example, SP1 has a
local_client
with the user-id
4086578118
. The client wishes to make and receive
calls on SP3. The SP1
InboundCallRoute
shall include the following rule:
{4086578118>:sp3}
The SP3
InboundCallRoute
shall be:
{sp1(
408657118@local_client
)}
For more information on SP
n
table in the
section.
Automated Attendant
The device call processing Automated Attendant (AA) is invoked by including “aa” in the inbound call routing
rule associated the interface on the device processing an incoming call. When connecting to the AA in this
manner, there are two options at present.
Customizing AA Prompt Lists
AA does not play individual user prompts directly. Instead it plays a comma-separated list of prompt
elements, known as a
Prompt List
. A prompt element can be a user prompt with optional parameters, or a
control element. A user prompt is referred as
%User<N>%
where
<N>
= 1 – 10. In a prompt list this can be
followed by a
;r=<start>-<end>
parameter that specifies the range to play for that prompt, where
<start>
= starting time mark in milliseconds. 0 is the default if
<start>
is omitted.
<end>
= ending time mark in milliseconds. the end of the prompt is the default if
<end>
is omitted.
If the
r=
parameter is omitted, the full range of the prompt is played.
Examples:
%User1%;r=1000
means play the User1 prompt starting at 1000 ms mark to the end.
%User2%
means play the entire User2 prompt from start to finish.
%User3%;r =1300-3720
means play the User3 prompt starting from the1300 ms mark to the 3720
ms mark.
%User4%;r=3200-1200
means don’t play anything since
<end>
is less than
<start>
.
Each prompt list control elements starts with a ‘
&
’ in a prompt list. The following control elements are
supported:
&pause(<duration>)
means pause playing for a number of seconds as given by the
<duration>
parameter.
An example prompt list:
%User1%;r=105,&pause(3),%User5%,%User9%;r=0-1350,&pause(15)
You can replace any of the following AA prompt lists with your own specified prompt lists:
The HDA50 supports only one session of AA at a time. Additional calls routed to the AA while a
session is in progress are rejected by the AA as busy.