Status: Accepted
Owner: jean.deruelle
Labels: Type-Defect Priority-Medium Component-Sip-Servlets MSS-1.8.0.FINAL
Roadmap-Fix TelScale-6.1.2.GA
New issue 146 by jean.deruelle: @SipApplicationSessionKey usage can break
replication
http://code.google.com/p/sipservlets/issues/detail?id=146
What steps will reproduce the problem?
1. Deploy ClickToCallDistributable on both nodes
2. Use Converged LB
3. Make HTTP Request
4. REGISTER one SIP Client
5. Access both nodes click to call
What is the expected output? What do you see instead?
Only one node displays the REGISTERed Client instead of both.
It seems that when the SipApplicationSessionKey is used there is first a
unique uuid chosen then the generatedappkey is set which leads to a
different uuid being set thus the app session can't be retrieved from the
replicated store
Please use labels and text to provide additional information.