# nccSendDigits

Continues the process of sending digits to place an outbound call (for protocols that support overlapped sending of digits).

#### Prototype

DWORD nccSendDigits ( NCC_CALLHD callhd, char *digits, void *senddigitparms )

Argument | Description
callhd | Handle of the call for which to send digits.
digits | Digit string to send. A digit string ending with a ~ indicates that more digit strings will be sent.
senddigitsparms | Pointer to a protocol-specific NaturalAccess nccSendDigits parameter structure. For protocol-independent applications, set this argument to NULL to use the default parameters.

#### Return values

Return value | Description
SUCCESS | The digit string was successfully sent.
CTAERR_BAD_ARGUMENT | The digits string is NULL.
CTAERR_INVALID_HANDLE | The call handle is not valid. It may have been released.
CTAERR_INVALID_STATE | The line is not in the appropriate state to invoke this function.
CTAERR_SVR_COMM | A server communication error occurred.
NCCERR_INVALID_CALL_STATE | The call is not in the placing state.
NCCERR_NOT_CAPABLE | The protocol does not support the overlapped sending capability.

#### Details

Signaling protocols (for example, ISDN) may support the overlapped sending of digits. Such signaling may supply a partial dialing sequence in the initial nccPlaceCall invocation, and then use nccSendDigits to complete delivery of the remaining dialing sequence. The final character of each partial digit string should be a ~. When all digits are sent, the digit string specified in nccSendDigits should not include the final ~ character. This signals to the protocol that all digits have arrived. See the protocol-specific documentation for details.

Depending on the protocol, calledaddr and callingaddr can be digit strings, IP addresses, or endpoint names.

If the application receives an incoming call while it is placing a call and sending digits, it must abandon call placement and process the incoming call.

The application can determine whether the protocol supports the overlapped sending of digits by examining the NCC_CAP_OVERLAPPED_SENDING bit in the capabilitymask returned by nccQueryCapability.

The application can obtain protocol-specific information concerning the call, such as the B-channel location of a wireless protocol implementation, by invoking nccGetExtendedCallStatus.