InfinityOne - Known Issues
Known Issues identified in Release 3.0
The following are issues that have been identified in Release 3.0:
- The url used for initial login on an iOS device must match the Site URL Host Name settings in the InfinityOne Administration / General / Network settings including the use of upper and lower case characters otherwise push notifications will fail. Recommended practice is to always use lower case characters.
- Logging out of an Android device by selecting "Logout from servername" in the Settings then reconnecting the same device to the same server will result in no speech path for all subsequent calls for that client until the InfinityOne server is restarted. If Android users wish to avoid receiving calls during off-hours, the could activate the Make Set Busy / Do Not Disturb feature by pressing the DND softkey, a regular key programmed for Make Set Busy, the Feature Key followed by 8 5, or by dialing * 7 8,
Known Issues identified in Release 2.0
The following are issues that have been identified in Release 2.0:
- The Android client (when released) will require the Android 9 operating system in order to receive notifications when the app is not open and/or the screen is locked. Android 9 introduced the required messaging as part of the Notification Toolkit. Earlier versions of the Android operating system may allow the InfinityOne app to run, but the app will required to be open and active to receive notifications.
Addressing Known Issues from Release 1.0
Release 1 of InfinityOne documented the following as "known issues". Please refer to the Status entry after each "known issue" to understand how it is addressed.
- A user may only be logged in one device. Logging in on a second device will log out the other device.
- Some limited actions can cause the page to reload which will drop any active calls.
- Only Google Chrome and Chrome Canary browsers are supported.
- The InfinityOne Softphone is not yet supported on mobile devices, but the chat part of the app should work reasonably.
- Video calls are not yet supported. Do NOT enable the feature in Administration -> WebRTC