text
stringlengths
0
152
yes, no
delete
no, yes
nextaf
tercmd
passwordlo
cation
yes, no
spooldir
Notes
If attach is enabled and messages are stored in different formats, this defines
which format is sent with the email notifications. Often wav49 is a good choice, as
it uses a better compression algorithm and thus will use less bandwidth, but
doesn’t sound crappy, as gsm does.
There are options that allow the callers to exit the voicemail system when they are
in the process of leaving a message (for example, pressing 0 to get an operator). By
default, the context the caller came from will be used as the exit context. If desired,
this setting will define a different context for callers exiting the voicemail system.
This should almost always be set to yes (even though it defaults to no). People
get upset if your voicemail system does not allow them to review their messages
prior to delivering them.
Best practice dictates that you should allow your callers to “zero out” from a
mailbox, should they not wish to leave a message. Note that an o extension (not
“zero,” but “oh”) is required in the exitcontext in order to handle these calls.
After an email message notification is sent (which could include the message itself),
the message will be deleted. This option is risky, because the fact that a message
was emailed is not a guarantee that it was received (spam filters seem to love to
delete Asterisk voicemail messages). On a new system, leave this at no until you
are certain that no messages are being lost due to spam filters.
This handy little setting will save you some time, as it takes you directly to the next
message once you’ve finished dealing with the current message.
If you want, you can have mailbox passwords stored in the spool folder for each
mailbox.a One of the advantages of using the spooldir option is that it will
allow you to define file #include statements in voicemail.conf (meaning you can
store mailbox references in multiple files, as you can with, for example, dialplan
code). This is not possible otherwise, because app_voicemail normally writes
password changes to the filesystem, and cannot update a mailbox password stored
outside of either voicemail.conf or the spool. If you do not use passwordloca
tion, you will not be able to define mailboxes outside of voicemail.conf, since
password updates will not happen. Storing passwords in a file in the specific
mailbox folder in the spool solves this problem.
a Typically the spool folder is /var/spool/asterisk, and it can be defined in /etc/asterisk/asterisk.conf.
The [zonemessages] Section
The next section of the voicemail.conf file is the [zonemessages] section. The purpose
of this section is to allow time zone–specific handling of messages, so you can play
back to the user messages with the correct timestamps. You can set the name of the
zone to whatever you need. Following the zone name, you can define which time
zone you want the name to refer to, as well as some options that define how time‐
stamps are played back. You can look at the ~//src/asterisk-16.<TAB>/configs/
samples/voicemail.conf.sample file for syntax details. Asterisk includes the examples
shown in Table 8-3. Any valid time zone known to the Linux system should be
The voicemail.conf File
|
135
configurable. Just use the Linux name for the zone, and then provide the details of
how you want it handled.
Table 8-3. [zonemessages] section options for voicemail.conf
Zone name
eastern
central
cen
tral24
military
Value/example
America/New_York|'vm-received'
Q 'digits/at' IMp
America/Chicago|'vm-received' Q
'digits/at' IMp
America/Chicago|'vm-received' q
'digits/at' H N 'hours'
Zulu|'vm-received' q 'digits/at'
H N 'hours'
'phonetic/z_p'
Notes
This value would be suitable for the Eastern time
zone (EST/EDT).
This value would be suitable for the Central time