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" integrates with the Summa API (version indicated in the code) to perform various operations on telecom-related resources. Specifically, for the HLR Subscription resource and the Remove Camel Service operation, this node allows users to remove a CAMEL (Customized Applications for Mobile network Enhanced Logic) service from a subscriber's HLR (Home Location Register) subscription.
This operation is useful in telecom environments where managing subscriber services dynamically is required, such as disabling certain value-added services or modifying subscriber profiles remotely.
Practical example:
A telecom operator wants to deactivate a specific CAMEL service template associated with a subscriber identified by their IMSI (International Mobile Subscriber Identity). Using this node, they can specify the subscriber's IMSI, the template name of the CAMEL service, and the type of CAMEL service to be removed, automating the process via n8n workflows.
Properties
| Name | Meaning |
|---|---|
| Imsi | The IMSI (International Mobile Subscriber Identity) of the subscriber whose CAMEL service will be removed. This uniquely identifies the subscriber. |
| Template Name | The name of the CAMEL service template that should be removed from the subscriber's HLR subscription. |
| Camel Service Type | The type/category of the CAMEL service to remove. This specifies which kind of CAMEL service is targeted. |
Output
The node outputs JSON data representing the result of the Remove Camel Service operation. This typically includes confirmation of success or failure, status messages, and any relevant details returned by the Summa API about the removal action.
No binary data output is indicated or expected for this operation.
Dependencies
- Requires an active connection to the Summa API, authenticated via an API key credential configured in n8n.
- The node depends on internal helper classes for HTTP requests, state management, and operation resolution/execution.
- Proper configuration of the Summa API credentials within n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Invalid or missing IMSI: The operation requires a valid IMSI; ensure it is correctly provided.
- Incorrect template name or CAMEL service type: If these do not match existing entries in the backend system, the removal will fail.
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions.
- Network or connectivity problems with the Summa API endpoint.
Error messages:
- Authentication failures usually indicate invalid or expired API credentials.
- Validation errors may occur if required parameters are missing or malformed.
- Backend API errors might return messages indicating the CAMEL service was not found or could not be removed.
To resolve these, verify all input parameters, check API credentials, and confirm the availability and correctness of the target CAMEL service.
Links and References
- CAMEL Services Overview – General information about CAMEL in mobile networks.
- Summa API documentation (not publicly linked here) – Consult your organization's API docs for detailed usage and parameter definitions.