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," interacts with the Summa API to perform various operations related to telecommunications data management. Specifically, for the IMSI resource and the "Set LTE And HLR Teleservice" operation, it updates or configures LTE and HLR teleservice templates associated with a given IMSI (International Mobile Subscriber Identity). This is useful in telecom environments where managing subscriber services and configurations programmatically is required.
Practical examples include:
- Updating the teleservice templates for a mobile subscriber identified by their IMSI.
- Automating the configuration of LTE and HLR teleservices during subscriber provisioning or maintenance.
- Integrating with backend systems to synchronize subscriber service settings.
Properties
| Name | Meaning |
|---|---|
| Imsi | The International Mobile Subscriber Identity (IMSI) string identifying the subscriber. |
| Lte Teleservices Template Name | The name of the LTE teleservices template to apply to the subscriber's profile. |
| Hlr Teleservices Template Name | The name of the HLR teleservices template to apply to the subscriber's profile. |
Output
The node outputs JSON data representing the result of the operation performed on the Summa API. This typically includes confirmation of the update or details about the applied teleservice templates for the specified IMSI. The exact structure depends on the API response but generally contains status information and any relevant metadata.
No binary data output is indicated.
Dependencies
- Requires an active connection to the Summa API via an API key credential configured in n8n.
- Uses an HTTP client internally to communicate with the Summa backend.
- The node depends on the Summa API version as indicated in its description (version referenced dynamically).
Troubleshooting
Common issues:
- Invalid or missing IMSI value will cause the operation to fail.
- Incorrect template names for LTE or HLR teleservices may lead to errors from the API.
- Network connectivity problems or invalid API credentials will prevent successful execution.
Error messages:
- Authentication failures indicate issues with the provided API key credential; verify and reconfigure if necessary.
- Validation errors from the API usually specify which input property is incorrect; double-check IMSI and template names.
- Timeout or network errors suggest connectivity issues; ensure the n8n instance can reach the Summa API endpoint.
Links and References
- Summa API Documentation (replace with actual URL)
- n8n HTTP Request Node documentation for understanding underlying HTTP communication: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/