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, specifically supporting various telecommunication-related resources and operations. For the HLR Subscription resource with the Set PDPs operation, this node allows users to configure Packet Data Protocol (PDP) contexts for a subscriber identified by their IMSI (International Mobile Subscriber Identity). This is useful in scenarios where network operators or service providers need to update or set data session parameters on a subscriber's profile within the Home Location Register (HLR).
Practical examples include:
- Setting multiple PDP contexts for a mobile subscriber to enable different types of data services.
- Sending raw JSON data to configure PDPs directly if advanced customization is needed.
- Managing subscriber data sessions programmatically as part of automated workflows in telecom management.
Properties
| Name | Meaning |
|---|---|
| Imsi | The IMSI (International Mobile Subscriber Identity) of the subscriber whose PDPs are set. |
| Send Json | Boolean flag indicating whether to send raw JSON data (true) or use structured PDP templates (false). |
| Json Data | Raw JSON data representing PDP configurations; required if "Send Json" is true. |
| Pdp Templates | A collection of PDP template values; used when "Send Json" is false to define PDPs in a structured way. |
Output
The node outputs JSON data representing the response from the Summa API after attempting to set the PDPs for the specified IMSI. This typically includes status information about the operation, such as success confirmation or error details.
If binary data were involved (not indicated here), it would represent files or media related to the operation, but this node focuses on JSON responses only.
Dependencies
- Requires an API key credential for authenticating with the Summa API.
- Uses an HTTP client internally to communicate with the Summa backend.
- Needs proper configuration of the Summa API credentials within n8n.
- Relies on the Summa API version defined in the node (version referenced in the description).
Troubleshooting
- Common issues:
- Invalid or missing IMSI value will cause the operation to fail.
- Incorrect JSON format when "Send Json" is enabled can lead to parsing errors.
- Network or authentication failures due to invalid API credentials.
- Error messages:
- Authentication errors indicate problems with the provided API key; verify and re-enter credentials.
- Validation errors may occur if required fields are missing or incorrectly formatted.
- API response errors should be checked against Summa API documentation for specific 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 custom nodes.
- General info on IMSI and PDP contexts in mobile networks for background understanding.