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 various telecommunication subscription services. Specifically, for the SS Subscription resource and the Add Call Forwarding Custom Supplementary Service operation, it allows users to add a custom call forwarding service to a subscriber's profile.
Typical use cases include telecom operators or service providers who want to programmatically configure call forwarding settings on subscribers' accounts, such as forwarding calls to another number under specific conditions.
For example, a user can specify a subscriber by their IMSI (International Mobile Subscriber Identity), define the forwarding number (FTN), select the type of call forwarding service, and decide whether the calling party should be notified when the call is forwarded.
Properties
| Name | Meaning |
|---|---|
| Imsi | The International Mobile Subscriber Identity identifying the subscriber to modify. |
| Ftn | The forwarding telephone number where calls will be redirected. |
| Call Forward Service Type | The type of call forwarding service to apply (e.g., unconditional, busy, no reply). |
| Notify To Calling Party | Boolean flag indicating if the calling party should be notified about the call forwarding. |
Output
The node outputs JSON data representing the result of the API call to add the call forwarding supplementary service. This typically includes confirmation details such as success status, any identifiers related to the created service, or error messages if the operation failed.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Summa API via an API key credential.
- The node depends on the
summaApicredential configured in n8n for authentication. - Internally uses HTTP client utilities and operation resolvers to communicate with the Summa backend.
Troubleshooting
Common Issues:
- Invalid or missing IMSI or FTN values may cause the API to reject the request.
- Incorrect call forward service type values not supported by the API.
- Authentication failures due to invalid or expired API credentials.
- Network connectivity issues preventing communication with the Summa API.
Error Messages:
- Errors returned from the API will typically indicate invalid parameters or authorization problems.
- If the "Notify To Calling Party" flag is set incorrectly, the API might return validation errors.
Resolutions:
- Verify all required fields are correctly filled and formatted.
- Ensure the API key credential is valid and has necessary permissions.
- Check network access and endpoint availability.
- Consult API documentation for valid call forward service types.
Links and References
- Summa API Documentation (replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- Telecom standards for Call Forwarding Services