Summa icon

Summa

Consume Summa API (v.0.1.7)
Join our community

Actions182

Overview

This node integrates with the Summa API to manage telecommunication subscription services. Specifically, the "Create Call Line Identification Restriction For SS Subscription" operation allows users to configure call line identification restrictions on a supplementary service subscription via a SOAP interface.

Typical use cases include:

  • Telecom operators managing subscriber call line identification settings.
  • Automating provisioning or updating of call restrictions for subscribers.
  • Enforcing privacy or regulatory compliance by controlling how caller ID is presented.

For example, an operator might use this node to activate or deactivate call line identification restrictions for a subscriber’s supplementary service, specifying states like activation, induction, and registration.

Properties

Name Meaning
Activation State The activation status of the restriction; options: NOT_ACTIVE, ACTIVE_AND_OPERATIVE.
Induction State The induction status indicating if the restriction has been induced; options: NOT_INDUCED, INDUCED.
Presentation Mode The mode of presentation for the call line identification restriction (string value).
Provisioning State The provisioning status of the restriction; options: NOT_PROVISIONED, PROVISIONED.
Registration State The registration status of the restriction; options: REGISTERED, NOT_REGISTERED, ERASED, NOT_APPLICABLE.
Supplementary Service Type The type of supplementary service to which the restriction applies (string).
SS Subscription ID Identifier of the supplementary service subscription to modify (string).
Operator ID Identifier of the operator performing the operation (string).

Output

The node outputs JSON data representing the result of the create call line identification restriction operation. This typically includes confirmation of the applied settings, status codes, or error messages returned by the Summa API.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the Summa API, authenticated via an API key credential.
  • The node depends on internal helper classes for HTTP requests, state management, and operation resolution.
  • Proper configuration of the Summa API credentials in n8n is necessary before using this node.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect or missing required properties (e.g., SS Subscription ID, Operator ID) may result in validation errors.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • Authentication errors indicate invalid or expired API keys; verify and update credentials.
    • Validation errors suggest missing or incorrect input parameters; ensure all required fields are correctly filled.
    • API response errors may include detailed messages from the Summa backend; review these for specific causes.

Links and References

Discussion