Handling user data

From Genesys Documentation
Jump to: navigation, search
This topic is part of the manual Voice Microservices Events and Models Reference for version Current of Voice Microservices.

Learn how user data is handled in Voice Microservices.

Voice Microservices support the scenarios described on this page. User data events are not produced to Kafka. User data attached to a call is available in call-related events.

Attaching or updating user data to internal call

The following diagram and table describe attaching/updating user data to an internal call.

For simplicity, the following example uses ConnID 1, however – in actual events – the ConnID displays as <ConnID>@<metainformation>.

Voicemcs events handling user data in internal call.png

Party A Party B
Call-establishing phase (ConnID 1)
Attach user data to a call (TUpdateUserData)
EventAttachedDataChanged:

ConnID 1
ThisDN A
ThirdPartyDN A

EventAttachedDataChanged:

ConnID 1
ThisDN B
ThirdPartyDN A

Release phase (ConnID 1)

Attaching or updating user data to call by third party

The following diagram and table describe attaching/updating user data to a call by a third party.

For simplicity, the following example uses ConnID 1, however – in actual events – the ConnID displays as <ConnID>@<metainformation>.

Voicemcs events handling user data by third party.png

Party A Party B Party C
Call-establishing phase (ConnID 1)
Attach user data to a call (TUpdateUserData)
EventAttachedDataChanged:

ConnID 1
ThisDN A
ThirdPartyDN C

EventAttachedDataChanged:

ConnID 1
ThisDN B
ThirdPartyDN C

EventAttachedDataChanged:

ConnID 1
ThirdPartyDN C

Release phase (ConnID 1)
Comments or questions about this documentation? Contact us for support!