epSpecificCallHookFlashProcessing
MX-EPSERV-MIB ·
.0.1700.1.100.400.1.400
Object
column
r/w
Enumeration
Endpoint Specific Call Hook Flash Processing
Selects how to process hook-flash detection.
When a call is in progress, the user can normally put the
call on hold, transfer the call, or even initiate a
conference call. DefaultCallHookFlashProcessing defines
whether these subscriber services are handled by the unit or
delegated to a remote party.
* ProcessLocally: Hook-flash is processed locally. The
actual behavior of the 'flash' button depends on which
subscriber services are enabled for this endpoint.
* TransmitUsingSignalingProtocol: Hook-flash is processed
by a remote party. The hook-flash event is carried by a
signaling protocol message. The actual behavior of the
'flash' button depends on the remote party. This option
also enables the unit to receive call waiting events with
caller ID via the signaling protocol.
This configuration overrides the default configuration set in
the DefaultCallHookFlashProcessing parameter if the
EpSpecificCall.EnableConfig parameter is set to 'Enable'.
Context
- MIB
- MX-EPSERV-MIB
- OID
.0.1700.1.100.400.1.400- Type
- column
- Access
- readwrite
- Status
- current
- Parent
- epSpecificCallEntry
- Table
- epSpecificCallTable
- Siblings
- 2
Syntax
Enumeration
Values & Constraints
Enumerated Values
100 | processLocally |
200 | transmitUsingSignalingProtocol |
Related Objects
Sibling Objects
| Object | Type | Syntax | OID |
|---|---|---|---|
| epSpecificCallEpId Endpoint Identifier
String that identifies an endpoint in other tables. | column | OctetString | .0.1700.1.100.400.1.100 |
| epSpecificCallEnableConfig Enable Configuration
Defines the configuration to use for a specific endpoint.
* Disable: The endpoint uses the default configuration as
define… | column | MX-TCMxEnableState | .0.1700.1.100.400.1.200 |