Messages

2416

General Asterisk configuration / Re: Custom queue_log Entries

« on: July 03, 2008, 08:56:09 »

 

2417

General Asterisk configuration / Re: Custom queue_log Entries

« on: July 02, 2008, 15:16:45 »

QueueMetrics is able to handle this case by using a special option of QLoaderd called subqueues.
See http://queuemetrics.com/faq.jsp#faq-037-subqueues-bug239

2418

General Asterisk configuration / Re: Enabling Agent's page action

« on: July 01, 2008, 10:17:39 »

There is no callfile.actionname.enabled=true or false in the configuration.properties. I only find this:

callfile.outmonitoring.enabled=true

callfile.agentdial.enabled=true

callfile.calloutcome.enabled=true

callfile.agentlogin.enabled=true

callfile.agentlogoff.enabled=true

callfile.agentpause.enabled=true

callfile.agentunpause.enabled=true

That's them - actionname is a placeholder for the actual action you want to enable or disable.

2419

General Asterisk configuration / Re: Enabling Agent's page action

« on: June 28, 2008, 09:52:48 »

In the configuration.properties file that is under the system directory (you can find that in QM 1.4.4. by going to the Licence page).

On most unix systems you can find it by:

Code: [Select]

updatedb
locate configuration.properties


2420

MySQL storage and Qloaderd/Uniloader / Re: asterisk/mysql and queuemetrics in different servers

« on: June 27, 2008, 16:47:29 »

That's fine. 

2421

QueueMetrics installation / Re: AsteriskNow

« on: June 26, 2008, 09:04:31 »

I wonder why Digium did not choose one of the "big", proven distros as a basis for AsteriskNow - using a Debian or RedHat derived system like everybody else seems to be doing.

2422

QueueMetrics installation / Re: QM 1.4 and Trixbox 2.6.1

« on: June 25, 2008, 11:34:54 »

I see you already have the new technology dial-out. It was not previously there.

here is queuedial
-- Called 1230800@queuedial/n
    -- Executing [1230800@queuedial:1] Set("Local/1230800@queuedial-f7bd,2", "QDIALER_QUEUE=q-1 23") in new stack
    -- Executing [1230800@queuedial:2] Set("Local/1230800@queuedial-f7bd,2", "QDIALER_NUMBER=0800") in new stack
    -- Executing [1230800@queuedial:3] Set("Local/1230800@queuedial-f7bd,2", "QDIALER_AGENT=Agent/27") in new stack
    -- Executing [1230800@queuedial:4] Set("Local/1230800@queuedial-f7bd,2", "QDIALER_CHANNEL=SIP/0800") in new stack
    -- Executing [1230800@queuedial:5] Set("Local/1230800@queuedial-f7bd,2", "QueueName=q-123")              in new stack
    -- Executing [1230800@queuedial:6] MixMonitor ("Local/1230800@queuedial-f7bd,2", "Q-q-123-12             14338925.15.WAV|b|") in new stack
    -- Executing [1230800@queuedial:7] Goto("Local/1230800@queuedial-f7bd,2", "qm-queuedial|s|1             ") in new stack
    -- Goto (qm-queuedial,s,1)

This is correct, save for the SIP/0800 that should likely be SIP/myprovider/0800 or whatever. Find the line where QDIALER_CHANNEL is set and edit that.

Please note that you DO NOT have the dialplan below

[queuedial]
exten => _XXX.,1,Set(MY_QUE=${EXTEN:0:3})
exten => _XXX.,2,Set(MY_NUM=${EXTEN:3})
exten => _XXX.,3,Set(MY_AGENT=${CALLERIDNUM})
exten => _XXX.,4,NoOp,Ag: ${MY_AGENT} N: ${MY_NUM} Q: ${MY_QUE}
exten => _XXX.,5,MixMonitor(Q-${MY_QUE}-${UNIQUEID}.wav|b|)
exten => _XXX.,6,DeadAGI(queueDial.agi|${MY_NUM}|SIP/user.provider.ent/${MY_NUM}|q-
${MY_QUE}|Agent/${MY_AGENT})
exten => _XXX.,7,Congestion

So make sure what files are you importing.  You do not need it as you have the new one, but beware because the log you posted does not match the dialplan you reported here.

2423

QueueMetrics installation / Re: Adding new QA Items

« on: June 25, 2008, 11:26:20 »

You should enter something as the engagement code, otherwise it will not work.

2424

QueueMetrics installation / Re: QM 1.4 and Trixbox 2.6.1

« on: June 24, 2008, 12:46:30 »

I do not even see the MY_QUE=.... entries that were in te previous log. Did you use Set() as specified above?

2425

MySQL storage and Qloaderd/Uniloader / Re: asterisk/mysql and queuemetrics in different servers

« on: June 23, 2008, 16:57:11 »

Connection refused makes me think that MySQL is not answering on port 3306 and/or there is some firewall or binding rule taht prevents it to do so. Otherwise it would print something to state that your user was incotrrect.

2426

QueueMetrics installation / Re: TOMCAT5_SECURITY=yes, one issue left

« on: June 23, 2008, 16:54:54 »

Pls let us know if you encounter any problems.

2427

QueueMetrics installation / Re: agent URL Screenpops not working when using SQL backend

« on: June 23, 2008, 16:53:19 »

Cool. This is correct. 
We'll fix that for 1.4.5 (bug #416).

2428

QueueMetrics news / Summer break 2008

« on: June 21, 2008, 16:14:53 »

Loway offices will be closed during the Summer Break, that will be from July 5th to July 20th, 2008. We will do no custom developement during this period and all calls will go to voicemail. 

We will be only running a support line by email for getting temporary licences, general commercial questions and technical support for installation and running systems. See Contact us page for email details.

2429

QueueMetrics installation / Re: jdm - SQL connection problems

« on: June 20, 2008, 09:13:07 »

"Could not create..." makes me think of a connection error. Are you sure MySQL is doing a bind on the correct address/port?

2430

QueueMetrics installation / Re: Listening to live calls: Unattended Call Monitoring

« on: June 20, 2008, 09:11:23 »

Follow the TrixBox guide, it works on any FreePBX based system.