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, including the IMSI resource with the "Get Enhanced Coverage" operation. The node facilitates querying enhanced coverage information related to a given IMSI (International Mobile Subscriber Identity).
Typical use cases include telecommunications or mobile network management scenarios where users need to retrieve detailed coverage data for specific subscriber identities. For example, a telecom operator might use this node to check enhanced network coverage details for troubleshooting or service optimization.
Properties
| Name | Meaning |
|---|---|
| Imsi | The IMSI (International Mobile Subscriber Identity) string for which enhanced coverage information is requested. This property is required for the "Get Enhanced Coverage" operation under the IMSI resource. |
Output
The node outputs JSON data containing the enhanced coverage information associated with the provided IMSI. The exact structure depends on the Summa API response but generally includes coverage metrics, status, and possibly geographic or network-related details relevant to the IMSI.
If the node supports binary data output, it would typically represent any non-JSON payloads returned by the API; however, based on the provided code and context, the primary output is JSON-formatted coverage data.
Dependencies
- Requires an active connection to the Summa API, authenticated via an API key credential configured in n8n.
- Uses internal helper classes for HTTP requests, state management, and operation resolution.
- The node depends on the
summaApicredential being properly set up and tested within n8n. - No additional external services beyond the Summa API are indicated.
Troubleshooting
Common Issues:
- Missing or invalid IMSI input will cause the node to fail or return errors.
- Incorrect or expired API credentials will prevent successful API calls.
- Network connectivity issues may result in timeouts or unreachable host errors.
Error Messages:
- Authentication failures typically indicate problems with the API key credential; verify and update as needed.
- Validation errors on the IMSI parameter suggest that the input does not meet expected format requirements.
- API response errors should be checked against Summa API documentation for specific error codes and messages.
Links and References
- Summa API official documentation (refer to your organization's internal or public API docs).
- n8n documentation on creating and using API credentials.
- Telecommunications standards for IMSI and coverage concepts for deeper understanding of the domain.