TF filler

AMERICAN NATIONAL STANDARD C12.19-200x
Contribution #: [TF0404-113-2]
CONTRIBUTION
TableFest II
Project:
ANSI C12.19-1997,IEEE 1377-1997, MC12.19
Title: Expanded Capabilities for the 90s Decade
Eugene Falendysz
Michael Miller
Author(s): Robert McMichael
Michael Anderson
Aaron F. Snyder
Name: Aaron F. Snyder
Organization: Schlumberger Electricity Inc.
Address Line 1: 313b North Hwy. 11
Address Line 2:
Contact: City, State, &
West Union, SC 29696
Zip:
Phone Number: +1 (864) –718-1269
Fax Number: +1 (864)-638-4900
E-Mail Address: asnyder@oconee.sema.slb.com
Related Document(s): Working Document, “WG2-0309.doc”, C12.21-1999
Supersedes TF0404-113-1
Submission Date: April 27, 2004
 Industry Canada Task Force members
Distribution:  ANSI C12 SC17 members
 IEEE SCC31 members
Extension of 90’s decade tables to support modern devices and better status
Abstract:
reporting.
8. Table Support for Communication
Objectives addressed
8.1. C12.21 (90’s decades)
and/or introduced:
9. Syntax corrections and extensions
1. Section 9.10.1 Table 90 Added a Boolean (EXTENDED_STATUS) to indicate
that extended status reporting is supported. Removed the FILLER.
2. Section 9.10.2 Table 91 Added EXTENDED_STATUS to
TELEPHONE_FLAGS_BFLD Identifier list
3. Section 9.10.3 Added information about PSEM_IDENTITY from C12.21
4. Section 9.10.4 Table 93 Added fields for managing retries of dial out
Summary of
attempts.
modifications to the
5. Section 9.10.8 Table 97 Added extended status information
Standard Document:
LAST_CALL_PURPOSE_RCD to show the purpose for the last dial out for
each phone number.
6. Section 9.10.9 Added Table 98 that contains status information about phone
home triggers.
7. Added PROCEDURE 21 (Table 7) “Clear Pending Call Status” to allow table
98 to be cleared.
Contribution List
Modernization of the Modem Tables
“Subject” Column
Contribution List
April 04
“Date” Column
Contribution List
Expanded Capabilities for the 90s Decade
“Title” Column
Contribution List Eugene Falendysz
Disclaimer: Page 1 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).
AMERICAN NATIONAL STANDARD C12.19-200x
“Contributor” Column
Disclaimer: Page 2 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).
AMERICAN NATIONAL STANDARD C12.19-200x
9.10 DECADE 9: Telephone Control Tables
This decade contains tables associated with the use of a telephone modem.
9.10.1 Table 90 Dimension Telephone Table
Table 90 Data Description
DIM_TELEPHONE_TBL (Table 90) specifies the maximum dimensional values for this decade.
TYPE TELEPHONE_FLAGS_BFLD = BIT FIELD OF UINT8
ANSWER_FLAG : BOOL(0);
S_ANCHOR_DATE_FLAG : BOOL(1);
OFFHOOK_DETECT_FLAG : BOOL(2);
BIT_RATE : UINT(3..4);
ID_IN_PURPOSE : BOOL(5);
NO_LOCKOUT_PARM : BOOL(6);
EXTENDED_STATUS : BOOL(7)
END;
TYPE TELEPHONE_RCD = PACKED RECORD
TELEPHONE_FLAGS : TELEPHONE_FLAGS_BFLD;
NBR_ORIGINATE_WINDOWS : UINT8;
NBR_SETUP_STRINGS : UINT8;
SETUP_STRING_LENGTH : UINT8;
PREFIX_LENGTH : UINT8;
NBR_ORIGINATE_NUMBERS : UINT8;
PHONE_NUMBER_LENGTH : UINT8;
NBR_RECURRING_DATES : UINT8;
NBR_NON_RECURRRING_DATES : UINT8;
NBR_EVENTS : UINT8;
NBR_WEEKLY_SCHEDULES : UINT8;
NBR_ANSWER_WINDOWS : UINT8;
NBR_CALLER_IDS : UINT8;
CALLER_ID_LENGTH : UINT8;
END;
TABLE 90 DIM_TELEPHONE_TBL = TELEPHONE_RCD;
Identifier Value Definition
TELEPHONE_FLAGS_BFLD
ANSWER_FLAG FALSE End device is not capable of answering a phone
call.
TRUE End device is capable of answering a phone
call.
S_ANCHOR_DATE_FLAG FALSE End device is not capable of accepting a
separate telephone schedule anchor date for the
Period/Delta RDATE type (recurring date).
Disclaimer: Page 3 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).
AMERICAN NATIONAL STANDARD C12.19-200x
TRUE End device is capable of accepting a separate
telephone schedule anchor date for the
Period/Delta RDATE type (recurring date).
OFFHOOK_DETECT_FLAG FALSE End device is not capable of detecting off hook
conditions.
TRUE End device is capable of detecting off hook
conditions.
BIT_RATE 0 End device is not capable of modifying its bit
rate.
1 End device is capable of modifying globally its
originating and answering bit rate.
2 End device is capable of modifying separately its
originating and answering bit rate.
3 Reserved.
ID_IN_PURPOSE FALSE End device is not capable of including an ID
field in CALL_PURPOSE_TBL.
TRUE End device is capable of including an ID field in
CALL_PURPOSE_TBL (Table 96).
NO_LOCKOUT_PARM FALSE End device is capable of supporting lockout
parameters in table
ANSWER_PARAMETERS_TBL (Table 95).
TRUE End device is not capable of supporting lockout
parameters in table
ANSWER_PARAMETERS_TBL (Table 95).
EXTENDED_STATUS FALSE End device is not capable of including Last call
purpose in the CALL_STATUS_TBL (Table 97)
TRUE End device is capable of including
Last call purpose in the CALL_STATUS_TBL (Table
97)
TELEPHONE_RCD
TELEPHONE_FLAGS See definition above.
NBR_ORIGINATE_WINDOWS 0..255 Maximum number of originate time window
descriptions supported by the end device.
NBR_SETUP_STRINGS 0..255 Maximum number of setup strings supported by
the end device.
SETUP_STRING_LENGTH 0..255 Maximum length (in bytes) of setup strings
supported by the end device.
PREFIX_LENGTH 0..255 Maximum length (in bytes) of phone number
prefix supported by the end device.
NBR_ORIGINATE_NUMBERS 0..255 Maximum number of originate phone numbers
supported by the end device.
PHONE_NUMBER_LENGTH 0..255 Maximum length (in bytes) of phone numbers
supported by the end device.
Disclaimer: Page 4 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).
AMERICAN NATIONAL STANDARD C12.19-200x
NBR_RECURRING_DATES 0..255 Maximum number of recurring dates supported
to create the origination schedule.
NBR_NON_RECURRRING_DATES 0..255 Maximum number of non-recurring
dates supported to create the origination
schedule.
NBR_EVENTS 0..255 Maximum number of events supported to create
the origination schedule.
NBR_WEEKLY_SCHEDULES 0..255 Maximum number of weekly schedules
supported to create the origination schedule.
NBR_ANSWER_WINDOWS 0..255 Maximum number of answer time window
descriptions supported by the end device.
NBR_CALLER_IDS 0..255 Maximum number of Caller ID strings supported
by the end device.
CALLER_ID_LENGTH 0..255 Maximum length (in bytes) of Caller ID strings
supported by the end device.
Disclaimer: Page 5 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).
AMERICAN NATIONAL STANDARD C12.19-200x
9.10.2 Table 91 Actual Telephone Table
Table 91 Data Description
ACT_TELEPHONE_TBL (Table 91) contains actual dimension values for this decade.
TABLE 91 ACT_TELEPHONE_TBL = TELEPHONE_RCD;
Identifier Value Definition
TELEPHONE_FLAGS_BFLD
ANSWER_FLAG FALSE End device shall not answer a phone call.
TRUE End device may answer a phone call.
S_ANCHOR_DATE_FLAG FALSE End device does not accept a separate
telephone schedule anchor date for the
Period/Delta RDATE type (recurring date).
TRUE End device accepts a separate telephone
schedule anchor date for the Period/Delta
RDATE type (recurring date).
OFFHOOK_DETECT_FLAG FALSE End device does not currently detect off hook
conditions.
TRUE End device currently detects off hook conditions.
BIT_RATE 0 Bit rate can not be controlled.
1 Answering and originating bit rate can be
controlled globally in
GLOBAL_PARAMETERS_TBL (Table 92).
2 Answering and originating bit rate can be
controlled separately in
ORIGINATE_PARAMETERS_TBL (Table 93)
and ANSWER_PARAMETERS_TBL (Table
95).
3 Reserved.
ID_IN_PURPOSE FALSE End device does not currently include an ID field
in CALL_PURPOSE_TBL (Table 96).
TRUE End device currently includes an ID field in
CALL_PURPOSE_TBL (Table 96).
NO_LOCKOUT_PARM FALSE End device currently includes lockout
parameters in table
ANSWER_PARAMETERS_TBL (Table 95).
TRUE End device does not currently include lockout
parameters in table
ANSWER_PARAMETERS_TBL (Table 95).
EXTENDED_STATUS FALSE End device is not including last call purpose
information in the CALL_STATUS_TBL (Table
97)
Disclaimer: Page 6 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).
AMERICAN NATIONAL STANDARD C12.19-200x
TRUE End device is including last call purpose
information in the CALL_STATUS_TBL (Table
97)
TELEPHONE_RCD
TELEPHONE_FLAGS See definition above.
NBR_ORIGINATE_WINDOWS 0..255 Actual number of originate time window
descriptions used by the end device.
NBR_SETUP_STRINGS 0..255 Actual number of setup strings used by the end
device.
SETUP_STRING_LENGTH 0..255 Actual length (in bytes) of setup strings used by
the end device.
PREFIX_LENGTH 0..255 Actual length (in bytes) of phone number prefix
used by the end device.
NBR_ORIGINATE_NUMBERS 0..7 Actual number of originate phone numbers used
by the end device.
PHONE_NUMBER_LENGTH 0..255 Actual length (in bytes) of phone numbers used
by the end device.
NBR_RECURRING_DATES 0..255 Actual number of recurring dates used to create
the origination schedule.
NBR_NON_RECURRRING_DATES 0..255 Actual number of non-recurring dates
used to create the origination schedule.
NBR_EVENTS 0..255 Actual number of events used to create the
origination schedule.
NBR_WEEKLY_SCHEDULES 0..255 Actual number of weekly schedules used to
create the origination schedule.
NBR_ANSWER_WINDOWS 0..255 Actual number of answer time window
descriptions used by the end device.
NBR_CALLER_IDS 0..255 Actual number of Caller ID strings used by the
end device.
CALLER_ID_LENGTH 0..255 Actual length (in bytes) of Caller ID strings used
by the end device.
Disclaimer: Page 7 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).
AMERICAN NATIONAL STANDARD C12.19-200x
9.10.3 Table 92 Global Parameters Table
Table 92 Data Description
GLOBAL_PARAMETERS_TBL (Table 92) defines general parameters used both for answering and
originating a call.
TYPE SETUP_STRING_RCD = PACKED RECORD
SETUP_STRING :
ARRAY[ACT_TELEPHONE_TBL.SETUP_STRING_LENGTH] OF CHAR;
END;
TYPE GLOBAL_PARAMETERS_RCD = PACKED RECORD
PSEM_IDENTITY : UINT8;
IF ACT_TELEPHONE_TBL.BIT_RATE = 1 THEN
BIT_RATE : UINT32;
END;
MODEM_SETUP_STRINGS : ARRAY[ACT_TELEPHONE_TBL.NBR_SETUP_STRINGS]
OF SETUP_STRING_RCD;
END;
TABLE 92 GLOBAL_PARAMETERS_TBL = GLOBAL_PARAMETERS_RCD;
Identifier Value Definition
SETUP_STRING_RCD
SETUP_STRING Modem setup string used to configure the
modem.
GLOBAL_PARAMETERS_RCD
PSEM_IDENTITY 0..255 Value used by the <identity> field in Layer 2 of
C12.21
{ End device (meter, etc.) identity. It identifies
the end device in both the request and response
packets.
In requests, this byte may be set to 00 H as a
universal identity. All devices shall respond to
this identifier value as a minimum. This value
(00H)should not be used in a multidrop
environment.
The individual end device identity must be in the
range 01H to FEH.
In requests, this byte may be set to FFH to target
the calling party during an inbound call. Only the
end device that initiated the inbound call shall
process packets with identity byte equal to FFH.
The value FFH may be used in both single drop
and multidrop environments.
Disclaimer: Page 8 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).
AMERICAN NATIONAL STANDARD C12.19-200x
The end device shall use its own identity byte in
the response for all requests. Including 00 H and
FFH }
BIT_RATE Bit rate at which the end device will originate or
answer a call. Zero denotes an externally
defined bit rate.
MODEM_SETUP_STRINGS An array of Modem Setup Strings
Disclaimer: Page 9 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).
AMERICAN NATIONAL STANDARD C12.19-200x
9.10.4 Table 93 Originate Parameters Table
Table 93 Data Description
ORIGINATE_PARAMETERS_TBL (Table 93) defines originate configuration parameters. Originate
refers to the end device placing calls to a utility host.
TYPE STIME_RCD = PACKED RECORD
SWITCH GEN_CONFIG_TBL.TM_FORMAT OF
CASE 0: NOTHING : NIL;
CASE 1: HOUR : BCD;
MINUTE : BCD;
CASE 2: HOUR : UINT8;
MINUTE : UINT8;
CASE 3: D_TIME : UINT32;
CASE 4: D_TIME : UINT32;
END;
END;
TYPE DAYS_BFLD = BIT FIELD OF UINT8
SUNDAY : BOOL(0);
MONDAY : BOOL(1);
TUESDAY : BOOL(2);
WEDNESDAY : BOOL(3);
THURSDAY : BOOL(4);
FRIDAY : BOOL(5);
SATURDAY : BOOL(6);
FILLER : FILL(7..7);
END;
TYPE WINDOW_RCD = PACKED RECORD
BEGIN_WINDOW_TIME : STIME_RCD;
WINDOW_DURATION : STIME_RCD;
WINDOW_DAYS : DAYS_BFLD;
END;
TYPE PHONE_NUMBER_RCD = PACKED RECORD
PHONE_NUMBER :
ARRAY[ACT_TELEPHONE_TBL.PHONE_NUMBER_LENGTH] OF CHAR;
END;
TYPE PHONE_NUMBERS_RCD = PACKED RECORD
PREFIX :
ARRAY[ACT_TELEPHONE_TBL.PREFIX_LENGTH] OF CHAR;
PHONE_NUMBERS :
ARRAY[ACT_TELEPHONE_TBL.NBR_ORIGINATE_NUMBERS]
OF PHONE_NUMBER_RCD;
END;
TYPE ORIGINATE_PARAMETERS_RCD = PACKED RECORD
IF ACT_TELEPHONE_TBL.BIT_RATE = 2 THEN
Disclaimer: Page 10 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).
AMERICAN NATIONAL STANDARD C12.19-200x
ORIGINATE_BIT_RATE : UINT32;
END;
DIAL_DELAY : UINT8;
ORIGINATE_PHONE_NUMBERS : PHONE_NUMBERS_RCD;
WINDOWS :
ARRAY[ACT_TELEPHONE_TBL.NBR_ORIGINATE_WINDOWS]
OF WINDOW_RCD;
IF EXTENDED_STATUS
ANSWER_TIMEOUT : UINT8;
RETRY_INTERVAL : UNIT16;
MAX_RETRIES : UINT8;
END;
END;
TABLE 93 ORIGINATE_PARAMETERS_TBL = ORIGINATE_PARAMETERS_RCD;
Identifier Value Definition
STIME_RCD
HOUR 0..23 Hour of the day.
24..31 Unassigned.
MINUTE 0..59 Minute of hour.
60..63 Unassigned.
D_TIME Time in seconds since 00:00:00 local time.
DAYS_BFLD
SUNDAY FALSE This window does not start each Sunday.
TRUE This window does start each Sunday.
MONDAY FALSE This window does not start each Monday.
TRUE This window does start each Monday.
TUESDAY FALSE This window does not start each Tuesday.
TRUE This window does start each Tuesday.
WEDNESDAY FALSE This window does not start each Wednesday.
TRUE This window does start each Wednesday.
THURSDAY FALSE This window does not start each Thursday.
TRUE This window does start each Thursday.
FRIDAY FALSE This window does not start each Friday.
TRUE This window does start each Friday.
SATURDAY FALSE This window does not start each Saturday.
TRUE This window does start each Saturday.
WINDOW_RCD
BEGIN_WINDOW_TIME The time of day the window starts.
WINDOW_DURATION The duration of the window.
Disclaimer: Page 11 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).
AMERICAN NATIONAL STANDARD C12.19-200x
WINDOW_DAYS See DAYS_BFLD above. Defines the days that
a window can start.
PHONE_NUMBER_RCD
PHONE_NUMBER Phone number to use to place a call.
PHONE_NUMBERS_RCD
PREFIX This number will be inserted at the beginning of
every phone number before beginning dialing.
PHONE_NUMBERS An array of originate phone numbers.
ORIGINATE_PARAMETERS_RCD
ORIGINATE_BIT_RATE Bit rate at which the end device will originate a
call. Zero denotes an externally defined bit rate.
DIAL_DELAY 0..255 Delay in seconds the end device will wait before
dialing after going off-hook.
ORIGINATE_PHONE_NUMBERS See PHONE_NUMBER_RCD above.
WINDOWS An array of call originate windows.
ANSWER_TIMEOUT 0..255 Delay in seconds the end device will wait after
dialing before declaring no answer.
RETRY_INTERVAL 0..65535 Delay in seconds the end device will wait after a
failed call before trying again. May include a
random offset.
MAX_RETRIES 0..255 Absolute maximum number of attempts. Same
value used for all
ORIGINATE_PHONE_NUMBERS. This value
starts at zero for each unique call-out event.
9.10.5 Table 94 Originate Schedule Table
Table 94 Data Description
ORIGINATE_SCHEDULE_TBL (Table 94) is used to configure when and why a metering device
originates a call.
TYPE CTRL_BFLD = BIT FIELD OF UINT8
PRIMARY_PHONE_NUMBER : UINT(0..2);
FILLER : FILL(3..3);
SECONDARY_PHONE_NUMBER : UINT(4..6);
USE_WINDOWS : BOOL(7);
END;
Disclaimer: Page 12 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).
AMERICAN NATIONAL STANDARD C12.19-200x
TYPE RECURRING_DATES_RCD = PACKED RECORD
ORIGINATE_DATE : RDATE;
START_TIME : TIME;
ORIGINATE_CTRL : CTRL_BFLD;
END;
TYPE NON_RECURRRING_DATES_RCD = PACKED RECORD
ORIGINATE_DATE : DATE;
START_TIME : TIME;
ORIGINATE_CTRL : CTRL_BFLD;
END;
TYPE EVENTS_RCD = PACKED RECORD
ED_STD_STATUS1 : ED_STD_STATUS1_BFLD;
ED_STD_STATUS2 : ED_STD_STATUS2_BFLD;
ED_MFG_STATUS : ED_MFG_STATUS_RCD;
ORIGINATE_CTRL : CTRL_BFLD;
END;
TYPE WEEKLY_SCHEDULE_RCD = PACKED RECORD
DAYS : DAYS_BFLD;
START_TIME : TIME;
ORIGINATE_CTRL : CTRL_BFLD;
END;
TYPE ORIGINATE_SCHEDULE_RCD = PACKED RECORD
IF ACT_TELEPHONE_TBL.S_ANCHOR_DATE_FLAG THEN
S_ANCHOR_DATE : DATE;
END;
RECURRING_DATES :
ARRAY[ACT_TELEPHONE_TBL.NBR_RECURRING_DATES]
OF RECURRING_DATES_RCD;
NON_RECURING_DATES :
ARRAY[ACT_TELEPHONE_TBL.NBR_NON_RECURRRING_DATES]
OF NON_RECURRRING_DATES_RCD;
EVENTS : ARRAY[ACT_TELEPHONE_TBL.NBR_EVENTS]
OF EVENTS_RCD;
WEEKLY_SCHEDULES :
ARRAY[ACT_TELEPHONE_TBL.NBR_WEEKLY_SCHEDULES]
OF WEEKLY_SCHEDULE_RCD;
END;
TABLE 94 ORIGINATE_SCHEDULE_TBL = ORIGINATE_SCHEDULE_RCD;
Identifier Value Definition
CTRL_BFLD
PRIMARY_PHONE_NUMBER 0..7 Selection of the primary phone number to use to
originate the call. This value is an index into the
PHONE_NUMBERS array in the
ORIGINATE_PARAMETERS_TBL (Table 93).
Disclaimer: Page 13 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).
AMERICAN NATIONAL STANDARD C12.19-200x
Seven (7) indicates that no call should take
place.
SECONDARY_PHONE_NUMBER 0..7 Selection of the secondary phone
number to use to originate a call. This value is
an index into the PHONE_NUMBERS array in
the ORIGINATE_PARAMETERS_TBL (Table
93). Seven (7) indicates that no secondary
number is provided.
USE_WINDOWS FALSE An originate time window will not be used to
restrict the period available to place this call. The
call will be placed immediately.
TRUE An Originate time window will be used to restrict
the period available to place this call. Calls
originating outside a window will be delayed until
the next open window.
RECURRING_DATES_RCD
ORIGINATE_DATE Recurring date at which call originate
procedures should begin.
START_TIME Time at which call originate procedures should
begin.
ORIGINATE_CTRL See CTRL_BFLD above.
NON_RECURRRING_DATES_RCD
ORIGINATE_DATE Specific date at which a call originate procedure
should begin.
START_TIME Time at which a call originate procedure should
begin.
ORIGINATE_CTRL See CTRL_BFLD above.
EVENTS_RCD
ED_STD_STATUS1 Standard status events which initiate a call
originate procedure.
FALSE No call should take place for this status bit.
TRUE A call should take place if an event is detected
for this status bit.
ED_STD_STATUS2 Standard status events which initiate a call
originate procedure.
FALSE No call should take place for this status bit.
TRUE A call should take place if an event is detected
for this status bit.
ED_MFG_STATUS Manufacturer status events which initiate a call
originate procedure.
FALSE No call should take place for this status bit.
Disclaimer: Page 14 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).
AMERICAN NATIONAL STANDARD C12.19-200x
TRUE A call should take place if an event is detected
for this status bit.
ORIGINATE_CTRL See CTRL_BFLD above.
WEEKLY_SCHEDULE_RCD
DAYS Days of the week in which the call originate
procedure should begin.
START_TIME Time at which the call originate procedure
should begin.
ORIGINATE_CTRL See CTRL_BFLD above.
ORIGINATE_SCHEDULE_RCD
S_ANCHOR_DATE A separate telephone schedule anchor date
used with an RDATE recurring date using the
PERIOD/OFFSET mechanism. If this table
contains an anchor date it is used with RDATE.If
not present, and an anchor date is provided in
table 54 (CALENDAR_TBL) then RDATE will
use that anchor date. If neither anchor date is
present then the anchor date is defined by the
manufacturer.
RECURRING_DATES Array of recurring call origination dates.
NON_RECURING_DATES Array of non recurring call origination dates.
EVENTS Array of call origination trigger events.
WEEKLY_SCHEDULES Array of call origination days.
Disclaimer: Page 15 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).
AMERICAN NATIONAL STANDARD C12.19-200x
9.10.6 Table 95 Answer Parameters
Table 95 Data Description
ANSWER_PARAMETERS_TBL (Table 95) defines the answer configuration for receiving calls placed by
a utility host.
TYPE CALLER_ID_RCD = PACKED RECORD
CALLER_ID : ARRAY[ACT_TELEPHONE_TBL.CALLER_ID_LENGTH] OF
CHAR;
END;
TYPE ANSWER_PARAMETERS_RCD = PACKED RECORD
IF ACT_TELEPHONE_TBL.BIT_RATE = 2 THEN
ANSWER_BIT_RATE : UINT32;
END;
IF NOT ACT_TELEPHONE_TBL.NO_LOCKOUT_PARM THEN
LOCKOUT_DELAY : UINT8;
RETRY_ATTEMPTS : UINT8;
RETRY_LOCKOUT_TIME : UINT8;
END;
NBR_RINGS : UINT8;
IF ACT_TELEPHONE_TBL.NBR_ANSWER_WINDOWS > 0 THEN
NBR_RINGS_OUTSIDE : UINT8;
END;
CALLER_IDS : ARRAY[ACT_TELEPHONE_TBL.NBR_CALLER_ID]
OF CALLER_ID_RCD;
WINDOWS :
ARRAY[ACT_TELEPHONE_TBL.NBR_ANSWER_WINDOWS]
OF WINDOW_RCD;
END;
TABLE 95 ANSWER_PARAMETERS_TBL = ANSWER_PARAMETERS_RCD;
Identifier Value Definition
CALLER_ID_RCD
CALLER_ID Caller ID string. Incoming calls must have a
valid caller ID for the call to be answered.
ANSWER_PARAMETERS_RCD
ANSWER_BIT_RATE 0..232-1 Bit rate at which the end device will answer a
call. Zero indicates an externally defined bit rate.
LOCKOUT_DELAY 0..255 Number of minutes to lockout call answering
after detecting a voice call.
RETRY_ATTEMPTS 0..255 Maximum number of consecutive security
violations allowed before lockout.
Disclaimer: Page 16 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).
AMERICAN NATIONAL STANDARD C12.19-200x
RETRY_LOCKOUT_TIME 0..255 Minutes to lockout logons after security retry
attempts exceeded.
NBR_RINGS 0..255 The number of rings to wait before answering
while inside a time window. A value of 0 means
do not answer.
NBR_RINGS_OUTSIDE 0..255 The number of rings to answer while outside a
time window. A value of 0 means do not answer.
CALLER_IDS An array of caller IDs.
WINDOWS An array of answer time windows.
Disclaimer: Page 17 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).
AMERICAN NATIONAL STANDARD C12.19-200x
9.10.7 Table 96 Call Purpose
Table 96 Data Description
CALL_PURPOSE_TBL (Table 96) indicates the purpose for the current call originated by the end device.
TYPE CALL_PURPOSE_BFLD = BIT FIELD OF UINT16
POWER_OUTAGE :BOOL(0);
POWER_RESTORAL :BOOL(1);
SCHEDULED_CALL :BOOL(2);
STATUS_CALL :BOOL(3);
IMMEDIATE_CALL :BOOL(4);
FILLER :FILL(5..11);
MANUFACTURER_PURPOSES :UINT(12..15);
END;
TYPE CALL_PURPOSE_RCD = PACKED RECORD
CALL_PURPOSE : CALL_PURPOSE_BFLD;
CALL_TRIGGER_STATUS : ED_MODE_STATUS_RCD;
IF ACT_TELEPHONE_TBL.ID_IN_PURPOSE THEN
IDENT : IDENT_RCD;
END;
END;
TABLE 96 CALL_PURPOSE_TBL = CALL_PURPOSE_RCD;
Identifier Value Definition
CALL_PURPOSE_BFLD
POWER_OUTAGE This phone call was triggered by the detection of
a power outage.
POWER_RESTORAL This phone call was triggered by the detection of
a power restoration.
SCHEDULED_CALL This phone call is a normal call.
STATUS_CALL This phone call was triggered by an change in
the status record.
IMMEDIATE_CALL This phone call was triggered by an immediate
call procedure.
MANUFACTURER_PURPOSES This field if non-zero indicates that the
phone call was triggered by a manufacturer
defined purpose.
CALL_PURPOSE_RCD
CALL_PURPOSE See definitions of CALL_PURPOSE_BFLD
above.
IDENT Identity of the call originating device (Table 5).
Disclaimer: Page 18 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).
AMERICAN NATIONAL STANDARD C12.19-200x
CALL_TRIGGER_STATUS If the STATUS_CALL bit is TRUE then this field
indicates which status bit change(s) caused the
call. The field is in the image of
ED_MODE_STATUS_TBL.
Disclaimer: Page 19 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).
AMERICAN NATIONAL STANDARD C12.19-200x
9.10.8 Table 97 Call Status
Table 97 Data Description
CALL_STATUS_TBL (Table 97) indicates the status of the most recent call to each defined phone
number.
TYPE LAST_CALL_PURPOSE_RCD = PACKED RECORD
CALL_STATUS_ARRAY : UINT8;
IF EXTENDED_STATUS
CALL_PURPOSE : CALL_PURPOSE_BFLD;
CALL_TRIGGER_STATUS : ED_MODE_STATUS_RCD;
LAST_CALL_TIME : LTIME_DATE;
END;
END;
TYPE CALL_STATUS_RCD = PACKED RECORD
CALL_STATUS_ARRAY : ARRAY[ACT_TELEPHONE_TBL.NBR_ORIGINATE_NUMBERS]
OF LAST_CALL_PURPOSE_RCD;
END;
TABLE 97 CALL_STATUS_TBL = CALL_STATUS_RCD;
Identifier Value Definition
LAST_CALL_PURPOSE_RCD
CALL_STATUS_ARRAY Status or disposition of the most recent call to
each phone number. Entries are defined as
follows:
0 No phone call made
1 Phone call in progress
2 Dialing
3 Waiting for a connection
4 Communicating
5 Completed normally
6 Not completed
7 Not completed, Line busy
8 Not completed, No dial tone
9 Not completed, Line cut
10 Not completed, No connection
11 Not completed, No modem response
CALL_PURPOSE This field indicates the reason the most recent
call was attempted. See
CALL_PURPOSE_BFLD in Table 96 for
definition.
CALL_TRIGGER_STATUS From Table 96. This field indicates the reason
the most recent call was attempted. The field is
in the image of ED_MODE_STATUS_RCD
defined in Table 3.
LAST_CALL_TIME This field indicates the time and date the most
recent call attempt was made.
Disclaimer: Page 20 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).
AMERICAN NATIONAL STANDARD C12.19-200x
Disclaimer: Page 21 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).
AMERICAN NATIONAL STANDARD C12.19-200x
9.10.9 Table 98 Originate Status
Table 98 Data Description
ORIGINATE_STATUS_TBL (Table 98) indicates the status of the defined Originate Schedule.
TYPE ORIGINATE_STATUS_RCD = PACKED RECORD
IMMEDIATE_STATUS :
SET((ACT_TELEPHONE_TBL.NBR_ORIGINATE_NUMBER
S + 7)/ 8);
RECURRING_STATUS : SET((ACT_TELEPHONE_TBL.NBR_RECURRING_DATES +
7)/ 8);
NON_RECURRING_STATUS :
SET((ACT_TELEPHONETBL.NBR_NON_RECURRING_DATES + 7)/ 8);
WEEKLY_STATUS :
SET((ACT_TELEPHONE_TBL.NBR_WEEKLY_SCHEDULES + 7)/ 8);
CALL_TRIGGER_STATUS :
ARRAY(ACT_TELEPHONE_TBL.NBR_EVENTS) OF ED_MODE_STATUS_RCD;
WINDOW_STATUS :
SET((ACT_TELEPHONE_TBL.NBR_ORIGINATE_WINDOWS + 7)/ 8);
NEXT_RECURRING_DATE :
ARRAY[ACT_TELEPHONE_TBL.NBR_RECURRING_DATES]
OF LTIME_DATE_RCD;
NEXT_WEEKLY_SCHEDULE :
ARRAY[ACT_TELEPHONE_TBL.NBR_WEEKLY_SCHEDULES]
OF LTIME_DATE_RCD;
END;
TABLE 98 ORIGINATE_STATUS_TBL = ORIGINATE_STATUS_RCD;
Identifier Value Definition
IMMEDIATE_STATUS This is an array of bits. Each bit is set when an
immediate call is requested and is cleared when
the call is completed.
RECURRING_STATUS This is an array of bits. Each bit is set when the
recurring date occurs and is cleared when the
call is completed.
NON_RECURRING_STATUS This is an array of bits. Each bit is set when the
non-recurring date occurs and is cleared when
the call is completed.
WEEKLY_STATUS This is an array of bits. Each bit is set when the
Weekly Schedule occurs and is cleared when
the call is completed.
CALL_TRIGGER_STATUS A bit set in this record indicates that the
corresponding status bit change has occurred
and is configured as a call home reason. The bit
is cleared when the call is complete.
Disclaimer: Page 22 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).
AMERICAN NATIONAL STANDARD C12.19-200x
WINDOW_STATUS This is an array of bits.
Each bit is set when the corresponding window is
open, cleared when it is
closed.NEXT_RECURRING_DATE Array of
actual dates for the next occurrence of each
recurring date.
NEXT_WEEKLY_SCHEDULE Array of actual dates for the next occurrence of
each weekly schedule.
Disclaimer: Page 23 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).
AMERICAN NATIONAL STANDARD C12.19-200x
Note: The follow describes an additional standard procedure that is not defined in ANSI C12.19-1997.
Table 7. This highlighted text to not be included in the Working Document.
PROCEDURE 23 Clear Pending Call Status
This procedure causes the end device to immediately clear all pending call reasons in Table 98 Originate
Status.
TBL_PROC_NBR 23 Procedure number.
PARM_RCD Not used.
RESP_DATA_RCD Not used.
Disclaimer: Page 24 of 24
This contribution has been prepared to assist TableFest II. This document is offered as a basis for
discussion in accordance with the submission rules of TableFest II (ANSI C12.19-1997, IEEE 1377-
1997, MC-Requirements and TF9804-001).