Datasets:
Squidnutz
/
extractedtest

Dataset card Data Studio Files
xet
 Community
1
text
stringlengths
0
152
parkedcallstimeout context.
The dialplan (and contexts) were discussed in detail in Chap‐
ter 6.
The extension they will be sent to will be built from the name of the channel that
parked the call. For example, if a SIP peer named 0004F2040808 parked this call, the
extension will be SIP_0004F2040808.
If this extension does not exist, the call will be sent to the s extension in the parked
callstimeout context instead. Finally, if the s extension of parkedcallstimeout does
not exist, the call will be sent to the s extension of the default context.
196
|
Chapter 11: PBX Features, Including Parking, Paging, and Conferencing
Additionally, for any calls where comebacktoorigin=no, there will be an extension of
SIP_0004F2040808 created in the park-dial context. This extension will be set up to
do a Dial() to SIP/0004F2040808.4
If you are using parking, you are also going to need a way to announce the parked
calls so users know how to retrieve them. While you could just run down the hall
yelling “Bob, there’s a call for you on 701!,” the more professional method is to use a
paging system (more formally known as a public address system), which we will dis‐
cuss now.
Paging (aka Public Address)
In many PBX systems, it is useful to connect the telephone system to some sort of
public address system. This involves dialing a feature code or extension that makes a
connection to a public address resource of some kind, and then making an
announcement through the handset of the telephone that is broadcast to all devices
associated with that paging resource (perhaps you’ve heard the clerk at your grocery
store request a price check through the telephone). Often, this will be an external
paging system consisting of an amplifier connected to overhead speakers; however,
paging through the speakers of office telephones is also popular (mainly for cost rea‐
sons). If you have the budget (or an existing overhead paging system), overhead pag‐
ing is generally better, but set-based paging can work well in many environments. It is
also possible to have a mix of set-based and overhead paging, where, for example, set-
based paging might be in use for the administrative offices, but overhead paging
would be used for warehouse, hallway, parking lot, and public areas (cafeteria, recep‐
tion, etc.).
In Asterisk, the Page() application is used for paging. This application simply takes a
list of channels as its argument, calls all of the listed channels simultaneously, and, as
they are answered, puts each one into a conference room. With this in mind, it
becomes obvious that one requirement for paging to work is that each destination
channel must be able to automatically answer the incoming connection and place the
call onto a speaker of some sort (in other words, Page() won’t work if all the phones
just ring).
So, while the Page() application itself is painless and simple to use, getting all the des‐
tination channels to handle the incoming pages correctly is a bit trickier. We’ll get to
that shortly.
4 We hope you realize that the actual extension will be related to the channel name that parked the call, and will
not be SIP_0004F2040808 (unless Leif sells you the Polycom phone from his lab).
Parking and Paging
|
197
The Page() application takes three arguments: 1) the group of channels the page is to
be connected to, 2) the options, and 3) the timeout:
exten => *724,1,Noop(Page)
same => n,Set(ChannelsToPage=${UserA_DeskPhone}&${UserA_SoftPhone}}&${UserB_DeskPhone})
same => n,Page(${ChannelsToPage},i,120)
The options (outlined in Table 11-2) give you some flexibility with respect to how
Page() works, but the majority of the configuration is going to have to do with how
the target devices handle the incoming connection. We’ll dive into the various ways
you can configure devices to receive pages in the next section.
Table 11-2. Page() options
Option Description
d
Enables full-duplex audio
i
q
r
s
A(x)
n
Ignores attempts to
forward the call