Download 5.0.3.0 Companion Release Notes

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

SIP extensions for the IP Multimedia Subsystem wikipedia , lookup

Remote Desktop Services wikipedia , lookup

Transcript
Release Notes for
CompanionTM
Version 5.0.3.0
Prepared by:
Alan Himes
Compunetix, Inc.
Video Systems Division
2420 Mosside Boulevard
Monroeville, PA 15146
October 1, 2014
Compunetix Document Number: 05-CPN-RN-5030 00
05-CPN-RN-5030 00
Confidential
October 1, 2014
PROPRIETARY INFORMATION
©Compunetix, Inc. 2014 All Rights Reserved
This document and the data included in this document is proprietary to
Compunetix, Inc. and is not to be reproduced, used, or disclosed in whole or in
part to anyone without the express written permission of
Compunetix, Inc. The content of this document is provided for informational use
only and is subject to change without notice.
Questions about this document or the features it describes should be directed to:
Compunetix, Inc.
Video Systems Division
2420 Mosside Boulevard
Monroeville, PA 15146
2
Compunetix Document 05-CPN-RN-5030 00
Confidential
05-CPN-RN-5030 00
Confidential
October 1, 2014
Table of Contents
Table of Contents .......................................................................................................................................... 3
Related Documents ....................................................................................................................................... 6
1
Introduction ...................................................................................................................................... 7
1.1
Package Release Summary ........................................................................................................ 7
1.2
System Requirements ................................................................................................................ 7
1.3
Version Compatibility ............................................................................................................... 8
2
What’s New in This Version.......................................................................................................... 10
3
Issues Fixed or Improved in this Release....................................................................................... 11
3.1
Unicode Support for Hardware Devices.................................................................................. 11
3.2
Camera Description with Japanese Characters........................................................................ 11
3.3
Enhanced Firewall Traversal Server ....................................................................................... 11
3.4
Hang on Shutdown .................................................................................................................. 11
3.5
Translation Matrix ................................................................................................................... 11
3.6
Stability Fixes for the Session Border Controller.................................................................... 11
3.7
Fixed Video Resolution Interpolation ..................................................................................... 11
3.8
Unicode transcode Error .......................................................................................................... 12
3.9
“My View” not Working Consistently .................................................................................... 12
4
Operational Consideration ............................................................................................................. 13
4.1
Configuration of EVERGREEN in Multi Network configuration .......................................... 13
4.2
Companion running on a multi-NIC PC .................................................................................. 13
4.3
Installation/Upgrade Instructions ............................................................................................ 13
4.4
Webcam and Audio Drivers .................................................................................................... 13
4.5
Headset recommended ............................................................................................................ 14
4.6
Companion will connect asymmetrically ................................................................................ 14
4.7
Inactive conferences ................................................................................................................ 14
4.8
Contact window....................................................................................................................... 15
4.9
Status not updating in contact window.................................................................................... 15
4.10
Companion.exe might not terminate on abnormal exit ........................................................... 15
4.11
Conference Auto Erase ............................................................................................................ 15
3
Compunetix Document 05-CPN-RN-5030 00
Confidential
05-CPN-RN-5030 00
Confidential
October 1, 2014
4.12
Public Network Bandwidth ..................................................................................................... 15
4.13
H.323 Application Layer Gateway .......................................................................................... 15
4.14
EVERGREEN 4.0.0.0 ............................................................................................................. 16
5
Known Issues in this Release ......................................................................................................... 17
5.1
Echo Canceling........................................................................................................................ 17
5.2
Connection failure ................................................................................................................... 17
5.3
Incorrect endpoint state ........................................................................................................... 17
5.4
Companion decoder freezing ................................................................................................... 17
5.5
The GNUGK causing severe packet loss ................................................................................ 17
5.6
Companion will sometimes fail to close down correctly ........................................................ 18
5.7
Microsoft Visual C++ 2008 SP1 Redistributable .................................................................... 18
5.8
Incorrect status if multiple instances of a contact exists on a system...................................... 18
5.9
Companion fails to remove from Contacts .............................................................................. 18
5.10
Java had to close dialog box after installation ......................................................................... 18
5.11
The help screens option is disabled ......................................................................................... 18
5.12
Stale video between connections ............................................................................................. 18
5.13
Companion exceeds maximum allowable bitrate .................................................................... 19
6
How to Obtain Compunetix Assistance ......................................................................................... 20
6.1
Email ....................................................................................................................................... 20
6.2
Telephone ................................................................................................................................ 20
6.3
Fax ........................................................................................................................................... 20
7
Appendix: Known Companion-compatible cameras ..................................................................... 20
7.1
Logitech B910 HD .................................................................................................................. 20
7.2
Logitech B525 HD .................................................................................................................. 20
7.3
Logitech QuickCam Ultra Vision ............................................................................................ 20
7.4
Logitech QuickCam Pro 9000 ................................................................................................. 20
7.5
Logitech QuickCam Pro 4000 ................................................................................................. 20
7.6
Dynex DX-WEB1C (1.3MP Webcam) ................................................................................... 20
7.7
Envision VCAM-II .................................................................................................................. 20
8
Appendix: MCU Configurations................................................................................................... 21
8.1
No EVERGREEN control ....................................................................................................... 21
4
Compunetix Document 05-CPN-RN-5030 00
Confidential
05-CPN-RN-5030 00
8.2
Confidential
October 1, 2014
Minimum required EVERGREEN permissions for full functionality of Companion. ........... 22
5
Compunetix Document 05-CPN-RN-5030 00
Confidential
05-CPN-RN-5030 00
Confidential
October 1, 2014
Related Documents
The following documents contain further information regarding use of the EVERGREEN™
system.
Note: Some documents may not be updated for this release.
6

Companion User Guide 05-CPN-UMCPN-5000

xWOC User Guide 05-EVG-UMWOC-3400

xOC User Guide 05-EVG-UMXOC-3400

xWMC User Guide 05-EVG-UMXWMC-3400

Session Border Controller Installation Guide 05-CPN-SBCIG-5030
Compunetix Document 05-CPN-RN-5030 00
Confidential
05-CPN-RN-5030 00
Confidential
October 1, 2014
1 Introduction
This document describes the latest software release for Companion. Companion is an H.323 PC
based video terminal.
This document describes all modifications since version 5.0.1.0.
1.1
Package Release Summary
Companion 5.0.3.0 includes only bug fixes.
1.2
System Requirements
The current version of Companion runs only on the Windows platform. Below is a summary of
the requirements:

Operating System: Windows® XP or Windows® 7 (32 and 64-bit)

1 GB RAM memory

250 MB free hard disk space (125 reclaimed after installation)

Pentium IV 3GHZ processor or equivalent (CIF only)

Intel I5 2.67GHZ or equivalent (HD)

Java JRE 1.6 (32-bit) or 1.7 (32-bit). 64-bit Java will not allow some of the drivers to
load, so cannot be used at this time

Microsoft® Visual C++ 2008 Redistributable*

Webcam (Windows® XP or 7 compatible)

Most current drivers for webcam and soundcard are recommended
*The installer for Companion contains the Microsoft Visual C++ 2008 Redistributable. If
it is not installed on the PC, the installer will prompt the user to do so.
7
Compunetix Document 05-CPN-RN-5030 00
Confidential
Confidential
05-CPN-RN-5030 00
1.3
October 1, 2014
Version Compatibility
Companion 5.0.3.0 is incompatible with all 64-bit versions of Java. However, it is fine running on
64-bit PCs.
Although Companion 5.0.3.0 is H.323 compliant, it is designed to connect only with the
EVERGREEN MCU. The full features are available based on the following table. However,
Companion 5.0.3.0 is generally backwards compatible with all EVERGREEN versions between
EVERGREEN 3.0.0.0 to 4.0.0.0. Please review the compatibility table below:
EVERGREEN and Companion 5.0.3.0 Compatibility
EG
Release
Primary
Video
MCU
Control
H.239
Requires
Service
4.0.0.0
✓
✓
✓
✓
3.5.0.0
✓
✓
✓
X
3.4.1.3
✓
✓
✓
X
3.4.1.1
✓
✓
✓
X
3.4.1.0
✓
✓
✓
X
3.4.0.11
✓
✓
✓
X
3.4.0.10
✓
✓
✓
X
3.4.0.8
✓
✓
✓
X
3.4.0.6
✓
✓
✓
X
3.4.0.0
✓
✓
✓
X
3.1.5.1
✓
✓
✓
X
3.3.5.0
✓
✓
✓
X
3.3.0.3
✓
✓
✓
X
3.3.0.2
✓
✓
✓
X
3.3.0.1
✓
✓
✓
X
3.3.0.0
✓
✓
X
X
Prior to EVERGREEN release 3.0.0.0, the EVERGREEN xPM will not allow a login because of
8
Compunetix Document 05-CPN-RN-5030 00
Confidential
05-CPN-RN-5030 00
Confidential
October 1, 2014
a compatibility issues. An upgrade to version EVERGREEN 4.0.0.0 is highly recommended if
you wish to use this release of Companion.
Starting with EVERGREEN 4.0.0.0, Companion will require an attended or unattended service
on EVERGREEN to be able to dial into it. This is an added security feature for EVERGREEN to
prevent unexpected incoming calls. If both services are allowed for a given login, then users will
be required to pick the appropriate service (IP Address) when they login. Companion will
remember this choice for each subsequent login. The user can change the network later if they
wish, under settings. Companion will only remember one setting. If the MCU services change or
the user logs into a different MCU, then they will be prompted again, and the new settings will
overwrite the old.
Compatibility with future EVERGREEN releases will be maintained to the greatest possible
degree. However, compatibility with all future EVERGREEN releases cannot be guaranteed.
9
Compunetix Document 05-CPN-RN-5030 00
Confidential
05-CPN-RN-5030 00
Confidential
2 What’s New in This Version
This section lists the new features available in this release.
N/A
10
Compunetix Document 05-CPN-RN-5030 00
Confidential
October 1, 2014
05-CPN-RN-5030 00
Confidential
October 1, 2014
3 Issues Fixed or Improved in this Release
This section describes the issues that have been fixed or improved since the 5.0.1.0 software
release.
3.1
Unicode Support for Hardware Devices
Problems with microphone volume control were reported with Companion 5.0.1.0. There were a
few problems reported, but they all were a result of problems with Companion interacting with
Windows DirectShow.
Windows returned strings in two different formats depending on the device drivers and what
native language version of windows. These problems have been addressed, but not all languages
were tested with Companion 5.0.3.0, so lingering problems may exist.
3.2
Camera Description with Japanese Characters
Problems reported with Companion when the camera device name has Japanese Characters have
been fixed.
3.3
Enhanced Firewall Traversal Server
Available in this release is an upgraded Firewall Traversal Server. The previous server did not
allow for very many concurrent connections.
The upgraded server requires a Linux PC and a special Network Interface Card.
The server will be released as a third party software package for Companion and will have an
installation guide. Please see the Session Border Controller Installation Guide for more details.
3.4
Hang on Shutdown
Occasionally, Companion would freeze as it was shutting down. This was rarely seen, but could
be observed when using a Logitech 4000 camera on a PC running Windows XP. Companion was
unable to disengage the camera every time, due to a timing issue. Companion will now wait for
the camera shutdown before continuing to close itself down.
3.5
Translation Matrix
Companion’s translation matrix is being updated so that all of the internationalization works as
expected. The matrix documents are still being revised, but will be available soon.
3.6
Stability Fixes for the Session Border Controller
Some unhandled fault exceptions were addressed in the GNU 3.6 Session Boarder Controller.
3.7
Fixed Video Resolution Interpolation
Occasionally Companion would treat an XGA video resolution as 4CIF due to a calculation error.
This error was corrected.
11
Compunetix Document 05-CPN-RN-5030 00
Confidential
05-CPN-RN-5030 00
3.8
Confidential
October 1, 2014
Unicode Transcode Error
When the terminal name uses Unicode characters, Companion was not correctly formatting the
name before adding it to the EVERGREEN contact directory. As a result, the contact directory
would show “???” instead of the terminal name. This problem was corrected.
3.9
“My View” not Working Consistently
My View in Companion allows Companion to have a unique continuous presence layout. This is
a view of the conference only seen by the Companion user. This feature was previously not
working, but has been fixed.
12
Compunetix Document 05-CPN-RN-5030 00
Confidential
05-CPN-RN-5030 00
Confidential
October 1, 2014
4 Operational Consideration
4.1
Configuration of EVERGREEN in Multi Network configuration
For Companion to operate correctly on an EVERGREEN in a multi-network environment, it is
mandatory to configure the user roles and the partition parameters carefully. Please reference the
Companion User’s Manual for details on how the roles must be configured.
Users of Companion will need to understand from the EVERGREEN System Administrators,
which network needs to be used, based on Companions location in the network topography.
4.2
Companion running on a multi-NIC PC
If Companion is launched on a PC that has more than one viable Network Interface Card, then the
user will be prompted as to which IP address to use for Companion. The user must understand
which NIC is the correct one to use otherwise the connection will fail. The correct NIC will be
the one with access to the EVERGREEN MCU.
Once a network is selected, it cannot be changed without restarting Companion. This is true even
if the network originally selected become unavailable.
Laptop users need to be especially cognizant of this.
4.3
Installation/Upgrade Instructions
Administrator rights on the PC are required to install Companion; user rights are sufficient to run
it.
An administrator account is also required to uninstall an existing version of Companion.
To install Companion, one must simply double click setup.exe located in the setup or setup+JRE7
folder while logged in as an administrator on the PC. The installer will automatically adjust the
permissions of Companion so that any level of user for the PC can use it.
If a user has a Companion installed that predates Companion 3.0.0.0, please manually uninstall
Companion from the control panel, before installing Companion 4.0.0.0. If a problem persists
after installing, manually uninstall Companion, and delete the Companion folder located under
Compunetix in the Program Files (x86) folder.
4.4
Webcam and Audio Drivers
It is required that users obtain and install the latest webcam and audio drivers prior to installing
the Companion application. Go to the device manufacturer’s website to obtain the latest drivers.
Without the latest drivers, the webcam may not be recognized and the microphone audio may be
distorted. Generally, this is more commonly seen with laptops that have integrated webcams.
Additionally, the webcam software should be run at least one time to ensure that the camera is
operational. Some manufacturers of webcams do not fully install all of the drivers until the
camera has been operated with its native software at least one time.
13
Compunetix Document 05-CPN-RN-5030 00
Confidential
05-CPN-RN-5030 00
4.5
Confidential
October 1, 2014
Headset recommended
With the addition of echo cancellation (AEC) on Companion, the need for a head set is reduced.
However, using a headset is still recommended as the easiest way to prevent echo in the
conference.
4.6
Companion will connect asymmetrically
An asymmetrical connection will be established between Companion and EVERGREEN if so
negotiated.
4.7
Inactive conferences
Inactive conferences are Stored Conferences that have been preconfigured for Companion users.
These conferences need to have both a Host and a Guest passcode. The characteristics of the
conference are determined according to how the Stored Conference is setup.
The ability to activate a Stored Conference and stay connected to the conference is determined by
how the conference is configured. When configuring a Stored Conference, the user should
consider the following:
14

Companion cannot initiate the action to join a Stored Conference if the conference has
not been assigned a host and guest passcode. In all cases, a host and guest passcode are
required. However, a Stored Conference can be configured to dial out to a Companion
user, even if it does not have a passcode.

Companion can activate a Stored Conference in any of five different ways.
o
Double-click an Inactive Conference in the Conference Window. Companion
will attempt to activate the conference using a Host passcode. As the initiator of
the conference, Companion is expected to be the Host. If there is a Host
passcode, the activation will be successful. If there is no Host passcode, then the
conference will not launch. The user will be warned that no Host passcode exists.
o
Right-click an Inactive Conference and select “Join as Host.” This behaves the
same as double-clicking an inactive conference.
o
Right-click an Inactive Conference and Select “Join as Guest.” If there is a
Guest passcode, the conference will activate. The behavior of the conference will
depend on its configuration. Either based on the duration, Auto Breakdown
setting, and the Host action, the Guest Companion will be allowed to hold the
conference open as active, or it will be disconnected.
o
Right-click an Inactive Conference and Select “Activate.” This will activate the
Stored Conference. The Stored Conference will now show up as an Active
Conference indicated by the Conference name being green in the Conferences
pane.
o
Enter the Host or Guest passcode of the Stored Conference in the Conference
Passcode input box and press Connect. This will activate and connect Companion
to the conference as Host or Guest depending on the passcode used.
Compunetix Document 05-CPN-RN-5030 00
Confidential
05-CPN-RN-5030 00
4.8
Confidential
October 1, 2014
Contact window
Contacts in the Contact window are uniquely identified based on their E.164 alias. However, this
alias is not 100% guaranteed to be unique. If it is not, then they will also be shown as having the
same status.
4.9
Status not updating in contact window
When a Companion user double-clicks their own entry in the Contact Directory, the connection
progress will show, and the final connection displayed, but it will subsequently be removed. This
is expected behavior. By double clicking yourself in the contact directory, you are directing the
MCU to dial out to the same Companion, that you initiated a dial in. When the EVERGREEN
fails to connect what is essentially a busy terminal, it will return to disconnected. The effect is
that the connected status will be removed.
4.10 Companion.exe might not terminate on abnormal exit
If Companion terminates abnormally, the Companion.exe will sometimes remain running in the
background, even though there is no visible sign of it running. In this case, Companion will
appear in the task manager. The user should select the Companion.exe and end process.
4.11 Conference Auto Erase
When Companion creates a conference by double clicking a contact or an inactive conference, the
conference will erase when Companion disconnects.
However, if a stored conference is activated, then Companion joins via the “connect as host” or
“connect as guest” options, the EVERGREEN setting for handling “no host action” will enforce
the behavior. The same behavior will occur when creating a conference, then joining it after it is
running.
4.12 Public Network Bandwidth
Some public networks such as ones at a hotel, or coffee shop have limited bandwidth. When
using Companion on these types of networks it is necessary to set the maximum bitrate in the
settings to a level that the network will allow. Trying to connect at a higher bitrate than what a
network allows will make the media playback to stutter. In extreme situations, this may even
cause no media to be transferred at all. Because of this, it is recommended to use a low bitrate
such as 384. This can be set in the Connection Settings tab of the Settings Window.
4.13 H.323 Application Layer Gateway
An H.323 Application Layer Gateway is a network component that is designed to manage the
H.323 protocol over a firewall and NAT. The H.323 ALG is normally used to allow endpoints
behind a firewall or NAT to receive media when communicating with other endpoints outside of
the firewall or NAT. Some H.323 ALG gateways do not understand the H.460 protocol and will
interfere with how the H.460 protocol works. This could result in behavior such as H.460 calls
not being completed, or scenarios where Companion will not be notified of an incoming call for a
15
Compunetix Document 05-CPN-RN-5030 00
Confidential
05-CPN-RN-5030 00
Confidential
October 1, 2014
short time after Companion disconnects from another call.
4.14 EVERGREEN 4.0.0.0
Starting with EVERGREEN 4.0.0.0 Companion users will require the See Call Service
permission to be able to dial into the EVERGREEN. This change was necessary because
EVERGREEN will no longer allow endpoints to dial using TCS-4 unless there is a service
enabled.
16
Compunetix Document 05-CPN-RN-5030 00
Confidential
05-CPN-RN-5030 00
Confidential
October 1, 2014
5 Known Issues in this Release
This section describes the known issues in this Companion software release.
5.1
Echo Canceling
Although Companion supports echo canceling, the solution it utilizes is only effective in some
environments. This solution employed by Companion is being re-examined for improvements.
5.2
Connection failure
When using Unicode characters in the display name, if the user adds spaces at the end of the
string, companion will sometimes fail to connect to the MCU. Any attempt to connect after this
state is triggered would fail. Companion would need restarted after the display name is fixed to
remove the blank spaces.
The root cause of this problem is not understood, but will be fixed in the next release.
5.3
Incorrect endpoint state
When Companion connects to EVERGREEN 4.0.0.0, the state is not always reported correctly
every time. This is due to a difference in the endpoint data structure, which was changed for
EVERGREEN 4.0.0.0. This problem will be resolved in the next release.
5.4
Companion decoder freezing
In a few rare cases, Companion’s decoder will freeze. Every case was only found during test
scenarios where Companion was connected to a PC that was put into power saving mode. In
every case, the computer went to screen saver mode, then the problem happened 30 minutes later.
The root cause of this problem is undetermined, but power saving mode is suspected. It is under
investigation.
This problem will be fixed in the next release.
5.5
The GNUGK causing severe packet loss
If Companion is configured to use H.460 (FW traversal) and the GNUGK is used for the Session
Border Controller (SBC), packet loss will start after the fifth or sixth video terminal (including
Companions) are connected in video calls. This is a known issue with the GNUGK.
The GNUGK developers believe this to be a problem with the configuration, as the developer
testing showed the limit is near 50 (fifty per GNUGK). This problem is being examined jointly
with the GNUGK team.
When the investigation is complete and the correct GNUGK configuration is set, a supplemental
configuration guide will be published.
Although the GNUGK is the recommended SBC for EVERGREEN, any SBC can be used. If a
high number of simultaneous connections are needed, a commercial SBC should be used instead
17
Compunetix Document 05-CPN-RN-5030 00
Confidential
05-CPN-RN-5030 00
Confidential
October 1, 2014
of the free GNUGK.
5.6
Companion will sometimes fail to close down correctly
If Companion is running when the network interface is suddenly disabled (as in undocking a
laptop with a wired docking LAN connection) then Companion will fail to shutdown correctly. If
this occurs, then Companion will fail to launch when you next attempt to use it (as it is still
running in the background).
To correct the problem, kill the “Companion.exe” from the task manager or reboot.
5.7
Microsoft Visual C++ 2008 SP1 Redistributable
Companion requires the Microsoft Visual C++ 2008 Redistributable package to run. The Installer
will attempt to install this if it is not already installed. In some rare cases, this installation will
fail. It is okay to continue with the Companion installation. However, it is recommended that you
attempt to manually install the 2008 redistributable.
5.8
Incorrect status if multiple instances of a contact exists on a system
If the same terminal is listed several times within the contact list or within active conferences,
then the endpoint status displayed in the contact window may be incorrect.
5.9
Companion fails to remove from Contacts
Occasionally, Companion will shut down before being able to successfully remove itself from the
MCU contact directory. This will result in multiple instances of Companion in the directory.
These can be deleted by using Companion or any of EVERGREEN’s user interfaces.
In most cases, the Companion user will have closed the application while still in a conference.
To insure proper bookkeeping in the contact directory, please disconnect from your conference
before closing Companion.
5.10 Java had to close dialog box after installation
After the installation, if the user has attempted to launch the application and a Java dialog box
appears stating that Java had to close, the user should reboot their computer.
5.11 The help screens option is disabled
The help screens were not updated for this release of Companion and have been disabled. They
are expected to be updated and restored in a future release.
5.12 Stale video between connections
If Companion is not restarted between connections, then the last frame received by the prior video
call is sometimes seen before the new connection is complete.
18
Compunetix Document 05-CPN-RN-5030 00
Confidential
05-CPN-RN-5030 00
Confidential
October 1, 2014
5.13 Companion exceeds maximum allowable bitrate
Companion occasionally exceeds the maximum bitrate set in the settings. When this happens, the
bitrate could go as high as 10% above the maximum. This will not happen for extended periods.
19
Compunetix Document 05-CPN-RN-5030 00
Confidential
05-CPN-RN-5030 00
Confidential
October 1, 2014
6 How to Obtain Compunetix Assistance
Companion is a product of the Compunetix Video Systems Division (VSD).
6.1
Email
Companion support inquiries should be submitted to [email protected]
6.2
Telephone
You may contact Compunetix for technical assistance at +1 (412) 373-8110; ask for the Video
Systems Division.
6.3
Fax
Messages may be faxed to VSD Support at +1 (412) 858-6348.
7 Appendix: Known Companion-compatible cameras
7.1
Logitech B910 HD
Driver Version: 2.0.1 (Logitech) or later
7.2
Logitech B525 HD
Driver Version: 2.51.828.0 (Logitech) or later
7.3
Logitech QuickCam Ultra Vision
Driver Version: 10.5.1.2023 (Logitech) or later
7.4
Logitech QuickCam Pro 9000
Driver Version: 12.0.1278.0 (Logitech) or later
Firmware Version: 2.96.6009
7.5
Logitech QuickCam Pro 4000
Driver Version: 10.5.1.2023 (Logitech) or later
7.6
Dynex DX-WEB1C (1.3MP Webcam)
Plug and Play (No installation required)
7.7
Envision VCAM-II
20
Compunetix Document 05-CPN-RN-5030 00
Confidential
05-CPN-RN-5030 00
Confidential
October 1, 2014
8 Appendix: MCU Configurations
The following section describes how to configure the roles and permissions in a single network
environment to get different behavior from Companion.
8.1
No EVERGREEN control
The user will have a limited feature set while using Companion. The user will be limited to
connecting to EVERGREEN via the use of a Passcode while dialing in. Alternatively, an
EVERGREEN operator can dial out to Companion using one of EVERGREEN’s user interfaces.
1. Login to the xWMC (Maintenance Console).
2. Navigate to the Group page using the Group link on the left navigation panel.
i. If User Group exists, proceed to step three.
ii. If User Group does not exist, create a Group for the user.
3. Navigate to the Role page using the Role link on the left navigation panel.
a. Click the Create button to launch the Create Role window.
b. Name the Role “Companion Basic”.
i. If using a 4.0.0.0 or newer EVERGREEN navigate to the Call Services tab within
the Role window. Select one or more of the following 3 options:
1. Any resource (Companion will be able to see both Public and Group
Services on EVERGREEN).
2. If resource is in public (Companion will only be able to see Public
Services on EVERGREEN).
3. If resource is in group (Companion will only be able to see Services on
EVERGREEN that are in your group).
4. Navigate to the Users page using the Users link on the left navigation panel.
a. Create a new User.
b. Under the Groups tab, assign this User to the Group from Step 2.
c. Under the Roles tab, assign this User to the Role from Step 3.
5. Launch Companion
6. Log into Companion using the Username and Password you created from Step 4.
21
Compunetix Document 05-CPN-RN-5030 00
Confidential
05-CPN-RN-5030 00
8.2
Confidential
October 1, 2014
Minimum required EVERGREEN permissions for full functionality of
Companion.
The following describes how to allow Companions full feature set of MCU control, while setting
only the minimum roles on the MCU to obtain this level of access.
1. Login to the xWMC (Maintenance Console).
2. Navigate to the Groups page using the Group link on the left navigation panel.
3. If User Group exists, proceed to step five.
4. If User Group does not exist, create a Group for the user.
5. Navigate to the Roles page using the Role link on the left navigation panel.
6. Create a new Role named Companion Full Access and select the following permissions with one
of the 3 available selections (Any resource, If resource is public, If resource is private). This will
determine if Companion Users assigned this Role can view certain resources on the bridge.
a. Active Confs (See active conference, Create active conference, Modify active
conference, Delete active conference)
b. Active EPs (See active endpoint in conference, Create active endpoint in conference,
Modify active endpoint in conference, Delete active endpoint in conference, Connect
active endpoint in conference, Disconnect active endpoint in conference)
c. Stored Confs (See stored conference, Activate stored conference)
d. Contacts (See contact, Create contact, Modify contact, Delete contact)
e. Call Services (See call service). This is only required for EVERGREEN versions 4.0.0.0
or newer.
7. Navigate to the Users page using the Users link on the left navigation panel.
a. Create a new User.
b. Under the Groups tab, assign this User to the Group from Step 2.
c. Under the Roles tab, assign this User to the Role from Step 3.
8. Launch Companion
9. Log into Companion using the Username and Password you created from Step 4.
22
Compunetix Document 05-CPN-RN-5030 00
Confidential