Page 503 - Asterisk™: The Future of Telephony
P. 503
verbose
When you connect to the Asterisk console and set a verbosity of 3 or higher, you’ll
see output on the console showing what Asterisk is doing. You can save this output
to a logfile by adding a line such as verbose_log => verbose to your logger.conf file.
Note that a high amount of verbosity can quickly eat up hard drive space.
notice
A notice is used to inform you of minor changes to the system, such as when a peer
changes state. It is normal to see these types of messages, and the events they
indicate generally have no adverse effects on the server.
warning
A warning happens when Asterisk attempts to do something and is unsuccessful.
These types of errors are usually not fatal, but they should be investigated, espe-
cially if a lot of them are seen.
error
Errors are often related to Out of Memory errors. They generally indicate serious
problems that may lead to Asterisk to crash or freeze.
manager.conf
The Asterisk Manager Interface is an API that external programs can use to commu-
nicate with and control Asterisk, much as you would do from the Asterisk console.
The Manager gives programs the ability to run commands and request
information from the Asterisk server. However, it is not very secure; its
authentication mechanism defaults to using plain-text passwords, and
all connected terminals default to receiving all events. The Asterisk
Manager should be used only on a trusted local area network, or locally
on the box. The permit and deny constructs allow you to restrict access
to certain extensions or subnets.
Many of the available graphical interfaces to Asterisk—such as the Flash Operator
Panel—use the Manager to pull data and determine the status of applications. The
manager.conf file defines the way programs authenticate with the Manager.
The Manager commands (which you can list by typing show manager commands at the
Asterisk console) have varying degrees of privilege. You can control the read and write
permissions for these commands with the use of the read and write options in the
manager.conf file.
Here’s a sample manager.conf file:
[general]
enabled = no
port = 5038
bindaddr = 0.0.0.0
manager.conf | 475