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). Specifically, for the resource Send Protocol and operation Send Diameter Cancel Location SGSN, it sends a Diameter protocol message to cancel the location of an SGSN (Serving GPRS Support Node) identified by an IMSI. This operation is typically used in mobile network management scenarios where subscriber session or location information needs to be invalidated or updated in the network.
Practical examples include:
- Cancelling the current SGSN location of a subscriber when they move to a different serving node.
- Triggering reattachment procedures by setting flags indicating whether the subscriber should reattach.
- Managing subscriber mobility and session state in LTE or 3G networks via Diameter signaling.
Properties
| Name | Meaning |
|---|---|
| Imsi | The International Mobile Subscriber Identity (IMSI) identifying the subscriber uniquely. |
| Cancellation Type | The type of cancellation to perform; defines how the location cancellation is processed. |
| Reattach Required Flag | Indicates whether the subscriber is required to reattach after cancellation (e.g., "true" or "false"). |
| Serving Node | Identifier of the current serving node (SGSN) from which the location cancellation is sent. |
Output
The node outputs JSON data representing the response from the Summa API after sending the Diameter Cancel Location SGSN message. This output typically includes status information about the request, any error messages, and confirmation details of the cancellation operation.
If the node supports binary data output, it would represent raw protocol messages or logs, but based on the provided code and context, the output is primarily JSON structured data 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 client communication, state management, and operation methods.
- The node expects proper configuration of the Summa API credentials within n8n.
Troubleshooting
Common issues:
- Invalid or missing IMSI value will cause the API call to fail.
- Incorrect cancellation type or flag values may result in unexpected behavior or errors from the API.
- Network connectivity problems or incorrect API credentials will prevent successful communication with the Summa API.
Error messages:
- Authentication failures indicate issues with the provided API key credential; verify and update credentials as needed.
- Validation errors from the API usually point to malformed or missing input properties; ensure all required fields are correctly filled.
- Timeout or connection errors suggest network issues; check connectivity and endpoint availability.
Links and References
- Diameter Protocol Overview
- Mobile Network SGSN Functionality
- Summa API documentation (refer to your organization's internal API docs for detailed usage)