System information

queue_log_to_file

Controls whether the queue log should be written to a file even when a real time

backend is present. Valid values are yes or no (defaults to no).

queue_log_name

Controls the name of the queue log. The default is queue_log.

The queue log is a pipe-separated list of events. The fields in the queue_log file are as

follows:

• Epoch timestamp of the event

• Unique ID of the call

• Name of the queue

• Name of bridged channel

• Type of event

• Zero or more event parameters

The information contained in the event parameters depends on the type of event. A

sample queue_log file might look something like the following:

1292281046|psy1-1292281041.87|7100|NONE|ENTERQUEUE||4165551212|1

1292281046|psy1-1292281041.87|7100|Local/9996@MemberConnector|RINGNOANSWER|0

1292281048|psy1-1292281041.87|7100|Local/9990@MemberConnector|CONNECT|2

|psy1-1292281046.90|0

1292284121|psy1-1292281041.87|7100|Local/9990@MemberConnector|COMPLETECALLER|2|3073|1

1292284519|psy1-1292284515.93|7100|NONE|ENTERQUEUE||4165551212|1

1292284519|psy1-1292284515.93|7100|Local/9996@MemberConnector|RINGNOANSWER|0

1292284521|psy1-1292284515.93|7100|Local/9990@MemberConnector|CONNECT|2

|psy1-1292284519.96|0

1292284562|psy1-1292284515.93|7100|Local/9990@MemberConnector|COMPLETECALLER|2|41|1

As you can see from this example, there might not always be a unique ID for the event.

In some cases external services, such as the Asterisk Manager Interface (AMI), perform

actions on the queue; in this case you’ll see something like MANAGER in the Unique ID

field.

The available events and the information they provide are described in Table 13-9.

Queue Statistics: The queue_log File | 297