| VTM-970 | Minor | Entity names (Service Group, Service Catalog, Transport Stream
and Frequency Templates, etc.) with a different case are not
considered as duplicate entries throughout VTM screens. | Case sensitivity must be considered when assigning entity name
values. |
| VTM-1470 | Minor | Upon importing Service Catalog Entries from a CSV file, VTM
currently allows case insensitive values for “sourceType” and
“pidType”. | Ensure that the “sourceType” and “pidType” values align to any
pre-existing Service Catalog Entry values in VTM. |
| VTM-2011 | Minor | VARPD details are seen on RPD channel details screen for non
applicable SG channels (DsScQAM, DsScte55-1). | vARPD details should be disregarded for non UsScte55-1
channels. |
| VTM-2027 | Minor | Selecting display column view options remain selected even if
they are not applied to the current UI screen being viewed. | Manually deselect the column display view options to match what
is being displayed. |
| VTM-2045 | Minor | Able to create a Downstream OOB Service Group having more than 1
frequency. | OOB DS Service Groups should only be configured with one and only
one Frequency channel. VTM will prevent this from happening during
SG creation or modification. However, problems can arise if RPDs
assigned to existing OOB SGs are attempted to be assigned to other
existing OOB SGs with an OOB DS channel/frequency configured. If
such a situation occurs, then the affected SGs would have to be
recreated. |
| VTM-2080 | Minor | Older field values are retained on the TS template UI if
navigated away from the UI screen without saving. | Re-modifications are required in this case (and then
saving). |
| VTM-2139 | Minor | Modulation mode value on the channel template is being over
ridden by the Default value set on the SG channel config UI. | Ensure the desired modulation mode is set before saving the SG.
Especially, in the case where channels have been manually added and
then a channel template has been applied. |
| VTM-2182 | Minor | The modulation mode on VUE channel is seen as QAM256 for a DSOOB
channel. | In the VUE system, the modulation mode is always defaulted to
QPSK for SCTE55-1 DS channels. |
| VTM-2186 | Minor | Deletion of last frequency from the frequency template is
allowed. | Re-edit the template with any desired frequencies. |
| VTM-2189 | Minor | Service catalog of type DS OOB should not support type PID as
Service group of type DS OOB does not support the assignment of PID
Service Catalog Entries (mappings). | Attempts to assign PID catalog entries (mappings) to an OOB DS
transport stream should not be attempted. Operationally, this is a
not a valid scenario. |
| VTM-2213 | Minor | The NULL PID BW is allowed to be set via the Swagger (VTM) API
for a DSOOB SG. | Null PID B/W values/setting are not applicable to OOB DS
transport streams and will have no effect if set via the VTM API.
The VTM UI prevents Null PID B/W values from being set. |
| VTM-2217 | Minor | In a TS template, leaving the null PID BW field as empty retains
the previously added value. | Re-edit the TS Template and assign valid null BW value. |
| VTM-2221 | Minor | No check present to avoid creation of an Aux core with duplicate
name , Aux core id , and GCP IP address within or across VUE systems
managed by the VTM. | Ensure at least the Aux core name, id or GCP IP address is unique
for all aux cores in a VUE system. |
| VTM-2224 | Minor | ACCP config status "Unknown" is not seen when the VUE is not
reachable. | There are cases where the config status of an aux core is not
immediately reflected as unknown following an VUE system being
unreachable, incorrect IP address assignment, etc. Subsequent sync
operations will eventually result in the correct status being
displayed. |
| VTM-2230 | Minor | 500 Internal Error seen on editing a VUE which has incorrect
Username/password specified. | Ensure valid/correct VUE credentials are used for VUE
systems. |
| VTM-2306 | Minor | VUE IP address specified using VTM is not being
validated. | Ensure a valid IP address is used when adding or modifying a VUE
system. |
| VTM-2694 | Minor | PID templates are incorrectly required to be associated with an
AutoMap SCE. | Create a PID Template with no PID entries and assign the PID
Template to the AutoMap Service Catalog Entry. |
| VTM-2695 | Minor | RF Channel Index Template should be modifiable on RxDs synced
from Domain Manager. | Currently, only the default RF channel index template can be used
for RMDs synced from Domain Manager. |
| VTM-2697 | Minor | PID Templates should not allow PID values of zero to be
specified. | PID 0 values should not be used. They are (by default)
automatically mapped to the output transport streams by the
VUE. |
| VTM-2770 | Major | The VTM does not update the secondary (Geo Redundant) source
information on VUE for a Service Catalog Entry (mapping). | The VUE EM must be used as a work around. |
| VTM-2779 | Major | The VTM does not process Input Transport Stream Redundancy
Failover alarms. | Since the failover alarms are not processed by the VTM, they can
only be observed on the VUE Element Manager. |
| VTM-2839 | Major | Secondary Source Information (Multicast, Source IP) for Input
Transport Stream Redundancy configuration is not validated for white
space or invalid characters. | Ensure valid IP and Multicast addresses are entered when
configuring the secondary source information (i.e., no white space
or invalid characters). |
