Summa icon

Summa

Consume Summa API (v.0.1.7)

Actions182

SS Subscription SOAP → Create Call Line Identification Presentation For SS Subscription

AI-generated

Overview

This node integrates with the Summa API to manage SS (Supplementary Service) Subscription SOAP operations, specifically enabling the creation of a Call Line Identification Presentation for an SS Subscription. It is useful in telecom or network management scenarios where automated provisioning and configuration of supplementary services on subscriber lines are required. For example, a telecom operator can use this node to programmatically activate or update call line identification presentation settings on subscriber accounts via the Summa platform.

Properties

Name Meaning
Activation State The activation status of the service; options: NOT_ACTIVE, ACTIVE_AND_OPERATIVE.
Id Unique identifier for the subscription or service instance.
Induction State Indicates whether the service has been induced; options: NOT_INDUCED, INDUCED.
Override Category Whether to override the existing category; options: FALSE, TRUE.
Provisioning State The provisioning status of the service; options: NOT_PROVISIONED, PROVISIONED.
Registration State Registration status of the subscription; options: REGISTERED, NOT_REGISTERED, ERASED, NOT_APPLICABLE.
Supplementary Service Type The type of supplementary service being configured (string).
Hlr Subscription ID Identifier for the HLR (Home Location Register) subscription associated with this service.
Operator ID Identifier of the operator managing the subscription/service.

Output

The node outputs JSON data representing the result of the Create Call Line Identification Presentation operation for the SS Subscription. This typically includes confirmation of the operation's success, details of the updated subscription state, and any relevant metadata returned by the Summa API. The output does not explicitly mention binary data, so it is assumed to be purely JSON structured.

Dependencies

  • Requires an active connection to the Summa API.
  • Needs an API key credential for authentication with the Summa platform.
  • The node uses internal helper classes for HTTP requests and state management.
  • No additional external dependencies beyond the Summa API and its credentials.

Troubleshooting

  • Common Issues:
    • Invalid or missing API credentials will cause authentication failures.
    • Providing incorrect or incomplete property values (e.g., missing required fields like id or operatorId) may lead to API errors.
    • Network connectivity issues can prevent successful communication with the Summa API.
  • Error Messages:
    • Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
    • Validation errors from the API suggest missing or malformed input parameters; ensure all required properties are correctly set.
    • Timeout or connection errors imply network problems; check internet access and API endpoint availability.

Links and References

Discussion