i'm using the Java SDK subscribe for "v2.routing.queues." + queueId + ".conversations.calls";
I subscribed for two queues. each topic have a dedicated NotificationListener, (two listeners).
When an agent transfer the call from 1st queue to 2nd queue. I still received events of the conversation on the first Notification Listener.
is this work as designed ? if it is, then if a call transfer multiple times cross 4 queues, that means all the previous queue Notification listener will continue receives events of the call.
Yes, this works as designed.
The conversation notification topics on queues ("v2.routing.queues.{id}.conversations") work differently from the conversation notification on users ("v2.users.{id}.conversations").
With queues topics, you will start receiving notifications on a conversation as soon as the queue is added as a participant of this conversation.
And you will continue to receive notifications about this conversation until it is fully terminated/ended - even after the conversation has "left" the queue (ex: when the conversation is connected to an agent, and the customer chats with the agent).
If you are only interested in the notifications related to a call which is still in queue, you will have to parse the notifications you receive and check if the queue participant session still appears as connected (and ignore the other notifications).