Recent Posts

Pages: 1 [2] 3 4 ... 10
11
I think your idea is very good.
12
Running WombatDialer / Re: Can't set values with UserEvent for the call
« Last post by Jonathan on February 08, 2018, 10:51:55 »
I agree with your opinion very much. 
13
Whether itís a regular election or the Prime Minister of Japan calls for a snap election. To capitalize on an electoral opportunity or decide on some pressing social issue. Polling gives political candidates a picture of where they stand with the electorate.

Discover how you can develop an effective Asterisk based telephone survey system using WombatDialer predictive dialer.

Read the "Asterisk IVR dialer" case history at

https://www.wombatdialer.com/blog/blog/2018/01/30/asterisk-ivr-dialer?lid=U064
14
Hi Gustavo,

that's weird actually, could you send the queue_log of one test call?

Mirko
15
Hello,

i'm using asterisk 1.6 with queuemetrics xxx, and the field Caller is empty for outbound calls. Does anyone knows how to fix this?
When i used old versions the field contains the number dialed. The outbound dialler are working very well, but this issue are dificulting the monitoring job.

extensions_queuemetrics:
Code: [Select]
> 0x7f6b3c019640 -- Probation passed - setting RTP source address to 10.10.10.122:58126
[2018-01-28 14:12:26] NOTICE[27503][C-00002e9f]: res_rtp_asterisk.c:4569 ast_rtp_read: Unknown RTP codec 126 received from '(null)'
       > Channel SIP/9054-000061d0 was answered
    -- Executing [28@queuemetrics:1] Answer("SIP/9054-000061d0", "") in new stack
  == Manager 'admin' logged off from 127.0.0.1
    -- Executing [28@queuemetrics:2] NoOp("SIP/9054-000061d0", " "QM: Agent Custom Dial. Dialing 004121694154 on queue 9001  made by 'Agent/9054'" ") in new stack
    -- Executing [28@queuemetrics:3] Set("SIP/9054-000061d0", "QDIALER_QUEUE=9001") in new stack
    -- Executing [28@queuemetrics:4] Set("SIP/9054-000061d0", "QDIALER_NUMBER=004121694154") in new stack
    -- Executing [28@queuemetrics:5] Set("SIP/9054-000061d0", "QDIALER_AGENT=Agent/9054") in new stack
    -- Executing [28@queuemetrics:6] Set("SIP/9054-000061d0", "QDIALER_CHANNEL=SIP/6400/004121694154") in new stack
    -- Executing [28@queuemetrics:7] Set("SIP/9054-000061d0", "QueueName=9001") in new stack
    -- Executing [28@queuemetrics:8] MixMonitor("SIP/9054-000061d0", "Q-9001-1517159541.28376.WAV,b,") in new stack
    -- Executing [28@queuemetrics:9] Goto("SIP/9054-000061d0", "qm-queuedial,s,1") in new stack
  == Begin MixMonitor Recording SIP/9054-000061d0
    -- Goto (qm-queuedial,s,1)
    -- Executing [s@qm-queuedial:1] NoOp("SIP/9054-000061d0", " "Outbound call - A:Agent/9054 N:004121694154 Q:9001 Ch:SIP/6400/004121694154" ") in new stack
    -- Executing [s@qm-queuedial:2] Set("SIP/9054-000061d0", "CDR(accountcode)=QDIALAGI") in new stack
    -- Executing [s@qm-queuedial:3] Set("SIP/9054-000061d0", "ST=1517159546") in new stack
    -- Executing [s@qm-queuedial:4] Set("SIP/9054-000061d0", "GM=QDV-Agent/9054") in new stack
    -- Executing [s@qm-queuedial:5] Set("SIP/9054-000061d0", "GLOBAL(QDV-Agent/9054)=U") in new stack
  == Setting global variable 'QDV-Agent/9054' to 'U'
    -- Executing [s@qm-queuedial:6] Set("SIP/9054-000061d0", "GLOBAL(QDV-Agent/9054ans)=0") in new stack
  == Setting global variable 'QDV-Agent/9054ans' to '0'
    -- Executing [s@qm-queuedial:7] Macro("SIP/9054-000061d0", "queuelog,1517159546,1517159541.28376,9001,Agent/9054,CALLOUTBOUND,,004121694154") in new stack
    -- Executing [s@macro-queuelog:1] Set("SIP/9054-000061d0", "ADDINFO=,004121694154,") in new stack
    -- Executing [s@macro-queuelog:2] QueueLog("SIP/9054-000061d0", "9001,1517159541.28376,Agent/9054,CALLOUTBOUND,,004121694154,") in new stack
    -- Executing [s@qm-queuedial:8] Dial("SIP/9054-000061d0", "SIP/6400/004121694154,300,gM(queuedial-answer^1517159541.28376^QDV-Agent/9054^9001^Agent/9054^1517159546)") in new stack
  == Using SIP RTP TOS bits 184
  == Using SIP RTP CoS mark 5
    -- Called SIP/6400/004121694154
       > 0x7f6b3c019640 -- Probation passed - setting RTP source address to 10.10.10.122:58126
       > 0x7f6b38003e20 -- Probation passed - setting RTP source address to 10.10.60.3:32128
    -- SIP/6400-000061d1 is making progress passing it to SIP/9054-000061d0
       > 0x7f6b38003e20 -- Probation passed - setting RTP source address to 10.10.60.3:32128
    -- SIP/6400-000061d1 answered SIP/9054-000061d0
    -- Executing [s@macro-queuedial-answer:1] NoOp("SIP/6400-000061d1", ""Macro: queuedial-answer UID:1517159541.28376 GR:QDV-Agent/9054 Q:9001 A:Agent/9054 E:1517159546"") in new stack
    -- Executing [s@macro-queuedial-answer:2] Set("SIP/6400-000061d1", "NOW=1517159550") in new stack
    -- Executing [s@macro-queuedial-answer:3] Set("SIP/6400-000061d1", "WD=4") in new stack
    -- Executing [s@macro-queuedial-answer:4] Macro("SIP/6400-000061d1", "queuelog,1517159550,1517159541.28376,9001,Agent/9054,CONNECT,4") in new stack
    -- Executing [s@macro-queuelog:1] Set("SIP/6400-000061d1", "ADDINFO=4,,") in new stack
    -- Executing [s@macro-queuelog:2] QueueLog("SIP/6400-000061d1", "9001,1517159541.28376,Agent/9054,CONNECT,4,,") in new stack
    -- Executing [s@macro-queuedial-answer:5] Set("SIP/6400-000061d1", "GLOBAL(QDV-Agent/9054)=A") in new stack
  == Setting global variable 'QDV-Agent/9054' to 'A'
    -- Executing [s@macro-queuedial-answer:6] Set("SIP/6400-000061d1", "GLOBAL(QDV-Agent/9054ans)=1517159550") in new stack
  == Setting global variable 'QDV-Agent/9054ans' to '1517159550'
    -- Executing [s@macro-queuedial-answer:7] NoOp("SIP/6400-000061d1", ""Macro queuedial-answer terminating" ") in new stack
    -- Executing [s@qm-queuedial:9] Set("SIP/9054-000061d0", "CAUSECOMPLETE=C") in new stack
    -- Auto fallthrough, channel 'SIP/9054-000061d0' status is 'ANSWER'
    -- Executing [h@qm-queuedial:1] NoOp("SIP/9054-000061d0", " "Call exiting: status A answered at: 1517159550 DS: ANSWER"  ") in new stack
    -- Executing [h@qm-queuedial:2] Goto("SIP/9054-000061d0", "case-A") in new stack
    -- Goto (qm-queuedial,h,7)
    -- Executing [h@qm-queuedial:7] Set("SIP/9054-000061d0", "COMPLETE=COMPLETECALLER") in new stack
    -- Executing [h@qm-queuedial:8] Set("SIP/9054-000061d0", "WT=4") in new stack
    -- Executing [h@qm-queuedial:9] Set("SIP/9054-000061d0", "CT=3") in new stack
    -- Executing [h@qm-queuedial:10] Macro("SIP/9054-000061d0", "queuelog,1517159553,1517159541.28376,9001,Agent/9054,COMPLETECALLER,4,3") in new stack
    -- Executing [s@macro-queuelog:1] Set("SIP/9054-000061d0", "ADDINFO=4,3,") in new stack
    -- Executing [s@macro-queuelog:2] QueueLog("SIP/9054-000061d0", "9001,1517159541.28376,Agent/9054,COMPLETECALLER,4,3,") in new stack
    -- Executing [h@qm-queuedial:11] Hangup("SIP/9054-000061d0", "") in new stack
  == Spawn extension (qm-queuedial, h, 11) exited non-zero on 'SIP/9054-000061d0'


ERROR IMG:




Thanks.
16
QueueMetrics news / Tutorial Automatic e-mail notifications with WombatDialer
« Last post by Mausabot on January 24, 2018, 11:24:30 »
Version 16.06 of WombatDialer has been released with a lot of improvements and news. This includes a large number of bug fixes and a few interesting new features.

The most important feature is e-mail notifications. You can now tell WombatDialer to send you an e-mail when a campaign completes or changes its run status. Discover how to use this feature in the new tutorial.

Read it at https://www.wombatdialer.com/blog/blog/2018/01/23/wombatdialer-email-notification/?lid=U063
17
Running WombatDialer / Re: HTTP API Add Numbers to List
« Last post by terry_tate on January 17, 2018, 22:25:28 »
I was able to successfully upload leads using POST by using a content type of 'application/x-www-form-urlencoded'. I could not get json or form-data to work. Hopefully this helps someone.
18
QueueMetrics news / QueueMetrics Tutorial: Wallboard Queue Filtering
« Last post by Mausabot on January 17, 2018, 14:41:20 »
Do you ever wish you could create your own custom wallboard to understand at a glance whatís going on in your Asterisk call center?
Do you need to monitor multiple queues as a single entity, yet maintaining a perception of how the singular queues are doing?
If the answer is yes, read now the new tutorial about queue management with QueueMetrics:

https://www.queuemetrics.com/blog/2018/01/17/wallboard-queue-filtering?lid=U061
19
Running WombatDialer / HTTP API Add Numbers to List
« Last post by terry_tate on January 08, 2018, 23:26:38 »
I'm having trouble using the "add numbers to a list" API call. I've been able to successfully add numbers using HTTP GET.  However when I use HTTP POST it will not add numbers to the call list. I receive a 200 OK response but the body of the response returns this: "\n\n\n\n\n\n<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\"\n   \"http://www.w3.org/TR/html4/loose.dtd\">\n\n\n\nERROR: Unknown operation: \n\n". I have no idea what this error indicates. Can someone help me figure out what this error means?
20
QueueMetrics installation / Re: Agents with multiple queues problem
« Last post by mirkox on January 08, 2018, 09:55:59 »
Hi, theres nothing to wait, it depends only on your PBX configuration. Check the "Skip Busy Agent" configuration on all your queues.

Pages: 1 [2] 3 4 ... 10