Previous PageTable Of Contents../index.htmlIndexNext Page

dx_gtcallid( )

Description | Cautions | Example | Errors | See Also

Name:

int dx_gtcallid (chdev, bufferp)

Inputs:

int chdev

  Channel device handle

 

unsigned char *bufferp

  Pointer to where to return calling line Directory Number

Returns:

0 success

 

-1 error return code

Includes:

srllib.h

 

dxxxlib.h

Category:

Caller ID

Mode:

synchronous

Top Of PageDescription

The dx_gtcallid( ) function returns the calling line Directory Number (DN) sent by the Central Office (CO).

This function has the following parameters:

Parameter

Description

chdev:

Channel device handle.

bufferp:

Pointer to where to return calling line Directory Number (DN).

On successful completion, a NULL terminated string containing the caller's phone number (DN) is placed in the buffer.

NOTE:
Non-numeric characters (punctuation, space, dash) may be included in the number string. The string may not be suitable for dialing without modification.

Caller ID information is available for the call from the moment the ring event is generated (if the ring event is set to occur on or after the second ring (CLASS, ACLIP) or set to occur on or after the first ring (CLIP, JCLIP) until either of the following occurs:

NOTE:
To determine if Caller ID information has been received from the CO before issuing a dx_gtcallid( ) or dx_gtextcallid( ) Caller ID function, check the event data in the event block. When the ring event is received, the event data field in the event block is bitmapped and indicates that Caller ID information is available when bit 0 (LSB) is set to a 1. See the function code examples for further information.

Based on the Caller ID options provided by the CO and for applications that require only the calling line Directory Number (DN), issue the dx_gtcallid( ) function to get the calling line DN.

If the call is not answered and the ring event is received before the Caller ID information has been received from the CO, Caller ID information will not be available until the beginning of the second ring (CLASS, ACLIP) or the beginning of the first ring (CLIP, JCLIP).

Based on the Caller ID options provided by the CO and for applications that require additional Caller ID information, issue the dx_gtextcallid( ) function for each type of Caller ID message required. As an argument in the dx_gtextcallid( ) function, the type of Caller ID message to access is specified (infotype).

Top Of PageCautions

To allow the reception of Caller ID information from the Central Office before answering a call (application channel goes off-hook):

NOTE:
If the call is answered before Caller ID information has been received from the CO, Caller ID information will not be available.

Top Of PageExample

Top Of PageErrors

If this function returns -1 to indicate failure, use ATDV_LASTERR( ) and ATDV_ERRMSGP( ) to retrieve one of the following error reasons:

EDX_BADPARM

Invalid parameter

EDX_BUSY

Channel is busy

EDX_CLIDBLK

Caller ID is blocked or private or withheld
(other information may be available using dx_gtextcallid( ))

EDX_CLIDINFO

Caller ID information not sent or Caller ID information invalid

EDX_CLIDOOA

Caller ID is out of area
(other information may be available using dx_gtextcallid( ))

EDX_SYSTEM

Error from operating system; use dx_fileerrno( ) to obtain error value

Top Of PageSee Also


Previous PageTable Of ContentsTop Of PageIndexNext Page

Click here to contact Dialogic Customer Engineering

Copyright 2002, Dialogic Corporation
All rights reserved
This page generated February, 2002