Messages

1

Outbound and QueueMetrics / Re: Unable to get outbound working with FreePBX 2.10 and Asterisk 1.8

« on: June 21, 2013, 17:56:54 »

I'm not sure, if I dial the number from my phone it works but not from QueueMetrics. Can you suggest any configuration changes I could make?

2

Outbound and QueueMetrics / Re: Unable to get outbound working with FreePBX 2.10 and Asterisk 1.8

« on: May 14, 2013, 19:19:20 »

If I dial 18004563355 I am able to connect to Dell, is there anything else I can check or look at?

3

Outbound and QueueMetrics / Re: Unable to get outbound working with FreePBX 2.10 and Asterisk 1.8

« on: May 10, 2013, 18:44:06 »

This is that section for me, I commented out the ones that were there and modified per your instructions.

[queuedial]
; this piece of dialplan is just a calling hook into the [qm-queuedial] context that actually does the
; outbound dialing - replace as needed - just fill in the same variables.
exten => _XXX.,1,Set(QDIALER_QUEUE=q-${EXTEN:0:3})
exten => _XXX.,n,Set(QDIALER_NUMBER=${EXTEN:3})
;exten => _XXX.,n,Set(QDIALER_AGENT=Agent/${CALLERID(num)})
exten => _XXX.,n,Set(QDIALER_AGENT=Agent/${FROMEXTEN})
;exten => _XXX.,n,Set(QDIALER_CHANNEL=SIP/${QDIALER_NUMBER})
exten => _XXX.,n,Set(QDIALER_CHANNEL=SIP/MYOUTBOUNDTRUNKNAME/${QDIALER_NUMBER})
exten => _XXX.,n,Set(QueueName=${QDIALER_QUEUE})
exten => _XXX.,n,MixMonitor(Q-${QDIALER_QUEUE}-${UNIQUEID}.WAV,b,)
;exten => _XXX.,n,Set(CALLERID(all)="1234567890" <1234567890>) ; Uncomment and change this if you need to set your own caller ID
exten => _XXX.,n,Goto(qm-queuedial,s,1)

Do I need to modify this section or any of the others? I see QDIALER referenced a few different places.

; extension 28: agent custom dial
exten => 28,1,Answer
exten => 28,n,NoOp( "QM: Agent Custom Dial. Dialing ${EXTTODIAL} on queue ${OUTQUEUE}  made by '${QM_LOGIN}'" )
exten => 28,n,Set(QDIALER_QUEUE=${OUTQUEUE})
exten => 28,n,Set(QDIALER_NUMBER=${EXTTODIAL})
exten => 28,n,Set(QDIALER_AGENT=Agent/${AGENTCODE})
exten => 28,n,Set(QDIALER_CHANNEL=SIP/${QDIALER_NUMBER})
exten => 28,n,Set(QueueName=${QDIALER_QUEUE})
exten => 28,n,MixMonitor(Q-${QDIALER_QUEUE}-${UNIQUEID}.WAV,b,)
;exten => 28,n,Set(CALLERID(all)="1234567890" <1234567890>) ; Uncomment and change this if you need to set your own caller ID
exten => 28,n,Goto(qm-queuedial,s,1)
exten => 28,n,Hangup


When I dial 8 123 18004563355 I get the following in the asterisk logs

   -- Executing [812318004563355@from-internal:1] ResetCDR("SIP/9385-00008cd8", "") in new stack
    -- Executing [812318004563355@from-internal:2] NoCDR("SIP/9385-00008cd8", "") in new stack
    -- Executing [812318004563355@from-internal:3] Progress("SIP/9385-00008cd8", "") in new stack
    -- Executing [812318004563355@from-internal:4] Wait("SIP/9385-00008cd8", "1") in new stack
    -- Executing [812318004563355@from-internal:5] Progress("SIP/9385-00008cd8", "") in new stack
    -- Executing [812318004563355@from-internal:6] Playback("SIP/9385-00008cd8", "silence/1&cannot-complete-as-dialed&check-number-dial-again,noanswer") in new stack
    -- <SIP/9385-00008cd8> Playing 'silence/1.ulaw' (language 'en')
    -- <SIP/9385-00008cd8> Playing 'cannot-complete-as-dialed.ulaw' (language 'en')

4

Outbound and QueueMetrics / Unable to get outbound working with FreePBX 2.10 and Asterisk 1.8

« on: May 09, 2013, 19:52:18 »

I am using FreePBX distro 1.814.210.58-2  (Asterisk 1.8 and FreePBX 2.10) and am trying to setup outbound call tracking with QueueMetrics.

http://queuemetrics.com/manuals/QM_Trixbox-chunked/ar01s03.html

I have a custom trunk that has a custom dial string of "Local/$OUTNUM$\@queuedial/n" which is used by an outbound route that has 8 as a prefix.

From my understanding I should dial 8 (to use that route) then 123 for example which notates which campaign I am doing then the number (18004563355).

Below is part of the log when I made this call

<code>-- Executing [12318004563355@queuedial:1] Set("Local/12318004563355@queuedial-0a2d;2", "QDIALER_QUEUE=q-123") in new stack
    -- Executing [12318004563355@queuedial:2] Set("Local/12318004563355@queuedial-0a2d;2",
"QDIALER_NUMBER=18004563355") in new stack
    -- Executing [12318004563355@queuedial:3] Set("Local/12318004563355@queuedial-0a2d;2",
"QDIALER_AGENT=Agent/3032288750") in new stack
   -- Executing [12318004563355@queuedial:4] Set("Local/12318004563355@queuedial-0a2d;2",
"QDIALER_CHANNEL=SIP/18004563355") in new stack
    -- Executing [12318004563355@queuedial:5] Set("Local/12318004563355@queuedial-0a2d;2", "QueueName=q-123") in new stack</code>

QM support said said the channel is wrong?

QDIALER_CHANNEL=SIP/18004563355

They said it should likely be SIP/mypprovider/1800.....

QDIALER_AGENT=Agent/3032288750

They also the agent should have the code the call will appear under in QM, so it's likely agent/101.

Anyways, sorry for a long post but can anyone help me get this working?

5

Improving QueueMetrics / Re: Passwords in arch_users stored in clear text

« on: April 12, 2013, 17:57:07 »

I would also like to see passwords encrypted in the database and not shown on the user page. Additionally I would like to see the diagnostic page and license information to be hidden by default and a security key added so that the admin class can see it at all times.