The
page shows a table containing all types of
exceptions (unexpected results) found while processing SDS to HLRR relay or
export functionality. Consequently, all fields do not always contain data. All
entries in the Relay Exception Log contain enough data so you can determine
what SDS data caused the exception.
Ideally, the Relay Exception Log would be empty, which
means SDS has all of the data required to create an HLRR provisioning command
and all of the required Network Entities are provisioned for the
HLR
Router. Because the most likely cause of an error would be associated with
relaying new provisioning commands to HLRR, the Relay Exception Log displays
column headings for exceptions created by pdbrelay. Deviations for other
creators include:
- If no command is relayed to HLRR, the Derived Relay
Request value is
None.
- If the Creator value is not equal to
pdbrelay, the Derived Relay Request value
from the SDS Command Log section is blank.