Messages

1

Running QueueMetrics / Re: Agents currently logged in not parsed correctly

« on: January 19, 2011, 12:57:07 »

Perfekt! Thank you for your help!

Try to do the logins/logoffs as g-1234-1 instead of g-1234. Qm will stripo off the final "-1" and yiou should be OK.

2

Running QueueMetrics / Re: Agents currently logged in not parsed correctly

« on: January 14, 2011, 16:35:55 »

Hi,

the strange thing is, that in "Calls being processed" our accounts seam to work


This is why I think there must be some type of difference in the code parsing the account.

Here is our extension for login/logout


exten => _*77-.,n,System( echo "${EPOCH}|${UNIQUEID}|NONE|SIP/${SIPCHANINFO(peername)}|AGENTLOGOFF|-|${RV}" >> /var/log/asterisk/queue_log )

exten => _*77-.,n,System( echo "${EPOCH}|${UNIQUEID}|${queue${num}}|SIP/${SIPCHANINFO(peername)}|ADDMEMBER|-" >> /var/log/asterisk/queue_log )

Best regards,

Oliver

3

Running QueueMetrics / Re: Agents currently logged in not parsed correctly

« on: January 11, 2011, 20:23:10 »

Could you post a piece of your queue_log for inspection?

sure:


1294760074|1294760073.7989|7|SIP/g-000186|REMOVEMEMBER|-|4489
1294760074|1294760073.7989|6|SIP/g-000186|REMOVEMEMBER|-|4489
1294760074|1294760073.7989|2|SIP/g-000186|REMOVEMEMBER|-|4489
1294760074|1294760073.7989|8|SIP/g-000186|REMOVEMEMBER|-|4489
1294760074|1294760073.7989|3|SIP/g-000186|REMOVEMEMBER|-|4489
1294760074|1294760073.7989|5|SIP/g-000186|REMOVEMEMBER|-|4489
1294760074|1294760073.7989|15|SIP/g-000186|REMOVEMEMBER|-|4489
1294760074|1294760073.7989|14|SIP/g-000186|REMOVEMEMBER|-|4489
1294760074|1294760073.7989|35|SIP/g-000186|REMOVEMEMBER|-|4489
1294760074|1294760073.7989|46|SIP/g-000186|REMOVEMEMBER|-|4489
1294760074|1294760073.7989|26|SIP/g-000186|REMOVEMEMBER|-|4489

1294760645|1294760645.8113|35|SIP/g-000038|ADDMEMBER|-
1294760645|1294760645.8113|46|SIP/g-000038|ADDMEMBER|-
1294760645|1294760645.8113|7|SIP/g-000038|ADDMEMBER|-
1294760645|1294760645.8113|6|SIP/g-000038|ADDMEMBER|-
1294760645|1294760645.8113|2|SIP/g-000038|ADDMEMBER|-
1294760645|1294760645.8113|8|SIP/g-000038|ADDMEMBER|-
1294760645|1294760645.8113|3|SIP/g-000038|ADDMEMBER|-
1294760645|1294760645.8113|5|SIP/g-000038|ADDMEMBER|-
1294760645|1294760645.8113|15|SIP/g-000038|ADDMEMBER|-
1294760645|1294760645.8113|14|SIP/g-000038|ADDMEMBER|-
1294760645|1294760645.8113|24|SIP/g-000038|ADDMEMBER|-
1294760645|1294760645.8113|26|SIP/g-000038|ADDMEMBER|-



1294773186|1294773155.10666|7|NONE|ENTERQUEUE||+4123456789
1294773226|1294773225.10678|24|NONE|ENTERQUEUE||+4123456789
1294773227|1294773225.10678|24|SIP/g-000040-0a338b80|CONNECT|1
1294773236|1294773155.10666|7|NONE|ABANDON|1|1|50
1294773246|1294773225.10678|24|SIP/g-000040-0a338b80|COMPLETECALLER|1|19
1294773265|1294772835.10625|7|SIP/g-000186-0a54a288|COMPLETEAGENT|108|272
1294773277|1294773057.10658|6|SIP/g-000039-0a64e138|COMPLETECALLER|3|186
1294773294|1294773294.10685|24|NONE|ENTERQUEUE||+4123456789
1294773295|1294773294.10685|24|NONE|ABANDON|1|1|1
1294773323|1294773259.10682|8|NONE|ENTERQUEUE||+4123456789
1294773330|1294773259.10682|8|SIP/g-000186-0a6b9c98|CONNECT|7
1294773332|1294773268.10683|8|NONE|ENTERQUEUE||+4123456789
1294773334|1294773268.10683|8|SIP/g-000039-0a33b7a0|CONNECT|2
1294773338|1294773338.10696|24|NONE|ENTERQUEUE|+4123456789
1294773340|1294773338.10696|24|SIP/g-000040-0a37cba0|CONNECT|2
1294773355|1294773291.10684|8|NONE|ENTERQUEUE||+4123456789
1294773362|1294773259.10682|8|SIP/g-000186-0a6b9c98|COMPLETEAGENT|7|32
1294773363|1294773291.10684|8|SIP/g-000186-0a3512f8|CONNECT|8
1294773372|1294773291.10684|8|SIP/g-000186-0a3512f8|COMPLETECALLER|8|9
1294773424|1294773382.10703|6|NONE|ENTERQUEUE||+4123456789
1294773428|1294773382.10703|6|SIP/g-000186-0a3512f8|CONNECT|4
1294773490|1294773139.10662|8|SIP/g-000183-0a3a0150|COMPLETECALLER|8|339
1294773504|1294773268.10683|8|SIP/g-000039-0a33b7a0|COMPLETEAGENT|2|170
1294773525|1294773468.10708|6|NONE|ENTERQUEUE||+4123456789
1294773527|1294773468.10708|6|SIP/g-000183-0a2b44a0|CONNECT|2
1294773554|1294773338.10696|24|SIP/g-000040-0a37cba0|COMPLETECALLER|2|214
1294773572|1294773530.10712|6|NONE|ENTERQUEUE||+4123456789
1294773576|1294773530.10712|6|SIP/g-000039-0a356b38|CONNECT|4

4

Running QueueMetrics / Re: Agents currently logged in not parsed correctly

« on: January 10, 2011, 14:44:18 »

Hi,

It would be very difficult to change the userid as they are automatically generated and there are ~ 15k users provisioned.

With the old version the "-" was no problem.

My only solution for now would be to modify the perl import script and replace the "-" to nothing. Which I think is only a temp solution.

Best regards,

Oliver

5

Running QueueMetrics / Re: Agent not getting added to the selected queue

« on: January 05, 2011, 19:34:46 »

maybe this is the same problem I am having.

What is your userid for the sip accounts? Is there a "-" somewhere?

Oliver

6

Running QueueMetrics / Agents currently logged in not parsed correctly

« on: January 03, 2011, 13:34:51 »

Hi,

We have recently updated from Loway QueueMetrics - 1.3.5 to the news one 1.6.3.0. The upgrade worked without a problem. I only noticed that the real time view is not showing the logged in users.

We are using g-xxxxxx as userids for our sip accounts. It seams like the part "agents currently logged in" splits the string somewhere at "-" as I only see "sip/g" logged in.

I first thought the qloaderd could cause the problem and turned on debugging - the g-123456 accounts are inserted into the DB. I also did a check on the Database, what Data was stored - everything looks ok.

If I connect to the old 1.3.5 Version - at this version the real time view is still working.

Could you please check on this issue.

Thank you and Happy New Year,

Oliver Polterauer