Step 1 - Set up a Service Account
The instructions below are separated by device type. Please follow the relevant instructions to create a service account on the component being added:
Note: MCU supervisor blades and slave blades in an MCU cluster do not need to be added.
For Cisco Multipoint Control Units (Codian MCUs):
- Log into the infrastructure with any Administrator account.
- Click on the User tab.
- Select Add New User.
- Enter the User ID as vyopta_svc and Account Name as vyopta_svc
- Enter and Re-enter the password.
- Uncheck the box for Force user to change password on next login.
- Set the Privilege level to administrator.
- Leave the E.164 phone number blank.
- When finished, add the User.
Figure 4-1: Add MCU User Service Account
For Cisco TelePresence Servers (TPS):
- Log into the infrastructure with any Administrator account.
- Click on the User tab.
- Select Add New User.
- Enter in the User ID as vyopta_svc and Account Name as vyopta_svc.
- Enter and re-enter the password.
- Set the privilege level to API access.
- When finished, select Add User.
Figure 4-2: Add TPS User Service Account
Note: Please ensure that http is enabled for your TP Server. If it is not enabled, call quality will not be reported for TP Server in Real Time/Historical. |
Figure 4-3: HTTP can be enabled within your TP Server under Network→ Services→ HTTP
For Cisco Codian (MCU)
In order to maximize the number of call detail records stored on the MCU you must enable CDR permanent storage by performing the following:
- Log into the device with an administrator account.
- Navigate to Logs -> CDR logs.
- Click on the Enable CDR permanent storage button.
Figure 4-4: Click to enable CDR permanent storage
Step 2 - Add MCU or TPS in Vyopta
To add a Cisco MCU orTelepresence Server requires the following:
- Access to the FQDN/ IP address of the video device from the Vyopta Data Collector
- Previously created user service account credentials on each video device
Note: If you have multiple MCUs, TPS peers, or clusters you must add a connector for each individual device or blade. Do not add slave MCUs as all information is obtained from the Master MCU. |
Please follow the instructions below to add the CMS instance:
- Navigate to the Vyopta Admin Portal and log in with your Vyopta credentials
- Select the Infrastructure menu or Icon, then select New Infrastructure at the bottom of the page
- From the selection of infrastructure types, click either 'Cisco TelePresence Server' or 'Cisco Multipoint Control Unit (MCU)
Note: We recommend using hostname rather than IP as IP addresses are subject to change. It is also helpful to name the infrastructure in a 'friendly' or easily understood way. |
- Enter a user friendly name for the device.
- Enter the description of the device. This can include the device type, location, and other unique identifiers.
- Enter the infrastructure hostname or IP address.
- Enter the username and password created on the video device.
- Click Save
- Find the newly added MCU or TPS in the Infrastructure List and click the Edit icon.
- On the Settings Page for the device, click the Validate button.
- If the connection to the video component succeeded, click the Save button.
Figure 4-5: MCU Configuration Example
Reference Tables
Cisco TelePresence Multipoint Control Unit (MCU) Reference Table
Cisco TelePresence MCU |
|
Version |
MCU version 4.1 or above |
Device Access |
Server IP/FQDN |
User/Service Account |
Local account with Administrator privileges |
TCP Ports |
Vyopta Data Collector outbound to the MCU device(s) TCP 443 (https)
If MCU is in a cluster only the Master needs to be added |
Cisco TelePresence Server (TPS) Reference Table
Cisco TelePresence Server (TPS) |
|
Version |
TPS 3.1 or above |
Device Access |
Server IP/FQDN |
User/Service Account |
Local account with API Access (or Administrator privileges) |
TCP Ports |
Vyopta Data Collector outbound to the TPS device(s) TCP 443 (https)
TPS device(s) outbound to the Vyopta Data Collector TCP 22280 |
Comments
Please sign in to leave a comment.