Opencell

Overview

The Opencell Mediation: Register CDR List operation allows you to submit a list of Call Detail Records (CDRs) to the Opencell mediation API for registration. This is typically used in telecom or billing scenarios where batches of usage records (CDRs) need to be processed, rated, and stored. The node supports both manual entry of CDRs and JSON input, making it flexible for integration with various data sources.

Common use cases:

• Importing call or event records from external systems into Opencell for further processing.
• Automating the batch upload of CDRs as part of ETL (Extract, Transform, Load) workflows.
• Integrating with upstream systems that generate CDRs, such as switches, mediation platforms, or custom applications.

Example:
A telecom operator receives daily CDR files from its network. Using this node, they can automate the ingestion of these records into Opencell for rating and billing.

---

Properties

Name	Type	Meaning
Authentication	options	Selects the authentication method: Basic Authentication or OAuth2.
JSON Input	boolean	If enabled, allows direct input of CDRs as a JSON array; otherwise, CDRs are entered via UI fields.
CDRs	fixedCollection	Manual entry of one or more CDRs, each with a "CDR Code". Used when JSON Input is disabled.
CDRs (JSON)	json	Raw JSON array of CDRs. Used when JSON Input is enabled.
Additional Fields	collection	Optional settings for how the CDR list is processed:
	- Mode	options
	- Return EDRs	boolean
Body Content Type	hidden	Always set to "multipart-form-data" (internal use).

---

Output

• The output is a JSON object containing the response from the Opencell API after registering the CDR list.
• The structure of the output depends on the Opencell API's response, but typically includes:
  • Status information about the registration process.
  • Details about any errors encountered.
  • Optionally, a list of EDR (Event Detail Record) IDs if "Return EDRs" is enabled.

Example output:

{
  "status": "SUCCESS",
  "message": "CDR list registered successfully.",
  "edrIds": [12345, 12346, 12347]
}

Note: Actual fields may vary depending on Opencell configuration and API version.

---

Dependencies

• External Service: Requires access to an Opencell instance with the mediation API enabled.
• Authentication: Needs valid credentials for either Basic Authentication or OAuth2, configured in n8n credentials.
• n8n Configuration: No special environment variables required beyond standard credential setup.

---

Troubleshooting

Common Issues:

• Invalid Credentials: If authentication fails, ensure your credentials are correct and have sufficient permissions.
• Malformed JSON Input: When using JSON Input, invalid JSON will cause parsing errors. Ensure the input is a valid JSON array.
• API Errors: If the Opencell API returns an error (e.g., due to invalid CDR format), check the error message for details.

Error Messages:

• "Invalid credentials (unknown error)" or "Username/password error. Error code : ..."
  → Check your authentication settings.
• "Unable to parse JSON"
  → Verify that your CDRs (JSON) field contains valid JSON.
• "Server response: ..."
  → Review the detailed server message for hints on what went wrong (e.g., missing required fields).

---

Links and References

• Opencell Documentation
• n8n Docs: Creating Custom Nodes
• CDR (Call Detail Record) Wikipedia

---