Table of Contents

Index

NMS Glossary

Previous Page

Next Page

(Page 11 of 23 in this chapter) Version

nccPlaceCall

Description

Places an outbound call.

Prototype

DWORD nccPlaceCall ( CTAHD linehd,
char *calledaddr,
char *callingaddr,
void *mgrcallparms,
void *protcallparms,
NCC_CALLHD *callhd )
linehd The CT Access context handle on which NCC line is opened via ctaOpenServices.
calledaddr A pointer to the address of the remote party (must be a NULL terminated string with a maximum of 32 digits).
callingaddr A pointer to the address of the local party (must be a NULL terminated string with a maximum of 32 digits). Can be NULL if the protocol implementation allows.
mgrcallparms A pointer to a manager-specific CT Access call placement parameter structure. Specify NULL to use default values. See the manager-specific documentation for details.
protcallparms A pointer to a protocol-specific CT Access call placement parameter structure. Specify NULL to use default values. See the protocol-specific documentation for details.
callhd A pointer to NCC_CALLHD. NCC assigns a valid call handle to a successfully initialized outbound call. This call handle is used in other call-related API functions, such as nccHoldCall or nccReleaseCall.

Return Values

SUCCESS
CTAERR_BAD_ARGUMENT
The calledaddr string is NULL, is not NULL terminated, or has more than 32 digits. The callingaddr string is not NULL terminated or has more than 32 digits.
CTAERR_INVALID_HANDLE
The NCC service is not opened on this CT Access context handle.
CTAERR_INVALID_STATE
The line is not in the appropriate state to invoke this function.
NCCERR_ADDRESS_BLOCKED
Too many calls placed to this address, or a call was placed too recently.

Events

NCCEVN_PLACING_CALL
The call placement operation completed successfully and the call entered the placing state.
NCCEVN_CALL_RELEASED
An incoming call was detected during call placement. The TCP released the outbound call. The event value field contains NCC_RELEASED_GLARE.
NCCEVN_CALL_PROCEEDING
The switch accepted the call setup. The receiving side is being rung. The call enters the proceeding state.
NCCEVN_REMOTE_ALERTING
The remote end is in an alerting state (is ringing). This event is generated only if the NCC_REPORT_ALERTING bit is set in the NCC.START.eventmask parameter (see Appendix C).
NCCEVN_REMOTE_ANSWERED
This event is generated at the first positive indication that the remote party has answered (for example, out-of-band signaling, voice, or modem tone). The event value field contains the indication type. This event is generated only if the NCC_REPORT_ANSWERED bit is set in the NCC.START.eventmask parameter (see Appendix C).
NCCEVN_CALL_CONNECTED
Both parties are now connected. The call enters the connected state.

Details

calledaddr and callingaddr can be digit strings, IP addresses, or endpoint names, depending on the protocol.
If the application receives NCCEVN_CALL_RELEASED (with an NCC_RELEASED_GLARE reason code) instead of NCCEVN_PLACING_CALL, the line was seized for an incoming call before glare was resolved, and the TCP has released the outgoing call. The application should immediately abandon outbound call placement and handle the incoming call.
The application can obtain protocol-specific information concerning the call, such as the B-channel location of a wireless protocol implementation, by invoking nccGetExtendedCallStatus.
Signaling protocols (for example, ISDN) may support overlapped sending of digits. Such signaling may supply a partial dialing sequence when invoking nccPlaceCall, and use nccSendDigits to complete delivery of the remaining dialing sequence, in one or more chunks. 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.
The application can determine whether or not a protocol supports overlapped sending of digits by examining the NCC_CAP_OVERLAPPED_SENDING bit in the capabilitymask returned by nccQueryCapability. For more information about overlapped sending of digits, see Section 4.3.4.

See Also

nccSendDigits

Table of Contents

Index

NMS Glossary

Previous Page

Next Page

(Page 11 of 23 in this chapter) Version

Want to send us feedback on our documentation? Email: Tech_Pubs@nmss.com

Copyright © 2000, Natural MicroSystems, Inc. All rights reserved.