Summa icon

Summa

Consume Summa API (v.0.1.7)

Actions182

Overview

This node integrates with the Summa API to perform various operations related to telecommunications data management. Specifically, for the HLR Subscription resource and the Add GMLC Number operation, it allows users to add a Gateway Mobile Location Center (GMLC) number to a subscriber's HLR (Home Location Register) subscription record.

This is useful in scenarios where location services need to be configured or updated for mobile subscribers, such as enabling location-based services or emergency call routing.

Practical example:
A telecom operator wants to update the location service settings for a subscriber by adding a new GMLC number associated with their IMSI (International Mobile Subscriber Identity). This node facilitates that update via the Summa API.

Properties

Name Meaning
Imsi The International Mobile Subscriber Identity of the subscriber to whom the GMLC number will be added.
Address The GMLC number address to be added.
Address Type The type of the address (e.g., IP address, MSISDN, etc.).
Address Nature The nature of the address, describing its format or usage context.
Numbering Plan The numbering plan used for the address (e.g., ISDN, data numbering plan).

Output

The node outputs JSON data representing the result of the Add GMLC Number operation. This typically includes confirmation of the update, any relevant status messages, and possibly the updated subscription details.

If the operation involves binary data (not indicated here), it would be summarized accordingly, but this operation appears to deal solely with JSON data.

Dependencies

  • Requires an active connection to the Summa API, authenticated via an API key credential.
  • The node depends on the summaApi credential to authenticate requests.
  • No additional environment variables are explicitly required beyond the API credentials.
  • Uses internal helper classes for HTTP communication and operation resolution.

Troubleshooting

  • Common issues:

    • Invalid or missing IMSI value may cause the API to reject the request.
    • Incorrect formatting of the address or mismatched address type/nature/numbering plan can lead to errors.
    • Authentication failures if the API key credential is invalid or expired.
    • Network connectivity issues preventing access to the Summa API endpoint.
  • Error messages:

    • "Authentication failed" — Verify the API key credential is correctly configured and valid.
    • "Invalid IMSI" — Check that the IMSI provided matches the expected format.
    • "Address format error" — Ensure the address and its associated properties conform to the API requirements.
    • "Operation not supported" — Confirm that the resource and operation names are correct and supported by the API version.

Links and References

Discussion