Roaming agreement must exist within CostGuard to process calls for a roaming partner.
Common Cause
This roaming agreement (“Serving SID-Home SID” in CDMA) or (“Serving PMN-Home PMN” in GSM) is unknown to RateBill.
Common Resolution(s)
Actions you can take to resolve the problem:
The roaming agreement for this serving/home pair may have been disconnected more than ‘X days’ (mentioned below) ago. In order to bill this usage, the disconnect date of that roaming agreement may need to be pushed forward
This roaming agreement may have never been set up. In this case, set up a new roaming agreement in CostGuard under the appropriate Roaming Partner account.
If the roaming agreement appears to be bogus in the usage record and this occurs frequently, it’s possible that the CDR 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 roaming agreements that have been disconnected before the “X days ago” setting. This allows the system to perform efficiently by not clogging up RateBill caches with roaming agreements 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 roaming agreement with this SID pair (or PMN pair) has been active during the past X days.