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 SS (Supplementary Service) Subscriptions via SOAP. Specifically, the "Create Basic Supplementary Service For SS Subscription" operation allows users to create and configure a basic supplementary service linked to an existing SS subscription.
Typical use cases include telecom operators or service providers who need to programmatically manage supplementary services such as call waiting, call forwarding, or other value-added services on subscriber accounts. For example, activating call waiting for a subscriber or setting the provisioning state of a supplementary service can be automated using this node.
Properties
| Name | Meaning |
|---|---|
| Activation State | The activation status of the supplementary service. Options: NOT_ACTIVE, ACTIVE_AND_OPERATIVE |
| Induction State | Indicates whether the supplementary service is induced or not. Options: NOT_INDUCED, INDUCED |
| Provisioning State | The provisioning status of the supplementary service. Options: NOT_PROVISIONED, PROVISIONED |
| Registration State | The registration status of the supplementary service. Options: REGISTERED, NOT_REGISTERED, ERASED, NOT_APPLICABLE |
| Supplementary Service Type | The type/name of the supplementary service to create (e.g., CallWaiting). |
| SS Subscription ID | Identifier of the SS subscription to which the supplementary service will be added. |
| Operator ID | Identifier of the operator managing the subscription/service. |
Output
The node outputs JSON data representing the result of the creation operation for the basic supplementary service. This typically includes confirmation details such as the status of the request, identifiers, and any relevant metadata returned by the Summa API.
If the operation involves binary data (not indicated here), it would represent related files or attachments, but in this case, the output is purely JSON-based.
Dependencies
- Requires an active connection to the Summa API, authenticated via an API key credential.
- The node depends on the
summaApicredential configured in n8n for authentication. - Uses internal helper classes for HTTP requests, state management, and operation resolution/execution.
- No additional external dependencies beyond the Summa API and its credentials.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect SS Subscription ID or Operator ID may lead to errors indicating that the subscription or operator was not found.
- Providing invalid values for states (activation, induction, provisioning, registration) may cause validation errors from the API.
Error Messages:
- Authentication errors: Check that the API key credential is correctly set up and valid.
- Validation errors: Ensure all required fields are provided and conform to expected options.
- Network or timeout errors: Verify network connectivity to the Summa API endpoint.
Resolving these typically involves verifying input parameters, ensuring correct credential configuration, and confirming network access.
Links and References
- Summa API Documentation (Replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes
- General SOAP API integration concepts and best practices.