Generating count for total agents logged in to Genesys environment

[vrbros]

Dear Ecki,

[i]"It is enough when the reason is with request agent loggin. It does not have to be with request agent loggout as well. So you are safe in any case. Important is that agents are using softphone when they are logging in. Then the softphone can die and still Stat server will capture the right statistics because the loggin event is counted."[/i]

The idea of sending a KVP for stat server to get the count that agent is logging in is OK. But how would stat server understand the logout without the KVP? I am sorry I was not able to test this as I was stuck with some documentation for site and lost track of this thread.

CHEERS!!

[ecki]

Hi,

Have look in to the Stat Server user guide Filter section. Just for info, Logged in is durable action.

>>>>>
For durable actions and statuses, Stat Server uses the number of times that
a filter condition was true on an action (or status) and the duration of time
for which the filter was true.
>>>>>>

[tony]

I'd like to take a step back here...  There are some statements I think it might be worthwhile exploring...

It's been stated that the Agent has 2 options to log out - via GAD and via the physical turret.  The problem statement is that the StatServer is informed of the GAD Logout but not a physical turret logout...?

In my experience;

Using GAD to log out the Agent send a TEvent [b]Request [/b] = [i][b]TAgentLogout[/b][/i].  Once the T-Event is confirmed, the Switch/ACD will send an [b]Event [/b] to confirm the [i][b]TAgentLogout[/b][/i].
A physical Turret Logout [i]should [/i] invoke an instruction to the Switch/ACD [i]directly[/i], which is subsequently sent via the CTI Link to the T-Server, in the form of an [b]Event[/b] = [i][b]TAgentLogout[/b][/i].

So, in my opinion the TServer should be up-to-date(?) It is only the StatServer which is not obtaining the correct status updates - for Agents Logging out using their physical turret instead of GAD(?)

I suggested using the LOGIN Table, earlier in this thread.  I have not had an opportunity to explore whether both scenarios for Logout (GAD vs. Turret) increment/decrease entries in the LOGIN Table.  It is populated as a result of input from the TServer via the StatServer but I think it may work, in this scenario.

We have use of an Avaya and I have the LOGIN Table set up in our DEV environment - I'll take a look at what entries are updated (and how) when using;

A.  A physical turret LOGIN (i.e. no Genesys)
B.  A physical turret LOGOUT (i.e. no Genesys)
C.  A GAD LOGIN
D.  A GAD LOGOUT
E.  A GAD LOGIN with a physical turret LOGOUT
F.  A physical turret LOGIN with a GAD LOGOUT

I'll get back to you all with results...

Tony

[ecki]

Hi Tony,

I think the matter is rather in that they have two types of agent. One type are using GAD during entire CC work from login to logout and the other are using purely the hard phones (no CTI at all) although the place is monitored by Genesys. Probably those agents does not need CTI or does not have skill to do so. And as I understood it right, they want to know, how many agents were working on the particular day with Softphone and how many without.

[tony]

Understood - so, as long as the TServer and IServer ([i]not [/i] IXNServer ) are effectively monitoring the whole ACD/GAD range (CTI and non-CTI) then we [i]should [/i] get LOGIN/LOGOUT result through TEvents, which [i]should [/i] be monitored by a StatServer, as long as it has all of the relevant TServer(s) and IServer(s) as connections and is correctly connected/configured via a DAP/DBServer to write the results into the LOGIN Table... ?

I'm taking a look at it, today...

Tony

[tony]

OK - From what I can gather, you will be able to obtain a LOGINID and an indication of a LOGIN or LOGOUT, as well as a Timestamp from the LOGIN table and various other Configuration References.

I have tested a few scenarios and the TServer accepts all relevant EVENTS from the attached Switch/PBX (Avaya) then as long as the CME environment lists/registers [b]all [/b] LOGINID's (DN's) for both CTI and non-CTI Hard Phone/turret Extensions.  For some clarity - if you add an IServer to the Connections of the StatServer, it can extract all of the associated LOGIN/LOGOUT EVENTS from the GAD, too.

For this to work, I need to make an assumption that the Extensions/DN's themselves are identifiable as "CTI" and "non-CTI".  The results Table (LOGIN) can be extracted and queried on the basis of the Extension/LOGINID, Timestamp (Time Range) and Status (1 = LOGIN, 0 = LOGOUT)

Further to this, the following information is available on the LOGIN Table;

SWITCHDBID, DBDBID, QUEUEDBID, AGENTDBID, PLACEDBID, STATUS, TIME and LOGINID.

- It follows that it would be possible to create a LOOKUP Query from this information, to determine which LOGINID's (or PLACEDBID's) are logged in - and when they logged out.  Of course, if the Agent simply closes GAD without logging out, you'd need to find a clever way of determining a "time-out" period of inactivity, to emulate a LOG OUT for those types of instances.

I'm sayng it [i]can [/i] work when using the LOGIN Table - with a bit of development!

- Anyone else want to venture their opinion?

Tony

[René]

[quote]For some clarity - if you add an IServer to the Connections of the StatServer, it can extract all of the associated LOGIN/LOGOUT EVENTS from the GAD, too.[/quote]

Tony, could you explain me why you need IServer for GAD? GAD is application based on Genesys AIL (Agent Interaction Layer) and communicates directly with TServer (on server side of course). IServer is virtual application used by IVR TServer. I don't see any connection between these two apps...

If StatServer monitors particular DN then login/logout events occurring on that DN (place) will be saved to LOGIN table. StatServer only need one connection for that - connection to TServer.

R.

[ecki]

Tony,

The issue is from what I understood, that the same extension is used by both types of agents. Agents who uses GAD for whole time of their session (except when agent is lazy to use softphone for log out or some component just crash down) and Agents who does not use GAD at all. As the extension is monitored by TServer, Stat Server is getting all events no matter if Agents are using GAD or not. How are you going to separate those two agents using data from LOGIN table? Or did I understand the core problem whatsoever?

e.

[tony]

Rene,

The suggestion is that, [i]if [/i] you have a blended environment, you may want to connect to the TServer for Voice and also an IServer (based on the TServer template) for Interactions information.  I tried to explain that it was [b]not [/b] an IVR TServer, but an MCR IServer - which is, in essence, a TServer too...!

Tony

[quote author=René link=topic=4096.msg18215#msg18215 date=1240320833]
[quote]For some clarity - if you add an IServer to the Connections of the StatServer, it can extract all of the associated LOGIN/LOGOUT EVENTS from the GAD, too.[/quote]

Tony, could you explain me why you need IServer for GAD? GAD is application based on Genesys AIL (Agent Interaction Layer) and communicates directly with TServer (on server side of course). IServer is virtual application used by IVR TServer. I don't see any connection between these two apps...

If StatServer monitors particular DN then login/logout events occurring on that DN (place) will be saved to LOGIN table. StatServer only need one connection for that - connection to TServer.

R.
[/quote]

[tony]

Understood  - I mentioned that the LOGIN Table also contains a Field called "PLACEDBID".  Any entries on the LOGIN Table [i]with [/i] a PLACEDBID = CTI/Genesys, [i]without [/i] a PLACEDBID = non-CTI/Genesys...

At least, I [i]think [/i] that's right...?

Tony


[quote author=ecki link=topic=4096.msg18216#msg18216 date=1240321960]
Tony,

The issue is from what I understood, that the same extension is used by both types of agents. Agents who uses GAD for whole time of their session (except when agent is lazy to use softphone for log out or some component just crash down) and Agents who does not use GAD at all. As the extension is monitored by TServer, Stat Server is getting all events no matter if Agents are using GAD or not. How are you going to separate those two agents using data from LOGIN table? Or did I understand the core problem whatsoever?

e.
[/quote]

[René]

[quote]I tried to explain that it was not an IVR TServer, but an MCR IServer - which is, in essence, a TServer too...![/quote]

OK. Now it's clear to me. Thank for the explanation Tony

Personally, I'm using the abbreviation IxnServer for Interaction Server to avoid confusiong with IVR IServer

[quote]Understood  - I mentioned that the LOGIN Table also contains a Field called "PLACEDBID".  Any entries on the LOGIN Table with a PLACEDBID = CTI/Genesys, without a PLACEDBID = non-CTI/Genesys...[/quote]

Have you tested that? I would say that PLACEDBID will be filled even for non-CTI logins as StatServer uses place as the primary object internally.

R.

[tony]

Going to try it out, tomorrow...

[quote author=René link=topic=4096.msg18221#msg18221 date=1240326103]
[quote]I tried to explain that it was not an IVR TServer, but an MCR IServer - which is, in essence, a TServer too...![/quote]

OK. Now it's clear to me. Thank for the explanation Tony

Personally, I'm using the abbreviation IxnServer for Interaction Server to avoid confusiong with IVR IServer

[quote]Understood  - I mentioned that the LOGIN Table also contains a Field called "PLACEDBID".  Any entries on the LOGIN Table with a PLACEDBID = CTI/Genesys, without a PLACEDBID = non-CTI/Genesys...[/quote]

Have you tested that? I would say that PLACEDBID will be filled even for non-CTI logins as StatServer uses place as the primary object internally.

R.


[/quote]

[tony]

OK - I have found that an AGENTDBID is not appended to the entry in the LOGIN Table, when a hard phone/turret is used to LOGIN or LOGOUT - but the entry is valid in all other respects (SWITCHDBID, DBDBID, QUEUEDBID, PLACEDBID, STATUS, TIME and LOGINID are all populated.)

This would mean that you [i]can [/i] differentiate between CTI and non-CTI LOGIN's and LOGOUT's using the LOGIN Table Option of the StatServer.  [i]How [/i] you do that is (and report from it) is the next problem...

Tony