SCP Administration (SID) Field Descriptions |
||
Field/Object |
Descriptions |
Valid Values/Actions |
SCP ID |
A mandatory key data entry field. The first 2 characters must be alphabetic and conveys the CCS Network ID in which the SCP resides. |
Unique 4-character alphanumeric identifier of the SCP. A maximum of 16 SCPs per network is allowed and it is also configurable. The last 2 characters convey the Entity number of the SCP and must be a number in the range of 01-16. This is user- specified, but cannot be modified, once created. |
Node ID |
Represents the location and function of telecommunications equipment. |
11-character alphanumeric identifier. (CLLI Location Code). The 11-character CLLI code follows:
|
Templates Supported |
It is used to indicate if the SCP supports the Customer Records Template Feature. This field is populated by the user. Valid values can be Yes or No. |
A Boolean indicator |
Queue State |
It conveys whether or not Customer Record (CAD) update messages are to be queued for transmission to this SCP. The Queue State defined on SID is for the CMSDB application. When first defining an SCP for CMSDB application type, this field is TFNRegistry™ generated, protected and set to “Not Queue”. If the application type is NODE, this field is N/A or not applicable. Queue means that SCP is up and running and can receive the messages for input. Whereas Not Queue means that SCP is not up and running and can’t receive the messages for input. This field can only be modified to change “Queue” to “Not Queue” for CMSDB application when appropriate. |
Valid values:
|
Version |
Data field that identifies the version number of the SCP application software. |
TFNRegistry generated field.
|
Interface Manual |
Data field that identifies the interface manual of the TFNRegistry to SCP interface specifications that the SCP application supports. |
TFNRegistry generated field. |
Application |
It defines the name of the SCP Application.
|
TFNRegistry generated field. Valid Values include the following values:
|