McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 701

↗ View in doc context
page
701
source
cucm/v15/jtapi-dev-guide/jtapi-dev-guide.md
chunk_id
cucm::v15::jtapi-dev-guide::jtapi-dev-guide::703

Description Field Interface This constant is used when the application invokes silent recording invocation type. The call recording status is not reflected on the Cisco IP device display. Silent recording is the default behavior in releases prior to Release 9.0. If an application uses the startRecording(int playToneDirection) method that was introduced prior to Release 9.0, it will default to the RECORDING_INVOCATION_TYPE_SILENT invocation type. RECORDING_INVOCATION_TYPE_SILENT static int This constant is used when the application invokes user recording invocation type. The call recording status is reflected on the Cisco IP device display. Applications can query the device for this recording type. RECORDING_INVOCATION_TYPE_USER static int Inherited Fields From Interface javax.telephony.callcontrol.CallControlTerminalConnection BRIDGED, DROPPED, HELD, IDLE, INUSE, RINGING, TALKING, UNKNOWN From Interface javax.telephony.TerminalConnection ACTIVE, PASSIVE Parameters invocationType The invocationType parameter allows an application to specify a recording invocation type. The parameter is passed as one of the constants RECORDING_INVOCATION_TYPE_SILENT or RECORDING_INVOCATION_TYPE_USER. String contentID A String representing a specific video. Max 128 characters. New Error Codes CTIERR_ILLEGAL_CALLSTATE Occurs if the request is made on a TerminalConnection associated with an invalid call. The only valid state to invoke this request is ‘Connected’. JTAPI throws InvalidStateException with description as “Line is not in a legal state to invoke command.” Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 637 Cisco Unified JTAPI Extensions Inherited Fields

Page 701 diagram