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 perform various operations related to telecommunications subscriptions and services. Specifically, for the "SS Subscription" resource and the "Remove Supplementary Service By MSISDN" operation, it removes a supplementary service associated with a given MSISDN (mobile number). This is useful in scenarios where a telecom operator or system administrator needs to deactivate or remove additional services linked to a subscriber's phone number.
Practical examples include:
- Removing call forwarding or call barring services from a subscriber.
- Deactivating value-added services that are no longer needed by the user.
- Managing subscription changes programmatically via API calls.
Properties
| Name | Meaning |
|---|---|
| Msisdn | The mobile number (MSISDN) of the subscriber whose supplementary service will be removed. |
| Template Name | The name of the template defining the parameters or configuration for the removal request. |
| Supplementary Service Typel | The type identifier of the supplementary service to be removed. |
Output
The node outputs JSON data representing the result of the removal operation. This typically includes status information indicating success or failure, any messages returned by the Summa API, and possibly details about the affected subscription or service state after removal.
If the node supports binary data output, it would represent any raw response or files returned by the API, but based on the provided code and context, the primary output is structured JSON.
Dependencies
- Requires an API key credential for authenticating with the Summa API.
- Uses an HTTP client internally to communicate with the Summa backend services.
- Depends on the n8n environment having this credential configured and tested.
- The node relies on bundled internal modules for managing state, resolving operations, and executing requests.
Troubleshooting
Common issues:
- Invalid or missing MSISDN input can cause the API call to fail.
- Incorrect template name or supplementary service type may lead to errors or no action taken.
- Authentication failures if the API key credential is not set up correctly.
- Network connectivity problems affecting communication with the Summa API.
Error messages:
- Authentication errors usually indicate invalid or expired credentials; reconfigure the API key.
- Validation errors often point to missing or malformed input properties; verify all required fields.
- API response errors might include service-specific codes; consult Summa API documentation for details.
Links and References
- Summa API official documentation (not provided here, but recommended to consult for detailed API usage).
- n8n documentation on creating and using custom nodes.
- General telecom supplementary services concepts for understanding service types and templates.