Messages

1561

Outbound and QueueMetrics / Re: Exclude an external number from reporting

« on: February 23, 2010, 09:47:03 »

There is no simple way to do that..... but you can avoid that behavior by using an unattended transfer, so that the talk time stops when the agent transfers the call.
 

1562

Running QueueMetrics / Re: autoopenurl

« on: February 23, 2010, 09:44:36 »

Why do you need it before the custom button gets the URL?

1563

Running QueueMetrics / Re: Error occurred in the Transaction handler [solved]

« on: February 23, 2010, 09:43:04 »

The error message:

**** DTSC - Please contact Loway Research for a renewal

Means that the current key has expired.

1564

Running QueueMetrics / Re: AgentCallBackLogin-replacement

« on: February 19, 2010, 09:38:20 »

The thing is far from being trivial, unfortunately.

1565

Running QueueMetrics / Re: autoopenurl

« on: February 19, 2010, 09:37:47 »

Do you think you could give me an example of how to "define the URL by queue"?

It's a part of the queue configuration....

1566

Lost licences / Re: Temp license never received

« on: February 18, 2010, 15:08:13 »

We'll contact you by email ASAP.

1567

Outbound and QueueMetrics / Re: Outbound Calls & Incoming call status

« on: February 18, 2010, 15:06:23 »

Pause them for inbound, or have them log off and then on again.

1568

Running QueueMetrics / Re: AgentCallBackLogin-replacement

« on: February 18, 2010, 15:05:35 »

We have been working on a solution for hotdesking, but it is really tied to 1.6's because older Asterisks are too buggy to use chan Local extensively under load.
A few of uor clients use "blank" softphones, so that the agent has to log in every time with their credentials; this is a sad form of hotdesking.

1569

QueueMetrics installation / Re: BAD packet signature 18245

« on: February 18, 2010, 15:02:28 »

I have never seen that error.
Still, that error seems to be related to jk (the connector from Apache to Tomcat) - try and use the native Tomcat web server.

1570

QueueMetrics news / [OT] Asterisk security alert

« on: February 17, 2010, 10:18:47 »

Hello everyone,
this is not exactly related to QueueMetrics, but being an important Asterisk issue, we are posting it here.

Many VoIP protocols support a large character set, that may cause harm in your dialplan

You need to change entries that look like:

Code: [Select]

[incoming-from-voip]
exten => _X., 1, dial(SIP/${EXTEN})

See http://lists.digium.com/pipermail/asterisk-users/2010-February/244721.html
See also: http://www.asterisk.org

1571

Outbound and QueueMetrics / Re: Outbound with Asterisk 1.6

« on: February 17, 2010, 09:10:04 »

If you need to support xagents, that piece of dialplan stores everything in a ready-to-read format in AstDB so it should be trivial to detect.

1572

Running QueueMetrics / Re: autoopenurl

« on: February 17, 2010, 09:08:11 »

This is it:

realtime.agent_autoopenurl=true

You also need to define the URL by queue, so that it has a URL to open; it will open the URL when you refresh the page.

We are planning to do a rework of the whole agent page, but the problem is that we want to keep the load on the server to a minimum.

1573

Outbound and QueueMetrics / Re: Outbound with Asterisk 1.6

« on: February 16, 2010, 19:20:40 »

You should check that in the dialplan - IIRC there is a function to tell wjhether an agent is logged on or not.

1574

Running QueueMetrics / Re: autoopenurl

« on: February 16, 2010, 19:19:49 »

No if you set the autoOpenURL it will try and open the latest new URL as soon as you refreshed the page.

1575

Running QueueMetrics / Re: [solved] "Il verbo '' non e stato trovato tra quelli caricati."

« on: February 16, 2010, 19:19:09 »

What it basically means is that the main controller servlet was called but from the calling parameters it could not understand what it was supposed to do. As you always POST to that page, this is what you get if you send it a GET request.