These are the Service Control Point (SCP) limits that should be taken into consideration when building complex record (complex Customer Records (CADs) (also known as CRs) and complex Template Records (TADs) (also known as TRs).
- A CR and TR cannot have more than 255 branches per Call Processing Record (CPR) node due to an inherent limit in the SCP network. For additional details, refer to the section titled: Customer Record Branches.
- A CR and TR cannot be more than 170,000 bytes in size in terms of the length of the message that is transmitted to the SCPs. This message length is determined at the time the record is being downloaded to the SCPs. If the actual message size for a record is larger than 170,000 bytes, the status of the record will be set to FAILED. The TFNRegistry™ will indicate the failure or rejection of the record by sending a message to the Controlling (current, old) Resp Org’s generic email address.
- When creating a record, make sure the message size (as calculated per the formula in the table below) that is downloaded by TFNRegistry to the SCPs is below 170,000 bytes. However, please note that even if TFNRegistry allows a record with message size below 170,000 bytes to be sent to the SCPs, the SCPs may have their limitations (e.g., based on the SCP’s storage limitations) that may result in one or more SCPs rejecting a record, resulting in the record remaining in SENDING status.
- The following formula can be used to estimate the length of a CR’s or TR’s message that is to be sent to the SCPs.
For more information regarding SCP statuses for a record, please click here.
Estimated Record Size Formula:
# bytes estimate = 91+ (24 * # rows) + (10 * # decision nodes * # rows) + (X * # LAD values)
Notes for the above table:
- The constant ‘X’ can be either ‘6’ or ‘3’. Set X to 6 if the LAD types are primarily 6# or 10#; otherwise set X to 3. Setting X to 6 yields a high estimate whereas setting X to 3 yields a low estimate.
- # decision nodes = # of CPR column headers that are deciding factors for routing, which means CPR columns that are not any of the following types: Carrier, Tel#, Announcement, Switch or Go To.
- This calculation is to be used as an estimate only, and results greater than or less than 170,000 based on this formula will not guarantee that the ACTUAL size is greater than or less than 170,000, and therefore will not guarantee that the record is accepted or rejected by TFNRegistry or the SCPs.
Customer Record Limits: The figure below provides a sample of a CPR with branches. A branch results when a preceding node contains a single value and is followed by a row, or rows, of unique values. A CR cannot have more than 255 branches per node and a node may contain LAD labels which may additionally consist of up to 255 LAD values. The LAD label is considered to be a single entry of the branch although it may contain up to 255 values.
Disclaimer: Any images in this article are intended to be used as a guide for educational purposes only and they may differ slightly from the Production Environment.
In this example, there are five branches that stem from AB and AK. Each row is a branch, provided the rows are not duplicated. In this example, the State column consists of three branches: AB, AK and OTHER. However, in the 6 Digit column the values in the rows change and create three branches from AB and two branches from AK. Three branches stem from the 6 Digit 403-001. No additional branches stem from 403-200, 403-201 or *LABEL, two branches from 403-227, and no additional branches from AK-OTHER.
Learn more about this topic in the following video!
Disclaimer: This video is intended to be used as a guide for educational purposes only. Pages shown in the video may differ slightly from the Production Environment.