Summa icon

Summa

Consume Summa API (v.0.1.7)
Join our community

Actions182

Overview

This node, named "Summa," interacts with the Summa API to perform various operations related to telecommunications resources. Specifically, for the LTE Subscription resource and the Set EDRX Cycle Lengths operation, it allows users to configure the EDRX (Extended Discontinuous Reception) cycle lengths for a given LTE subscription identified by its IMSI (International Mobile Subscriber Identity). This is useful in scenarios where optimizing device power consumption and network signaling is important, such as managing IoT devices or mobile subscriptions that require customized sleep/wake cycles.

Practical example: A telecom operator can use this node to update the EDRX cycle length template for a subscriber’s LTE device to balance battery life and network responsiveness according to the subscriber's usage profile.

Properties

Name Meaning
Imsi The unique identifier of the LTE subscription (International Mobile Subscriber Identity) for which the EDRX cycle lengths will be set.
Edrx Cycle Lengths Template Name The name of the predefined template specifying the desired EDRX cycle lengths configuration to apply to the LTE subscription.

Output

The node outputs JSON data representing the result of the Set EDRX Cycle Lengths operation. This typically includes confirmation of the update, status messages, or any relevant response data from the Summa API indicating success or failure of the request.

If the node supports binary data output, it would generally relate to raw API responses or logs, but based on the provided code and context, the primary output is structured JSON.

Dependencies

  • Requires an active connection to the Summa API via an API key credential.
  • The node depends on internal helper classes for HTTP communication (HttpClient), state management (State), and operation resolution/execution (ResOpResolver, ResOpExecutor).
  • Proper configuration of the Summa API credentials within n8n is necessary for authentication and authorization.

Troubleshooting

  • Common issues:

    • Invalid or missing IMSI value may cause the API call to fail.
    • Incorrect or non-existent EDRX cycle lengths template name will likely result in an error from the API.
    • Network connectivity problems or incorrect API credentials will prevent successful execution.

  • Error messages:

    • Authentication errors indicate invalid or expired API credentials; verify and update the API key.
    • Validation errors from the API about IMSI or template name suggest checking input values for correctness.
    • Timeout or network errors require checking internet connectivity and API endpoint availability.

Links and References

Discussion