QueueMetrics > Outbound and QueueMetrics

outboun calls

<< < (8/11) > >>

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?

Navigation

[0] Message Index

[#] Next page

[*] Previous page