| Supported Operating Systems |
Windows XP [SP3] and Windows7 [32 and 64-bit]. Note; users do not need any special permissions to install Unity in Win7. |
| Required Windows Components |
Unity requires .NET framework 4. This is installed as part of the Unity install if required. |
| Minimum System Requirements |
CPU – single core 2Ghz. Ram – 2MB. GPU 256MB onboard RAM. |
| Size & Location |
Unity requires approx 10MB of space on the local machine and will install to C://Program Files/Unity Client by default. |
| Supported BroadWorks Versions |
R14.9 and above. Note: Call Centre stats are only available in Unity Agent, Supervisor and Wallboard on R16 and above. |
| Off-Hook Call Control |
Answering and releasing calls using the call control buttons in Unity will take the endpoint off-hook provided the device supports this. |
| Unity BroadWorks Login |
To login to Unity the user needs their BWKS username and password and the server address of the providers BWKS platform. There is no other account creation needed for IM or other Unity features. |
| Unity License Provision |
Service providers can allocate Unity licences in two ways; either directly on the Kakapo Systems licensing portal, or by integration with their existing provisioning systems. Our licensing server supports XML integration allowing providers to create Unity services that are allocated when the users other BWKS services are assigned within their existing provisioning process. |
| IM Logging |
Kakapo Systems IM server acts as a relay, there is no central record kept of any IM conversations. By default, IM records are kept locally in the "C://Program Files/Unity Client/Instant Message Log" folder. Alternatively, a network location can be specified. |
| IM Encryption |
IM conversations are encrypted using industry standard DES. |
| Busy Lamp Field |
Unity will display either 8 [in Unity Lite] or 20 [in Unity Pro] monitored users. On first use Unity will populate the User Status tab [Busy Lamp Field] with the first 8 or 20 users in the BWKS Group alphabetically. The user can right-click to change the monitored users. These changes are saved in the registry. |
| Group and Enterprise Support |
Unity can be set for Enterprise support. For service providers that create customers as Enterprises, with Groups under that, there is a setting in the Kakapo licensing portal that allows users visibility across the Enterprise. |
| Unity Signalling |
Unity sends CAP commands directly to the BWKS OCI for call control and presence information. |
| Citrix/Terminal Services |
Unity will work in a terminal services environment. |
| LDAP & SQL |
Unity integrates with LDAP and SQL through a wizard. |
