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
The node named "Summa" is designed to interact with the Summa API (version indicated dynamically). It provides a flexible interface to perform various operations on different resources related to telecommunications data and services. Specifically, for the Resource "Operator" and Operation "Load Common Sim Security," this node fetches or loads security-related information associated with a common SIM security profile under a specified operator.
This node is beneficial in scenarios where telecom operators or service providers need to automate the retrieval and management of SIM security configurations across their network infrastructure. For example, it can be used to programmatically load security settings for SIM cards managed by a particular operator, facilitating integration with backend systems or workflows that require up-to-date SIM security data.
Properties
| Name | Meaning |
|---|---|
| Operator Name | The name of the operator whose common SIM security profile you want to load. |
| Common Sim Security Name | The identifier or name of the common SIM security profile to be loaded for the operator. |
Output
The node outputs JSON data representing the result of the "Load Common Sim Security" operation. This typically includes detailed information about the common SIM security profile associated with the specified operator, such as security parameters, keys, or configuration details relevant to SIM card security.
If the node supports binary data output (not explicitly shown in the provided code), it would represent any binary payloads related to the SIM security data, but based on the static analysis, the primary output is structured JSON data.
Dependencies
- Requires an active connection to the Summa API, authenticated via an API key credential.
- The node depends on internal helper classes and methods for HTTP communication (
HttpClient), state management (State), and operation resolution/execution (ResOpResolver,ResOpExecutor). - The user must configure the node with valid credentials for the Summa API.
- No additional external dependencies are indicated beyond the Summa API and its authentication.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will prevent successful communication with the Summa API.
- Incorrect operator or common SIM security names may lead to empty results or errors indicating that the requested resource was not found.
- Network connectivity issues could cause timeouts or failed requests.
Error Messages:
- Authentication failures typically indicate invalid or expired API tokens; verify and update credentials accordingly.
- Resource not found errors suggest checking the spelling and existence of the operator and common SIM security names.
- General HTTP errors should be investigated by reviewing API endpoint availability and network status.
Links and References
- Summa API Documentation (Replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes
- General information on SIM security concepts: SIM Card Security
Note: The above summary is based solely on static analysis of the provided source code and property definitions without runtime execution or access to external documentation.