Datasets:
Squidnutz
/
extractedtest

Dataset card Data Studio Files
xet
 Community
1
text
stringlengths
0
152
follows:
• UNIX 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
typical queue_log file will look something like the following:
1530389309|NONE|NONE|NONE|QUEUESTART|
1530409313|CLI|support|PJSIP/SOFTPHONE_B|ADDMEMBER|
1530409467|CLI|support|PJSIP/SOFTPHONE_B|REMOVEMEMBER|
1530409666|NONE|support|PJSIP/SOFTPHONE_B|PAUSE|Callbacks
1530411108|NONE|support|PJSIP/SOFTPHONE_B|UNPAUSE|FinishedCallbacks
Queue Statistics: The queue_log File
|
235
1530440239|1530440239.10|support|PJSIP/SOFTPHONE_A|ADDMEMBER|
1530440303|1530440303.16|support|PJSIP/SOFTPHONE_A|REMOVEMEMBER|
1530497165|1530497165.54|support|Local/PJSIP-SOFTPHONE_A@MemberConnector|ADDMEMBER|
1530497388|CLI|support|Local/PJSIP-SOFTPHONE_A@MemberConnector|REMOVEMEMBER|
1530497408|1530497408.60|support|Local/PJSIP-SOFTPHONE_A@localMemberConnector|ADDMEMBER|
1530497506|1530497506.71|support|NONE|ENTERQUEUE||SOFTPHONE_B|1
1530497511|1530497506.71|support|PJSIP/SOFTPHONE_A|CONNECT|5|1530497506.72|4
1530497517|1530497506.71|support|PJSIP/SOFTPHONE_A|COMPLETEAGENT|5|6|1
1530509861|1530509861.134|support|NONE|ENTERQUEUE||SOFTPHONE_B|1
1530509864|1530509861.134|support|PJSIP/SOFTPHONE_A|RINGCANCELED|2224
1530509864|1530509861.134|support|NONE|ABANDON|1|1|3
1530510503|1530510503.156|support|NONE|ENTERQUEUE||103|1
1530510503|1530510503.156|support|PJSIP/SOFTPHONE_A|RINGNOANSWER|0
1530510511|1530510503.156|support|NONE|ABANDON|1|1|8
1530510738|1530510738.163|support|NONE|ENTERQUEUE||123|1
1530510742|1530510738.163|support|PJSIP/SOFTPHONE_A|CONNECT|4|1530510738.164|4
1530510752|1530510738.163|support|PJSIP/SOFTPHONE_A|COMPLETECALLER|4|10|1
As you can see from this example, there may not always be a unique ID for the event.
External services, such as the Asterisk CLI, can perform actions on the queue, and in
these cases you’ll see something like CLI in the Unique ID field.
The available events and the information they provide are described in Table 12-7.
Table 12-7. Events in the Asterisk queue log
Event
ABANDON
ADDMEMBER
AGENTDUMP
AGENTLOGIN
AGENTLOGOFF
COMPLETE
AGENT
COMPLETECAL
LER
CONFIGURE
LOAD
CONNECT
Information provided
Written when a caller in a queue hangs up before his call is answered by an agent. Three parameters are
provided for ABANDON: the position of the caller at hangup, the original position of the caller when
entering the queue, and the amount of time the caller waited prior to hanging up.
Written when a member is added to the queue. The bridged channel name will be populated with the
name of the channel added to the queue.
Indicates that the agent hung up on the caller while the queue announcement was being played, prior to
them being bridged together.
Recorded when an agent logs in. The bridged channel field will contain something like Agent/9994 if
logging in with chan_agent, and the first parameter field will contain the channel logging in (e.g.,
SIP/0000FFFF0001).
Logged when an agent logs off, along with a parameter indicating how long the agent was logged in for.
Note that since you will often use RemoveQueueMember() for agent log off, this parameter may not
be written. See the REMOVEMEMBER event instead.
Recorded when a call is bridged to an agent and the agent hangs up, along with parameters indicating
the amount of time the caller was held in the queue, the length of the call with the agent, and the
original position at which the caller entered the queue.
Same as COMPLETEAGENT, except the caller hung up and not the agent.
Indicates that the queue configuration was reloaded (e.g., via module reload app_queue.so).
Written when the caller and the agent are bridged together. Three parameters are also written: the
amount of time the caller waited in the queue, the unique ID of the queue member’s channel to which