6.43. voicemail.conf
1. Summary: This tutorial is written for the configuration files for the Asterisk functionality called VoiceMail. The idea of the Voicemail is similar to that of the answering machine. With the powerful engine that Asterisk provides us, we can extend this functionality beyond the imagination of the common user.
* A keyword is a predefined (by Asterisk) word with the meaning of setting. The keyword is located on the leftmost side of an entry line. Other words with similar meaning: setting, configuration setting and system variable
* An association statement is of the value '=' or '=>'. It delimits the keyword from the data and option fields in an entry.
* A data is the value that is been assigned to a keyword or option. Other words with similar meaning: value and set.
* An option is a string of characters which usually follows a data. Other words with similar meaning: optional keyword and optional setting.
* An entry is a single line of text containing a keyword, an association statement, a data and zero or more options.
* A comment is a line (entry) which is not been processed by Asterisk. This entry begins with ';' and is used for useful notes. Other words with similar meaning: note.
* A section is a string of characters enclosed in square brackets [abcdef123] and is used to denote a particular area of the configuration file.
* A context is a section which is equal to a context defined in other Asterisk configuration files.
* A mailbox_number is a special case of keyword for a numeric string defining a particular mailbox.
* A mailbox_password is a special case of keyword for a number string which represents the password for particular mailbox account.
* A User Name is a character string which represents the name of the owner of the particular mailbox.
* An account_mail is a character string which defines the primary e-mail of particular mailbox account.
* An account_pager is a character string which defines the secondary e-mail address for particular voicemail account. Most commonly used to send messages to pagers and SMS.
* A user_option(s) are options and other settings which apply to the current mailbox account only.
* A mailbox account is defined by unique mailbox_number, mailbox_password and optionally by account_mail, account_pager and user_options(s).
* A voicemail account is equal to mailbox account.
2. General Configuration – the general section of “voicemail.conf “ contains the settings which will be applied to every mailbox account. This section must be defined in the configuration file. The entries are in the following format: 'keyword=data'. If particular keyword is not presented in the general section its value won't change and it will remain with its default value (data). The keywords available in the general section are as follows:
3. Zonemessages configuration - except [general], there is one more special area in voicemail.conf , this is the [zonemessages]. In this section of this tutorial we will describe the use of [zonemessages] area. In this section of voicemail.conf you can specify custom timezones for your voicemail users. Timezones configuration begins with the [zonemessages] tag and finishes at the beginning of the next context. The declaration of a timezone has the following syntax:
Country - the Country that the user is located in
City - the name of the City that the user is located in.
Asterisk searches your timezones files for the Country and City that you have specified. By default the timezones files are located in /usr/share/zoneinfo (basically they are the valid timezones that you can set in as timezone of your computer). In Options you can specify the rest of the configuration of the current timezone. Most of the options are concerning the way that the date and time are pronounced for the current timezone. Here are the possible configurations (note that everything that is within the quotes in the upper description is been pronounced by Asterisk server) :
Here is sample of a [timemessages] configuration:
Basically sofia12 is an abstract name of the timezone. Asterisk will detect the timezone of Sofia (which is +2 GMT) and will coordinate the time. The options indicate that Asterisk will first play the file named "received-bg", then it will play the date (following the format of q, which is "", "yesterday", weekday, or ABdY), then Asterisk will play file named "time-was-bg", then it will play the current hour (in 12 hour clock format), then it will "announce", how much minutes have passed after the beginning of the current hour, and finally it will pronounce if it is AM or PM. This abstract name is used only for applying the timezone on the target user and the name of the zone have no relations with the timezone settings. In order to apply a timezone to a target voice mail user you should use the 'tz' keyword (and set the wanted timezone name as value to the 'tz' keyword) as an option.
4. Mailbox accounts - mailboxes are stored into one or more contexts. By default there is a [default] context but you can remove it if you like so. Even if you remove the [default] context from voicemail.conf Asterisk will create a virtual [default] context when parsing your configuration file. The server won't add it (the virtual [default] context) to your voicemail.conf but if you list your mailboxes by using the 'voicemail list users' you will see that there is such context. The reason for this behavior is that based on usercontext keyword, if you set the data of usercontext (the default data of usercontext is default, see usercontext keyword for more details) to other context, Asterisk won't create [default]. However if you set usercontext to non-existing context, Asterisk will create it in the same manner as [default].
Defining mailboxes is similar to extensions and zonemessages syntax. There are three obligatory components of the definition: mailbox number, mailbox secret and mailbox's user's name. The mailbox number should be a unique string for each context (this means that you can't have duplicated mailboxes in one context). However you can have two mailboxes with identical mailbox number, but only if they are in different contexts. The mailbox's secret and the user's name are not unique fields and they can be duplicated even in one context. The mailbox's number may contain only numbers and letters in it. Any different symbols included into this filed will result in unexpected behavior of the server, such as parsing errors, unaccessible mailbox or even server crashes. The mailbox's secret may contain only numbers and 'A','B','C','D' (as letters), but the use of those letters is not recommended, any different symbols included into the secret will result in unexpected behavior of the server, such as parsing errors, unaccessible mailbox or even server crashes. The user's name may contain numbers, letters and ' '(spaces), but special symbols are forbidden. The syntax of declaring mailbox is the following:
There are some optional fields in the definition of a voicemail account. You can define user's e-mail address for notification messages, secondary e-mail address (SMS, pager) and almost all options available in the [general] area. Here is the syntax for those optional fields:
Mailboxes 1111, 2222 and 3333 are defined correctly. The rest of the mailboxes (4444, 5555 and 6666) have the following mistakes:
Here are the correct versions of the mistaken mailboxes:
5. Links related to voicemail
6. Examples - some real examles that will show you how to use all this in order to make it work.
Some notes and definitions to the reader to understand this tutorial:
* A keyword is a predefined (by Asterisk) word with the meaning of setting. The keyword is located on the leftmost side of an entry line. Other words with similar meaning: setting, configuration setting and system variable
* An association statement is of the value '=' or '=>'. It delimits the keyword from the data and option fields in an entry.
* A data is the value that is been assigned to a keyword or option. Other words with similar meaning: value and set.
* An option is a string of characters which usually follows a data. Other words with similar meaning: optional keyword and optional setting.
* An entry is a single line of text containing a keyword, an association statement, a data and zero or more options.
* A comment is a line (entry) which is not been processed by Asterisk. This entry begins with ';' and is used for useful notes. Other words with similar meaning: note.
* A section is a string of characters enclosed in square brackets [abcdef123] and is used to denote a particular area of the configuration file.
* A context is a section which is equal to a context defined in other Asterisk configuration files.
* A mailbox_number is a special case of keyword for a numeric string defining a particular mailbox.
* A mailbox_password is a special case of keyword for a number string which represents the password for particular mailbox account.
* A User Name is a character string which represents the name of the owner of the particular mailbox.
* An account_mail is a character string which defines the primary e-mail of particular mailbox account.
* An account_pager is a character string which defines the secondary e-mail address for particular voicemail account. Most commonly used to send messages to pagers and SMS.
* A user_option(s) are options and other settings which apply to the current mailbox account only.
* A mailbox account is defined by unique mailbox_number, mailbox_password and optionally by account_mail, account_pager and user_options(s).
* A voicemail account is equal to mailbox account.
2. General Configuration – the general section of “voicemail.conf “ contains the settings which will be applied to every mailbox account. This section must be defined in the configuration file. The entries are in the following format: 'keyword=data'. If particular keyword is not presented in the general section its value won't change and it will remain with its default value (data). The keywords available in the general section are as follows:
attach – this keyword determines if the audio file (containing voice mail message) will be send to the user via attachment to the e-mail notification message.
attachfmt - this keyword specify which of the recorded formats should be attached to the email notification message. By default Asterisk attaches the first format specified in format keyword. This keyword can used for alternation of the format that is been sent to all users and also to specify different format curtain mailboxes.
authpassword – this keyword represents the password that Asterisk will use in order to authorize to the IMAP server. Usually this keyword is specified as option to every user rather to set it global in the [general]. The username (specified in authuser) should be registered on the IMAP server, and the password specified in the current keyword should be a valid combination on the IMAP server if you want to work with the IMAP storage functionality.
authuser – this keyword represents the username that Asterisk will use in order to authorize to the IMAP server. This username should be registered on the IMAP server if you want to work with the IMAP storage functionality.
callback – this keyword determines the outgoing context for the “return phone call” feature available in the advanced voice mail features menu.
cidinternalcontexts – this keyword defines the so called internal contexts. You may specify a list of contexts, which will be detected as internal for the dial plan. This will result in change of the voice prompt (the prompt will evolve from “Call from 987654321” to “Call from extension ...”).
dbhost – this keyword specifies the database server hostname. You may specify an IP address as well as hostname. This host will be used only from Voicemail module. If you want to use it for other modules, you will have to include it in their configuration files by using the appropriate keyword (the keyword might differ 'dbhost' for other modules).
dbname – this keyword specifies the MySQL or PostgreSQL database name. This database name will be used only from Voicemail module. If you want to use it for other modules, you will have to include it in their configuration files by using the appropriate keyword (the keyword might differ 'dbname' for other modules).
dboption – this keyword specifies additional options for PostgreSQL database. These additional options will be used only from Voicemail module. If you want to use them for other modules, you will have to include them in their configuration files by using the appropriate keyword (the keyword might differ 'dboption' for other modules).
dbpass – this keyword specifies the password that is been used for the connection (authorization and authentication process) to the database (MySQL or PostegreSQL). This password will be used only from Voicemail module. If you want to use it for other modules, you will have to include it in their configuration files by using the appropriate keyword (the keyword might differ 'dbpass' for other modules).
dbuser – this keyword specifies the username that is been used for the connection (authorization and authentication process) to the database (MySQL or PostegreSQL). This username will be used only from Voicemail module. If you want to use it for other modules, you will have to include it in their configuration files by using the appropriate keyword (the keyword might differ 'dbuser' for other modules).
delete – this keyword defines if the voice mail files (audio and configuration files) should be deleted (after been e-mailed for example).
dialout – this keyword determines the outgoing context for the “place an outgoing call” feature available in the advanced voice mail features menu.
emailbody – this keyword contains the notification message that is been sent via e-mail. This keyword supports variable substitution.
emaildateformat - this keyword defines the format of the date of the notification message. You can combine some valid arguments with free text.
emailsubject– this keyword contains the subject of the notification message that is been sent via e-mail. This keyword supports variable substitution.
envelope – this keyword defines if Asterisk will play the message envelope (date/time) before playing the message itself. This does not affects the envelop playing in the advanced voice mail menu.
exitcontext – this keyword sets an optional context in which the user will be dropped after leaving the voice mail (by pressing * or 0).
expungeonhangup – this keyword defines if Asterisk will delete all messages marked for deletion (but not deleted) after the connection is hanged up.
externnotify – this keyword defines an external application (script) which will be executed when a user exits the system (finishes leaving message in the mailbox or exits the Voice Mail menu created by the VoiceMailMenu() application). The program is run with the following arguments: context, extension, number of messages in the current mailbox.
externpass - this keyword defines an external application (script) which will be executed when a user changes his mailbox's password.
forcegreetings – when a 'new user' connects to the voice mail system (by using VoiceMailMain() application) he/she will be forced by Asterisk to make new recording of his/hers greeting.
forcename – when a 'new user' connects to the voice mail system (by using VoiceMailMain() application) he/she will be forced by Asterisk to make new recording of his/hers name.
format – this keyword defines in which format the audio message will be encoded and saved on the HDD.
fromstring – this keyword contains the from field of the notification message that is been sent via e-mail. This keyword supports variable substitution.
hidefromdir – this keyword (if set to yes) force Asterisk to hide curtain mailbox (if you use it in general Asterisk will apply this keyword to all mailboxes) from the list that is created by app_directory.
imapflags – this keyword defines a string which is used during the work with IMAP server. This string represents any options and settings different from hostname, port, username and password.
imapport – this keyword defines the port that Asterisk will use in order to connect to IMAP server. By default the port is 143, however it exact port depends on IMAP server configuration (find at which port IMAP server is working). The value of imapport should be a positive integer lower than 65536 (in order be a valid port).
imapserver – this keyword defines the address/hostname of the IMAP server. If you set a hostname (like imap.domain.com) Asterisk will try to resolve it with the default DNS server that is been set for the server. If you set an IP address Asterisk will try to make a direct connection to it.
mailcmd – by using this keyword you can override the default mailer application. Instead of executing the default mailer application, Asterisk will execute your custom program.
maxgreet – this keyword defines the time limitation of the user-recordable voice mail greeting. The value of 0 means there is no limitation. This keyword applies to the lengths of the unavailable greeting, the busy greeting and the user name message. The keyword accepts integer values, where the value is the limitation in seconds.
maxlogins – this application defines the maximum unsuccessful login attempts before Asterisk hang up the connection to the user. This keyword accepts only positive integer values.
maxmessage – this keyword defines the time limitation of the the voice mail message. The value of 0 means that there is no limitation.
maxmsg – this keyword defines the maximum amount of messages for curtain mailbox. If a mailbox reaches the value that is assigned to maxmsg keyword no new messages can be recorded in this mailbox. Additionally vm-mailboxfull is been played to the caller in case the mailbox is full.
maxsilence – if Asterisk detects a contiguous period of silence, the server will stop recording the message by hanging up the call. If a value of 0 is presented, the silence detector is disabled for Voicemail module. The keyword accepts positive integers (or zero) where the value is the period in seconds.
minmessage – this keyword defines the the time minimum limitation of the the voice mail message. The value of 0 means that there is no minimum limitation. If the audio file that the server has recorded is too short it won't be processed (won't be e-mailed, saved on the HDD, etc...).
nextaftercmd – this keyword defines if Asterisk should automatically play the next message after deletion of a voice mail message.
operator – this keyword defines the availability of the “Operator” functionality while the voice mail message is being recorded. Additionally this keyword defines the availability of the same functionality after the end of the recording process.
pagerbody – this keyword contains the notification message that is sent to the pager address. This keyword supports variable substitution.
pagerfromstring – this keyword contains the from field of the notification message that is sent to the pager address. This keyword supports variable substitution.
pagersubject – this keyword contains the subject of the notification message that is sent to the pager address. This keyword supports variable substitution.
pbxskip – this setting defines if the PBX string should be skipped in the subject of the e-mail notification message that is sent to the user.
review – this keyword defines if the caller will be able to hear his recorded message before it is been processed. The caller have options to commit the message (by pressing '#') or hang up the call (this will result in no message delivered).
saycid – this keyword defines the priority of playing between the caller's phone number and the voice mail message itself. If the value of saycid is set to yes Asterisk will first play the caller's phone number and then the message itself.
sendvoicemail – this keyword defines if the “Leave a message” menu option is available in the Advanced Options menu. If this functionality is enabled, a voice mail user will be able to directly send a voice mail message to another user via his voice mail menu.
severemail – this keyword’s value is been used for the source (return e-mail address) of the voicemail notification message. If the data string is a valid e-mail address (account@somemail.com), Asterisk will send the notification message with this return address. If you set the string without ‘@’, Asterisk will append @somehost.com, where somehost.com will be the server’s hostname.
silencethreshold – this keyword configures the silence detection threshold, which is used for maxsilence keyword. If you set a lower value to the silencethreshhold keyword, the sensitivity of the silence detector will fall down (the system will recognize silence in more noisy calls). The value of silencethreshold should be greater or equal to 0 and lower than 256.
tempgreetwarn - this keyword toggles the working state of the functionality to remind the user if their temporary greeting is set.
* data: set /yes | no /
* default: no
* remark: Asterisk will attach only the file with the first format included into format keyword.
* remark: Asterisk will send attachment only to the primary e-mail address.
* default: no
* remark: Asterisk will attach only the file with the first format included into format keyword.
* remark: Asterisk will send attachment only to the primary e-mail address.
attachfmt - this keyword specify which of the recorded formats should be attached to the email notification message. By default Asterisk attaches the first format specified in format keyword. This keyword can used for alternation of the format that is been sent to all users and also to specify different format curtain mailboxes.
* data: string /format/
* default: empty string /Asterisk takes the default format from format keyword/
* default: empty string /Asterisk takes the default format from format keyword/
authpassword – this keyword represents the password that Asterisk will use in order to authorize to the IMAP server. Usually this keyword is specified as option to every user rather to set it global in the [general]. The username (specified in authuser) should be registered on the IMAP server, and the password specified in the current keyword should be a valid combination on the IMAP server if you want to work with the IMAP storage functionality.
* data: string /password/
* default: empty string
* remark: this keyword is available only if you compile Asterisk with IMAP support.
* remark: the support of IMAP has been introduced in Asterisk version 1.4
* default: empty string
* remark: this keyword is available only if you compile Asterisk with IMAP support.
* remark: the support of IMAP has been introduced in Asterisk version 1.4
authuser – this keyword represents the username that Asterisk will use in order to authorize to the IMAP server. This username should be registered on the IMAP server if you want to work with the IMAP storage functionality.
* data: string /username/
* default: empty string
* remark: this keyword is available only if you compile Asterisk with imap support.
* remark: the support of imap has been introduced in Asterisk version 1.4
* default: empty string
* remark: this keyword is available only if you compile Asterisk with imap support.
* remark: the support of imap has been introduced in Asterisk version 1.4
callback – this keyword determines the outgoing context for the “return phone call” feature available in the advanced voice mail features menu.
* data: string /context/
* default: empty string
* remark: this keyword (setting) is available only in the extended versions of Asterisk with advanced voice mail * feature support.
* default: empty string
* remark: this keyword (setting) is available only in the extended versions of Asterisk with advanced voice mail * feature support.
cidinternalcontexts – this keyword defines the so called internal contexts. You may specify a list of contexts, which will be detected as internal for the dial plan. This will result in change of the voice prompt (the prompt will evolve from “Call from 987654321” to “Call from extension ...”).
* data: string array, delimiter – comma (contexts list separated with commas)
* default: empty srting (no contexts defined).
* remark: this keyword (setting) is available only in the extended versions of Asterisk with advanced voice mail feature support.
* default: empty srting (no contexts defined).
* remark: this keyword (setting) is available only in the extended versions of Asterisk with advanced voice mail feature support.
dbhost – this keyword specifies the database server hostname. You may specify an IP address as well as hostname. This host will be used only from Voicemail module. If you want to use it for other modules, you will have to include it in their configuration files by using the appropriate keyword (the keyword might differ 'dbhost' for other modules).
* data: string (hostname or IP address)
* default: empty srting (no hostname specified).
* remark: you should compile your Asterisk with database (PostgreSQL or MySQL) support if you use database. If you specify this keyword without database support, nothing will happen.
* default: empty srting (no hostname specified).
* remark: you should compile your Asterisk with database (PostgreSQL or MySQL) support if you use database. If you specify this keyword without database support, nothing will happen.
dbname – this keyword specifies the MySQL or PostgreSQL database name. This database name will be used only from Voicemail module. If you want to use it for other modules, you will have to include it in their configuration files by using the appropriate keyword (the keyword might differ 'dbname' for other modules).
* data: string (database name)
* default: “vmdb” (without the quotes)
* remark: you should compile your Asterisk with database (PostgreSQL or MySQL) support if you use database. If you specify this keyword without database support, nothing will happen.
* default: “vmdb” (without the quotes)
* remark: you should compile your Asterisk with database (PostgreSQL or MySQL) support if you use database. If you specify this keyword without database support, nothing will happen.
dboption – this keyword specifies additional options for PostgreSQL database. These additional options will be used only from Voicemail module. If you want to use them for other modules, you will have to include them in their configuration files by using the appropriate keyword (the keyword might differ 'dboption' for other modules).
* data: string (options)
* default: empty string
* remark: you should compile your Asterisk with PostgreSQL database support if you use this keyword.
* default: empty string
* remark: you should compile your Asterisk with PostgreSQL database support if you use this keyword.
dbpass – this keyword specifies the password that is been used for the connection (authorization and authentication process) to the database (MySQL or PostegreSQL). This password will be used only from Voicemail module. If you want to use it for other modules, you will have to include it in their configuration files by using the appropriate keyword (the keyword might differ 'dbpass' for other modules).
* data: string (password)
* default: “test” (without the quotes)
* remark: you should compile your Asterisk with database (PostgreSQL or MySQL) support if you use database. If you specify this keyword without database support, nothing will happen.
* default: “test” (without the quotes)
* remark: you should compile your Asterisk with database (PostgreSQL or MySQL) support if you use database. If you specify this keyword without database support, nothing will happen.
dbuser – this keyword specifies the username that is been used for the connection (authorization and authentication process) to the database (MySQL or PostegreSQL). This username will be used only from Voicemail module. If you want to use it for other modules, you will have to include it in their configuration files by using the appropriate keyword (the keyword might differ 'dbuser' for other modules).
* data: string (username)
* default: “test” (without the quotes)
* remark: you should compile your Asterisk with database (PostgreSQL or MySQL) support if you use database. If you specify this keyword without database support, nothing will happen.
* default: “test” (without the quotes)
* remark: you should compile your Asterisk with database (PostgreSQL or MySQL) support if you use database. If you specify this keyword without database support, nothing will happen.
delete – this keyword defines if the voice mail files (audio and configuration files) should be deleted (after been e-mailed for example).
* data: set /yes|no/
* default: no (it won't delete the message)
* remark: this keyword (when used as “per account”option) needs to be prefixed by different keyword, for example: 1234 => 7890,My Name,my.name@office.org,,attache=yes|delete=yes
* default: no (it won't delete the message)
* remark: this keyword (when used as “per account”option) needs to be prefixed by different keyword, for example: 1234 => 7890,My Name,my.name@office.org,,attache=yes|delete=yes
dialout – this keyword determines the outgoing context for the “place an outgoing call” feature available in the advanced voice mail features menu.
* data: string /context/
* default: empty string
* remark: this keyword (setting) is available only in the extended versions of Asterisk with advanced voice mail feature support.
* default: empty string
* remark: this keyword (setting) is available only in the extended versions of Asterisk with advanced voice mail feature support.
emailbody – this keyword contains the notification message that is been sent via e-mail. This keyword supports variable substitution.
* data: string /message/
* default: the default message that is hard coded into Asterisk
* remark: The emailbody keyword's value can only be up to 512 characters due to a limitation in the Asterisk configuration subsystem.
* default: the default message that is hard coded into Asterisk
* remark: The emailbody keyword's value can only be up to 512 characters due to a limitation in the Asterisk configuration subsystem.
emaildateformat - this keyword defines the format of the date of the notification message. You can combine some valid arguments with free text.
* data: string /date, see valid arguments/
* default: %A, %B %d, %Y at %r
* valid arguments:
* default: %A, %B %d, %Y at %r
* valid arguments:
%a - The abbreviated weekday name according to the current locale.
%A - The full weekday name according to the current locale.
%b - The abbreviated month name according to the current locale.
%B - The full month name according to the current locale.
%c - The preferred date and time representation for the current locale.
%C - The century number (year/100) as a 2-digit integer. (SU)
%d - The day of the month as a decimal number (range 01 to 31).
%D - Equivalent to %m/%d/%y. (Yecch — for Americans only. Americans should note that in other countries %d/%m/%y is rather common. This means that in international context this format is ambiguous and should not be used.) (SU)
%e - Like %d, the day of the month as a decimal number, but a leading zero is replaced by a space. (SU)
%E - Modifier: use alternative format, see below. (SU)
%F - Equivalent to %Y-%m-%d (the ISO 8601 date format). (C99)
%G - The ISO 8601 year with century as a decimal number. The 4-digit year corresponding to the ISO week number (see %V). This has the same format and value as %y, except that if the ISO week number belongs to the previous or next year, that year is used instead. (TZ)
%g - Like %G, but without century, i.e., with a 2-digit year (00-99). (TZ)
%h - Equivalent to %b. (SU)
%H - The hour as a decimal number using a 24-hour clock (range 00 to 23).
%I - The hour as a decimal number using a 12-hour clock (range 01 to 12).
%j - The day of the year as a decimal number (range 001 to 366).
%k - The hour (24-hour clock) as a decimal number (range 0 to 23); single digits are preceded by a blank. (See also %H.) (TZ)
%l - The hour (12-hour clock) as a decimal number (range 1 to 12); single digits are preceded by a blank. (See also %I.) (TZ)
%m - The month as a decimal number (range 01 to 12).
%M - The minute as a decimal number (range 00 to 59).
%n - A newline character. (SU)
%O - Modifier: use alternative format, see below. (SU)
%p - Either ‘AM’ or ‘PM’ according to the given time value, or the corresponding strings for the current locale. Noon is treated as ‘pm’ and midnight as ‘am’.
%P - Like %p but in lowercase: ‘am’ or ‘pm’ or a corresponding string for the current locale. (GNU)
%r - The time in a.m. or p.m. notation. In the POSIX locale this is equivalent to ‘%I:%M:%S %p’. (SU)
%R - The time in 24-hour notation (%H:%M). (SU) For a version including the seconds, see %T below.
%s - The number of seconds since the Epoch, i.e., since 1970-01-01 00:00:00 UTC. (TZ)
%S - The second as a decimal number (range 00 to 60). (The range is up to 60 to allow for occasional leap seconds.)
%t - A tab character. (SU)
%T - The time in 24-hour notation (%H:%M:%S). (SU)
%u - The day of the week as a decimal, range 1 to 7, Monday being 1. See also %w. (SU)
%U - The week number of the current year as a decimal number, range 00 to 53, starting with the first Sunday as the first day of week 01. See also %V and %W.
%V - The ISO 8601:1988 week number of the current year as a decimal number, range 01 to 53, where week 1 is the first week that has at least 4 days in the current year, and with Monday as the first day of the week. See also %U and %W. (SU)
%w - The day of the week as a decimal, range 0 to 6, Sunday being 0. See also %u.
%W - The week number of the current year as a decimal number, range 00 to 53, starting with the first Monday as the first day of week 01.
%x - The preferred date representation for the current locale without the time.
%X - The preferred time representation for the current locale without the date.
%y - The year as a decimal number without a century (range 00 to 99).
%Y - The year as a decimal number including the century.
%z - The time-zone as hour offset from GMT. Required to emit RFC 822-conformant dates (using "%a, %d %b %Y %H:%M:%S %z"). (GNU)
%Z - The time zone or name or abbreviation.
%+ - The date and time in date(1) format. (TZ) (Not supported in glibc2.)
%% - A literal ‘%’ character.
%A - The full weekday name according to the current locale.
%b - The abbreviated month name according to the current locale.
%B - The full month name according to the current locale.
%c - The preferred date and time representation for the current locale.
%C - The century number (year/100) as a 2-digit integer. (SU)
%d - The day of the month as a decimal number (range 01 to 31).
%D - Equivalent to %m/%d/%y. (Yecch — for Americans only. Americans should note that in other countries %d/%m/%y is rather common. This means that in international context this format is ambiguous and should not be used.) (SU)
%e - Like %d, the day of the month as a decimal number, but a leading zero is replaced by a space. (SU)
%E - Modifier: use alternative format, see below. (SU)
%F - Equivalent to %Y-%m-%d (the ISO 8601 date format). (C99)
%G - The ISO 8601 year with century as a decimal number. The 4-digit year corresponding to the ISO week number (see %V). This has the same format and value as %y, except that if the ISO week number belongs to the previous or next year, that year is used instead. (TZ)
%g - Like %G, but without century, i.e., with a 2-digit year (00-99). (TZ)
%h - Equivalent to %b. (SU)
%H - The hour as a decimal number using a 24-hour clock (range 00 to 23).
%I - The hour as a decimal number using a 12-hour clock (range 01 to 12).
%j - The day of the year as a decimal number (range 001 to 366).
%k - The hour (24-hour clock) as a decimal number (range 0 to 23); single digits are preceded by a blank. (See also %H.) (TZ)
%l - The hour (12-hour clock) as a decimal number (range 1 to 12); single digits are preceded by a blank. (See also %I.) (TZ)
%m - The month as a decimal number (range 01 to 12).
%M - The minute as a decimal number (range 00 to 59).
%n - A newline character. (SU)
%O - Modifier: use alternative format, see below. (SU)
%p - Either ‘AM’ or ‘PM’ according to the given time value, or the corresponding strings for the current locale. Noon is treated as ‘pm’ and midnight as ‘am’.
%P - Like %p but in lowercase: ‘am’ or ‘pm’ or a corresponding string for the current locale. (GNU)
%r - The time in a.m. or p.m. notation. In the POSIX locale this is equivalent to ‘%I:%M:%S %p’. (SU)
%R - The time in 24-hour notation (%H:%M). (SU) For a version including the seconds, see %T below.
%s - The number of seconds since the Epoch, i.e., since 1970-01-01 00:00:00 UTC. (TZ)
%S - The second as a decimal number (range 00 to 60). (The range is up to 60 to allow for occasional leap seconds.)
%t - A tab character. (SU)
%T - The time in 24-hour notation (%H:%M:%S). (SU)
%u - The day of the week as a decimal, range 1 to 7, Monday being 1. See also %w. (SU)
%U - The week number of the current year as a decimal number, range 00 to 53, starting with the first Sunday as the first day of week 01. See also %V and %W.
%V - The ISO 8601:1988 week number of the current year as a decimal number, range 01 to 53, where week 1 is the first week that has at least 4 days in the current year, and with Monday as the first day of the week. See also %U and %W. (SU)
%w - The day of the week as a decimal, range 0 to 6, Sunday being 0. See also %u.
%W - The week number of the current year as a decimal number, range 00 to 53, starting with the first Monday as the first day of week 01.
%x - The preferred date representation for the current locale without the time.
%X - The preferred time representation for the current locale without the date.
%y - The year as a decimal number without a century (range 00 to 99).
%Y - The year as a decimal number including the century.
%z - The time-zone as hour offset from GMT. Required to emit RFC 822-conformant dates (using "%a, %d %b %Y %H:%M:%S %z"). (GNU)
%Z - The time zone or name or abbreviation.
%+ - The date and time in date(1) format. (TZ) (Not supported in glibc2.)
%% - A literal ‘%’ character.
emailsubject– this keyword contains the subject of the notification message that is been sent via e-mail. This keyword supports variable substitution.
* data: string /subject/
* default: the default subject that is hard coded into Asterisk
* remark: see appendix for available variables and examples.
* default: the default subject that is hard coded into Asterisk
* remark: see appendix for available variables and examples.
envelope – this keyword defines if Asterisk will play the message envelope (date/time) before playing the message itself. This does not affects the envelop playing in the advanced voice mail menu.
* data: set /yes|no/
* default: yes
* remark: this keyword is available for use in Asterisk CVS verions dated 19/05/04 or later.
* default: yes
* remark: this keyword is available for use in Asterisk CVS verions dated 19/05/04 or later.
exitcontext – this keyword sets an optional context in which the user will be dropped after leaving the voice mail (by pressing * or 0).
* data: string /context/
* default: empty string
* default: empty string
expungeonhangup – this keyword defines if Asterisk will delete all messages marked for deletion (but not deleted) after the connection is hanged up.
* data: set /yes|no/
* default: no
* remark: this keyword is available only if you compile Asterisk with IMAP support.
* remark: the support of IMAP has been introduced in Asterisk version 1.4
* default: no
* remark: this keyword is available only if you compile Asterisk with IMAP support.
* remark: the support of IMAP has been introduced in Asterisk version 1.4
externnotify – this keyword defines an external application (script) which will be executed when a user exits the system (finishes leaving message in the mailbox or exits the Voice Mail menu created by the VoiceMailMenu() application). The program is run with the following arguments: context, extension, number of messages in the current mailbox.
* data: string /[path and] application/
* default: empty string (nothing runs)
* default: empty string (nothing runs)
externpass - this keyword defines an external application (script) which will be executed when a user changes his mailbox's password.
*data: string /[path and] application/
*default: empty string (Asterisk uses its internal function for password management)
*remark: the use of this keyword prevents Asterisk from running the internal function change_password in order to regenerate the “voicemail.conf” configuration file. Which means that you'll have to regenerate it yourself.
*remark: before Asterisk version 1.0.10, the server have to be reloaded in order the the password to be updated in the memory. Since version 1.0.10, the server handles the change of the password immediately.
*default: empty string (Asterisk uses its internal function for password management)
*remark: the use of this keyword prevents Asterisk from running the internal function change_password in order to regenerate the “voicemail.conf” configuration file. Which means that you'll have to regenerate it yourself.
*remark: before Asterisk version 1.0.10, the server have to be reloaded in order the the password to be updated in the memory. Since version 1.0.10, the server handles the change of the password immediately.
forcegreetings – when a 'new user' connects to the voice mail system (by using VoiceMailMain() application) he/she will be forced by Asterisk to make new recording of his/hers greeting.
*data: set /yes|no/
*default: no
*remark: the definition of 'new user' is the following - every user whose password is the same as his mailbox number is marked as 'new user' by the Asterisk
*default: no
*remark: the definition of 'new user' is the following - every user whose password is the same as his mailbox number is marked as 'new user' by the Asterisk
forcename – when a 'new user' connects to the voice mail system (by using VoiceMailMain() application) he/she will be forced by Asterisk to make new recording of his/hers name.
*data: set /yes|no/
*default: no
*remark: the definition of 'new user' is the following - every user whose password is the same as his mailbox number is marked as 'new user' by the Asterisk
*default: no
*remark: the definition of 'new user' is the following - every user whose password is the same as his mailbox number is marked as 'new user' by the Asterisk
format – this keyword defines in which format the audio message will be encoded and saved on the HDD.
*data: set array (delimiter |)
*default: wav49|gsm|wav (be sure to set this keyword up)
*remark: Asterisk will attach to email only the file with the first format included into format keyword.
*remark: for more information on formats see the appendix.
*remark: see Tips & Tricks for some examples.
*default: wav49|gsm|wav (be sure to set this keyword up)
*remark: Asterisk will attach to email only the file with the first format included into format keyword.
*remark: for more information on formats see the appendix.
*remark: see Tips & Tricks for some examples.
fromstring – this keyword contains the from field of the notification message that is been sent via e-mail. This keyword supports variable substitution.
*data: string /from/
*default: From: Asterisk PBX <who>
*default: From: Asterisk PBX <who>
hidefromdir – this keyword (if set to yes) force Asterisk to hide curtain mailbox (if you use it in general Asterisk will apply this keyword to all mailboxes) from the list that is created by app_directory.
*data: set /yes|no/
*default: no
*remark: this keyword has relation with app_directory. By default this application is compiled with Asterisk. Using this keyword without this application might have unexpected results.
*default: no
*remark: this keyword has relation with app_directory. By default this application is compiled with Asterisk. Using this keyword without this application might have unexpected results.
imapflags – this keyword defines a string which is used during the work with IMAP server. This string represents any options and settings different from hostname, port, username and password.
*data: string /optional flags/
*default: empty string
*remark: this keyword is available only if you compile Asterisk with IMAP support.
*remark: the support of IMAP has been introduced in Asterisk version 1.4
*default: empty string
*remark: this keyword is available only if you compile Asterisk with IMAP support.
*remark: the support of IMAP has been introduced in Asterisk version 1.4
imapport – this keyword defines the port that Asterisk will use in order to connect to IMAP server. By default the port is 143, however it exact port depends on IMAP server configuration (find at which port IMAP server is working). The value of imapport should be a positive integer lower than 65536 (in order be a valid port).
*data: integer /port/
*default: 143
*remark: this keyword is available only if you compile Asterisk with IMAP support.
*remark: the support of IMAP has been introduced in Asterisk version 1.4
*default: 143
*remark: this keyword is available only if you compile Asterisk with IMAP support.
*remark: the support of IMAP has been introduced in Asterisk version 1.4
imapserver – this keyword defines the address/hostname of the IMAP server. If you set a hostname (like imap.domain.com) Asterisk will try to resolve it with the default DNS server that is been set for the server. If you set an IP address Asterisk will try to make a direct connection to it.
*data: string /hostname or IP address/
*default: empty string
*remark: this keyword is available only if you compile Asterisk with IMAP support.
*remark: the support of IMAP has been introduced in Asterisk version 1.4
*default: empty string
*remark: this keyword is available only if you compile Asterisk with IMAP support.
*remark: the support of IMAP has been introduced in Asterisk version 1.4
mailcmd – by using this keyword you can override the default mailer application. Instead of executing the default mailer application, Asterisk will execute your custom program.
*data: string /[path and] application/
*default: /usr/bin/sendmail -t
*default: /usr/bin/sendmail -t
maxgreet – this keyword defines the time limitation of the user-recordable voice mail greeting. The value of 0 means there is no limitation. This keyword applies to the lengths of the unavailable greeting, the busy greeting and the user name message. The keyword accepts integer values, where the value is the limitation in seconds.
*data: integer (limit)
*default: 0 (no limitation)
*default: 0 (no limitation)
maxlogins – this application defines the maximum unsuccessful login attempts before Asterisk hang up the connection to the user. This keyword accepts only positive integer values.
*data: positive integer (logins)
*default: 3
*default: 3
maxmessage – this keyword defines the time limitation of the the voice mail message. The value of 0 means that there is no limitation.
*data: integer (limit)
*default: 0
*default: 0
maxmsg – this keyword defines the maximum amount of messages for curtain mailbox. If a mailbox reaches the value that is assigned to maxmsg keyword no new messages can be recorded in this mailbox. Additionally vm-mailboxfull is been played to the caller in case the mailbox is full.
*data: positive integer, should be less than 9999 (limit)
*default: 100
*remark: this keyword is available since Asterisk 1.2. In previous versions of Asterisk, the maximum amount of messages was constantly set to 100.
*default: 100
*remark: this keyword is available since Asterisk 1.2. In previous versions of Asterisk, the maximum amount of messages was constantly set to 100.
maxsilence – if Asterisk detects a contiguous period of silence, the server will stop recording the message by hanging up the call. If a value of 0 is presented, the silence detector is disabled for Voicemail module. The keyword accepts positive integers (or zero) where the value is the period in seconds.
*data: integer (limit)
*default: 0 (disabled)
*default: 0 (disabled)
minmessage – this keyword defines the the time minimum limitation of the the voice mail message. The value of 0 means that there is no minimum limitation. If the audio file that the server has recorded is too short it won't be processed (won't be e-mailed, saved on the HDD, etc...).
*data: integer (limit)
*default: 0
*default: 0
nextaftercmd – this keyword defines if Asterisk should automatically play the next message after deletion of a voice mail message.
*data: set /yes|no/
*default: no
*default: no
operator – this keyword defines the availability of the “Operator” functionality while the voice mail message is being recorded. Additionally this keyword defines the availability of the same functionality after the end of the recording process.
*data: set /yes|no/
*default: no
*remark: note that if you change the subject by using emailsubject keyword, the using of this setting is pointless.
*remark: the user will be able to contact the operator after the end of the recording if preview setting is been set to yes.
*remark: the operator extension is been specified with 'o' in extensions.conf
*default: no
*remark: note that if you change the subject by using emailsubject keyword, the using of this setting is pointless.
*remark: the user will be able to contact the operator after the end of the recording if preview setting is been set to yes.
*remark: the operator extension is been specified with 'o' in extensions.conf
pagerbody – this keyword contains the notification message that is sent to the pager address. This keyword supports variable substitution.
*data: string /message/
*default: the default message that is hard coded into Asterisk
*remark: see appendix for available variables and examples.
*remark: The pagerbody keyword's value can only be up to 512 characters due to a limitation in the Asterisk configuration subsystem.
*default: the default message that is hard coded into Asterisk
*remark: see appendix for available variables and examples.
*remark: The pagerbody keyword's value can only be up to 512 characters due to a limitation in the Asterisk configuration subsystem.
pagerfromstring – this keyword contains the from field of the notification message that is sent to the pager address. This keyword supports variable substitution.
*data: string /from/
*default: From: Asterisk PBX <who>
*default: From: Asterisk PBX <who>
pagersubject – this keyword contains the subject of the notification message that is sent to the pager address. This keyword supports variable substitution.
*data: string /subject/
*default: the default subject that is been hard coded into Asterisk
*remark: see appendix for available variables and examples.
*default: the default subject that is been hard coded into Asterisk
*remark: see appendix for available variables and examples.
pbxskip – this setting defines if the PBX string should be skipped in the subject of the e-mail notification message that is sent to the user.
*data: set /yes|no/
*default: no
*remark: note that if you set pbxskip=no (as is the default setting) the subject of the e-mail will be “Subject: [PBX]: New messages M in mailbox N”
*remark: note that if you change the subject by using emailsubject keyword, the using of this setting is pointless.
*default: no
*remark: note that if you set pbxskip=no (as is the default setting) the subject of the e-mail will be “Subject: [PBX]: New messages M in mailbox N”
*remark: note that if you change the subject by using emailsubject keyword, the using of this setting is pointless.
review – this keyword defines if the caller will be able to hear his recorded message before it is been processed. The caller have options to commit the message (by pressing '#') or hang up the call (this will result in no message delivered).
*data: set /yes|no/
*default: no
*remark: note that if you change the subject by using emailsubject keyword, the using of this setting is pointless.
*default: no
*remark: note that if you change the subject by using emailsubject keyword, the using of this setting is pointless.
saycid – this keyword defines the priority of playing between the caller's phone number and the voice mail message itself. If the value of saycid is set to yes Asterisk will first play the caller's phone number and then the message itself.
*data: set /yes|no/
*default: no
*remark: this keyword (setting) is available only in the extended versions of Asterisk with advanced voice mail feature support.
*default: no
*remark: this keyword (setting) is available only in the extended versions of Asterisk with advanced voice mail feature support.
sendvoicemail – this keyword defines if the “Leave a message” menu option is available in the Advanced Options menu. If this functionality is enabled, a voice mail user will be able to directly send a voice mail message to another user via his voice mail menu.
*data: set /yes|no/
*default: no
*default: no
severemail – this keyword’s value is been used for the source (return e-mail address) of the voicemail notification message. If the data string is a valid e-mail address (account@somemail.com), Asterisk will send the notification message with this return address. If you set the string without ‘@’, Asterisk will append @somehost.com, where somehost.com will be the server’s hostname.
*data: string /e-mail address/
*default: asterisk@localhost.localdomain
*default: asterisk@localhost.localdomain
silencethreshold – this keyword configures the silence detection threshold, which is used for maxsilence keyword. If you set a lower value to the silencethreshhold keyword, the sensitivity of the silence detector will fall down (the system will recognize silence in more noisy calls). The value of silencethreshold should be greater or equal to 0 and lower than 256.
*data: integer (limit)
*default: 128
*default: 128
tempgreetwarn - this keyword toggles the working state of the functionality to remind the user if their temporary greeting is set.
*data: set /yes|no/
*default: no
*default: no
3. Zonemessages configuration - except [general], there is one more special area in voicemail.conf , this is the [zonemessages]. In this section of this tutorial we will describe the use of [zonemessages] area. In this section of voicemail.conf you can specify custom timezones for your voicemail users. Timezones configuration begins with the [zonemessages] tag and finishes at the beginning of the next context. The declaration of a timezone has the following syntax:
zonename=Country/City|Options
Country - the Country that the user is located in
City - the name of the City that the user is located in.
Asterisk searches your timezones files for the Country and City that you have specified. By default the timezones files are located in /usr/share/zoneinfo (basically they are the valid timezones that you can set in as timezone of your computer). In Options you can specify the rest of the configuration of the current timezone. Most of the options are concerning the way that the date and time are pronounced for the current timezone. Here are the possible configurations (note that everything that is within the quotes in the upper description is been pronounced by Asterisk server) :
Option Description
'filename' filename of an audio file (do not remove the quotes)
${VAR} variable substitution
A Day of week ("Monday", "Sunday")
a Day of week ("Monday", "Sunday")
B Month name ("January", "February", ...)
b Month name ("January", "February", ...)
h Month name ("January", "February", ...)
d numeric day of month ("first", "second", ..., "thirty-first")
e numeric day of month ("first", "second", ..., "thirty-first")
Y Year
I Hour, 12 hour clock
i Hour, 12 hour clock
H Hour, 24 hour clock (single digit hours preceded by "oh")
k Hour, 24 hour clock (single digit hours NOT preceded by "oh")
M Minute
P AM or PM
p AM or PM
Q "today","yesterday" or ABdY
q "" (won't pronounce anything for today), "yesterday", weekday, or ABdY
R 24 hour time, including minuteHere is sample of a [timemessages] configuration:
Basically sofia12 is an abstract name of the timezone. Asterisk will detect the timezone of Sofia (which is +2 GMT) and will coordinate the time. The options indicate that Asterisk will first play the file named "received-bg", then it will play the date (following the format of q, which is "", "yesterday", weekday, or ABdY), then Asterisk will play file named "time-was-bg", then it will play the current hour (in 12 hour clock format), then it will "announce", how much minutes have passed after the beginning of the current hour, and finally it will pronounce if it is AM or PM. This abstract name is used only for applying the timezone on the target user and the name of the zone have no relations with the timezone settings. In order to apply a timezone to a target voice mail user you should use the 'tz' keyword (and set the wanted timezone name as value to the 'tz' keyword) as an option.
4. Mailbox accounts - mailboxes are stored into one or more contexts. By default there is a [default] context but you can remove it if you like so. Even if you remove the [default] context from voicemail.conf Asterisk will create a virtual [default] context when parsing your configuration file. The server won't add it (the virtual [default] context) to your voicemail.conf but if you list your mailboxes by using the 'voicemail list users' you will see that there is such context. The reason for this behavior is that based on usercontext keyword, if you set the data of usercontext (the default data of usercontext is default, see usercontext keyword for more details) to other context, Asterisk won't create [default]. However if you set usercontext to non-existing context, Asterisk will create it in the same manner as [default].
Defining mailboxes is similar to extensions and zonemessages syntax. There are three obligatory components of the definition: mailbox number, mailbox secret and mailbox's user's name. The mailbox number should be a unique string for each context (this means that you can't have duplicated mailboxes in one context). However you can have two mailboxes with identical mailbox number, but only if they are in different contexts. The mailbox's secret and the user's name are not unique fields and they can be duplicated even in one context. The mailbox's number may contain only numbers and letters in it. Any different symbols included into this filed will result in unexpected behavior of the server, such as parsing errors, unaccessible mailbox or even server crashes. The mailbox's secret may contain only numbers and 'A','B','C','D' (as letters), but the use of those letters is not recommended, any different symbols included into the secret will result in unexpected behavior of the server, such as parsing errors, unaccessible mailbox or even server crashes. The user's name may contain numbers, letters and ' '(spaces), but special symbols are forbidden. The syntax of declaring mailbox is the following:
mailbox_number => mailbox_secret,User NameHere are some examples:
There are some optional fields in the definition of a voicemail account. You can define user's e-mail address for notification messages, secondary e-mail address (SMS, pager) and almost all options available in the [general] area. Here is the syntax for those optional fields:
mailbox_number => mailbox_secret,User Name,somebody@mail.com,somebody@pager.com, keyword1=data1|keyword2=data2|keyword3=data3|keyword4...If you don't specify options you don't have to put the ',' symbol. Here are some examples:
Mailboxes 1111, 2222 and 3333 are defined correctly. The rest of the mailboxes (4444, 5555 and 6666) have the following mistakes:
4444 - options are directly after the user's name. Asterisk expects a valid e-mail address at that location
5555 - secondary e-mail is at the place of the primary. This misht cause unexpected behavior of the server. The additional options fields are at the place of the secondary e-mail. Asterisk expects a valid e-mail address at this location.
6666 - options are directly after the user's primary e-mail. Asterisk expects a valid e-mail address (or empty string) at this location.
5555 - secondary e-mail is at the place of the primary. This misht cause unexpected behavior of the server. The additional options fields are at the place of the secondary e-mail. Asterisk expects a valid e-mail address at this location.
6666 - options are directly after the user's primary e-mail. Asterisk expects a valid e-mail address (or empty string) at this location.
Here are the correct versions of the mistaken mailboxes:
4444 => 5555,No Name,,,maxmsg=5|externpass=/bin/application 5555 => 6666,No Name,,pager@pager.com,attach=no|delete=yes|maxmsg=9999 6666 => 7777,No Name,okmail@company.com,,attach=no
5. Links related to voicemail
Asteriskguru Voicemail tutorial
HasNewVoicemail - application that allows you to check your mailbox if you have a new message there.
HasVoicemail - application that is an improved version of the HasNewVoicemail application.
MailboxExists - application that allows you to check whether certain mailbox exists or not.
VoiceMail - application that allows you to leave a voicemail message.
VoiceMailMain - application that allows you to enter the Asterisk’s voicemail system.
HasNewVoicemail - application that allows you to check your mailbox if you have a new message there.
HasVoicemail - application that is an improved version of the HasNewVoicemail application.
MailboxExists - application that allows you to check whether certain mailbox exists or not.
VoiceMail - application that allows you to leave a voicemail message.
VoiceMailMain - application that allows you to enter the Asterisk’s voicemail system.
6. Examples - some real examles that will show you how to use all this in order to make it work.
Example 1 - in this tutorial you will find:
Example 4 - [in progress]
* how to check for current voicemail accounts
* how to create a new voicemail.conf from a scratch
* how to add a new timezone
* how to add global keywords and options
* how to add new contexts
* how to add new users
* how to add options per-user
* how to edit your dialplan in order to activate voicemail functionality
* how to check your voicemail
Example 2 - in this tutorial you will find:* how to create a new voicemail.conf from a scratch
* how to add a new timezone
* how to add global keywords and options
* how to add new contexts
* how to add new users
* how to add options per-user
* how to edit your dialplan in order to activate voicemail functionality
* how to check your voicemail
* how to send e-mail notification messages
* how to attach audio files to notification messages
* how to customize the notification messages
* how to use voicemail.conf keywords in order to reduce the amount of HDD usage
* how to use macros in order to simplify extensions.conf
Example 3 - [in progress]* how to attach audio files to notification messages
* how to customize the notification messages
* how to use voicemail.conf keywords in order to reduce the amount of HDD usage
* how to use macros in order to simplify extensions.conf
Example 4 - [in progress]
| Add Comment |
Latest Headlines:
-
T.38 faxing with Zoiper 2.15 is now easier than ever
section: voip software
-
Asterisk 1.4.21 Released
section: Asterisk
-
Asterisk 1.4.20 Released
section: Asterisk
-
Asterisk 1.4.20-rc2 Released
section: Asterisk
-
Asterisk 1.4.20-rc1 Now Available
section: Asterisk
- News Archives (older news)
Latest Tutorials:
-
Sending Fax from Zoiper to Zoiper using T.38
added 08/Dec/2008 18:16
-
VMAuthenticate (dialplan application)
added 01/Mar/2008 15:57
-
Siptronic ST-530
added 06/Nov/2007 17:57
-
Siemens C455 IP hardphone
added 05/Nov/2007 10:24
-
Zoiper
added 22/Oct/2007 17:53
Latest Comments:
-
https://eurocarers.org/wp-content/upload...
tutorial: Asterisk 1.4.0 CLI commands
-
https://eurocarers.org/wp-content/upload...
tutorial: Asterisk 1.4.0 CLI commands
-
https://eurocarers.org/wp-content/upload...
tutorial: Asterisk 1.4.0 CLI commands
-
https://eurocarers.org/wp-content/upload...
tutorial: Asterisk 1.4.0 CLI commands
-
https://eurocarers.org/wp-content/upload...
tutorial: Asterisk 1.4.0 CLI commands