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 ... 202
I would try:
- stop the dialer
- make a backup of the DB
- delete all rows from hopper, hop_calls and hop_lists
- restart

If you can send us the database dump to our email support, we can see if there is a workaround to avoid such situations in the future.

You can add them to a black list automatically.
First you crete a campaign, and add to it a blacklist (maybe empty).
You have them press a key or something that ends the call in a specific extended status, eg "NOCALL"
You then add a Disposition Rules so that numbers ending in ext status "NOCALL" are added to your blacklist.

See specifically 3.6.4

WombatDialer Soporte en Español / Re: wombat dialer agent page
« on: September 28, 2015, 13:05:16 »
How was WombatDialer installed? because it works fine in our RPMs. Maybe you are using Tomcat 8?

AGAW / Re: AGAW not working - update
« on: September 28, 2015, 13:03:55 »
As you can see from the date it is VEEERY old.

The tavern / Re: Welcome everyone
« on: September 28, 2015, 13:02:10 »

I think that you need a newer version of MySQL, like 5.5, and possibly set:


Introduced   5.5.14
Command-Line Format   --innodb_large_prefix
System Variable   Name   innodb_large_prefix
Variable Scope   Global
Dynamic Variable   Yes
Permitted Values   Type   boolean
Default   OFF
Enable this option to allow index key prefixes longer than 767 bytes (up to 3072 bytes), for InnoDB tables that use the DYNAMIC and COMPRESSED row formats. (Creating such tables also requires the option values innodb_file_format=barracuda and innodb_file_per_table=true.) See Section 14.8.7, “Limits on InnoDB Tables” for the relevant maximums associated with index key prefixes under various settings.

For tables using the REDUNDANT and COMPACT row formats, this option does not affect the allowed key prefix length. It does introduce a new error possibility. When this setting is enabled, attempting to create an index prefix with a key length greater than 3072 for a REDUNDANT or COMPACT table causes an ER_INDEX_COLUMN_TOO_LONG error.

WombatDialer Soporte en Español / Re: wombat dialer agent page
« on: August 21, 2015, 09:38:40 »
Hello there,
try doing this cahnge to the page:

Before you see
Code: [Select]
String[] resLines = AgentsPopupHelper.httpPostToLines(apiReserve, parms);
Change it to:
Code: [Select]
System.out.println( "API RESERVE:" + apiReserve);
String[] resLines = AgentsPopupHelper.httpPostToLines(apiReserve, parms);

This will write a line to stdout (catalina.out) with the URL it is trying to access.
Can you post it here?

Running WombatDialer / Re: restart wombat after some changes
« on: June 17, 2015, 09:46:12 »
No - if you change Asterisk servers, trunk or endpoints you should stop and start it from the "dialer" controls on the home page.

Running WombatDialer / Re: Dailer Status Flapping
« on: June 17, 2015, 09:45:37 »
No errors on the log?

Running WombatDialer / Re: Lists AUTO
« on: June 17, 2015, 09:44:31 »
Yes these are lists that are created when you add numbers to a run.

Running WombatDialer / Re: uppercase
« on: June 17, 2015, 09:43:54 »
Pls make an example.

Running WombatDialer / Re: Install/configuration trouble
« on: June 17, 2015, 09:43:11 »
Try using a Local/n channel just to make sure everything works in the simpelst case.

Running WombatDialer / Re: Probleb with Dialstatus
« on: June 17, 2015, 09:42:35 »
The format for "Unable to request channel DAHDI/g0/09177367031@dialout/n" is incorrect. Should be something like "Unable to request channel DAHDI/g0/09177367031" instead!

Running WombatDialer / Re: Updating Wombat dialer
« on: June 17, 2015, 09:41:29 »
Please try again with the latest 0.9.1 should have fixed that.

The campaign should be running but appearing as WRONG_TIME.

Pages: 1 [2] 3 4 ... 202
# 2019-02-11