MIN must have a corresponding entry in the SIDNPARange table.
Common Cause
The MIN specified in this wireless (CDMA) record cannot be resolved to a home SID.
Common Resolution(s)
Actions you can take to resolve the problem:
Often this SPIN indicates that the SIDNPARange and SID tables need to be reloaded – contact IDI BCT to see if a newer table can be uploaded. If not, entries can be manually added to the SID and SID NPA Range tables using Applications/ Backoffice Management/ Roaming/ SID Maintenance and SID Line Ranges.
If this rarely occurs, the CDR may be bad or malformed. If so, it can be left alone (it will eventually age and no longer be visible) - or it can be purged immediately if desired.
If the usage record should be billed anyway, choose Override Rule on the usage record. If this is done frequently, consider a change to Unbillable Rules for this Unbillable Code. Note that ignoring lookup failures can have undesirable downstream repercussions – although some event type processing doesn’t care about MIN, in others the MIN is fundamental to determining the correct roaming agreement.
Details
CDMA voice and data usage records usually specify a MIN; the MIN should resolve to a Home SID as per the system’s SIDNPARange table. The Home SID indicates if this record should be direct billed or outcollected. In each case, the Home SID must be known to CostGuard in order to locate the correct roaming agreement. In this case, this is a CDMA usage record and the Home SID (as per the MIN) could not be found in the SIDNPARange table.