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 - QueueMetrics

Pages: 1 2 [3] 4 5 ... 202
If you use google TTS it may be that the TTS script is very slow to download audio files.
One thing you can do is to break a longer message up into several parts, so that TTS only downloads the relevant small part.

For example, if you have to sythesize "You have 36 apples in your basket" you could sythesize "You have", "36 apples" and " in your basket" as separate TTS calls. As content is cached, only the number will be downloaded.

Running WombatDialer / Re: Alternate numbers in list
« on: June 17, 2015, 09:37:15 »
Wombat supports multiple numbers in a round-robin fashion - depends on the attempts. So on the first attempt it dials the main number, and then tries all other numbers in sequence; when all of them are done, it tries again the main number and so on.

See chapter 4.3.4 "Multinumbers"

Open QueueMetrics Add-Ons / Re: Added Flantel wallboard
« on: June 17, 2015, 09:16:08 »
The wallboard was updated to reflect the latest version of QM - se

Scripting QueueMetrics / Updated working FlanTel wallboard
« on: June 17, 2015, 09:13:14 »
Hello all,
we updated the FlanTel wallboard to work out of the box with the latest version of QueueMetrics, plus we wrote a little doc about how to get started with it.
It is a good starting point to crete your own customized wallboard!
You can find it at

Running WombatDialer / Re: Problems running wombat dialer 0.8.0
« on: January 18, 2015, 12:28:05 »
It seems the startup order ow Wombat is incorrect. As a tweak, I suggest restarting WombatDialer in rc.local, so that we are sure that whatever happens before, Wombat is started last.

Running WombatDialer / Re: Appt confirmation - solved
« on: January 18, 2015, 12:26:53 »

QueueMetrics news / Tracking MOH in Asterisk - alpha testers wanted
« on: January 18, 2015, 12:22:13 »
Hello all,
we are developing a tool to make it easy to track music-on-hold events on queue calls. At the moment QueueMetrics tracks and reports those events, but producing them used to be very complex and required patching and recompiling Asterisk.

The module is currently in private alpha stage, so it may not work at all and might require a bit of tweaking to get it up and running.

We are looking for alpha testers who would like to run it on their own system and get this important functionality added.

If you'd like to be in, please contact our support services and we'll send you a link.

The QueueMetrics dev team.

Running WombatDialer / Re: Problems running wombat dialer 0.8.0
« on: January 08, 2015, 14:50:23 »
1. This error happens if MySQL is down when Wombat starts. Try restarting MySQL first and then manually restarting Wombat.

2. What we usually suggest is to create a context - say we call  it your-context - that will do the dialing, so that you address channels as Local/${num}@your-context/n

Running WombatDialer / Re: Appt confirmation
« on: September 25, 2014, 16:16:58 »
I would add a wait time after sending the event (if you do this before you hang up) to make sure Wombat received the events in order.

Running WombatDialer / Re: Appt confirmation
« on: September 25, 2014, 08:26:53 »
Can you explain what is not working? make sure your Asterisk systems does emit events before the call is hung up.
As a part of our quality process for releasing WD, we do a test of direct dialing with generated response events and we get 100% of events on about one million calls at 100 parallel calls per servers on two parallel servers, so we are pretty much sure it works.

Running WombatDialer / Re: Error after upgrade to 0.7.7
« on: September 18, 2014, 10:00:59 »
Did you delete the license key?
Just to be on the safe side, you can get your license key (say it's 'mykey' )

Code: [Select]
INSERT INTO arch_lic ( id ) VALUES ( 'mykey' )
Restart Wombat

What I would do is to store the unique-id of the main leg into a call variable, and use that to set up the name for the recording in the second leg (that will have a different unique-id).

- the main leg of the call has uniqueid of 1234.123
- we store it in a variable
- when we reach the second queue, we set the recording name to "olduniqueid-step2"

So you would have recordings like:

1234.123.wav  (fro the main leg)
1234.123-step2.wav (for the second leg)

It's not pretty but it should work.

Running WombatDialer / Re: Queue Config
« on: August 30, 2014, 07:22:29 »
Most likely the name of the queue is incorrect in the configuration or the queue is not set up to send events.


Running WombatDialer / Re: Wombat Queue configuration
« on: July 21, 2014, 13:45:06 »

Improving QueueMetrics / Re: Pause Time Alerts based on Code
« on: July 21, 2014, 13:44:46 »
Nice idea: we track this as Bug 2413 - RT: max pause duration alarm

Pages: 1 2 [3] 4 5 ... 202