outboun calls

[emel_punk]

  Nothing 
i mean i did  this

; extension 14 makes remote monitoring possible for OUTBOUND CALLS
exten => 14,1,Answer
exten => 14,2,NoOp( "QM_AGENT_CODE: ${QM_AGENT_CODE}" )
exten => 14,3,NoOp( "QM_EXT_MONITOR: ${QM_EXT_MONITOR}" )
exten => 14,4,NoOp( "QM_AGENT_EXT: ${QM_AGENT_EXT}" )
exten => 14,5,NoOp( "QM_LOGIN: ${QM_LOGIN}" )
;exten => 14,6,ChanSpy(Local/${QM_AGENT_CODE:6}@from-internal)
exten => 14,6,ChanSpy(SIP/${QM_AGENT_CODE:6})


this is the output when i dial to the number but nothing happens after i click on the icon type the extension and prees monitor buttom

servidor*CLI>
    -- Executing [73139000@from-internal:1] Answer("SIP/111-b760cd80", "") in new stack
    -- Executing [73139000@from-internal:2] Set("SIP/111-b760cd80", "anagent=1010") in new stack
    -- Executing [73139000@from-internal:3] GotoIf("SIP/111-b760cd80", "1?marcarag") in new stack
    -- Goto (from-internal,73139000,5)
    -- Executing [73139000@from-internal:5] DeadAGI("SIP/111-b760cd80", "queueDial.agi|3139000|sip/spa400/3139000|350|Agent/1010") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/queueDial.agi
    -- AGI Script Executing Application: (dial) Options: (sip/spa400/3139000||g)
    -- Called spa400/3139000
    -- SIP/spa400-094fd508 answered SIP/111-b760cd80
    -- AGI Script queueDial.agi completed, returning 0

 

[QueueMetrics]

Are your QM's tcp settings correct? and does it know that the call is OUTBOUND, i.e. it has a yellow icon?

[emel_punk]

where i can see my tcp settings?? cause im kinda confussed, and yes the call its outbounded by QM cause i can see my outbound call on QM on real time and on the reports  and the icon is yellow 

[QueueMetrics]

default.callfiledir

Of course I imagine you are using QM 1.5.1?

[emel_punk]

yes im using  QM 1.5.1 but i cant find that file !!!! 

aaa and by the way i got QM 1.5.0  in another machine and it works perfectlly  spying the outbound calls

[emel_punk]

I recently saw that   when i try to monitor Qm genereates a file on /var/spool/asterisk/outgoing  for every  call i try to spy, but all the files gets stucks on this folder.... i compare with some files generated by the Qm from another machine  that generated this files and  offcourse this machine do well the Spychan...here is the files:

file generated by QM not doing monitor now(spy)

Channel: Local/110@from-internal/n
MaxRetries: 0
RetryTime: 60
WaitTime: 30
Context: queuemetrics
Extension: 11
Priority: 1
SetVar: QM_AGENT_CODE=agent/1010
SetVar: QM_CALLERID=110
SetVar: QM_EXT_MONITOR=110
SetVar: QM_QUEUE=500
SetVar: QM_QUEUE_URL=
SetVar: QM_AGENT_EXT=-


file generated by QM doing monitor now(spy)

Channel: Local/10000@from-internal/n
MaxRetries: 0
RetryTime: 60
WaitTime: 30
Context: queuemetrics
Extension: 11
Priority: 1
SetVar: QM_AGENT_CODE=agent/8073
SetVar: QM_CALLERID=22870412
SetVar: QM_EXT_MONITOR=10000
SetVar: QM_QUEUE=8007
SetVar: QM_QUEUE_URL=
SetVar: QM_AGENT_EXT=-
StartRetry: 3867 1 (1237926412)
~
 

[emel_punk]

ohh i find out another  thing.. these files on /var/spool/asterisk/outgoing are being generated with root   privileges.. so if i  change manually to asterisk file is read it by asterisk... on asterisk 1.4

[QueueMetrics]

If you can, it's best not to use spool files but the direct TCP connection.

[QueueMetrics]

About your callfiles:
- is Local/10000@from-internal/n your local extension?
- it's trying to call 11@queuemetrics to do the spying, that is for INBOUND spying - you should set the queue to outbound.

[emel_punk]

yes indeed,  those files are for inbound... actually inbound or outbound its not working and  i got QM 1.5.1 and asterisk 1.4  ....


and about using direct TCP connection, how i do that?

[QueueMetrics]

The credentials supplied in the configuration.properties file should look like:

Code: [Select]

callfile.dir=tcp:dial:bingo@1.2.3.4
Where dial is the user name, bingo the password and 1.2.3.4 the IP address of your Asterisk box.

Check that they match the ones in Asterisk's own /etc/asterisk/manager.conf

[emel_punk]

i found this one.....

cluster.aleph.manager=tcp:dial:12345@10.10.3.5
cluster.aleph.queuelog=sql:P001
cluster.aleph.monitored_calls=z:/qm_streamcall/server_aleph
cluster.aleph.callfilesdir=
cluster.aleph.audioRpcServer=
cluster.aleph.agentSecurityKey=

cluster.trix.manager=tcp:admin:amp111@127.0.0.1
cluster.trix.queuelog=sql:P002
cluster.trix.monitored_calls=z:/qm_streamcall/server_trix
cluster.trix.callfilesdir=
cluster.trix.audioRpcServer=
cluster.trix.agentSecurityKey=


the second part  it match with  manager.conf

[QueueMetrics]

No you should edit it on top of the file.

[emel_punk]

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 

[emel_punk]

emmm what else should i do