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 telecommunication subscription services. Specifically, the "Add Call Forwarding Custom Supplementary Service By MSISDN" operation allows users to add a custom call forwarding service for a subscriber identified by their MSISDN (Mobile Station International Subscriber Directory Number). This is useful in scenarios where telecom operators or service providers want to programmatically configure call forwarding settings on subscribers' lines.
Practical examples include:
- Automatically setting up call forwarding rules when a customer subscribes to a new plan.
- Managing call forwarding preferences remotely via automation workflows.
- Enabling or disabling call forwarding based on business logic or customer requests.
Properties
| Name | Meaning |
|---|---|
| Msisdn | The subscriber's phone number (MSISDN) for which the call forwarding service will be added. |
| Ftn | The forwarding telephone number (FTN) to which calls will be forwarded. |
| Call Forward Service Type | The type of call forwarding service to apply. Possible values depend on the API but typically include options like unconditional, busy, no reply, etc. |
| Notify To Calling Party | Boolean flag indicating whether 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 service. This typically includes confirmation details such as success status, any identifiers related to the created service, and possibly error messages if the operation failed.
If the node supports binary data output, it would generally relate to raw response payloads or logs, but this specific operation primarily deals with JSON responses.
Dependencies
- Requires an active connection to the Summa API via an API key credential configured in n8n.
- The node depends on internal helper classes for HTTP communication and state management.
- No additional external dependencies beyond the Summa API and its authentication are required.
Troubleshooting
Common Issues:
- Invalid or missing MSISDN or FTN values can cause the API to reject the request.
- Incorrect call forward service type may lead to errors or unexpected behavior.
- Network connectivity issues or invalid API credentials will prevent successful execution.
Error Messages:
- Authentication failures indicate problems with the provided API key; verify and update credentials.
- Validation errors usually specify which input parameter is incorrect or missing.
- Timeout or network errors suggest connectivity problems; retry or check network settings.
Resolving these typically involves verifying input parameters, ensuring valid credentials, and confirming network access to the Summa API endpoint.
Links and References
- Summa API Documentation (Replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- General information on Call Forwarding Services
