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 LTE Subscription resource and the Get EDRX Cycle Lengths operation, it retrieves information about the EDRX (Extended Discontinuous Reception) cycle lengths associated with a given LTE subscription identified by an IMSI (International Mobile Subscriber Identity).
This node is useful in scenarios where telecom operators or service providers need to query detailed LTE subscription parameters programmatically, such as monitoring device power-saving configurations or optimizing network resource allocation.
Example use case:
A network engineer wants to fetch the EDRX cycle lengths for a specific subscriber's LTE connection to analyze device sleep intervals and improve battery life estimations.
Properties
| Name | Meaning |
|---|---|
| Imsi | The International Mobile Subscriber Identity (IMSI) string identifying the LTE subscription for which to retrieve EDRX cycle lengths. This is a required input. |
Output
The node outputs JSON data containing the EDRX cycle length details for the specified LTE subscription. The exact structure depends on the Summa API response but typically includes fields describing the cycle lengths and related parameters.
If the node supports binary data output, it would represent any non-JSON payloads returned by the API; however, based on the provided code and context, the output is primarily JSON.
Dependencies
- Requires an active connection to the Summa API via an API key credential configured in n8n.
- The node uses an HTTP client internally to communicate with the Summa backend services.
- Proper configuration of the Summa API credentials within n8n is necessary for authentication and authorization.
Troubleshooting
- Missing or invalid IMSI: Since IMSI is required, omitting it or providing an incorrect value will likely cause errors or empty responses. Ensure the IMSI is correctly formatted and valid.
- Authentication failures: If the API key credential is missing, expired, or invalid, the node will fail to authenticate with the Summa API. Verify the credential setup in n8n.
- Network issues: Connectivity problems between n8n and the Summa API endpoint can cause request timeouts or failures. Check network access and proxy settings if applicable.
- API errors: The Summa API might return error messages for unsupported IMSIs or internal server errors. Review the error details and consult Summa API documentation for resolution steps.
Links and References
- Summa API Documentation (Replace with actual URL if available)
- n8n HTTP Request Node Documentation (for understanding underlying HTTP communication)