Revision as of 06:49, December 15, 2016 by Sschlich (talk | contribs) (→‎SIP Feature Server 8.1.2 known issues and recommendations)
Jump to: navigation, search

Known issues and recommendations

SIP Feature Server 8.1.2 known issues and recommendations

This document includes SIP Feature Server issues and recommendations applicable to the 8.1.2 release.

The setup for Feature Server version 8.1.201.87 for Windows does not recognize the previous FS version, and as a result, the maintenance update does not occur. Genesys recommends that you install version 8.1.201.88 to correct—or to avoid—this limitation. Use the following procedure to upgrade to/from version 8.1.201.87.

Note: The Windows setup for version 8.1.201.88 will recognize old versions except 8.1.201.87.

  1. Back up the cassandra_home directory, including the /etc subdirectory.
  2. Check the cassandra_home parameter in launcher.xml at the current location. STEVE ASKS: What am I checking?
    Note: The "current location" is the location of the previously installed version that you are replacing.
  3. Run Setup.exe from the 8.1.201.88 IP (the new version that you are installing).
    1. When prompted, enter the Configuration Server host/port and user name/password.
    2. Select the Feature Server Application object to be upgraded.
    3. When prompted, enter a new location that is different from the current location.
    4. Type the Cassandra path as it is specified in the cassandra_home parameter of the current launcher.xml.
  4. Restore/replace the files located in the cassandra_home\etc directories that you backed up in step 1.
  5. Copy the launcher.xml file from its current location to the new location.
  6. Copy the /resources directory from its current location to the new location.
  7. Copy the keystore file from the current FS\etc directory to the new FS\etc directory.
  8. In the new deployment, verify that…
    1. The Feature Server application object has its new version and working directory.
    2. Launcher.xml contains the cassandra_home parameter.
    3. The file \cassandra_home\etc\cassandra.yaml has the same entries as before. Verify by comparing the new cassandra.yaml to the backed-up version.
    4. The cassandra-topology.properties file is in the new \resources directory—if the NetworkTopology strategy is being used.
    5. The SSL parameters must be configured as described on the Start SIP Server page, under the heading Jetty 9 configuration.
  9. Stop Feature Server from Solution Control Interface (SCI) or Genesys Administrator (GA).
  10. Start Feature Server from SCI or GA.

(SIPVM-4259)

Important upgrade step

If you are upgrading from a restricted release of SIP Feature Server 8.1.2 (any version prior to 8.1.200.83), you must manually restore the vms_host parameter, as follows:

  1. Open launcher.xml.
  2. In the vms_host section, in the line <format type="string" default="localhost" />, replace "localhost" with "0.0.0.0" or a specific IP address to restrict Feature Server web application access to that address.

If you are doing a fresh installation or upgrading from 8.1.200.83 or later, you can omit this step.

User-Device association might fail during initial data import

User-Device association (static) during initial data import from the Configuration Layer might fail if Feature Server runs in standalone mode in a multi-site environment within the same Tenant. This issue does not apply to post-import dynamic data synchronization. (SIPVM-1896)

Workaround

Reassign DNs to their respective Places.

Use IP addresses

Use IP Address or local host name, not FQDN, to access the Web application. FQDNs can cause unexpected logouts.

Group Mailbox Administrator privileges

Only users with the Group Mailbox Administrator role can use the web application or TUI to upload or change greetings and passwords.

RequestPrivateService MWI notification generated with incorrect values

In a multi-site environment, RequestPrivateService MWI notification for deposit and retrieval calls is intermittently generated with incorrect values. (SIPVM-1757)

Users unable to override default Forward on no answer setting

If Forward on no answer is set to default (disabled) and the user disables call waiting, after a timeout, calls unexpectedly follow Forward on busy (if existing and activated), or are sent to voicemail (if voicemail is enabled) or rejected (if voicemail is disabled), in that order. (SIPVM-1736)

When the network is disabled on the host on which Feature Server is running, Windows may terminate unexpectedly

Windows may terminate unexpectedly if the host on which Feature Server is running is removed from the network by clicking Disable from the Windows Local Area Connection dialog box. (SIPVM-1333)

Workaround

Stop Feature Server before disconnecting the network.

Message priority is not being considered during retrieval

The message priority selected during a call deposit is not taken into consideration during voicemail retrieval. (SIPVM-1248)

In the Telephone User Interface (TUI), User and Group mailboxes can be accessed only with mailbox credentials (mailbox number). DN, agent, and user credentials to access mailboxes is not supported. (SIPVM-859)

Comments or questions about this documentation? Contact us for support!