Understanding SoR Configuration Options
The SoR configuration database schema uses the following options to customize the application behavior:
- Maximum attempts
- Indicates the maximum number of registration attempts that might be rejected before the subscriber is allowed to subscribe through any MNO. This value limits the amount of time the subscription process might take.
- Maximum number of rejections per MNO
- Sets how often can Registration attempts by a subscriber over a certain non-preferred VPLMN be rejected before the subscriber is allowed to register through this non-preferred MNO. This is needed in case a subscriber does not receive coverage by a preferred MNO, then it preferable to reduce the time needed for a successful registration.
- Rejection code
- Indicates a specific (Experimental-) Result Code to be used when the DSR with SoR application must send an Answer message with error to the downstream peer. If this is not set, the ULA message is sent with an error code. If a rejection code is defined, the ULA is sent with an Experimental-Result AVP.
- Rejection text
- Defines the text to be added in an Error-Message AVP to indicate what caused the error.
- Unknown VPLMN
- Indicates how to handle ULRs messages that arrive from VPLMNs that are not listed explicitly or implicitly in the SoR_Profile table. The options are Reject/Accept.
A VPLMN is considered unknown if the included MCCMNC value in the ULR is not included explicitly or implicitly in the SoR_Profile table. See Configuring SoR_Profile Tables. Explicit inclusion indicates in this context that the MCC values contained in the MCCMNC value of the ULR message is included in the MCC column of the SoR_Profile table and one of the rows listing this MCC includes the MNC in the MNC column. Implicit inclusion indicates in this context that the MCC values contained in the MCCMNC value of the ULR message is included in the MCC column of the SoR_Profile table and while none of these rows includes the MNC of the VPLMN, one of the rows listing this MCC includes an asterisk (*) in the MNC column.
These values are stored in SoR configuration tables.
To track a users's registration history, the SoR application keeps subscriber-related records in a UDR Generic State database indexed by the subscriber's IMSI. This is accessible from the page.