QueueMetrics > Outbound and QueueMetrics

outbound calls not working if logged in via QM

(1/3) > >>

blackgecko:
Hi:

im implementing a queuemetrics for inbound and outbound monitor, inbound calls are working great.

With the outbound calls im having a problem, im forcing that only logged agents can call so im using the
queuedial-loggedon context.

The problem is that if the agent logs in vi the QM screen he can´t do outbound calls cause asterisk says agent-loggedoff

if they log on via the phone

[from-internal-custom]
exten => _*60[0-5],1,AgentCallBackLogin(||@from-internal)
exten => _*60[0-5],n,Hangup

it just works.

I´ve been doing some research comparing my dialplan for and the extensions_queuemetrics.conf and found this

exten => _*60[0-5],1,AgentCallBackLogin(||@from-internal)
exten => _*60[0-5],n,Hangup

exten => 20,1,Answer
exten => 20,2,NoOp( "QM: Logging on Agent/${AGENTCODE} to extension ${AGENT_EXT}@from-internal" )
exten => 20,3,AgentCallBackLogin(${AGENTCODE}||${AGENT_EXT}@from-internal)
exten => 20,4,Hangup

As i see i think the problem is within this line
exten => 20,3,AgentCallBackLogin(${AGENTCODE}||${AGENT_EXT}@from-internal)

wich is diferrent form this
exten => _*60[0-5],1,AgentCallBackLogin(||@from-internal)

where im not passing the ${AGENTCODE} and ${AGENT_EXT} as in the queuemetrics dialplan

Is there any way to make it work the same way ? i don want the to have to dial another code to log in cause this can add another point of failure.

Thanks in advance and great work with you software.

QueueMetrics:
To place an outbound call, it's not technically necessary that the agent be logged on - though it's nice for uniformity, etc. and you can logon any way you like, as long as it's a valid logon - so using or not using the QM dialplan, it's the same.
The QM dialplan was made to be called from the agent interface, so variables are set correctly.

blackgecko:
well but its not working, if an agent gets into QM, and logs in via the agent screen, even when in asterisk it appears as available 
1001         (Agente 1) available at '1001@from-internal' (musiconhold is 'default')

when he calls trough the quedial-loggedon context he gets the
aggent logedoff recording

if he logs in via the *600 extension he can call without problem

QueueMetrics:
OK what do you get in the CLI when you try calling the logon code from QM?

blackgecko:
 -- Executing [20@queuemetrics:1] Answer("Local/20@queuemetrics-01ae,2", "") in new stack
    -- Executing [20@queuemetrics:2] NoOp("Local/20@queuemetrics-01ae,2", " "QM: Logging on Agent/1002 to extension 1002@from-internal" ") in new stack
    -- Executing [20@queuemetrics:3] AgentCallbackLogin("Local/20@queuemetrics-01ae,2", "1002||1002@from-internal") in new stack
    -- <Local/20@queuemetrics-01ae,2> Playing 'agent-loginok' (language 'en')
       > Channel Local/20@queuemetrics-01ae,1 was answered.
    -- Executing [10@queuemetrics:1] Answer("Local/20@queuemetrics-01ae,1", "") in new stack
    -- Executing [10@queuemetrics:2] Wait("Local/20@queuemetrics-01ae,1", "10") in new stack
  == Callback Agent '1002' logged in on 1002@from-internal
    -- Executing [20@queuemetrics:4] Hangup("Local/20@queuemetrics-01ae,2", "") in new stack
  == Spawn extension (queuemetrics, 20, 4) exited non-zero on 'Local/20@queuemetrics-01ae,2'
  == Spawn extension (queuemetrics, 10, 2) exited non-zero on 'Local/20@queuemetrics-01ae,1'

Navigation

[0] Message Index

[#] Next page