Author Topic: Agent login logoff from QM agent page not working  (Read 6337 times)

tank30

  • Newbie
  • *
  • Posts: 46
  • Karma: 0
    • View Profile
Agent login logoff from QM agent page not working
« on: August 27, 2007, 14:40:41 »
Agents show up ok on reports, loging in and out when using the dial extension i have setup on Asterisk.
If an agent tries to login using the "LogOn" button from the agent's QM web interface it fails with error
"You do not have the rights to perform the requested action. "   

What rights exactly are we talking about here?   ???
Any ideas on how to resolve this?


thanks
KM

tank30

  • Newbie
  • *
  • Posts: 46
  • Karma: 0
    • View Profile
Re: Agent login logoff from QM agent page not working
« Reply #1 on: August 28, 2007, 13:41:03 »
This is what i have:

callfile.agentlogin.enabled=true
callfile.agentlogin.channel=Local/698@feature-extensions/n
callfile.agentlogin.extension=698
callfile.agentlogin.context=feature-extensions

and in context feature-extensions  i have the extension 698:

exten => 698,1,Answer
exten => 698,1,NoOp( "QM: Logging on Agent/${AGENTCODE} to extension ${AGENT_EXT}@sip" )
exten => 698,2,AgentCallBackLogin(${AGENTCODE}||${AGENT_EXT}@sip)
exten => 698,4,Hangup

Help, anyone?

 :'(





QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: Agent login logoff from QM agent page not working
« Reply #2 on: August 28, 2007, 15:02:31 »
To debug this case, open up the Asterisk CLI when you run the command from QM.
If you see activity on the Asterisk CLI, it's a dialplan problem; if you don't, it's QM that is not able to talk to the Asterisk server (likely the user/password for the tcp:user:password@server line are not correct).

One thing I'm noticing about your case is that when a message is sent to Asterisk, two call legs are opened and bridged by default; in your calse one will dial Local/698@feature-extension/n, and the other one will connect it to exten => 698,1 in context feature-extension. This is not correct; send the second leg to some dummy extension where a Wait() will be run and hangup.


tank30

  • Newbie
  • *
  • Posts: 46
  • Karma: 0
    • View Profile
Re: Agent login logoff from QM agent page not working
« Reply #3 on: August 31, 2007, 10:15:12 »
Hi,
  its probably a QM problem since nothing happens in asterisk console nor in Asterisk logs.
Also i tried to tail the logfiles of QM to see if i can find any errors but with no success.
Where exactly is the tcp password for the asterisk in QM configuration?

Below is my configuration properties for QM:
# This is the internal id (ex. 7, 49....) of the preselected default queue, leave blank for no default queue.
default.queue=1

# This is the default queue log file.
default.queue_log_file=/var/log/asterisk/queue_log

#This key is used only as a placeholder for CVS versioning information
00_version=$Id: configuration.properties,v 1.18 2007/06/18 21:03:05 lenz Exp $

#When the realtime page for an agent is computed, the queue_log is NOT read in its entirety but only the last 'n' bytes.
realtime.max_bytes_agent=65000

#The top level directory where monitored calls are held.
#Do NOT forget to add the ending slash.
default.monitored_calls=/var/spool/asterisk/

#How many digits to consider as a default area code
default.areacode_digits=2

default.start_hour=8

default.end_hour=17:30

default.days=7

#if liveclock is enabled, the system clock is synchronized with asterisk server system clock.
liveclock.enable=true

#The max delay that will be shown in the TOS graph
sla.max_monitored_delay=120

#How big are time intervals for the TOS graph
sla.interval=10

#Your company logo (full or relative path) - shall be resized to be an image 200 x 72
layout.logo=$WEBAPP/img/sm_your_logo.gif

#HTML string displayed on the login page.
layout.splash=Please ask your system administrator for the correct credentials to access this instance of QueueMetrics.

# Preset 1: standard DB access. Edit to suit your DB needs.
sqlPreset.1.table=queue_log
sqlPreset.1.f_time_id=time_id
sqlPreset.1.f_call_id=call_id
sqlPreset.1.f_queue=queue
sqlPreset.1.f_agent=agent
sqlPreset.1.f_verb=verb
sqlPreset.1.f_partition=partition
sqlPreset.1.f_data1=data1
sqlPreset.1.f_data2=data2
sqlPreset.1.f_data3=data3
sqlPreset.1.f_data4=data4
sqlPreset.1.f_incr=unique_row_count

sqlPreset.2.table=queue_log
sqlPreset.2.f_time_id=time_id
sqlPreset.2.f_call_id=call_id
sqlPreset.2.f_queue=queue
sqlPreset.2.f_agent=agent
sqlPreset.2.f_verb=verb
sqlPreset.2.f_partition=
sqlPreset.2.f_data1=data1
sqlPreset.2.f_data2=data2
sqlPreset.2.f_data3=data3
sqlPreset.2.f_data4=data4
sqlPreset.2.f_incr=unique_row_count

#Is the calls panel in the realtime page invisible by default? 0 false, 1 true
realtime.calls_invisible=0

#Is the agents panel in the realtime page invisible by default? 0 false, 1 true  
realtime.agents_invisible=0

#Are not  the only agents to be shown on the realtime page those who are "known" for the queue? 0 false, 1 true
realtime.members_only=1

#In how many seconds is the realtime page to refresh?
realtime.refresh_time=18


# Do we consider callback agents permanent until logoff (default as Asterisk 1.2), or do they get disconnected at restart?
default.permanentCallBackAgents=true

# Do we take into consideration sessions and calls that are not complet eyet for the main analysis?
default.considerIncompletetEntities=true

#callFile spool dir, set to blank for no call files at all.
callfile.dir=/var/spool/asterisk/outgoing

callfile.monitoring.enabled=true
callfile.monitoring.channel=Local/$EM@sip/n
callfile.monitoring.extension=11
callfile.monitoring.context=queuemetrics

callfile.agentdial.enabled=true
callfile.agentdial.channel=Local/13@queuemetrics/n
callfile.agentdial.extension=10
callfile.agentdial.context=queuemetrics

callfile.calloutcome.enabled=true
callfile.calloutcome.channel=Local/12@queuemetrics/n
callfile.calloutcome.extension=10
callfile.calloutcome.context=queuemetrics

#callfile.agentlogin.enabled=true
#callfile.agentlogin.channel=Local/20@queuemetrics/n
#callfile.agentlogin.extension=
#callfile.agentlogin.context=queuemetrics

callfile.agentlogin.enabled=true
callfile.agentlogin.channel=Local/698@feature-extensions/n
callfile.agentlogin.extension=698
callfile.agentlogin.context=feature-extensions

callfile.agentlogoff.enabled=true
callfile.agentlogoff.channel=Local/21@queuemetrics/n
callfile.agentlogoff.extension=10
callfile.agentlogoff.context=queuemetrics

callfile.agentpause.enabled=true
callfile.agentpause.channel=Local/22@queuemetrics/n
callfile.agentpause.extension=10
callfile.agentpause.context=queuemetrics

callfile.agentunpause.enabled=true
callfile.agentunpause.channel=Local/23@queuemetrics/n
callfile.agentunpause.extension=10
callfile.agentunpause.context=queuemetrics


# Rewrites Local/XXX@ext channels in the format Agent/XXX
default.rewriteLocalChannels=false

# DO NOT CHANGE
realtime.use_sql_now=false

#The default time zone offset. Valid values -24...24 hours
default.timeZoneOffset=0

#If an ongoing call has a wait time that exceeds this value, drop it. 0: ignore
default.maxOngoingWaitTime=0

#If an ongoing call has a talk time that exceeds this value, drop it. 0: ignore
default.maxOngoingTalkTime=0

#Ignore QUEUESTART statements.
default.ignoreQueueStarts=false


#The hour of the day to start realtime monitoring or sXX: sliding window of XX hours
realtime.startHour=0


# The default locale for QueueMetrics. DO NOT CHANGE unless you know what you're doing.
default.language=en
default.country=US

# Which channel name to show for a call: True: last one seen - False: first one found
default.useEndingChannelName=true

# How to create Excel files: True: Excel 2003 XML - False: CSV
default.useXmlExcel=false

# Show the queue composition or just the main queue name
default.showQueueComposition=true


# how long is an hour for hourly breakdown; default 60 minutes
default.hourly_slot=15

#Add the following key to enable default showing of all subqueues (default: no):
realtime.all_subqueues=1

# Join multi-stint calls as a default
default.joinMultiStintCalls=false

# Uses the starting or ending channel name in case they're different.
default.useEndingChannelName=false


# Decide whether to check for alarms on the wait time of ongoing conversations.
realtime.waitAlarmOnLiveCalls=true
sound.yellowAlarm=../img/sounds/dingdong.wav
sound.redAlarm=../img/sounds/ringer.wav



# Cluster to poll for RT data
# list of pipe-separated members of the cluster
# if callfilesdir = "", the commands will be sent through the manager API
cluster.servers=aleph|trix

cluster.aleph.manager=tcp:dial:12345@10.10.3.5
cluster.aleph.queuelog=sql:P001
cluster.aleph.monitored_calls=z:/qm_streamcall/server_aleph
cluster.aleph.callfilesdir=
cluster.aleph.audioRpcServer=
cluster.aleph.agentSecurityKey=

cluster.trix.manager=tcp:admin:amp111@10.10.3.100
cluster.trix.queuelog=sql:P002
cluster.trix.monitored_calls=z:/qm_streamcall/server_trix
cluster.trix.callfilesdir=
cluster.trix.audioRpcServer=
cluster.trix.agentSecurityKey=
« Last Edit: August 31, 2007, 10:17:40 by tank30 »

QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: Agent login logoff from QM agent page not working
« Reply #4 on: September 01, 2007, 18:28:39 »
Change this:

Code: [Select]
#callFile spool dir, set to blank for no call files at all.
callfile.dir=/var/spool/asterisk/outgoing

to

Code: [Select]
#callFile spool dir, set to blank for no call files at all.
callfile.dir=tcp:user:password@10.10.3.5

Where:
- user is your username
- password is your password
- 10.10.3.5 is your Asterisk server IP

With this it should attempt a call and you should see it in the Asterisk CLI.

QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: Agent login logoff from QM agent page not working
« Reply #5 on: March 26, 2008, 16:57:18 »
FYI: this problem made it to the FAQ:

http://queuemetrics.com/faq.jsp#faq-041-no_rights

 ::)