Datasets:
Squidnutz
/
extractedtest

Dataset card Data Studio Files
xet
 Community
1
text
stringlengths
0
152
At this point you should have a list of the various channel types that you want to
page. Since Page() will nearly always want to signal more than one channel, we rec‐
ommend setting a global variable in the [globals] section of your extensions.conf file
that defines the list of channels to include, and then calling the Page() application
with that string:
[globals]
MULTICAST=MulticastRTP/linksys/239.0.0.1:1234
;MULTICAST=MulticastRTP/linksys/239.0.0.1:1234/239.0.0.1:6061 ; if you have SPA phones
BOGEN=PJSIP/ATAforPaging ; Assumes an ATA named [ATAforPaging]
PAGELIST=${MULTICAST}&${BOGEN} ; Variable names are arbitrary.
;...
[sets]
; ...
exten => *731,1,Page(${PAGELIST},i,120)
Parking and Paging
|
203
This example offers several possible configurations, depending on the hardware.
While it is not strictly required to have a PAGELIST variable defined, we have found
that this will tend to simplify the management of multiple paging resources, espe‐
cially during the configuration and testing process.
Zone Paging
Zone paging is popular in places such as automobile dealerships, where the parts
department, the sales department, and perhaps the used car department all require
paging, but do not want to hear each other’s pages.
In zone paging, the person sending the page needs to select which zone to page into.
A zone paging controller such as a Bogen PCM2000 is generally used to allow signal‐
ing of the different zones: the Page() application signals the zone controller, the zone
controller answers, and then an additional digit is sent to select to which zone the
page is to be sent. Most zone controllers will allow for a page to all zones, in addition
to combining zones (for example, a page to both the new- and used-car sales
departments).
You could also have separate extensions in the dialplan going to separate ATAs (or
groups of telephones), but this may prove more complicated and expensive than sim‐
ply purchasing a paging controller that is designed to handle this. Zone paging
doesn’t require any significantly different technology, but it does require a little more
thought and planning with respect to both the dialplan and the hardware.
And that’s parking and paging. It’s a ton of information to digest, but once you get the
hang of it, it’s quite logical.
Advanced Conferencing
The ConfBridge() application is an enhanced conferencing application in Asterisk
that delivers high-definition audio and basic video conferencing. We previously
introduced a basic working setup for ConfBridge(). If you’ve been building out your
dialplan as you read along, you’ll find a basic conference bridge in your exten‐
sions.conf file that looks something like this:
exten => 221,1,NoOp()
same => n,ConfBridge(${EXTEN})
In a traditional Asterisk configuration, there would be a confbridge.conf file where we
could configure parameters to apply to various scenarios. That is still possible, but it
no longer makes much sense to do it that way. So, we’re going to skip right over the
whole configuration file, except to say that the sample file (found at ~/src/
asterisk-15.<TAB>/configs/samples/confbridge.conf.sample) now becomes an excellent
reference document, but no more than that. Read on and this should start to make
sense.
204
|
Chapter 11: PBX Features, Including Parking, Paging, and Conferencing
First up, we need to explain that there are three types of items that can be configured
for a conference, namely bridge, menu, and user.
The bridge type defines the conference rooms themselves, the menu type defines
menus that can be accessed from the conferences, and the user type allows different
participants in the conference to have specific configuration applied to them. For
example, a large conference call might have a speaker (who will do most of the talk‐
ing), an administrator (to assist the speaker), and dozens of participants (who might
not be allowed to speak).
Let’s lay down a subroutine to get us started:
[subConference]
exten => _[0-9].,1,Noop(Creating conference room for ${EXTEN})
same => n,Goto(${ARG1})
same => n,Noop(INVALID ARGUMENT ARG1: ${ARG1})
same => n(admin),Noop()
same => n,Authenticate(${ARG2}) ; Could also use ,Set(CONFBRIDGE(user,pin)=${ARG2})
same => n,Set(ConfNum=$[${EXTEN} - 1]) ; Hack: Subtract 1 to get the conf number
same => n,Set(CONFBRIDGE(bridge,record_conference)=yes) ; Record when admin arrives
same => n,Set(RecordingFileName=${ConfNum}-${STRFTIME(,,%Y-%m-%d %H:%m:%S)})
same => n,Set(CONFBRIDGE(bridge,record_file)=${RecordingFileName}) ; unique name
same => n,Set(CONFBRIDGE(user,admin)=yes) ; Admin