This service number (a.k.a. MDN, MSISDN) is unknown to RateBill.
Common Resolution(s)
Actions you can take to resolve the problem:
The service with this service number may have been disconnected more than ‘X days’ (mentioned below) ago. In order to bill this usage, the disconnect date of that service may need to be pushed forward.
This service number may have never been assigned to a service. In this case, set up a new service with this service number in CostGuard under the appropriate Subscriber.
If the service number appears to be bogus in the usage record and this occurs frequently, it’s possible that the CDR may be bad or malformed or it isn’t being parsed correctly. Contact IDI BCT; it’s possible that a software update is required.
Details
There is a ‘loadable window’ when loading usage, which causes the system to ignore any services that have been disconnected before the “X days ago” setting. This allows the system to perform efficiently by not clogging up RateBill caches with services that should never see any more usage, because they have been disconnected for a healthy length of time. In this case the call start time of this usage is recent (i.e. within the past X days as per the “Ignore overlaps older than X days" setting) but no service with this service number has been active during the past X days.