PBXware 4.1.2 Agents

From Bicom Systems Wiki

Queue agents are virtual system extensions. Agents log in to the queue member list and answer queue calls. The advantage of this system is that any system extension can login to the queue as an agent. This screen lists all system agents with the following details



  • Agent
Agent's full name
(ex. Sergej)
  • Number
Agent's number which is provided when the agent logs into the queue
(ex. 1000)
  • Login Type
Type of login the agent is using
(ex. Callback or Dynamic)
  • Wrap Up Time [ms]
Pause in miliseconds given to the queue agent before a new call is transferred to his extension
(ex. 4000 = 4 sec)
  • edit.png Edits Queue Agent configuration
(ex. Click to edit Agent configuration)
  • delete.png Deletes Queue Agent from the system
(ex. Click to delete Queue Agent from the system)


  • Search
Enter the agent number or name for which you want to search.
  • Agent
Select whether to search by agent name
  • Number
Select whether to search by agent number

Add/Edit Agent

Add/Edit Agent
  • Name:
Queue agent name, used only for easier navigation
(ex. John)
  • Surname:
Queue agent surname, used only for easier navigation
(ex. Smith)
  • Number:
The queue agent network number is provided by the agent when logging into a queue
(ex. 4010)
  • Login Type:
Type of login the agent will use
  • Callback or Dynamic
  • Only Callback
  • Only Dynamic
(Select box)

Types of Queue Members

Any queue can have 3 types of queue members with two additional variations of agent types. They can be: extensions, dynamic agents, or callback agents. Additionally, agents can be configured to choose whether they will be Dynamic or Callback and if they will auto login to the queue.

1.Extension - Member

If the queue for which the extension is added has the Static Member Login option turned on, the extension will have to login using the *200 access code before it will receive any calls from the queue. To log out of the queue extension, the agent will have to use the *201 access code.

If the Static Member Login option is not turned on, this member will always receive queue calls after it is added to the queues members list.

2.Dynamic Agents

This type of queue member can log in to a designated queue from any UAD on the network with access code *202. After the agent is logged on, the queue will start sending calls to the agent.

NOTE: The dynamic agent is "on call" all the time, meaning the agent's line is always open and receiving calls. Every time a caller hangs up, the agent hears the MoH and then receives the next call when it arrives. The dynamic agent logs out of the queue by hanging up the line. The agent MUST be created in the 'Agents' menu and assigned to the queue in question.

3.Callback Agents

This type of agent can login to a designated queue by dialing into one of the system extensions with access code *203. By default, the system will prompt for: AGENT NUMBER, AGENT PIN, and THE NUMBER where the agent is currently at. This number could be a local extension or some other remote destination

NOTE: The agent MUST be created in the 'Agents' menu and assigned to the queue in question. The callback agent must logout with *203 to stop receiving calls

Agents have two more type options to choose from:

1. Callback or Dynamic Agents

This type of agent is left with the choice of whether it will use the *202 access code and be a dynamic agent or the *203 access code and be callback agent.

2. Auto Login (Callback)

An agent of this type is actually a callback agent which the system will automatically log in to the queue as soon as it is added to the queue. For this to work, this agent needs to bind to an extension to which the system will send the calls.

  • PIN Required:
Whether the PIN is required when logging this agent in
(ex. Select Yes if you want the system to ask you to provide a PIN number to be able to log in using this agent)
(Option button)
  • PIN:
Queue agent PIN number provided by the agent when logging into the queue
(ex. 6583)
  • Bind to Extension:
Whether the system will bind the current agent to the extension specified in the Extension field.
(ex. Set this to Yes if you want the system to allow logins to this agent only from the extension supplied in the Extension field)
(Option button)
  • Extension:
Supply the extension from which the system will only allow logins to the current agent
(ex. Set 1543, for example, to limit logins to current agent only from extension 1543)
  • Wrap Up Time [ms]
Pause in milliseconds given to the queue agent before a new call is transferred to his extension.
NOTE: This optional number is set for the current Agent and overrides the value in Settings: General
(ex. 4000 = 4 sec)
  • URL list:
A new line-separated list of URLs that will open every time an agent opens the Bicom Systems AgentCOM application. NOTE: AgentCOM desktop app is deprecated and it is not supported anymore. Customers that are still using it will not be able to get any support on it.
(ex. www.google.com)
  • Member of:
Groups that the queue agent belongs to
(ex. By assigning an agent to multiple groups, the agent can log in to multiple queues with a single agent login. Use CTRL + mouse click to select/unselect groups)
(Select box)
  • Admin Agent
Whether this agent will have Administrator credentials.
If agent is set as Admin Agent, he will have an option to add or remove himself from a queue, he was granted administration credentials. This option is only available if agents are using AgentCOM.
(Yes, No)
  • Administrator for Queues
Select queues from the list for which you would like to assign administration credentials to this agent. For multiple selection, hold down Ctrl on your keyboard while clicking on multiple queues.


If you are updating from an earlier version of PBXware, agents in the system might not work. In that case, you need to re-save every agent in the system. This is needed because there are significant configuration changes in latest versions of PBXware.


To enable easier login into multiple queues, agents can be organized into groups.

This way, many agents can be added to a queue member list with a single click (by adding agent group instead of agents one by one). Also, when any system extension logs in as a queue member, it logs in automatically to all queues that the agent is a member of.

Agent Groups
  • Group:
Queue group number
(ex. 2000)
  • edit.png Edits the queue group configuration
(ex. Click to edit the queue group configuration)
  • delete.png Deletes a queue group from the system
(ex. Click to delete a queue group from the system)

Add/Edit Group

Add Edit Group
  • Group Name:
Unique network group identifier
(ex. Adding 'Sales' here will create a 'Sales' group. Select this group under 'Agents: Member of' to assign the user to this group).
([a-z] [0-9])

Pause Reasons

Pause Reasons

In PBXware version 4.0 we introduce the Pause Reason feature. When an Agent needs to stop receiving calls from a queue(s), but does not want to log out of the queue(s), they can pause. They will stop receiving queue calls until they un-pause, but will still be reported as logged in to the queue(s). In addition, the agent can provide a pause reason code to indicate the reason they are currently paused. This reason code is logged with their pause event.

Add Pause Reason

Add/Edit Pause Reason

gloCOM Pause Reason
gloCOM Pause Reason
  • Name:
Name of pause reason.
(ex. Lunch break)
  • Code:
Short code for pause reason.
(ex. 123)
  • Description
Short description of pause reason.
(ex. Went out for lunch break)
  • Billable
Whether a pause will be billed to an agent.
  • Payable
Whether a pause is payed to an agent.

In order to enable/disable this feature, the agent should dial the *204 access code and type the code for their pause reason. In Monitor->Queues you can see that if an agent is on pause and their pause reason. In gloCOM Agent Edition, the agent can use this feature by clicking the pause button next to the agent number. By choosing the appropriate pause reason, the agent will be paused.



Agents Settings
  • Wrap-up time [ms]:
Pause in milliseconds given to the queue agent before a new call is transferred to his extension
(ex. Agent Smith ends a queue call. A pause in ms (default 5000 = 5sec) is enforced so the agent can prepare himself for a new call)
  • Music On Hold:
Set the Music On Hold class played to queue agents
(ex. Select 'Default' to play all of the sound files located in that class to the queue agent while waiting for new calls)
(Select box)
  • Custom Beep:
Set the sound file name that is to be played to the queue agent before a call is transferred to him from the queue
(ex. Type 'arlington' to play the arlington.gsm sound file to the queue agent)
([a-z] [0-9])

Login/Logoff Options

  • Auto Logoff:
Auto Logoff will automatically log off agent after he fail to answer incoming call.
(ex. On/Off)
(Option button)
  • Dynamic Auto Logoff [sec]
Dynamic Logoff will work with dynamic agents only and would automatically log them out of queues after 60 seconds (default) of not taking calls.
(ex. 60)
  • Auto Pause
Whether you want to turn Auto Pause on/off for an agent in a queue.
  • Acknowledge CL:
Require agents that are logged in through agent callback to dial # to confirm their input.
(ex. With this option set to 'Yes', once an agent dials *203, he is asked to provide an extension number and acknowledge it by dialing #. After the correct extension, the agent is asked for the account password and to acknowledge it by dialing #)
(Option button)
  • Max. Login Retries:
Define the number of times that the agent can try to login before he receives a failed notification.
(ex. 3)
  • End Call with *:
Enable/Disable an agent to end a call with '*'.
(ex. Off)
(Option button)

Recording Options

  • Record Calls:
Record all calls made to callback queue agents
(ex. With this option set to 'Yes', all calls that an agent receives through the queue will be recorded)
(Option button)
  • Record Format:
Select the desired sound format for call recording
(ex. Select from the available sound formats: wav, gsm, wav49)
(Select box)

CDR Options

  • Update CDR:
Whether the CDR records should be changed so it is known which agent generates the call
(Option button)

Next -> 11.Voicemail