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.
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:
- Open launcher.xml.
- 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.
Initial data import might fail
Here is the detailed summary regarding the issue: ◾the problem affects FS working in Standalone Operational Mode only. ◾the problem concerns CME data import only (CME after-import dynamic synchronization is not affected). ◾it is an issue for "one tenant - two or more switches" use case only.
The defect can be treated as a known issue for the following scenario/environment: ◾it is about the initial import from CME. ◾is applicable to FS Standalone Operational Mode installation only. ◾is applicable to the "one tenant - two or more switches" use case/scenario/configuration only. The workaround: ◾reassign the DN to the Place in the CME.
(SIPVM-1896)
Dial plan port setting ignored
Feature Server always uses dial plan port 8800, regardless of the value of the option [dialplan]port. The heartbeat returns an error. (SIPVM-1801)
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)
VoIP service DN data not synchronizing
When a VoIP service DN is created under an invalid section name, the SERVICE_DATA does not properly synchronize to the Cassandra database. (SIPVM-1556)
Workaround
Create all VoIP service DNs under a valid section name.
Opt-out prompt playing when not enabled
After being disabled at the switch level, the opt-out prompt is still playing. (SIPVM-1408)
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)