The real time data output is similar to the following and shown in Fig. 2, page 17 and Fig. 3, page 19 . For the output format from memory see page 22 and Fig. 4, page 23.
01 I S 0276 G B3 09/26 11:28 AM 800-555-1212 AT&T INFORMATIO<CR/LF>
| Unit Output | Description | Number of chars | |
|---|---|---|---|
01 | Line number field | 2 char. | (preset by user) |
I | Inbound/Outbound field | 1 char. | (or O for outbound) |
S | Start/End of call field | 1 char. | (or E for end) |
0276 | Duration of call in seconds | 4 char. | (only sent at end of call) |
G | Good checksum for CID string | 1 char. | (or B for bad checksum) |
B3 | Number & Type[3] of Ring(s) | 2 char. | (only sent on end of call) |
09/26 | Date field | 5 char. | |
11:28 | Time field | 5 char. | (12 hour format) |
AM | AM/PM field | 2 char. | |
Phone # | Phone number field | 14 char. | (in some cases only 7 digits sent) |
Name | Name field | 15 char. | (sent only in some areas) |
Each data string is followed by a carriage return and a line feed. 1 space separates each field.
[3] Type of Ring is valid only if distinctive ring service is ordered from Telephone Company. If distinctive ring service is not present on the phone line, the A,B, or C character reported can be inaccurate
Copyright © 2010 CallerID.com