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 in the code). Specifically, for the resource CRUD PLMN and operation Get Total All PLMN By Operator Id, it retrieves aggregated data about all Public Land Mobile Networks (PLMNs) associated with a given operator ID. This can be useful in telecommunications scenarios where an operator needs to analyze or report on the total number of PLMNs they manage.
Practical examples include:
- Telecom operators querying their network infrastructure details.
- Systems that monitor or audit mobile network configurations.
- Integration workflows that require fetching summarized PLMN data by operator.
Properties
| Name | Meaning |
|---|---|
| Operator Id | The unique identifier of the operator whose total PLMN count is to be retrieved. This is a required string input. |
Output
The node outputs JSON data containing the total count or summary information of all PLMNs associated with the specified operator ID. The exact structure depends on the Summa API response but generally includes fields representing counts or lists of PLMNs.
If the node supports binary data output, it would typically represent related files or reports; however, based on the provided code and context, this node primarily outputs JSON data.
Dependencies
- Requires connection to the Summa API via an API key credential (referred generically as "an API key credential").
- Uses internal helper classes for HTTP requests, state management, and operation resolution.
- The node expects the user to configure the Summa API credentials within n8n before execution.
Troubleshooting
- Missing or invalid Operator Id: Since the operator ID is required, ensure it is provided and correctly formatted.
- Authentication errors: If the API key credential is missing, expired, or incorrect, the node will fail to authenticate with the Summa API.
- API connectivity issues: Network problems or incorrect endpoint configuration may cause request failures.
- Unexpected API responses: Changes in the Summa API or malformed responses could lead to errors during execution.
To resolve these:
- Verify the operator ID input.
- Check and update the API authentication credentials.
- Ensure network connectivity to the Summa API endpoint.
- Review API documentation for any changes affecting the response format.
Links and References
- Summa API official documentation (not provided in source, check your organization's resources)
- n8n documentation on creating and using API credentials
- Telecommunications standards on PLMN and operator identifiers