Stat Server Actions for Mediation DNs
- 1 Stat Server Actions for Mediation DNs
- 1.1 Durable, Non–Interaction-Related Actions
- 1.2 Durable, Interaction-Related Actions
- 1.3 Momentary, Interaction-Related Actions
- 1.4 Momentary, Non-Interaction-Related Action
- 1.5 Retrospective, Interaction-Related Actions
- 1.6 Retrospective, Interaction-Related Actions Reflecting Regular DNs
- 1.7 Retrospective, Interaction-Related Actions Generated on Virtual Queues
- 1.8 Generation of Retrospective, Interaction-Related Actions Reflecting Regular DNs for Virtual Queue Mediation DN Objects
- 1.9 Retrospective, Interaction-Related Action Generated on Interaction Distribution from One Mediation DN to Another Mediation DN
Durable, Non–Interaction-Related Actions
The following are the durable, non–interaction-related actions that Stat Server generates on mediation DNs:
AgentLogin (Mediation DNs)
Monitored (Mediation DNs)
NotMonitored (Mediation DNs)
UserEventReceived (Mediation DNs)
Durable, Interaction-Related Actions
CallWait is a durable, interaction-related action that Stat Server generates on mediation DNs.
Momentary, Interaction-Related Actions
The following are the momentary, interaction-related actions that Stat Server generates on mediation DNs:
Momentary, Non-Interaction-Related Action
UserEvent (Mediation DNs) is a momentary, non–interaction-related action that Stat Server generates on mediation DNs.
Retrospective, Interaction-Related Actions
The following are the retrospective, interaction-related actions that Stat Server generates on mediation DNs:
Retrospective, Interaction-Related Actions Reflecting Regular DNs
The following are the retrospective, interaction-related actions reflecting regular DNs that Stat Server generates on mediation DNs:
- CallAbandonedFromRinging (Mediation DNs)
- CallAnswered (Mediation DNs)
- CallReleased (Mediation DNs)
With the exception of the CallAnswered, CallAbandonedFromRinging, CallForwarded, StuckCallCleanedWhileRinging actions, these retrospective, interaction-related actions reflecting regular DNs work, without additional confirmation, only for ACD queues and T-Server applications that propagate the queue parameter in login messages. For T-Server applications that do not do this, you must explicitly configure the association between Agent objects and mediation DN in Genesys Administrator Extension, as follows:
- Select an agent (or place) group.
- On the Origination DNs tab, click Add.
- In the Origination DN dialog box, select the appropriate mediation DN.
- On the Origination DNs tab, click Save or Apply to save the configured association.
With the exception of the ACWMissed and CallMissed actions in this category, Stat Server propagates retrospective, interaction-related actions that reflect regular DNs, such as CallAnswered and CallAbandonedFromRinging, from an agent’s DN to the last physical mediation DN through which a call passes before being answered or abandoned while ringing in a single-site contact center. Stat Server propagates ACWMissed and CallMissed actions to all mediation DNs involved in the processing of the interaction except the last mediation DN from which the interaction was answered by a handling resource.
If, however, the call is queued in parallel to both an ACD queue DN and a routing point, and the ThirdPartyDN attribute of EventRouteUsed shows that the call was answered on some regular DN, then Stat Server will propagate this action to both.
Retrospective, Interaction-Related Actions Generated on Virtual Queues
The following are the retrospective, interaction-related actions that Stat Server generates on virtual queue objects that are controlled by a Multimedia-monitored switch:
CallAbandonedFromRinging (Virtual Queues)
CallAnswered (Virtual Queues)
CallReleased (Virtual Queues)
InteractionAbandonedDuringOffering (Virtual Queues)
- All mediation DN actions can be potentially generated for virtual queues, controlled by the Multimedia-monitored switch except voice actions listed below:
- In order to properly count any media-related interactions passing through a virtual queue, the virtual queue must be configured on a Multimedia-monitored switch.
Generation of Retrospective, Interaction-Related Actions Reflecting Regular DNs for Virtual Queue Mediation DN Objects
For virtual queue mediation DN objects, Stat Server generates retrospective, interaction-related actions reflecting regular DNs depending on the combination of settings of the following Stat Server configuration options, which are defined in the Framework Stat Sever Deployment Guide:
Using these options, you can change the algorithm for Stat Server’s generation of CallAnswered actions on virtual queue objects to meet your requirements. If you set vq-ignore-third-party-dn to true (the default value), Stat Server generates the CallAnswered action on all virtual queue objects through which a call passes before it is answered. If you set the option vq-ignore-third-party-dn to false, Stat Server references the ThirdPartyDN attribute in EventDiverted TEvents that Stat Server receives from Universal Routing Server for CallAnswered action generation. In this case, the rules of CallAnswered action generation depend on settings of the vq-treat-unknown-third-party-dn-asagent-dn option. Introduction of this option allows Stat Server to generate this action only on the last virtual queue object through which a call passes before being answered in single-site call monitoring scenarios (inbound call enters monitoring site, inbound call is queued on the routing point associated with the Virtual Queue on the same site and is routed to the target on the same site). Multi-site Call monitoring scenarios have some limitations in this rule because there are cases where ThirdPartyDN does not contain reliable information about the DN to which the call was diverted.[+] Scenarios