7.1 Introduction

7.2 Sending Protocol-Specific Info with a Function Call

7.3 Sending Protocol-Specific Call and Line Messages

7.1 Introduction

The NCC service provides an application the ability to send protocol-specific information with almost any function call. This information can include billing rate indications, user-to-user (UUI) information, or anything supported by the protocol. In addition, the NCC service API contains escape mechanisms for sending protocol-specific line or call messages without invoking a call control function.

This chapter describes how to send protocol-specific information with a call control function invocation or independently using the escape mechanisms.

7.2 Sending Protocol-Specific Info with a Function Call

Most NCC service API functions include a void* pointer, which the application can use to reference a protocol-specific parameter structure. In cases where default parameters exist for a function, the application can pass NULL to use the default settings. To learn more about using this pointer with your protocol, see your protocol documentation.

The following functions include the void* pointer:

• nccAcceptCall

• nccAnswerCall

• nccAutomaticTransfer (Two protocol-specific parameter structures can be passed with this function: one contains call placement parameters for the second call; the other contains call transfer parameters.)

• nccBlockCalls

• nccDisconnectCall

• nccHoldCall

• nccPlaceCall

• nccRejectCall

• nccReleaseCall

• nccRetrieveCall

• nccSendCallMessage

• nccSendDigits

• nccSendLineMessage

• nccStartProtocol

• nccStopProtocol

• nccTransferCall

• nccUnblockCalls

7.3 Sending Protocol-Specific Call and Line Messages

The NCC service API contains two functions which serve as escape mechanisms for sending call and line messages:

• nccSendCallMessage: sends a call message

• nccSendLineMessage: sends a line message

nccSendLineMessage can be invoked in any line state except uninitialized. nccSendCallMessage can only be invoked in active or idle line states.

Not all protocols support sending of call messages or line messages using these escape mechanisms. The application can call nccQueryCapability to determine if the protocol supports one and/or the other. The NCC_CAP_SEND_CALL_MESSAGE bit in the capabilitymask indicates if the application can use nccSendCallMessage. NCC_CAP_SEND_LINE_MESSAGE indicates if the application can use nccSendLineMessage.

The application may not use these mechanisms to specify a call or line message that causes a call or line state change as a result of successful message delivery.