I am currently investigating why this "would" happen. I am experiencing what I 
described above, its TLDR is "UA2 is getting invites that were destined to UA1" 
and they both were using the same port at a given time. 

Applying a patch for this is rather easy and has already been done. However, I 
am intrigued on why this happened and if there's something else that could be 
failing. Also, if this is still happening (it's hard to catch) then there is 
some processing taking place because of that "patch" that maybe we could get 
rid of. 

When the port is recycled, the mapping for the URI that was associated with 
that port is also cleared? (The AoR of the WS connection I mean)
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

Reply via email to