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 subscriptions and services. Specifically, for the resource IMS Subscription and operation Set GBA User Sec Settings Template To IMS Subscription, the node sets a GBA (Generic Bootstrapping Architecture) user security settings template on an IMS subscription identified by an IMSI number.
Typical use cases include automating configuration of IMS subscriptions in telecom environments where GBA security templates need to be applied programmatically. For example, a telecom operator might use this node to assign specific security templates to subscribers' IMS profiles as part of provisioning or updating subscriber data.
Properties
| Name | Meaning |
|---|---|
| Guss Template Name | The name of the GBA User Security Settings (GUSS) template to apply to the IMS subscription. This is a required string input. |
| Imsi | The IMSI (International Mobile Subscriber Identity) identifying the IMS subscription to which the GUSS template will be applied. This is a required string input. |
Output
The node outputs JSON data representing the result of the operation performed on the IMS subscription. This typically includes confirmation of the template being set, status messages, or any relevant response data from the Summa API.
If the node supports binary data output, it would relate to any files or binary responses returned by the API, but based on the provided code and context, the primary output is JSON structured data reflecting the API response.
Dependencies
- Requires an active connection to the Summa API via an API key credential configured in n8n.
- Uses internal helper classes for HTTP requests, state management, and operation resolution/execution.
- The node depends on the
summaApicredential for authentication. - No additional external dependencies are explicitly required beyond the Summa API access.
Troubleshooting
- Common issues:
- Invalid or missing API credentials can cause authentication failures.
- Incorrect IMSI or GUSS template names may lead to errors or no changes applied.
- Network connectivity problems to the Summa API endpoint.
- Error messages:
- Authentication errors usually indicate invalid or expired API keys; verify and update credentials.
- Validation errors may occur if required properties are missing or malformed; ensure all required inputs are correctly provided.
- API response errors should be checked against Summa API documentation for specific error codes and messages.
Links and References
- Summa API official documentation (not provided here, but users should consult their API docs).
- n8n documentation on creating and using custom nodes.
- Telecommunications standards on IMS and GBA for deeper understanding of the domain concepts.