Stat Server Actions Flashcards
Stat Server Actions
Actions(T-Event and ) occur at the DN level. The DN can have as many actions occur simultaneously. They are building blocks used to model activity occurring in the environment. Statistical value are base of these actions duration and occurrences. SS propagates action to the higher level objects.
Types of Actions
Durable, Retrospective and Momentary actions
non-interaction related actions
They do not have ConnID and mutually exclusive to the DN. Related to objects in the configuration but never include a ConnID attribute. Filter and custom formula cannot be used for this type of interaction.
Durable Actions
The Action has duration and ends when something else happens. An example would be a event ringing until it is answered.
Momentary Action
Has no duration and indicate that a durable action(call related) has started so they are corresponding with each other. One momentary action corresponding to a momentary action.
Retrospective Actions
Indicates an end to a durable actions such as CallRetrievedfromHold mark end of CallOnHold. There can be one or more based on the outcome of a durable actions.
NotMonitored Actions
Begins with EventServerDisconnected, EventLinkDisconnected, and EventDNOutOfService. It ends Monitor actions. Caused by CTI link disconnection with the T-Server or DN out of service.
Status Defined
Special type of durable action that define the object status. The status of an object is determined by the ongoing durable action with the highest rank on the status priority table. There can only be one status for an object.
Place Status
The status of the place is linked to the DN associated with it. Agent is based of the Place the agent is currently logged into. Hench the Status of Agent and Place is determine the underlying object.
What Determine Agent and Place Group Status
Determine by the Places and Agents part of the Group
What are Regular DN
Data, music, mixed extension, ACD position, Voice Treatment port, voice mail, cellular, CP, and fax
CallOnHold Status
The action mask other actions such as CallInbound, CallInternal, or CallUnknown statuses. Stat Server allows the CallOnHold Status to prevail against other occurring DN actions so CallOnHold will propagate to the highest leve(Agent). Another call that arrives for a second DN associated with the same place that CallInbound status will propagate to the highest level as well.
Special Action Types
The means of obtaining actions not normally associated with the DN. Restrospective call related actions Reflecting Regular DNs are a mean of obtaining Action Type normally associated with regular DN.
What are Mediation DN
Queues and Route Points
What actions result from Event Registered
Monitored and WaitForNextCall
Instantaneous Actions
Actions that indicate something has began or ended and the two types are momentary and retrospective action.
What are all the Mediation DNs Actions
NotMonitored, Monitored, AgentActive, AgentLogin, AgentReady, DNActive, DNLogin, DNReady
What are all the Regular DNs Actions
NotMonitored, Monitored, LoggedIn, LoggedOut, WaitForNextCall, NotReadyForNextCall, AfterCallWork, OffHook, OnHook. Mutually exclusive to DN. Some actions for same call can also be mutually exclusive such as CallDialing and CallRinging.
Determining Place and Agent Status when several DN are associated with the same place status?
1) Agent log into extension or position with status higher priority than NotReadyForNextCall. The SS will use status of DN of Position/Extension type in calculating place status.
2) If below NotReadyForNextCall than SS uses status of DN of Position/Extension and other types of DN that Agent are logged in to find the status.
3) If agent are logged into other DN type than SS calculates the status of DNs which agents are logged in to find the status.
4) If no agents logged into DN associated with the place than SS uses status of all DNs to calculate place.
5) If Place disabled than the status is NotMonitored
Monitored Action
Starts with EventRegistered when the Stat Server connects with the T-Server. Not Monitored has to be terminated. The actions ends when NotMonitored action starts.
LoggedIn
Action starts when Start Server detect agent login on DN. Ends when agent logout or NonMonitored.
LoggedOut
Actions starts with EventAgentLogout and ends either with EventAgentLogin or NotMonitored action starts.
Call Consult
The only durable action for call consult that has a momentary action which is CallConsultStarted. Do not form a cluster of logically related action including AfterCallWork.
Group Status Actions
Monitored, NotMonitored, WaitForNextCall, NotReadyForNextCall
Statistics Actions are based on three things
Data about the occurrence of an action, data attached to event starting or during an action. Action duration when applicable.
Action Mutually Exclusivity at a single DN
LoggedIn, LoggedOut, NotMonitored, Monitored, LoggedIn, LoggedOut, WaitForNextCall, NotReadyForNextCall, AfterCallWork, OffHook, OnHook
Some actions for same calls is the same such as CallDialing/CallRinging/Call[CallType]
NotMonitored
Begins when Stat Server recieves EventServerDisconnected/LinkDisconnected/DNOutOfService or link between the T-Server and Stat Server is down. Terminates all other DN Actions. Occurs if Stat Server receives EventOutOfService for a DN and persist until the EventBackIn is received.
Interaction Related Action
Events related to a call and Stat Sever remembers the ConnID of that specific call so it provides a criterion for distinguishing between such actions . Thus more than one call related action of the same kind can occur at the same time on the same DN.
Interaction Related Action for Mediation
(Durable)Call Wait -> (Intial)Call Enterted -> (Restrosepctive)CallDistributed/Abandoned/CallCleared/StuckCallCleared
(Intial)CallTreatmentStarted/NotStarted -> (Restrosepctive)CallTreatmentCompleted
