Messages

901

Outbound and QueueMetrics / Re: Outbound dialing using queue dial to multiple/fail over trunks

« on: February 08, 2011, 10:17:52 »

You can create a route that uses multiple custom trunks, one after the other.
You could create multiple trunks (copy and paste the queuedial context to queuedial1, queuedial2.... so you can edit each separately)

902

QueueMetrics installation / Re: Upgraded to QM 1.6.3.0

« on: February 08, 2011, 10:15:22 »

No do not disinstall anything - QM has its own dependencies only.

You'll find everything here: http://yum.loway.ch/RPMS/noarch/

I am not sure how, but you can surely add the complete repository instead of package by package.....

903

Outbound and QueueMetrics / Re: Outbound dialing using queue dial to multiple/fail over trunks

« on: February 04, 2011, 11:19:26 »

You should set it up at a higher level - when you define the trunk, the trunk will fail if the call does not go through, so you should try another one. It is correct that the single call on the single trunk just fails.
 

904

Running QueueMetrics / Re: All pause codes displaying "-"

« on: February 04, 2011, 11:17:51 »

 

905

General Asterisk configuration / Re: Something weired with Queue call distribution - Why is there unfair call distri?

« on: February 04, 2011, 11:17:28 »

The answer to your questions would be quite lengthy, but you can find about app_queue in Asterisk on Voip INFO wiki.


I would go look for the /var/log/asterisk/full that's where all stuff actually is.

906

Outbound and QueueMetrics / Re: Outbound dialing using queue dial to multiple/fail over trunks

« on: February 03, 2011, 09:28:48 »

It is seen as a normal trunk in TrixBox, so you should use it the way you would with any other trunk.

907

Running QueueMetrics / Re: All pause codes displaying "-"

« on: February 03, 2011, 09:21:28 »

Ah yes - how came you had it twice?

908

General Asterisk configuration / Re: Something weired with Queue call distribution - Why is there unfair call distri?

« on: February 03, 2011, 09:20:55 »

If I am to put through an hypothesis, I think that something went wrong with the first call - it sys it tried calling both phones every 5 seconds, but they would not actually ring - it looks like they were busy or something, because the call is retried immediately after trial. I'd go for a bug of some sort - the second call went through at the first attempt.
 

909

Running QueueMetrics / Re: All pause codes displaying "-"

« on: February 02, 2011, 17:06:10 »

Ok so this looks correct.

Can you post a piece of the queue_log, where you see an agent taking a call and then you make them go on pause?

910

Running QueueMetrics / Re: Listening to live calls: Unattended Call Moni- toring

« on: February 01, 2011, 16:57:40 »

If you use our script, the supplied entry will likely work.

911

Running QueueMetrics / Re: it takes a long time to open the /qm/popup_call.jsp

« on: February 01, 2011, 16:57:05 »

Just point the search to an empty directory.

912

Running QueueMetrics / Re: Communication error on wallboard

« on: February 01, 2011, 16:56:36 »

I did check and there is nothing like an error on the log.
I suspect that for some reason (maybe a cron job) the server is very loaded at that moment so the client times out.....

913

Running QueueMetrics / Re: All pause codes displaying "-"

« on: February 01, 2011, 16:49:31 »

If you run a report, do you see the pause codes being correct or not?
And what gets written to the queue_log file when an agent goes on pause?

914

General Asterisk configuration / Re: Something weired with Queue call distribution - Why is there unfair call distri?

« on: February 01, 2011, 16:48:11 »

Looks like an anomaly to me, but I'm not an expert on Trixbox.

If you have the callid for the second call (the one that was queued early but ended up being answered late) I would like you to run a text search on your queue_log file so we ca see the exact records that were written.

915

QueueMetrics installation / Re: queue_log rotation question

« on: February 01, 2011, 16:43:26 »

yes this is exactly what we meant.