User:Corinneh/VoiceMCSEventDescriptions - Revision history

WikiSysop at 20:00, April 19, 2022

2022-04-19T20:00:37Z

WikiSysop at 19:45, April 19, 2022

2022-04-19T19:45:34Z

WikiSysop at 19:30, April 19, 2022

2022-04-19T19:30:37Z

WikiSysop at 19:15, April 19, 2022

2022-04-19T19:15:31Z

WikiSysop: Created page with "=Voice Microservices event descriptions= NEED TO SAY SOMETHING ABOUT HOW THE EVENTS ARE GROUPED. ON THE TOPICS PAGE, I HAD THIS STATEMENT (WHICH COULD BE REWORDED HERE):
..."

2022-04-19T19:00:32Z

Created page with "=Voice Microservices event descriptions= NEED TO SAY SOMETHING ABOUT HOW THE EVENTS ARE GROUPED. ON THE TOPICS PAGE, I HAD THIS STATEMENT (WHICH COULD BE REWORDED HERE): ..."

New page

=Voice Microservices event descriptions=
NEED TO SAY SOMETHING ABOUT HOW THE EVENTS ARE GROUPED. ON THE TOPICS PAGE, I HAD THIS STATEMENT (WHICH COULD BE REWORDED HERE): 
The "grouping" attribute used in this documentation is not part of the topic or event structure in any way. Each grouping name is then used as section headings to group together similar events based on the purpose of events and the type of information that they convey.

==Agent state and DN events==
Voice Microservices support the following agent state and DN events.

===EventAgentLogin===
The agent has logged in to the ACD group specified by ThisQueue. Multiple agent logins are allowed for the same DN and agent ID combination (since EventAgentLogin does not indicate by itself a transition of agent state).

{|class="no‐border"
!Event attribute
!Description
|-
|Agent ID
|(optional) This parameter uniquely identifies the ACD agent.

AgentID must be present if the agent is logged in through T-Server or if the information is available.
|-
|CustomerID
|(optional) A pointer to the string containing the assigned Customer (Tenant) identifier through which the processing of the call was initiated. The attribute must be present in every event for a multi-tenant contact center.
|-
|Event
|(mandatory) The event identifier.
|-
|Reasons
|(optional) A pointer to an additional data structure that provides reasons for and results of actions taken by the user of ThisDN. Any Reasons attribute that appears in TEvent is taken directly from the corresponding request. (See ReferenceID in Events That Correspond to Requests.) There is no other source for the information found in the content of the Reasons attribute. That is, no Reasons attribute should be expected for an event that is unsolicited. An event with no reference ID has no identifiable request that prompted it. See Persistent Reasons for more information.

(Switch information of a similar nature to this Genesys Reasons attribute is sometimes available, but those switch reasons are passed in the Extensions attribute.)
|-
|ReferenceID
|(optional) ReferenceID is the identifier generated by T-Library or a TSetReferenceID() function call and attached to the request a client sends to T-Server. Every time a client sends a request to T-Server, it uses the current ReferenceID (increasing it by one each time). In response, T-Server generates an event. Only in the response to the client who initiated the request, as acknowledgment that the request has been fulfilled, the resulting event includes the same ReferenceID that was attached to the request. If the request fails, EventError will be sent only to the requestor.

For additional information, see the ReferenceID in Events That Correspond to Requests table, which lists the events in which you will find the ReferenceID corresponding to that found with the request that prompted its assignment initially.

For a limited number of specific requests, as noted in the ReferenceID in Events That Correspond to Requests table, T-Server may send more than one event with the same ReferenceID.
|-
|Server
|(mandatory) A local server handle to the T-Server in question. In other words, a unique identifier assigned by T-Library to the connection between a client and T-Server.
|-
|ThisDN
|(mandatory) The directory number of the most significant telephony object (except an ACD group or trunk group) with respect to the event in question. The application must be registered to this directory number to receive the event in question.
|-
|ThisQueue
|(optional) The directory number of the most significant ACD group with respect to the event in question.
|-
|time
|(mandatory) The structure specifies event generation time that is expressed in elapsed seconds and microseconds since 00:00 GMT, January 1, 1970 (zero hour). For more information, refer to the type Time in your API reference.
|-
|{{Editgrn_open}}AgentWorkMode{{Editgrn_close}} '''Corinne's Note:''' This was "WorkMode" in the legacy document, but json examples show it as AgentWorkMode for Kafka events. Which should I use for the Kafka event attribute name?
|(optional) This attribute indicates the agent/supervisor-related current work mode.
|-
|Extensions
|(optional) A pointer to an additional data structure that takes into account switch-specific features that cannot be described by the other parameters in an event or a request. Extensions that are specific to particular events are noted with their event information in the T-Library Events section. Some extensions for requests, however, are applicable to all T-Servers, and permit tuning of T-Server operations.

If present, the Extensions attribute can include a ReasonCode value specifically used to communicate hardware reasons.
|}

====Example====
<tt>{ "id": EventAgentLogin, AgentID, ThisDN, AgentWorkMode, Extensions: {}}</tt>

===EventAgentLogout===

{|class="no‐border"
!Event attribute
!Description
|-
|
|
|}

====Example====

@@ Line 4: / Line 4: @@
 ==Agent state and DN events==
-Agent state and DN events use the '''voice-agentstate''' topic.
+Agent state and DN events are stored in the '''voice-agentstate''' topic.
 Voice Microservices support the following agent state and DN events.

@@ Line 13: / Line 13: @@
 {|class="no‐border"
 !Event attribute
-!Description
+!Short description
 |-
 |Agent ID
@@ Line 48: / Line 48: @@
 |-
 |time
-|(mandatory) The structure specifies event generation time that is expressed in elapsed seconds and microseconds since 00:00 GMT, January 1, 1970 (zero hour). For more information, refer to the type Time in your API reference.
+|(mandatory) The structure specifies event generation time that is expressed in elapsed seconds and microseconds since 00:00 GMT, January 1, 1970 (zero hour).
 |-
 |{{Editgrn_open}}AgentWorkMode{{Editgrn_close}} <font color="#B24DE7">'''Corinne's Note:''' This was "WorkMode" in the legacy document, but json examples show it as AgentWorkMode for Kafka events. Which should I use for the Kafka event attribute name?</font>
@@ Line 71: / Line 71: @@
 {|class="no‐border"
 !Event attribute
-!Description
+!Short description
 |-
 |Event
-|(mandatory)
+|(mandatory) The event identifier.
 |-
 |Server
-|(mandatory)
+|(mandatory) A local server handle to the T-Server in question. In other words, a unique identifier assigned by T-Library to the connection between a client and T-Server.
 |-
 |ReferenceID
-|(optional)
+|(optional) ReferenceID is the identifier generated by T-Library or a TSetReferenceID() function call and attached to the request a client sends to T-Server. Every time a client sends a request to T-Server, it uses the current ReferenceID (increasing it by one each time). In response, T-Server generates an event. Only in the response to the client who initiated the request, as acknowledgment that the request has been fulfilled, the resulting event includes the same ReferenceID that was attached to the request. If the request fails, EventError will be sent only to the requestor.
 |-
 |CustomerID
-|(optional)
+|(optional) A pointer to the string containing the assigned Customer (Tenant) identifier through which the processing of the call was initiated. The attribute must be present in every event for a multi-tenant contact center.
 |-
 |AgentID
@@ Line 91: / Line 95: @@
 |-
 |ThisDN
-|(mandatory)
+|(mandatory) The directory number of the most significant telephony object (except an ACD group or trunk group) with respect to the event in question. The application must be registered to this directory number to receive the event in question.
 |-
 |ThisQueue
-|(optional)
+|(optional) The directory number of the most significant ACD group with respect to the event in question.
 |-
 |Reasons
-|(optional)
+|(optional) A pointer to an additional data structure that provides reasons for and results of actions taken by the user of ThisDN. Any Reasons attribute that appears in TEvent is taken directly from the corresponding request. (See ReferenceID in Events That Correspond to Requests.) There is no other source for the information found in the content of the Reasons attribute. That is, no Reasons attribute should be expected for an event that is unsolicited. An event with no reference ID has no identifiable request that prompted it. See <u>Persistent Reasons</u> for more information.
 |-
 | time
-|(mandatory)
+|(mandatory) The structure specifies event generation time that is expressed in elapsed seconds and microseconds since 00:00 GMT, January 1, 1970 (zero hour).
 |-
 | Extensions

@@ Line 1: / Line 1: @@
 =Voice Microservices event descriptions=
-NEED TO SAY SOMETHING ABOUT HOW THE EVENTS ARE GROUPED. ON THE TOPICS PAGE, I HAD THIS STATEMENT (WHICH COULD BE REWORDED HERE):<br/>
+{{Editgrn_open}}NEED TO SAY SOMETHING ABOUT HOW THE EVENTS ARE GROUPED. ON THE TOPICS PAGE, I HAD THIS STATEMENT (WHICH COULD BE REWORDED HERE):{{Editgrn_close}}<br/>
 The "grouping" attribute used in this documentation is not part of the topic or event structure in any way. Each grouping name is then used as section headings to group together similar events based on the purpose of events and the type of information that they convey.
 ==Agent state and DN events==
 Voice Microservices support the following agent state and DN events.
@@ Line 59: / Line 61: @@
 ====Example====
 <tt>{ "id": EventAgentLogin, AgentID, ThisDN, AgentWorkMode, Extensions: {}}</tt>
 ===EventAgentLogout===
 {|class="no‐border"
 !Event attribute
 !Description
 |-
+|Event
+|(mandatory)
 |}
 ====Example====