
NO.:
W62410 API
VERSION:
A
PAGE
115
To use the CallerID features, you will have to manage at least three commands:
EnableCallerID
,
ReturnCallerIDInfo
and
ContReturnCallerIDInfo
.
EnableCallerID:
This command allows you to force the CHIPSET to decode a particular type of
CallerID. Currently there are three CallerID decoders supported:
CallerID 1
as defined by US Bellcore 202 standard and the CCA (v.23)
standard as defined in the UK.
CallerID 1
as defined by the British Telecom Standard.
CallerID 2
for both US and UK
ReturnCallerIDInfo:
The first command to be send to the CHIPSET to specify if all or part of the
CallerID info has to be returned by the
ContReturnCallerIDInfo
command. It
gives the possibility to specify a field number in case of a
MDMF
message. This
command also returns if the message received is of the
SDMF
or
MDMF
type,
length of the message and if the CallerID is potentially corrupt (i.e. CRC
checksums are not corresponding).
ContReturnCallerIDInfo:
This command allows retrieving byte by byte the CallerID info as requested by
the ReturnCallerIDInfo command. Since the length of the buffer is returned by
the
ReturnCallerIDInfo
command, you have to call the
ContReturnCallerIDInfo
command, “length” times in order to get all the relevant ASCII characters of the
requested field.
To initialize all CallerID features, you have first to send the
EnableCallerID
command with the “C” flag
set to one and the stage parameter set to the required CallerID that has to be decoded.
Once a CallerID has been detected the corresponding I and F flags will be set. These flags can be
checked e.g. by using the
MonitorLine
command. You can then access the CallerID data by using the
ReturnCallerIDInfo
and
ContReturnCallerIDInfo
commands.
The above information is the exclusive intellectual property of Winbond Electronics and shall not
be disclosed, or reproduced without permission from Winbond.