Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - sylwat

Pages: [1]
1
Any resolution to the aforementioned issue? come to find out the agent is able to log in however its the splash screen behind the new agent page that is creating this issue.

2
Running QueueMetrics / Agent login gets http status 404-not found
« on: April 14, 2018, 03:49:44 »
the following message gets displayed as soon as an agent logs on, please help to resolve. thank you.
HTTP Status 404 Not Found
Type Status Report

Message /qm/agent_page_gwt_background.jsp

Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.

Apache Tomcat/8.5.12

3
QueueMetrics installation / Re: Agents can not enter pause
« on: June 17, 2015, 17:44:10 »
The same issue describe above was just reported to me too, using the following; Software release: Loway QueueMetrics - 15.02.2
 B: 5353 2015-03-13 09:24

Note: using the new agent page, when select pause code the wheel just keep spinning and after a while it stops however the agent is not paused. the only way it works is to totally log out of the queue then log in again then use the pause function and then it works.

4
QueueMetrics installation / Re: Call details
« on: June 16, 2015, 14:10:47 »
Anyone has a similar issue or input of how to fix? still getting the same errors.

5
QueueMetrics installation / Re: Call details
« on: June 15, 2015, 13:42:22 »
Software release: Loway QueueMetrics - 15.02.2
 B: 5353 2015-03-13 09:24 
 

6
QueueMetrics installation / Call details
« on: June 14, 2015, 06:35:58 »
After clicking on the details link icon on the reports page for an Answered details call I get the following error for every call link;

HTTP Status 404 - /queuemetrics/qm/qm_start


type Status report

message /queuemetrics/qm/qm_start

description The requested resource (/queuemetrics/qm/qm_start) is not available.


Apache Tomcat/6.0.33


Any help in resolving this will be appreciated.

Pages: [1]