+VCID - Caller ID Service
Type
Extended syntax parameter.
Command Line Format
AT [cmds] +VCID=<value>[;cmds] <CR>
Default
0
Stored by &Wn
yes
Displayed by &V
no
Description
This is the IS-101 command to enable Caller ID presentation. This command
controls the reporting and presentation of data associated the Caller ID
services in United States and Canada in the Incoming Call Line ID (ICLID)
data format. The ICLID data comes in one of two formats - Single Data Message
(SDM) format, or Multiple Data Message (MDM) format. The permitted values
are as follows:
Meaning <value>
0 Disable Caller ID reporting.
1 Enable Caller ID with formatted presentation to the DTE. The DCE presents the data items in a
<Tag><Value>pair format. The expected pairs are date, time, caller code (telephone number),
and name.
2 Enable Caller ID with unformatted presentation to the DCE. The DCE presents the entire packet of
information, excluding the leading Us (line seizure information), in ASCII hex as printable numbers.
Result Codes
OK The DCE returns this result code if the DCE accepts the command.
ERROR The DCE returns this result code if the <value>is out of
range.
The DCE reports any Caller Id information detected after the first ring.
Note: One or more <CR><LF>combinations may occur after
the RING result code.
The DCE presents all data items, found in the Single Message Format, contained
in the Single Data Message (SDM) and in the Multiple Data Message (MDM)
packets. The DTE can expect, at a minimum, to receive the date, time, and
caller code (telephone number or P or O).
The DCE presents the data items in the <tag><=><value>pair
format for the formatted and the unformatted presentation modes. Spaces
are present on both sides of the equal sign.
Formatted Caller ID Reporting
The DCE does not present the Caller ID information if the DCE detects
a checksum error in the Caller ID packet (either SDM or MDM) while in this
presentation mode. If the DCE receives multiple copies of the Caller ID
packets, the DCE presents one of the correct packets to the DTE. If the
DCE has never presented a correct packet, but has received the line seizure
information at least once, the DCE returns:
<MESG>=<ERROR_202><CR>.
The DCE breaks up the presentation of the date and time into two separate
<Tag><Value>pairs for those data items where the date and time
appear together.
Tag Descriptions:
DATE = MMDD where MM is the month number, 01 through 12 DD is the day number,
01 through 31.
Note: All numbers are in ASCII decimal, and for number less than
10, a filling ASCII zero is required.
TIME = HHMM where HH is the hour number, 00 through 23
MM is the minute number, 00 through 59.
NMBR = <Number>or P or O (ASCII 4F hex) where <Number>is the
telephone number of the caller, where P indicates that the calling number
information is not available since the originating caller has requested
Private service, and where O indicates that the calling number information
is not available since the out-of-area code or the service is unavailable.
The number may be up to 10 digits.
NAME =
MESG =
In the event of an unrecognized data tag, the DCE presents the given information
of the data item as printable ASCII numbers following the MESG tag. The
DCE follows the conventions of the Unformatted Form Reporting (defined below)
where applicable for the given data item only. (See the examples below.)
The DCE includes all Message Type Byte(s), Message Length Byte(s), Data
Byte(s), and Checksum Byte(s), if found, for the presentation.
The following example of Formatted Form Reporting illustrates the case where
the DCE does not recognize the tag of one given data item from a packet
of data items.
RING
DATE=0321
TIME=1405
NMBR=5045551234
NAME=JOHN DOE
MESG=060342424231
RING
The following example of Formatted Form Reporting illustrates the case where
the DCE does not recognize the tag of the packet.
RING
MESG = 060342424231
RING
Unformatted Reporting
The DCE does not present the Caller ID information if the DCE detects
a checksum error in the Caller ID packet (either SDM or MDM) while in this
presentation mode. If the DCE receives multiple copies of the Caller ID
packets, the DCE presents all of the packets to the DTE.
The DCE presents all data items and packet control information, found in
the Single Message Format, contained in the Single Data Message (SDM) and
in the Multiple Data Message (MDM) packets. The DCE will, however, exclude
the leading Us (line seizure information) from the presentation. The DCE
will include the checksum in the presentation and presents the entire Caller
ID packet in ASCII hex as printable numbers. The bytes in the ASCII hex
message are in the bit order presented to the DCE. The DCE does insert spaces,
<CR>, or <LF>ASCII codes, for formatting, between bytes or words
of the packet. The DCE does not check the checksum, and it is the responsibility
of the DTE to check the validity of the message(s).
Note: This means that the DCE will present the Caller ID information
even if the DCE detects a checksum error in the Caller ID packet (either
SDM or MDM) while in this presentation mode.
The DCE presents all information contained in the packet in ASCII hex as
printable characters (0-9 and A-F). The DCE includes all Message Type Byte(s),
Message Length Byte(s), Data Byte(s), and Checksum Byte(s) in the presentation.
The following example illustrates Unformatted Form Reporting:
RING
MESG=0412303332313134303539313435353132333435
RING
RING
+VCID?
The DCE returns the current value of the <value>parameter as
an ASCII decimal integer, followed by the OK result code.
+VCID=?
The DCE returns the possible <value>parameter values as a list
with a single Parameter Range
element (see section 3.18.). The OK result code follows the list.
The following example illustrates inquiring about the DCEs supported Caller
ID presentation modes. The DCE reports that it is capable of all the Caller
ID presentation modes.
AT+VCID=?
(0-2)
OK
Click here to return to the Contents page.