Summa icon

Summa

Consume Summa API (v.0.1.7)
Join our community

Actions182

Overview

This node integrates with the Summa API to manage LTE subscriptions, specifically allowing users to add a custom LTE ODB (Operator Determined Barring) entry. It is useful in telecom environments where managing subscriber barring settings dynamically is required, such as enabling or disabling certain call restrictions or packet services for specific subscribers.

A practical example would be a telecom operator who wants to programmatically update barring rules for a subscriber identified by their IMSI (International Mobile Subscriber Identity), either by sending a raw JSON payload or by specifying individual barring parameters through structured fields.

Properties

Name Meaning
Imsi The IMSI of the LTE subscription to which the custom ODB will be added.
Send Json Boolean flag indicating whether to send the barring data as a raw JSON object (true) or via structured additional fields (false).
Json Data The raw JSON data representing the custom LTE ODB configuration. Required if "Send Json" is true.
Additional Fields A collection of optional structured fields used to define the custom LTE ODB when "Send Json" is false. Includes:
- Id: Numeric identifier.
- Barring Of Outgoing Calls: Multiple entries of field-value pairs defining outgoing call barring.
- Operator Specific Barring Dto: String for operator-specific barring details.
- Barring Of Packet Oriented Services: String defining packet service barring.

Output

The node outputs JSON data representing the response from the Summa API after attempting to add the custom LTE ODB entry. This typically includes confirmation of success or failure and any relevant metadata returned by the API.

If binary data were involved, it would represent related files or attachments, but this node focuses on JSON responses only.

Dependencies

  • Requires an API key credential for authenticating with the Summa API.
  • Uses an HTTP client internally to communicate with the Summa backend.
  • The node depends on the Summa API being accessible and properly configured with valid credentials.

Troubleshooting

  • Common Issues:

    • Invalid or missing IMSI value will cause the operation to fail.
    • Incorrect JSON format when "Send Json" is enabled can lead to parsing errors.
    • Missing required fields in the additional fields collection when not sending JSON may cause incomplete requests.
    • Network or authentication failures due to invalid API credentials.

  • Error Messages:

    • Errors related to authentication usually indicate invalid or expired API keys; verify and update credentials.
    • JSON parsing errors suggest malformed JSON input; validate JSON syntax before sending.
    • API response errors might include detailed messages from the Summa API; review these to adjust request parameters accordingly.

Links and References

  • Summa API Documentation (replace with actual URL)
  • n8n HTTP Request Node documentation for understanding underlying HTTP communication.
  • General telecom resources on LTE subscription management and ODB concepts.

Discussion