POTS In

Telephone Country

Select the country in which the telephone service resides.

Telephone Tone Output

When 'Yes' is selected, the Ring, Entry, Exit, and DTMF tones are fed to a separate output channel (Tone Output) on the POTS In component. These tones can now be routed independent of the voice audio.

Enable Call Sync

Use the Call Sync component to simplify the integration of Q-SYS collaboration devices and calling systems. It synchronizes mute state, call controls, and LED light behavior across multiple calling components, including USB HID Conferencing, Softphone, and POTS Controller. See the Call Sync topic

Peak Input Level (dBFS)

Measures the analog input signal.

Clip

Red LED indicating if the signal is being clipped.

Clip Hold

Holds the clip indication until manually cleared by pressing this button to the Off position.

Invert

Toggle button to invert the digital output of the POTS In.

Mute

Mutes the output signal.

Gain (dB)

Controls the Gain of the digital output signal.

Status LED

This LED changes color to indicate the current status of the Core. See Status for the meanings of the various colors.

Status

Component status is conveyed with the Status LED and Status box, which uses both color and text to indicate the current condition:

• OK: The device is functioning normally.
• Initializing: The device is in the process of a firmware or configuration update, or the design is starting.
• Compromised: The device is functioning, but a non-fatal problem exists. Refer to the Status box for details.
• Missing: The device cannot be discovered.
• Fault: The device is malfunctioning or is not properly configured. Refer to the Status box for details.
• Unknown: This status appears during a Core reboot (for example, during a firmware update), or when a design is being uploaded to the Core and before it has started running.
• Not Present: If applicable to the device, this status appears when the device is not connected to the network and its Is Required component property is set to 'No'. This status also appears if the device component's Dynamically Paired property is set to 'Yes', pairing has not been assigned in Core Manager, and the device component's Is Required property is set to 'Yes'. See Dynamic Pairing.