Voice API Programming Guide — June 2005 135
11
11.Caller ID
This chapter provides information on caller ID:
•Overview of Caller ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
•Caller ID Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
•Accessing Caller ID Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
•Enabling Channels to Use the Caller ID Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
•Error Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
•Caller ID Technical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
11.1 Overview of Caller IDCaller Identification (caller ID) is a service provided by local telephone companies to enable the
subscriber to receive information about the caller. Caller ID information can include the calling
party’s directory number (DN), the date and time of the call, and the calling party’s subscriber
name. An application can enable the caller ID feature on specific channels to process caller ID
information as it is received with an incoming call. The caller ID information is transmitted using
FSK (frequency shift keying) to the subscriber from the service provider (telephone company
Central Office) at 1200 baud.
The functions and data structures associated with caller ID are described in the Voice API Library
Reference.
Notes: 1. The information in this chapter applies to caller ID on Springware boards. Caller ID on DM3
boards is available via the Global Call API. For more information, see the Global Call
Technology User’s Guide for your technology.
2. If caller ID is enabled, on-hook detection (DTMF, MF, and global tone detection) will not
function.
11.2 Caller ID FormatsThe following caller ID formats are supported:
CLASS (Custom Local Area Signaling Services)
a set of standards published by Bellcore (now known as Telcordia Technologies) and
supported on boards with loop-start capabilities in the following formats:
•Single Data Message (SDM) format
•Mltiple Data Message (MDM) format