Section D.4. agents.conf

D.4. agents .conf

This file allows you to create and manage agents for your call center. If you are using the Queue( ) application, you may want to configure agents for the queue. The agents.conf file is used to configure the AGENT channel driver.

The [general] section in agents.conf currently contains only one parameter. The persistentagents=yes parameter tells Asterisk to save the status of agents who use the callback feature of queues in the local Asterisk database. A logged-in remote agent will then remain logged in across a reboot (unless removed from the database through some other means).

The following parameters, which are specified in the [agents] section, are used to define agents and the way the system interacts with them. The settings apply to all agents, unless otherwise specified in the individual agent definitions:


Accepts the arguments yes and no . If set to yes , requires a callback agent to acknowledge login by pressing the # key after logging in. This works in conjunction with the AgentCallbackLogin( ) application.


Accepts an argument (in seconds) defining how long an agent channel should ring for before the agent is deemed unavailable and logged off.


Defines the groups to which an agent belongs, specified with integers. Specify that an agent belongs to multiple groups by separating the integers with commas.

musiconhold => class

Accepts a Music on Hold class as its argument. This setting applies to all agents.


Accepts the arguments yes and no . Used to define whether the source channel in the CDRs should be set to agent/agent_id to determine which agent generated the calls.


Accepts an argument (in milliseconds ) specifying the amount of time to wait after an agent has finished a call before that agent can be considered available to answer another call.

The remaining parameters are also specified in the [agents] section, but they are global to the chan_agent channel driver and thus cannot be defined on a per-agent basis:


Accepts the arguments yes and no . Inserts the name of the created recording in the CDR user field.


Accepts a filename as its argument. Can be used to define a custom notification tone to signal to an always-connected agent that there is an incoming call.


Accepts the arguments yes and no . Defines whether or not agent calls should be recorded.


Defines the format to record files in. The argument specified should be wav , gsm , or wav49 . The default recording format is wav .


Accepts a filesystem path as its argument. Allows you to override the default path of /var/spool/asterisk/monitor/ with one of your choosing.

Since the storage of calls will require a large amount of hard drive space, you will want to define a strategy to handle storing and managing these recordings.

This location should probably reside on a separate volume; one with very high performance characteristics.


Accepts a string as its argument. The string can be formed as a URL and is appended to the start of the text to be added to the name of the recording.

The final parameter is used to define agents. As in the zapata.conf file, configuration parameters are inherited from above the agent => definition. Agents are defined with the following format:

 agent =>   agent_id   ,   agent_password   ,   name   

For example, we can define agent Happy Tempura with the agent ID 1000 and password 1234, as follows .

 agent => 1000,1234,Happy Tempura 

Be aware that an agents.conf file is a complement to the queue configuration process. The most critical configuration file for your queues is queues.conf . You can configure a very basic queue without agents.conf .

Asterisk. The Future of Telephony
Asterisk: The Future of Telephony: The Future of Telephony
Year: 2001
Pages: 380

Similar book on Amazon © 2008-2017.
If you may any questions please contact us: