Lotus Sametime Unified Telephony allows the usage of connection-less protocols (such as UDP, User Datagram Protocol) as well as connection-oriented protocols (such as TCP).
When UDP transport is used for remote users connecting to the Lotus Sametime Unified Telephony via a central SBC (Session Border Controller), there are no provisioning considerations due to the SBC. The remote users are provisioned at Lotus Sametime Unified Telephony as if they were local users.
When TCP or TLS (Transport Layer Security) transport is used for remote users connecting to the Lotus Sametime Unified Telephony via a central SBC, an EP (Endpoint) should be created. This allows a single TCP/TLS connection to be used between the SBC (Session Border Controller) and Lotus Sametime Unified Telephony for all remote user SIP signaling traffic.
Create the EP as a statically registered EP with the IP address/port of the interface created on the core side of the SBC for remote users connecting to the Lotus Sametime Unified Voice. The alias name of the endpoint should also be the IP address of the interface created on the core side of the SBC.
Ensure that Registration Randomization is enabled in Lotus Sametime Unified Telephony.
The following EP attributes must also be set:
SIP ProxyParent topic: SBC (Session Border Controller)
Route via Proxy
RTP (Real-time Transport Protocol) configuration parameter (Srx/Sip/EnableProxyRegistration must be set to a value of true).