Overview

This node interacts with the Billing Booth One API to perform operations related to suppliers, specifically testing supplier CDR (Call Detail Record) configurations. It allows users to verify if a supplier supports CDRs and to configure various parsing options such as parser type, match type, header presence, delimiter, and custom JavaScript code for validation and parsing. This is useful in telecom billing or call data processing scenarios where accurate CDR handling is critical.

Use Case Examples

1. Testing if a supplier supports CDRs by enabling or disabling the feature.
2. Configuring the CDR parser to handle CSV or TSV formats.
3. Setting custom JavaScript code to validate the CDR file format or parse each row for complex CDR structures.

Properties

Output

JSON

• json - Response data from the Billing Booth One API after testing the supplier CDR configuration, including success or error details.

Dependencies

• Billing Booth One API key credential

Troubleshooting

• Error indicating missing or invalid binary property when expecting file input; ensure the binary property name is correct and the file is provided.
• Errors related to missing routing information for the specified resource and operation; verify the resource and operation names are correct and supported.
• API errors returned from the Billing Booth One service, which may include authentication issues, invalid parameters, or server errors; check API credentials and input parameters.

Links

• Billing Booth One API Documentation - Official API documentation for Billing Booth One, useful for understanding available endpoints and parameters.