Setting a session timeout for an external community

Setting a session timeout applies to the instant messaging capability only. By default, the session timeout is set on the translation protocol only and disabled at the external community level. Note that setting a community session to timeout may cause instant messaging sessions to expire, terminate, or be lost.

About this task

If the session timeout property is set for a community, the community value takes precedence over the translation protocol value.

You can set a session timeout on communities that use the following translation protocols:
  • SIP for Sametime® Gateway
  • SIP for legacy Sametime Gateway
  • SIP for AOL
  • SIP for Microsoft® Office Collaboration Server (OCS)/Lync Server
The session timeout does not apply to the VP or XMPP translation protocols.
Expected state:
  • Single server: the Sametime Gateway Server is started.
  • Cluster: the deployment manager is started, and the node agent and Sametime Gateway Server are started on at least one node.

Procedure

  1. In the Integrated Solutions Console, click Sametime Gateway > Communities.
  2. Select a community to view the community properties.
  3. Click Custom Properties.
  4. In this is the first time you are setting the session timeout at the community level, click New, otherwise click session_timeout to edit the custom property.
  5. Type session_timeout as the name for the property.
  6. Type an interval, in seconds, in the Value field, for example: 3600.
  7. Click OK, and then Save.
  8. Restart the Sametime Gateway Server. If you have a cluster of Sametime Gateway Servers, restart the cluster.