Home > @gnaudio/jabra-js > SignalType
SignalType enum#
Definitions for incoming signals from Jabra devices related to call control.
Signature:Enumeration Members#
| Member | Value | Description |
|---|---|---|
| ALT_HOLD | 35 | |
| ALT_VOLUME_DOWN | 234 | |
| ALT_VOLUME_UP | 233 | |
| ANSWER_ON_OFF | 116 | |
| 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). |
| HOOK_SWITCH | 32 | The signal is reported in multiple scenarios:- as an acknowledgement of a successful ICallControl.offHook(true) request made by your softphone,- 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.For further information, refer to the guide on device signals. |
| 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 softphone, and will also be sent from the device when other softphones 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.For further information, refer to the guide on device signals. |
| REDIAL | 36 | Indicates that the user requests the softphone to repeat the most recent call. |
| REJECT_CALL | 65533 | Indicates that the user requests to reject an incoming call. |
| RINGER | 158 | |
| SEND | 49 | |
| SPEAKER_PHONE | 43 | |
| SPEED_DIAL | 80 | |
| VOICE_MAIL | 112 |
Remarks#
This list might not be exhaustive.
There is a known issue with PHONE_KEY signals when using the SDK on Mac OS or Linux and running TransportContext.NODE. For further information, refer to the guide on device signals.