NCC, ADI

NCC: NCC.X.ADI_LPS
ADI: ADI.LPS

QX 2000/80-4L: LPS4
QX 2000/100-4L: LPS0

NCC: NMS CAS for Natural Call Control Developer's Reference Manual
ADI: NMS CAS for the ADI Service Developer's Reference Manual

Field Name	QX-Related Specifics
CIDalertmaxtime	None.
CIDmaxwaittime	None.
CIDminmarktime	None.
cidsupport	None.
CID type	None.
cleardownflag	None. (ADI only. This parameter is named playcleardown with NCC.)
connstring	None.
dialtonemintime	None.
dialtonewaittime	None.
freqdeglitchtime	None.
freqringhigh	None.
freqringlow	None.
freqringperiods	None.
freqtolerance	None.
interringmaxtime	None.
nodialtoneaction	None.
numrings	None. (ADI only. This parameter is named ringstoincoming with NCC.)
polaranswertime	None.
polardialtime	None.
qualloopoff	None.
qualreversal	None.
qualringoff	None.
qualringon	None.
reversalmode	None.
ringdetectmode	None.
ringsigmaxtime	None.
ringsigmintime	None.
ringstoincoming	None. (NCC only. This parameter is named numrings with ADI.)
xferstring	None.
xfersupport	None.

Enabling Caller ID

The following sections describe how to enable Caller ID in a QX application. The procedures differ depending upon whether you are using the NCC service or ADI service for call control.

Note: Caller ID is only available when France, Japan or United States is selected as the default country.

Enabling Caller ID (NCC Service)

To enable your application to receive Caller ID information, complete the following steps:

1. Enable Caller ID functionality by setting NCC.X.ADI_LPS.cidsupport = 1.
   Note: If caller ID is enabled, regardless of the setting of the NCC.X.ADI_LPS.numrings parameter, the NCCEVN_INCOMING_CALL event is not generated until the caller ID information is received.

2. Invoke the nccGetCallstatus function to retrieve the Caller ID information.
   Note: Do not change the NCC.X.ADI_LPS.CIDtype parameter. This parameter is set as follows for different countries:

   Setting	Protocol	Description
   0	BellCore CID	Data transmission occurs during the first long silent period between two ring patterns. Both multiple and single message formats are supported by the protocol.
   1	NTT Japan CID	Line reversal followed by CAR Alerting Signal precedes FSK modulation transmission. Normal rings start after data transmission. The protocol supports the multiple message format.
   2	ETSI Ringing Pulse Alerting Signal CID	Ringing Pulse Alert Signal precedes FSK modulation transmission. Normal rings start after data transmission. The protocol supports the multiple message format. Used in France.

Enabling Caller ID (ADI Service)

To enable your application to receive Caller ID information, complete the following steps:

1. Enable Caller ID functionality by setting ADI.LPS.cidsupport = 1.
   Note: If caller ID is enabled, regardless of the setting of the ADI.LPS.numrings parameter, the ADIEVN_INCOMING_CALL event is not generated until the caller ID information is received.

2. Invoke the adiGetCallstatus function to retrieve the Caller ID information.
   Note: Do not change the ADI.LPS.CIDtype parameter. This parameter is set as follows for different countries:

   Setting	Protocol	Description
   0	BellCore CID	Data transmission occurs during the first long silent period between two ring patterns. Both multiple and single message formats are supported by the protocol.
   1	NTT Japan CID	Line reversal followed by CAR Alerting Signal precedes FSK modulation transmission. Normal rings start after data transmission. The protocol supports the multiple message format.
   2	ETSI Ringing Pulse Alerting Signal CID	Ringing Pulse Alert Signal precedes FSK modulation transmission. Normal rings start after data transmission. The protocol supports the multiple message format. Used in France.