Normal routing consists of querying the DN database (for E.164 numbers) or IMSI database (for E.212 numbers), then routing the message to the preferred or mated Network Entity for the DN or IMSI that was queried. If normal routing fails, exception routing is performed. Exception routing consists of querying the Exception Routing table and routing the message based on the CdPA TT, the CdPA SSN, and the DPC of the incoming message.
HLR supports up to 256 exception routing records. When normal and exception routing fail HLR Router is unable to route a message.
The page allows you to view the current rules provisioned for routing a request when that subscriber is not found in the database, edit or delete an existing exception routing rule, or to insert a new exception routing rule.
This page is only available when logged into an SOAM.