srf listen session stickiness

[hadar-laguna]

Are invites that come through a request handler and go to a load balancer with N drachtio applications in kubernetes that use sip.listen sticky to that same pod that got the initial invite?

I need to retain the session because im basing myself on reInvites by the initial requester and bye from the initial requester, but it seems that the end call (bye) is arriving to a different pod.