Actions182
- LTE Subscription Actions
- Get Access Restriction Data For LTE
- Get Apn Info
- Get Lte Profile
- Set Lte Tele Service
- Get Lte Regional Subscription
- Get Scef Permissions
- Set APN Assignations To LTE Subscription
- Get EDRX Cycle Lengths
- Add Apn
- Get V2X Subscription Data
- Set Scef Permissions
- Set EDRX Cycle Lengths
- Set Access Restriction Data For LTE
- Set APNs To LTE Subscription
- Set APN Address Assignations To LTE Subscription
- Add LTE Subscription
- Set SCS Permissions
- Get SCS Permissions
- Get LTE ODB
- Add Custom LTE ODB
- Set LTE ODB Profile
- Get APN Assignations From LTE Subscription
- Remove APN Address Assignation From LTE Subscription
- Sim Swap Actions
- WLAN Subscription Actions
- HLR Subscription Actions
- Set HLR Profile
- Set PDP Address Assignation
- Set HLR Regional Subscription
- Remove PDP
- Remove GMLC Number
- Get HLR Teleservice
- Set MSRN Profile
- Remove PDP Assignations
- Set GMLC Numbers
- Get USSD Profile
- Set Camel Configuration
- Add Custom HLR ODB
- Add Camel Service
- Add GMLC Number
- Get GMLC Numbers
- Remove Camel Service
- Remove HLR Regional Subscription
- Set CSE Notification Profile
- Remove MSRN Profile
- Get ODB
- get HLR Profile
- Add PDP
- Get Camel Info
- Set HLR Teleservice
- Set SS Options
- Sim Swap Direct Without Remove
- Get Camel Configuration
- Clear All GMLC Number
- Set PDPs
- Apply Custom HLR ODB Settings
- Get Bearer Service
- Get Access Restriction Data Profile
- Get HLR Regional Subscription
- Remove PDP Address Assignation
- Add USSD Profile
- Set PDP Assignations
- Remove USSD Profile
- Set Access Restriction Data Profile
- Apply Subscription Settings
- Get PDP Info
- Get PDP Assignations
- Set HLR ODB Profile
- Remove CSE Notification Profile
- Get CSE Notification Profile
- Get HLR ODB
- Get MSRN Profile
- SS Subscription Actions
- Add Supplementary Service By Msisdn
- Add Call Forwarding Custom Supplementary Service
- Get All Supplementary Services By MSISDN
- Remove All Supplementary Service
- Remove All Supplementary Service By MSISDN
- Get Call Forward Information
- Get All Supplementary Services
- Remove Supplementary Service
- Add Supplementary Service
- Add Call Forwarding Custom Supplementary Service By MSISDN
- Get Call Forward Information By MSISDN
- Remove Supplementary Service By MSISDN
- SS Subscription SOAP Actions
- Get Imsi By Imsi
- Get Msisdn By Msisdn
- Create Basic Supplementary Service For SS Subscription
- Create Call Forward Supplementary Service For SS Subscription
- Create Calling Name Presentation For SS Subscription
- Create Call Line Identification Presentation For SS Subscription
- Create Call Line Identification Restriction For SS Subscription
- MSISDN Actions
- Subscriber Actions
- IMS Subscription Actions
- Send Cancel Location To Current VLR Of IMSI
- Add Transparent Data To IMPU
- Remove Transparent Data From IMPU
- Get IMS Volatile Data
- Add Service Profile To IMPU
- Add Public User Identity
- Add Private User Identity
- Remove Service Profile From IMPU
- Set GBA User Sec Settings Template To IMS Subscription
- Remove Public User Identity
- Get GBA User Sec Settings Template
- Get GBA User Sec Settings
- Delete IMS Subscription For IMSI
- IMSI Actions
- CRUD Operator Actions
- Operator Actions
- Sim Actions
- Send Protocol Actions
- Send Cancel Location MME
- Send RTR For IMPI
- Send Cancel Location To Current SGSN Of Imsi
- Send Cancel Location To Current VLR Of IMSI
- Send Cancel Location VLR
- Send Cancel Location SGSN
- Send Diameter Cancel Location SGSN
- Send Cancel Location To Current SGSN
- Send Cancel Location To All Currents Of IMSI
- Send Cancel Location To Current MME Of IMSI
- Send RTR For IMPU
- Send Cancel Location To Current VLR
- Send Cancel Location To Current MME
- CRUD PLMN Actions
- Templates Actions
Overview
This node, named "Summa," is designed to interact with the Summa API (version indicated dynamically). It supports multiple resources and operations related to telecommunications services management. Specifically, for the HLR Subscription resource and the Set HLR Teleservice operation, the node allows users to configure teleservice settings on a Home Location Register (HLR) subscription by specifying an IMSI and a teleservices template name.
Common scenarios where this node is beneficial include telecom operators or service providers who need to automate the management of subscriber services, such as enabling or modifying teleservices associated with a subscriber's HLR record. For example, setting a teleservice template for a subscriber identified by their IMSI to control call forwarding, barring, or other network services.
Properties
| Name | Meaning |
|---|---|
| Imsi | The International Mobile Subscriber Identity (IMSI) uniquely identifying the subscriber whose HLR teleservice settings are to be modified. This is a required string input. |
| Teleservices Template Name | The name of the teleservices template to apply to the HLR subscription. This template defines the set of teleservices (e.g., call forwarding, call barring) to be configured. This is a required string input. |
Output
The node outputs data in JSON format representing the result of the Set HLR Teleservice operation. This typically includes confirmation of the applied changes, status messages, or any relevant response data from the Summa API indicating success or failure of the teleservice configuration.
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 data reflecting the operation's outcome.
Dependencies
- Requires an active connection to the Summa API via an API key credential (referred generically as "an API key credential").
- The node uses an HTTP client internally to communicate with the Summa backend.
- Proper configuration of the Summa API credentials within n8n is necessary before execution.
- No additional external dependencies beyond the Summa API and its authentication are indicated.
Troubleshooting
Common Issues:
- Invalid or missing IMSI value will cause the operation to fail since IMSI is required to identify the subscriber.
- Incorrect or non-existent teleservices template names may lead to errors or no changes being applied.
- Authentication failures due to invalid or expired API credentials.
- Network connectivity issues preventing communication with the Summa API.
Error Messages and Resolutions:
- Authentication Error: Verify that the API key credential is correctly configured and has not expired.
- Invalid IMSI: Ensure the IMSI is correctly formatted and corresponds to an existing subscriber.
- Template Not Found: Confirm that the teleservices template name exists in the system and is spelled correctly.
- API Request Failed: Check network connectivity and API endpoint availability.
Links and References
- Summa API Documentation (Replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes
- General Telecom Concepts: Home Location Register (HLR)
- Understanding IMSI: International Mobile Subscriber Identity