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 subscriber management. Specifically, for the resource Send Protocol and operation Send Cancel Location To All Currents Of IMSI, the node sends a cancellation request targeting all current sessions associated with a given IMSI (International Mobile Subscriber Identity).
Typical use cases include:
- Cancelling or terminating active subscriber sessions across network elements.
- Managing subscriber mobility or session state in telecom environments.
- Triggering network-level cancellation procedures based on subscriber identity.
For example, a telecom operator might use this node to cancel all active locations of a subscriber identified by their IMSI when the subscriber changes service plans or terminates service.
Properties
| Name | Meaning |
|---|---|
| Imsi | The International Mobile Subscriber Identity (IMSI) string identifying the subscriber. |
| Map Cancellation Type | The type of cancellation to send using the MAP protocol (e.g., specific cancellation reason). |
| Diameter Cancellation Type | The type of cancellation to send using the Diameter protocol (e.g., specific cancellation reason). |
| Reattach | Boolean flag indicating whether the subscriber should be reattached after cancellation. |
Output
The node outputs JSON data representing the response from the Summa API after attempting to send the cancel location request. This typically includes status information about the cancellation operation, any error messages, and confirmation details.
If the node handles binary data, it would relate to raw protocol messages or logs, but based on the provided code and context, the output is primarily structured JSON reflecting the API response.
Dependencies
- Requires an API key credential for authenticating with the Summa API.
- Depends on the
@digital-boss/n8n-designpatternspackage for resource-operation resolution and execution patterns. - Uses internal backend modules for HTTP communication (
HttpClient), state management (State), and operation methods (operations). - The node expects proper configuration of the Summa API credentials within n8n.
Troubleshooting
Common issues:
- Invalid or missing IMSI value will cause the operation to fail.
- Incorrect cancellation types may lead to API errors or unexpected behavior.
- Network connectivity problems can prevent successful API calls.
- Missing or invalid API credentials will result in authentication failures.
Error messages:
- Authentication errors indicate issues with the provided API key; verify and update credentials.
- Validation errors usually point to missing required parameters like IMSI or cancellation types.
- Timeout or connection errors suggest network issues; check connectivity and endpoint availability.
Resolving these typically involves verifying input parameters, ensuring valid credentials, and confirming network access to the Summa API endpoint.
Links and References
- Summa API Documentation (replace with actual URL if available)
- n8n documentation on Creating Custom Nodes
- Telecommunications standards for MAP protocol
- Telecommunications standards for Diameter protocol
