Author Topic: outboun calls  (Read 26709 times)

QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: outboun calls
« Reply #45 on: April 07, 2009, 15:06:00 »
so now the files are been generated the call but some times it waits arround 15 seconds or more.. even to much waiting...

the file stays there for half and hour  :'(


You mean teh audio file? there is no reason why it should be removed at all.... neither Asterisk nor Qm remove it.

emel_punk

  • Jr. Member
  • **
  • Posts: 97
  • Karma: 0
    • View Profile
    • Email
Re: outboun calls
« Reply #46 on: April 13, 2009, 15:32:18 »
im talking about the file generated at /var/spool/asterisk/outgoing
the file that does make the call to extension 11 or 14 on queuemetrics and  can spy channels.
sometimes i have to wait a minutes or even more to recive the call from the extension i want to spy. ???

QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: outboun calls
« Reply #47 on: April 14, 2009, 15:20:05 »
Do not use a callfile, use a direct TCP connection. call files gent processed by asterisk when it wants to. :)

emel_punk

  • Jr. Member
  • **
  • Posts: 97
  • Karma: 0
    • View Profile
    • Email
Re: outboun calls
« Reply #48 on: April 14, 2009, 17:13:12 »
check out

callfile.monitoring.enabled=true
callfile.monitoring.channel=Local/$EM@from-internal/n
callfile.monitoring.extension=11
callfile.monitoring.context=queuemetrics

callfile.outmonitoring.enabled=true
callfile.outmonitoring.channel=Local/$EM@from-internal/n
callfile.outmonitoring.extension=14
callfile.outmonitoring.context=queuemetrics


now ist working on realtime the spy agent call but check this out its using extension 11 instead of using 14 for outbound call



Called 110
    -- SIP/110-09e1a448 is ringing
    -- SIP/110-09e1a448 answered Local/110@from-internal-cad5,2
       > Channel Local/110@from-internal-cad5,1 was answered.
  == Manager 'admin' logged off from 127.0.0.1
    -- Executing [11@queuemetrics:1] Answer("Local/110@from-internal-cad5,1", "") in new stack
    -- Executing [11@queuemetrics:2] NoOp("Local/110@from-internal-cad5,1", " "QM_AGENT_CODE: agent/1010" ") in new stack
    -- Executing [11@queuemetrics:3] NoOp("Local/110@from-internal-cad5,1", " "QM_EXT_MONITOR: 110" ") in new stack
    -- Executing [11@queuemetrics:4] NoOp("Local/110@from-internal-cad5,1", " "QM_AGENT_EXT: -" ") in new stack
    -- Executing [11@queuemetrics:5] ChanSpy("Local/110@from-internal-cad5,1", "agent/1010") in new stack
    -- <Local/110@from-internal-cad5,1> Playing 'beep' (language 'en')


:(

QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: outboun calls
« Reply #49 on: April 15, 2009, 18:33:42 »
It will use 11 or 14 depending if it sees the cal as inbound versus outbound.

emel_punk

  • Jr. Member
  • **
  • Posts: 97
  • Karma: 0
    • View Profile
    • Email
Re: outboun calls
« Reply #50 on: April 17, 2009, 15:28:55 »
Well i have to  modify extensions  11 and 14 to they work as in inbound or outbound  and finally it working  :-*

exten => 11,n,set(foo1=${DB(Agents/${QM_AGENT_CODE:6})})
exten => 11,n,ChanSpy(SIP/${foo1:0:3})
exten => 11,n,hangup

THANKS FOR ALL THE SUPPORT !!  :D ;D ;)

QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: outboun calls
« Reply #51 on: April 17, 2009, 20:54:00 »
Cool! it was not easy :-)