Creating the anonymous_users_tokens objects cache instance

Create an Anonymous_users_tokens object cache instance to allow IBM Sametime® clients to register with the Sametime SIP Proxy/Registrar server. Failure to create the Anonymous_users_tokens object cache instance generates the following message: Unable to read data from SIP registrar, check error logs for more details.

About this task

This procedure updates the resources-pme502.xml file in the following locations:
  • Stand-alone server - install_root\IBM\WebSphere\AppServer\profiles\PROFILE_NAME\config\cells\Sametime System Console cell\nodes\NODE_NAME\servers\STMediaServer
  • Clustered servers - install_root\IBM\WebSphere\AppServer\profiles\PROFILE_NAME\config\cells\Sametime System Console Cell\clusters\Proxy/Registrar cluster name\

Procedure

  1. Log in to the IBM® WebSphere® Integrated Solutions Console as the WebSphere administrator.
  2. Click Resources > Cache Instances > Object Cache Instances.
  3. Click the Scopes field.
  4. Change the scope to the scope of the SIP Proxy/Registrar server:

    Node=Proxy/Registrar, Server or Cluster=STAVSIPPR-Cluster

    Where STAVSIPPR-Cluster is the name of the SIP Proxy/Registrar server or cluster.

  5. Verify whether an anonymous_users_tokens object cache instance has been created.
    1. If the anonymous_users_tokens object cache instance has been created, click Cancel to exit.
    2. If there is no anonymous_users_tokens created for the object cache instance, click New and complete the following steps:
      1. In the Names field, enter anonymous_users_tokens.
      2. In the JNDI field, enter services/cache/anon_user_tokens
      3. In the Cache size field, enter 20000.
      4. Remove the check mark from the field Dependency ID Support.
      5. Click Apply and then click OK.
      6. Save the change to the master configuration by clicking the Save link in the "Messages" box at the beginning of the page.
      7. Resynchronize the nodes by clicking System administration > Nodes, selecting all of the nodes, and then clicking Full Resynchronize.
      8. Restart the Sametime SIP Proxy/Registrar servers, or if the servers are clusters, restart the Proxy/Registrar nodes and the WebSphere SIP proxy servers.