TFT Router Audit
The TSS maintains the master database for text enabled Toll-Free Numbers. Each downstream TFT Router therefore has an effective copy of the master database by downloading the add and delete events as they are made available by the TSS. In other words, the TFT Router’s database can logically be thought of as an exact, read-only, copy of the master. For various reasons, the TFT Router DB may not exactly reflect the master database (for example, if there is a mistake in the TSS or in the TFT Router, or perhaps a DB recovery situation). It is realistic to acknowledge that mistakes can happen for unanticipated reasons and therefore the TFT Router’s local database must be periodically compared to the TSS master database. This comparison is known as an audit.
Since the TFT Router is the REST/JSON client, it is expected to periodically initiate an audit of its local database (monthly for example). The required frequency of this audit is left to the discretion of the TSS and is intentionally left out of this specification. However, the TSS is likely to maintain statistics regarding when the last fully completed audit occurred for each TFT Router. It is up to the TSS to enforce an audit if it does not occur. This can happen through any method the TSS decides, including responding to download requests with temporary errors, or TSS support personnel may contact the TFT Router vendor and inform them that an audit is necessary.
The TFT Router should confirm the expected frequency of audits with the TSS before it first connects to the TSS.