#
# Login, Password, Permission file
# Store usernames, passwords, and permission/login types in this file

# The server will parse this file *every* time a login request is made, there is no need to reload the server
#  if a change is made to this file

# Permissions are as follows in order of highest permissions to lowest
# admin, monitor, agent

#####
# Permissions Explanation:
#####
# admin:    has the ability to see everything on a server, and has no limit on commands it can send
# monitor:  mainly only has the ability to see everything on the server, but has limited or no commands they can send
# agent:    has nearly no commands they can send, and only sees information relevent to themselves

# Permissions are not cumulative; you wouldn't put two permissions on one person. They inherit the permissions of the
# permission level under them. Admin already has all the permissions a monitor or agent has, etc.

# The trust parameter can be one of the folling values; 1, true, or yes
# Any other value for the trust parameter, including the absence of a setting, results in a false value

######
# AGENT / DEVICE CHANNELS
######
# New with asterisk deprecating agentcallbacklogin in lou of Dynamic Agents, we must now supply an agent channel.
#
# The agent channel is the actual channel that is added to the queue. This could be technology/exten such as
# SIP/300, AIX2/tommy, Zap/1, Local/15@agents, Agent/301, etc. Make sure to put the FULL channel, even if it's an
# old-school agent (i.e. Agent/300).
# 
# The device channel is used in one specific instance: If you add a Local/ channel to a queue, you must supply the
# actual device that channel will eventually ring. For example, you might have a Local/200@agents channel in the sales queue
# which would do some setup dial plan stuff, and then ring SIP/200. You must supply SIP/200 as the device channel.
# 
# If the agent channel IS the actual device channel, the device channel is not needed.
# Do NOT supply a device channel if your agent channel is of type AGENT (i.e. Agent/300), as it is not needed.
#
# Agent / Device channels are NOT needed for admin / monitor logins UNLESS those logins are taking calls from queues or
# are making outbound calls and you want to track them.

# One username per line
# The syntax is as follows:
# <username>,<password>,<permission type>,[<agent channel>],[<device channel>],[<communication format>],[<trust>]

#######
# Examples
#######

# A username with a password given monitor permissions using the default communication format:
# user1,secret,monitor,SIP/maryh

# A username with no password, given trust to admin permissions using xml format (not security minded eh?)
# user2,,admin,,,xml,yes

# A username with a password given *trust* to agent permissions using asterisk native format
#   (trust overrides the existance of a password!!)
# user3,secret,agent,Local/150@call-agent,SIP/450,asterisk,yes

# A trusted agent using the default format
# user4,,agent,IAX2/joebob,,,yes
