Print

Configuring SMS settings

Procedure

  1. Log in to the AE Services Management Console with System Administrator privileges.
  2. From the AE Services Management Console main menu, select AE Services > SMS > SMS Properties.
  3. Complete the SMS Properties page.

    The following list describes the SMS configuration settings and provides some guidelines for configuring SMS.

    • Default CM Host Address — If you administer a Communication Manager Host Address, SMS will attempt to connect to this Communication Manager host address, as long as no host address is explicitly specified in the authorization header of a client request. If this field is blank, all SMS requests must explicitly include the target Communication Manager host address.

    • Default CM Admin Port — By default the System Management Service will use 5022 to connect to a Communication Manager server. The Default Communication Manager Admin Port is a default setting that can be overridden at any time by an SMS request. If you manually administer a port number, make sure that there are no conflicts with other ports

    • CM Connection Protocol — The Communication Manager Connection Protocol setting and the Default Communication Manager Admin Port are interdependent.

      noteNote

      If you change the CM Connection Protocol, you may need to change the Default CM Admin Port. The default TUI (or SAT) ports on Communication Manager are as follows:

      SSH Port=5022

      Telnet Port=5023

    • SMS Logging — Use the default setting Normal unless you are debugging. Changing this setting to Verbose could result in a high volume of read and write operations.

    • SMS Log Destination — Use the default apache, unless you are debugging. The syslog setting is for debugging only.

    • CM Proxy Trace Logging — Use the default None, unless you are debugging. The Normal and Verbose settings are for debugging only.

    • Proxy Log Destination — Use the default destination /var/log/avaya/aes/ossicm.log for the CM Proxy Trace logs on the AE Server.

    • Max Sessions per CM — This is a safety setting that prevents SMS from consuming all of the TUI processes on Communication Manager. By default the setting is 5. You can specify from 1 to 5 sessions. The maximum number of sessions that SMS allows open on a single Communication Manager is 5 .

    • Proxy Shutdown Timer(s) — Use the default 1800 seconds, unless you are developing an SMS application that requires modifying this setting.

    • SAT Login Keepalive(s) — Use the default 180 seconds, unless you are developing an SMS application that requires modifying this setting.

    • CM Terminal Type — Use the default OSSIZ, unless you have the need to remove punctuation from extensions on list operations or security requirements. This setting allows for the ossicm proxy to change its default terminal type. Select from the following options:

      • OSSIZ (the default). Any customer-related superuser login to CM will be able to read as well as write station security codes.

      • OSSI3. Only the “init” user can read station security codes.

      • OSSIE. Exactly the same as OSSIZ except extension numbers do not contain punctuation.