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 the "Send Protocol" resource with the "Send Cancel Location VLR" operation. This particular operation likely sends a cancellation request related to a mobile subscriber's location in a Visitor Location Register (VLR), which is part of mobile network infrastructure.
Typical use cases include telecom operators or service providers who need to programmatically manage subscriber sessions or cancel location registrations in their network systems. For example, when a subscriber deregisters or moves out of a service area, this node can send a cancellation message to update the network state accordingly.
Properties
| Name | Meaning |
|---|---|
| Imsi | The International Mobile Subscriber Identity (IMSI) of the subscriber to cancel location for. |
| Serving Node | Identifier of the serving node (e.g., VLR or MSC) where the subscriber is currently registered. |
| Cancellation Type | Type of cancellation to perform; specific options are not listed but typically indicate the reason or method of cancellation. |
Output
The node outputs JSON data representing the response from the Summa API after executing the requested operation. This output typically includes confirmation of the cancellation request, status codes, messages, or any error details returned by the API.
If the node supports binary data output, it would represent raw protocol messages or logs, but based on the provided code and properties, the primary output is structured JSON data reflecting the API response.
Dependencies
- Requires an API key credential for authenticating with the Summa API.
- Uses internal helper classes for HTTP requests, state management, and operation resolution.
- The node depends on the
@digital-boss/n8n-designpatternspackage for operation execution patterns. - Proper configuration of the Summa API credentials within n8n is necessary.
Troubleshooting
Common Issues:
- Invalid or missing IMSI or Serving Node values will likely cause the API call to fail.
- Incorrect cancellation type may result in rejection or errors from the API.
- Network connectivity issues or invalid API credentials will prevent successful communication.
Error Messages:
- Authentication failures usually indicate incorrect or expired API keys.
- Validation errors from the API might mention missing or malformed parameters like IMSI or Serving Node.
- Timeout or connection errors suggest network problems or misconfigured endpoints.
Resolutions:
- Verify all required input fields are correctly filled.
- Ensure the API key credential is valid and has proper permissions.
- Check network access and endpoint URLs configured in the credential settings.
Links and References
- Summa API official documentation (not provided here, but recommended to consult for detailed parameter options and response formats).
- n8n documentation on creating and using custom nodes.
- Telecom standards references for VLR and cancellation procedures (for deeper understanding of the domain context).