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 supports multiple resources and operations, including one called "Operator" with an operation "Remove Common Sim Security". This particular operation likely removes a specified common SIM security configuration associated with an operator.
This node is beneficial in telecom or mobile network management scenarios where automated control over operator configurations is needed. For example, it can be used to programmatically remove outdated or compromised SIM security profiles from an operator's settings, helping maintain secure and up-to-date network configurations.
Properties
| Name | Meaning |
|---|---|
| Operator Name | The name of the operator from which the common SIM security will be removed. |
| Common Sim Security Name | The name of the common SIM security profile that should be removed from the operator. |
These properties are required inputs when using the "Remove Common Sim Security" operation under the "Operator" resource.
Output
The node outputs JSON data representing the result of the executed operation. While the exact structure is not explicitly detailed in the source code, typically such output would include confirmation of the removal action, status codes, messages, or any error details returned by the Summa API.
No binary data output is indicated or expected for this operation.
Dependencies
- Requires an active connection to the Summa API, authenticated via an API key credential.
- The node depends on internal helper classes for HTTP requests, state management, and operation resolution/execution.
- The user must configure the node with valid credentials for the Summa API.
- No additional external services beyond the Summa API are referenced.
Troubleshooting
Common issues:
- Invalid or missing API credentials will prevent successful communication with the Summa API.
- Incorrect operator or common SIM security names may cause the API to return errors indicating the target resource was not found.
- Network connectivity problems could lead to request timeouts or failures.
Error messages:
- Authentication errors suggest checking the provided API key or credential setup.
- Not found or invalid parameter errors indicate verifying the input property values for correctness.
- General API errors should be reviewed against Summa API documentation for specific troubleshooting steps.
Links and References
- Summa API official documentation (not provided in source; consult your API provider)
- n8n documentation on creating and configuring custom nodes
- Relevant telecom or SIM security management resources for understanding operator configurations