Audit
The RouteLink Server maintains the master CRN/CPR database. Each downstream RouteLink Client therefore has an effective copy of the master database by downloading the add and delete events as they are made available by the server. As discrepancies are found events are placed on the queue and the RouteLink Client downloads the corrective event.
List of discrepancies:
CRN missing in RouteLink Client
CRN present in RouteLink Client but not in RouteLink Server
Mismatched ROR
Mismatched CPR
Audit Message Flows
The sub chapters that follow describe the message flow for the audit for success and failure conditions. Lastly, this chapter enumerates the specific request and response messages used by the audit.
Starting an Audit
The RouteLink Server decides when an audit is necessary by placing an audit event for a specific prefix on the RouteLink Client's event queue. The following diagram describes the events and flow of messages that occur when a prefix audit for 800 is started. It's important to understand that there will be an audit for each 8xx prefix that is valid at the time of the audit. Currently these prefixes include 800, 833, 844, 855, 866, 877, 888, and 0 (zero). Numbers starting with a 0 denote template records. Please Note: This list will be expanded as new toll-free prefixes are added such as 822.
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.