---
title: "CDR047 - Data events that are to be outcollected to a GSM roaming partner require       a SGSN address"
slug: "cdr047-data-events-to-be-outcollected-to-gsm-roaming-partner-require-sgsn-addres"
updated: 2026-08-10T20:19:32Z
published: 2026-08-10T20:19:32Z
canonical: "help.idibilling.com/cdr047-data-events-to-be-outcollected-to-gsm-roaming-partner-require-sgsn-addres"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.idibilling.com/llms.txt
> Use this file to discover all available pages before exploring further.

# CDR047 - Data events that are to be outcollected to a GSM roaming partner require
      a SGSN address

Override is allowed

| Name | Data events that are to be outcollected to a GSM roaming partner require a SGSN address. |
| --- | --- |
| Common Cause | A piece of information that is vital to successful outcollect of a GSM Data event is absent. The record will likely be returned by the Clearinghouse if the record is outcollected. |
| Common Resolution(s) | Actions you can take to resolve the problem: - 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. - To outcollect the usage record despite this problem, choose Override Rule on the usage record. If this is done frequently, consider a change to Unbillable Rules for this Unbillable Code |
| Details | A field that is required in the TAP (outcollect) record is not present in the usage record. If a TAP record were to be generated and outcollected, it is likely it would be returned from the clearinghouse. If this happens frequently, the CDRs in question should be investigated. |