LST Configuration

To configure the Oracle Communications Unified Session Manager to use LSTs for authentication, you need to create a local subscriber table configuration element that identifies that LST. You then need to set the sip authentication profile configuration to reference that LST configuration so that when messages requiring authentication are received and processed by a sip registrar configuration element, the Oracle Communications Unified Session Manager will use the identified LST for authentication.

In a local subscriber table configuration, you must define an object name, identify the specific LST filename (and path). If the filename is entered without a path, the Oracle Communications Unified Session Manager looks in the default LST directory, which is /code/lst. If the LST file is located elsewhere on the Oracle Communications Unified Session Manager, you must specify the filename and absolute path. For example /code/path/01302012lst.xml.

The corresponding sip authentication profile must be set to use the local subscriber table configuration element you just created. First set credential retrieval method to local, set the digest realm appropriately (this is required for authentication), and finally set the credential retrieval config parameter to the name of the local subscriber table configuration element that you just created. At this point you may save and activate your configuration.

Unencrypted passwords for each user in the table is computed with the MD5 hash function as follows:

MD5(username:digest-realm:password)