The Mapping screen allows the you to view all UDP program, PID, and PassThru mappings for the entire VUE system or a specific VUE server. This screen does not include VOD or OOBM mappings as they are displayed on the VOD screen or OOBM screen respectively. Each mapping is listed with its current state (OK, Error, Inactive, or Idle) and input Continuity Count (CC) fault. Additional specific information for each mapping includes the mapping input stream configuration, program or PID values, and input interface IP.
- A green status of OK indicates successful multiplexing of the input to output mapping. A red error status indicates an issue with the input stream (for example, missing input, invalid or bad PSI, etc).
- Idle or Inactive indicates the mapping is currently not active and no attempt is being made to multiplex the mapping.
Mapping details for each mapping is available when you select a specific mapping row. This includes assigned VUE pipe, Input TS State, Mapping State, mapping creation date, last status update time, and other information. The Input TS State informs the current state of the input stream. Errors receiving input streams result in the mapping being unable to be properly multiplexed. An Input TS State of Input Received indicates the input stream is being received and processed by the VUE pipe. List of input TS states are defined below.
The Mapping State includes information on the current MPEG processing state of the mapping. Mapping State generally applies to UDP program mappings when input PSI (PATs and PMTs) are extracted and validated. Failures to detect and extract PATs and PMTs result in failures to properly multiplex the UDP program mapping. A Mapping State of Successfully Mapped indicates the input stream and mapping is being received and multiplex to the output by the VUE pipe. List of Mapping States are defined below.
| Input State | Description |
|---|---|
| Input received | Indicates OK for input received and being processed by VUE pipe. |
| Error – Loss of input stream | No packets seen on input. |
| Error – Bad interface address | Cannot convert numeric interface address to a string. |
| Error – Bad interface specified | Cannot find the physical interface associated with an address. |
| Error – Could not bind to interface | Cannot bind the socket to the physical interface. |
| Error – OS cannot open socket | Cannot create a socket. |
| Error – Failed SO_TIMESTMPNS | Ideally, the driver applies timestamps. This error indicates that the driver could not apply the timestamps. |
| Error – Failed sizing receive buffer | Cannot not size the receive buffer to minimum size required for proper operation. |
| Error – Failed SO_REUSEADDR | |
| Error – OS bind failed | Cannot bind the socket to the address. |
| Error – OS join failed | Cannot join the socket to the address. |
| Error – Dropping packets | Shared memory is full forcing us to drop packets on input. |
| Output State | Description |
|---|---|
| Waiting for input data to start mapping | Initial state of a mapping. |
| Successfully Mapped | Program is being remultiplexed. |
| Loss of input data | Input data is no longer being received for this mapping. |
| Waiting for PAT | Waiting for input PAT to be extracted. |
| Waiting for PMT | PAT Extracted, waiting for input PMT to be extracted. |
| PMT Missing Input Program | Input Program number not found in PAT. Verify the input program number used in mapping the program is correct. |
| PMT Error – ECM PID Unsupported | ECM PID is either unsupported or is the same as the PMT PID. |
| PMT Error – PCR PID Unsupported | PCR PID is an unsupported value. |
| PMT Error – ES PIDs Unsupported | One or more Component PIDs are an unsupported value. |
| PMT Error – Shared PID Violation | Component PIDs of the PMT are being shared with other PIDs. Component PID sharing is not supported. Two or more services cannot reference the same component PID. |