SignalType enum

Definitions for incoming signals from Jabra devices related to call control.

Signature

export declare enum SignalType

Enumeration Members

Member	Value	Description
`ALT_HOLD`	`35`	Indicates whether a call is on hold. `1` means there is a call on hold, while `0` means there is no call on hold.
`ALT_VOLUME_DOWN`	`234`	Indicates that the "volume down" button was pressed.
`ALT_VOLUME_UP`	`233`	Indicates that the "volume up" button was pressed.
`ANSWER_ON_OFF`	`116`	Toggles answering machine operation.
`FLASH`	`33`	This signal is reported in multiple scenarios: - when the user requests to hold a call by interacting with the device, - when the user requests to resume a call by interacting with the device, or - when the user requests to swap the 'active' call (if there's multiple calls running on their system).
`GN_PSEUDO_HOOK_SWITCH`	`65531`	Emitted if calling `offHook(true)` while the device is already in call state.
`HOOK_SWITCH`	`32`	The signal is reported in multiple scenarios: - as an acknowledgement of a successful ICallControl.offHook(true) request made by your UC Client, - when the user is trying to accept an incoming call by interacting with the device, or - when the user is trying to start a new outgoing call by interacting with the device.
`LINE_BUSY`	`151`	Indicates whether the device is currently in an active call (`true`) or not (`false`). The value of the signal is not exclusive to your UC Client, and will also be sent from the device when other UC Clients start a call.
`ONLINE`	`42`	This signal is reported by wireless adapters (Bluetooth and DECT). It gives information on whether the adapter is transmitting audio to a connected device (`true`) or if the device is in power saving mode instead. If the device is saving power, short audio cues might be cut off, as there is some latency before the device wakes up and re-establishes wireless audio link to the adapter.
`PHONE_KEY_0`	`176`	Indicates that the number pad 0 button was pressed.
`PHONE_KEY_1`	`177`	Indicates that the number pad 1 button was pressed.
`PHONE_KEY_2`	`178`	Indicates that the number pad 2 button was pressed.
`PHONE_KEY_3`	`179`	Indicates that the number pad 3 button was pressed.
`PHONE_KEY_4`	`180`	Indicates that the number pad 4 button was pressed.
`PHONE_KEY_5`	`181`	Indicates that the number pad 5 button was pressed.
`PHONE_KEY_6`	`182`	Indicates that the number pad 6 button was pressed.
`PHONE_KEY_7`	`183`	Indicates that the number pad 7 button was pressed.
`PHONE_KEY_8`	`184`	Indicates that the number pad 8 button was pressed.
`PHONE_KEY_9`	`185`	Indicates that the number pad 9 button was pressed.
`PHONE_KEY_POUND`	`187`	Indicates that the number pad # button was pressed.
`PHONE_KEY_STAR`	`186`	Indicates that the number pad * button was pressed.
`PHONE_MUTE`	`47`	Indicates a change in the mute state of the microphone.
`REDIAL`	`36`	Indicates that the user requests the UC Client to repeat the most recent call.
`REJECT_CALL`	`65533`	Indicates that the user requests to reject an incoming call.
`RINGER`	`158`	Indicates a change in the status of incoming calls.
`SEND`	`49`	This indicates that the user has completed entering digits and is ready to begin routing the phone call.
`SPEAKER_PHONE`	`43`	This command is used to switch from headset to speaker phone and from speaker phone to headset (for applicable devices).
`SPEED_DIAL`	`80`	Indicates that a speed dial operation is initiating.
`VOICE_MAIL`	`112`	Enters voice mail application.

Known issues

There is a known issue with PHONE_KEY signals when using the SDK on Mac OS or Linux and running TransportContext.NODE.