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 ... 28 29 [30] 31 32 ... 202
436
Outbound and QueueMetrics / Re: Call attempts via Quemetrics
« on: June 26, 2012, 12:29:19 »
You can edit that value in the DIAL string that QM performs.

437
It's weird, it seems to be there. Do you still get the very same error?

438
Running WombatDialer / Re: Trunk setup
« on: June 26, 2012, 12:26:48 »
Likely it is through I have no experience with PIAF.

We suggest NOT using a Local trunk for anything but testing - for testing you could create a dummy trunk that points to a SIP extension like in the [dialout] context explained here: http://blog.wombatdialer.com/post/23597570852/tut-idle


439
Running WombatDialer / Re: end point setup
« on: June 26, 2012, 12:23:50 »
Likely it will be SIP/701 in order to have calls routed to you.

440
Running WombatDialer / Re: Localhost for asterisk server
« on: June 26, 2012, 12:23:12 »
Thanks for opening up the WombatDialer forum! :)

The username and password are the ones you use to connect to Asterisk over AMI - see /etc/asterisk/manager.conf - give WD the full privileges.

441
It should already be present. Do you see it in core dialplan show qm-queuedial in the Asterisk CLI?

442
Thanks - this looks like there is an issue with your Java compiler, as Java 5 should have inferred the change. Just to be on the safe side we are applying this change to the main QM app, but it's really weird.

443
It looks like it's not finding the [qm-queuedial] context.

See:

Code: [Select]
-- Executing [4610013479445555@queuedial:7] Goto("Local/4610013479445555@queuedial-223e;2", "qm-queuedial,s,1") in new stack
  == Begin MixMonitor Recording Local/4610013479445555@queuedial-223e;2
    -- Goto (qm-queuedial,s,1)
  == Spawn extension (qm-queuedial, s, 1) exited non-zero on 'Local/4610013479445555@queuedial-223e;2'

I would expect to have a NoOp record at (qm-queuedial, s, 1) ....

444
Most likely it may be caused by having distinct channel names from the ones you are using for the agent logons. E.g having friendly names set, as in http://queuemetrics.com/faq.jsp#faq-085-friendly_names - could this be possible?

445
cached pages are cached at the browser level so you should clean the cache of the browser. You could also stop QM and look for a directory called tomcat/work and remove all its contents (that's where compiled pages are kept).

446
Looks like some of the pages are cached - either QM lets you in or it does not.

447

Try one thing at a time sending the call through through SIP or DAHDI in a way that you are sure works. This way we have less variables on our plate to understand what is going on.
l


Neither of those too worked for me. I actually had set as Local/EXTEN:5@from-internal/n, so this could pick up any of my 2 trunks.


448
Sorry I'm the world's worst typist  ;D

449

This is the cause - you should use CALOUTBOUND verbs, not ENTERQUEUEs :-)


Sure thing!

We are using the prefix 8300 before calls to have QM track them.

We have q-300 set as the queue in QM to track outbound calls.

Here is the output from queue_log in relation to my test calls.

Code: [Select]
1339532160|1339532160.76079|q-300|SIP/2178|ENTERQUEUE|-|901161405942016|
1339532166|NONE|NONE|SIP/2320|UNPAUSEALL|
1339532166|NONE|3011|SIP/2320|UNPAUSE|
1339532166|NONE|3010|SIP/2320|UNPAUSE|
1339532166|NONE|3008|SIP/2320|UNPAUSE|
1339532166|NONE|3009|SIP/2320|UNPAUSE|
1339532171|1339531912.76053|3008|SIP/2320|CONNECT|186|1339532167.76081|3
1339532172|1339532160.76079|q-300|SIP/2178|ABANDON|1|1|12
1339532183|1339532183.76084|q-300|SIP/2178|ENTERQUEUE|-|901161405942016|


450
Most likely this

Code: [Select]
QDIALER_CHANNEL=SIP/13479445555
should be

Code: [Select]
QDIALER_CHANNEL=SIP/provider/13479445555

Pages: 1 ... 28 29 [30] 31 32 ... 202