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 integrates with the Summa API to manage IMS (IP Multimedia Subsystem) subscriptions, specifically allowing users to add a Private User Identity to an IMS subscription. This operation is useful in telecommunications scenarios where managing user identities within IMS subscriptions is required, such as provisioning new private identities for subscribers or updating existing subscription details.
Practical examples include:
- Adding a new private identity to a subscriber's IMS profile.
- Configuring authentication parameters and public user identities associated with an IMS subscription.
- Automating IMS subscription management workflows in telecom service platforms.
Properties
| Name | Meaning |
|---|---|
| Send Json | Boolean flag to choose whether to send raw JSON data directly or use structured fields. |
| Json Data | Raw JSON input representing the private user identity data to be sent when "Send Json" is true. |
| Additional Fields | Collection of optional structured fields used when "Send Json" is false, including: |
| - Private Identity | The private user identity string to add. |
| - Nass Line Identifier | Identifier related to the network access server line. |
| - Max Bad Counter Passwd | Maximum allowed count for bad password attempts. |
| - Algorithm Name | Name of the algorithm used for authentication or encryption. |
| - Contact Address | Contact address associated with the private user identity. |
| - Secret Name | Name of the secret used for authentication. |
| - Public User Identities | Multiple entries of public user identities linked to this private identity. Each entry has a "Value". |
| - Loose Route Indication | Indicator for loose routing configuration. |
| - Priviledged Sender Indication | Indicator if the sender is privileged. |
| - Auth Scheme | Authentication scheme name. |
| - Ims Subscription Id | Numeric identifier of the IMS subscription to which the private user identity will be added. |
Output
The node outputs JSON data representing the result of the Add Private User Identity operation. This typically includes confirmation of the addition, any identifiers assigned by the backend, and status information returned by the Summa API.
If binary data were involved (not indicated here), it would represent files or media related to the IMS subscription, but this node focuses on JSON-based data exchange.
Dependencies
- Requires an active connection to the Summa API via an API key credential configured in n8n.
- The node depends on the
summaApicredential for authentication. - Uses internal helper classes for HTTP requests and operation resolution.
- No additional external services beyond the Summa API are required.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrectly formatted JSON in the "Json Data" property can lead to request errors.
- Missing required fields when not using raw JSON may cause validation errors from the API.
- Network connectivity issues to the Summa API endpoint.
Error Messages:
- Authentication errors: Verify that the API key credential is correctly set up and valid.
- Validation errors: Check that all required fields are provided and correctly formatted.
- Request timeouts or connection errors: Ensure network access to the Summa API is available.
Links and References
- Summa API Documentation (Replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- General IMS Subscription Concepts: 3GPP IMS Overview
Note: The above summary is based solely on static analysis of the provided source code and property definitions.