Caller ID

Caller Identity Software

In telecommunications systems, it is often necessary to detect the presence of a voice-band modem signal.

Features List

  • Conforms to Telcordia (Bellcore) GR-30-CORE
  • Conforms to ETSI ETS 300 778
  • Supports both transmit and receive functions
  • Supports multiple channels
  • C-Callable

Availability

Platforms
Arm Cortex-A8/A9/A15
Texas Instruments – TI TMS320C6000 C64x/C64x+/C66x/C674x | TI TMS320C5000 C55x / C54x

ADT Caller-ID is available on the above Platforms: Other configurations are available upon request.

Specifications

Description

Adaptive Digital’s Caller ID software generates and detects the Calling Number Delivery signal specified in Telcordia (Bellcore) GR-30-CORE and ETSI ETS 300 778 standards. The transmitter can be configured to operate in either type 1 mode (signal transmitted between ring bursts) or type 2 (signal generated in absence of ring bursts).

Caller ID enables a person receiving an incoming call to identify the calling party before answering the call. The information is usually displayed on a customer premise device that is inserted between the central office and the telephone. 

The Caller’s information can be sent when the receiving phone is on-hook or off-hook. In the case of off-hook transmission, the Caller ID device may block the transmitted modem signal from passing through to the telephone. On-hook Caller ID is referred to as “type 1”, which is specified in the ETSI ES 200 778-1. While off-hook Caller ID is known as “type 2”, which is specified in the ETSI ES 200 778-2. 

The ADT transmit Caller ID software supports two options for formatting the data link layer of a transmit CID burst, Full Format and Partial Format.

Function

API function call summary

Type 1 and Type 2 Caller ID:

CIDTX_ADT_init(…)             CIDRX_ADT_init(…)

CIDTX_ADT_transmit(…)         CIDRX_ADT_receive(…)

CIDRX_ADT_parseMessage(…)

Additional Type 2 Caller ID:

CIDRX_ADT_genACK(…)           CIDTX_ADT_detACK(…)

CIDTX_ADT_signalACK(…)

CIDRX_ADT_config(…)           CIDRX_ADT_getConfigStatus(…)