My organization has found 86 instances in the past 4 months where different conversations include sessions with the same session ID guid. The conversations typically start within a second of one another. Is this expected behavior? When modeling out conversation data, I would expect the guid to be a reasonable primary key for a table that would store session-specific data, and I would like to understand the expected behavior around these guids before I commit to that. Thanks!
Hi Ben,
The session ID is reused when a drag and drop conference is utilized. It is unique per conversation ID, but will be reused in this scenario with another conversation ID.
There may be other situations in which the session ID is reused but I'm not aware of them.
I encountered this issue after writing up a blueprint demonstrating how to design an SQL DB for storing conversation detail data.
I'm thinking this is something different, as the sessions with the same IDs are tied to conversations with the exact same start times, and in at least some of these cases there is no evidence of a drag and drop conference. I will open a customer care case.
FYI, it looks like the examples I was looking at were for a dialer. From Genesys Customer Care:
Depending on the dialing algorithm, the system will batch up several outbound call requests into a single request, as a result we get the same session id. Session Ids are not always unique to a conversation id.
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.