Before Lotus Sametime Unified Telephony starts a new SIP call, it reads information about the existing TLS connection between Lotus Sametime Unified Telephony and applicable SIP phones from the database; it then uses this information for the duration of the call.
If this connection information changes during the call such that the phone creates a new TLS connection on the other node after a communication failure, mid-call events as well as the final BYE messages will fail. This shortcoming will be addressed in a future release.
The following are examples of mid-call events:
Lotus Sametime Unified Telephony-initiated session timing (which can cause a stable call to fail)Parent topic: Cluster Redundancy
Putting a call on hold
Starting a three-way conference
BYE message (which ensures an accurate CDR record)