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," integrates with the Summa API to perform various operations related to telecommunications data. Specifically, for the resource LTE Subscription and operation Get Access Restriction Data For LTE, it retrieves access restriction information associated with a given LTE subscription identified by an IMSI (International Mobile Subscriber Identity). This is useful in scenarios where you need to verify or audit access restrictions applied to LTE subscribers, such as network operators managing subscriber permissions or compliance checks.
Practical examples include:
- Fetching access restriction data to determine if a subscriber is barred from certain network services.
- Integrating subscriber access control data into broader telecom management workflows.
- Automating audits of LTE subscription restrictions for regulatory compliance.
Properties
| Name | Meaning |
|---|---|
| Imsi | The International Mobile Subscriber Identity (IMSI) string that uniquely identifies the LTE subscription for which access restriction data will be retrieved. This property is required. |
Output
The node outputs JSON data containing the access restriction details for the specified LTE subscription. The exact structure depends on the Summa API response but typically includes fields describing the types of restrictions applied, their status, and any relevant metadata.
If the node supports binary data output, it would represent supplementary data related to the LTE subscription or access restrictions; however, based on the provided code and context, the primary output is JSON-formatted access restriction information.
Dependencies
- Requires an active connection to the Summa API via an API key credential configured in n8n.
- Uses internal helper classes for HTTP requests and state management.
- Depends on the
@digital-boss/n8n-designpatternspackage for resource-operation resolution and execution patterns. - No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common Issues:
- Invalid or missing IMSI parameter: Ensure the IMSI is correctly provided and formatted.
- Authentication failures: Verify that the API key credential is valid and has necessary permissions.
- Network connectivity problems: Confirm that the n8n instance can reach the Summa API endpoint.
- Unexpected API responses: Check if the Summa API service is operational and the requested resource/operation is supported.
Error Messages:
- Authentication errors typically indicate invalid credentials; reconfigure the API key.
- Parameter validation errors suggest missing or malformed input properties like IMSI.
- HTTP request failures may require checking network settings or API availability.
Links and References
- Summa API Documentation (Replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- IMSI Wikipedia article for understanding the identifier: https://en.wikipedia.org/wiki/International_Mobile_Subscriber_Identity