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.
Do not rename switches
Renaming a switch causes Feature Server to treat the switch as a new switch, creating duplicate data in Cassandra. Do not rename any switch.
Device management: Yealink phones
In a Business Continuity environment where one site is inoperative, ACD agents using Yealink phones cannot log in. (SIPVM-3285)
Device management: Agent login
ACD agents cannot effectively log in from multiple devices. The device accepts their credentials, but their only option is to log out. (SIPVM-3267)
Device management: Polycom phones
When Automatic Call Distribution (ACD) is enabled:
- Polycom SoundPoint phones with firmware version 4.1.0 or 4.1.1 become unresponsive on agent login.
- Polycom SoundPoint phones with firmware version 4.0.8 or lower do not display Not Ready reason codes.
- See Supported Hard Phones to determine the best firmware version for your phones.
(SIPVM-3255)
Device management: LDAP
- Genesys and AudioCodes phones: users cannot use the Number Attribute to search LDAP directories. (SIPVM-3218)
- Active Directory (LDAP) is not supported for Yealink Model T-20.
- To use LDAP, Polycom phones with firmware versions below 4.x require an appropriate license.
Notifications: Firefox formatting
Notifications: in the Firefox browser, the email and web message bodies do not retain line breaks. (SIPVM-3001)
Device management: Limited support for firewalls and SBCs
Device management pushes updated configurations to endpoints by sending unsolicited SIP NOTIFY messages directly to each endpoint. If a network device such as a firewall or SBC prevents delivery of the NOTIFY messages, then the configuration update does not occur until each endpoint is manually rebooted or each endpoint runs a scheduled check for a configuration update.
Device management: Firmware upgrades
- In business continuity and multisite deployments, a peer site cannot upgrade the firmware of phones belonging to the original site.
- If Feature Server terminates during a firmware upgrade, and the firmware upgrade completes after Feature Server is running again, the firmware version and upgrade status are not properly updated.
Device management: IVR Provisioning
- In a business continuity deployment, IVR provisioning is unavailable.
- High availability for IVR provisioning is not supported. For example, if Feature Server terminates during IVR provisioning, the administrator must re-provision the phone.
Device management: HTTPS
AudioCodes phones do not require CA certification configuration for Hypertext Transfer Protocol Secure (HTTPS) support.
Device management: Yealink phones
When you disable Call Forwarding using the Feature Server device profile Call Settings, phone users can still forward calls from Yealink phones.
Feature Server and GAX Server synchronization
You must always keep Feature Servers and GAX Servers synchronized within one second.
Keep one Feature Server instance running at all times
To avoid discrepancies between the Cassandra and Configuration Server databases, keep at least one Feature Server with active confSync running at all times.
Upgrade steps
If you are running the Feature Server-based dial plan, to upgrade your environment from 8.1.200.88 to 8.1.201.xx you must take the following actions:
- Run the Voicemail Enabled migration script.
- A user setting of Unconditional Forwarding in 8.1.200 sets an empty value for Forward All Calls To; all calls automatically go to voicemail. You must add the voicemail access number to Forward All Calls To. (SIPVM-2320)
- If the switch-level forwarding options in 8.1.200 were set to Voicemail, after upgrade these values are System (Voicemail). The administrator must set custom values at the switch level for Forwarding On Busy and Forwarding On No Answer, save the values, then reset those values to System (Off). (SIPVM-2315)
Feature Server GAX Plug-in does not support HTTPS
Feature Server GAX Plug-in does not support HTTPS URLs. (SIPVM-2852)
Workaround
Specify only http URLs as values for the fs_urls configuration option.
Multiple data center environment: exception occurs in nodes during startup
During the initial startup of a multiple data center environment, a TokenRangeOfflineException occurs, with a log message "[Voicemail] Failed to read mailbox". The cause is a voicemail-quorum configuration option value of true. (SIPVM-2840)
Workaround
When you first start Feature Server in a multiple data center environment, set the [VoicemailServer]voicemail-quorum configuration option value to false. After startup is complete, reset the value to true.
Master Feature Server can wait indefinitely for other nodes to start
After the master Feature Server starts, it sometimes waits indefinitely in the initializing state, waiting for other nodes to be started so it can retrieve all system data about the Cassandra cluster.
Workaround
If the master Feature Server is waiting at the initializing state, start the other Feature Server nodes in the Cassandra cluster.
Too many non-functioning Cassandra nodes can lead to inconsistent data
In a multi-node environment, if the option voicemail-quorum = true and the number of non-functioning Cassandra nodes is greater than or equal to the calculated quorum value (replication_factor/2 + 1, rounded down), Feature Server may return MWIs with incorrect counts, because not enough nodes are available to apply Cassandra Read /Write Consistency policies.
Workaround
Do not take multiple Feature Server instances offline at one time.
Installation on Windows 2012
Before attempting to install Feature Server under Windows 2012, verify that you have the latest Feature Server 8.1.201.xx installation package (IP) or CD. Open the IP Readme located on your CD or IP. If the Readme does not list Windows 2012 support, then you must obtain the latest Feature Server 8.1.201.xx IP.
Cassandra cluster outages can cause data synchronization issues
If the Cassandra cluster is not operational at all times, data synchronization-related issues in Feature Server instances can occur. (SIPVM-2280)
Forwarding On Busy or No Answer: calls not depositing voicemail to original mailbox
When a user or DN has Forwarding On Busy enabled (On), callers are unable to deposit voicemail into the mailbox of the user or DN they originally called. When Forwarding On Busy or No Answer is set to EXTERNAL_PUBLIC, the call does not return to the original mailbox. (SIPVM-2135)
Non-agents are incorrectly having mailboxes created automatically
In a standalone deployment, non-agents are incorrectly having mailboxes created automatically during initial import and real-time synchronization of data into Cassandra from Configuration Server. (SIPVM-2134)
Calls to agents with multiple mailboxes are sent to the first associated mailbox
When a person is statically associated to two agent logins, each of which has its own mailbox configured, all calls are sent to the first associated Agent Login mailbox. (SIPVM-2124)
Chrome users cannot replay a voicemail without reopening the player
Using Chrome, a user can play a voicemail message only once. Chrome users cannot fast forward or rewind messages. (SIPVM-2119)
Workaround
To replay a message, close and reopen the Chrome player. Fast forward and rewind are unavailable under any circumstances.
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.
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)
TUI: mailboxes are accessible only with mailbox credentials
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)