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 on telecom-related resources. Specifically, for the MSISDN resource and the Edit MSISDN operation, it allows users to update details related to a mobile subscriber's phone number configuration. This can be useful in scenarios such as updating routing profiles or alert indicators for a subscriber's MSISDN in a telecom system.
Practical examples include:
- Changing the SMS routing profile of a subscriber’s phone number to redirect messages through a different gateway.
- Updating alert indicators to modify how notifications are handled for a specific MSISDN.
Properties
| Name | Meaning |
|---|---|
| Msisdn | The phone number (MSISDN) to be edited. |
| Alert Indicator | A value indicating the alert status or type associated with the MSISDN. |
| Sms Routing Profile | The SMS routing profile to assign to the MSISDN, determining how SMS messages are routed. |
Output
The node outputs JSON data representing the result of the Edit MSISDN operation. This typically includes confirmation of the updated MSISDN details or any response data returned by the Summa API after the edit request.
If the operation involves binary data (not indicated here), it would represent files or media related to the MSISDN, but this node primarily deals with JSON responses.
Dependencies
- Requires an API key credential for authenticating with the Summa API.
- Uses an HTTP client internally to communicate with the Summa backend services.
- The node depends on the Summa API being accessible and properly configured with valid credentials.
Troubleshooting
- Authentication errors: Ensure that the API key credential is correctly set up and has the necessary permissions.
- Invalid MSISDN format: Verify that the MSISDN input follows the expected phone number format required by the Summa API.
- Missing required fields: All three properties (Msisdn, Alert Indicator, Sms Routing Profile) are mandatory; missing any will cause the operation to fail.
- API connectivity issues: Check network connectivity and endpoint availability for the Summa API.
- Unexpected API responses: Review the API documentation for error codes and ensure inputs conform to expected values.
Links and References
- Summa API Documentation (replace with actual URL if available)
- n8n HTTP Request Node documentation for understanding underlying HTTP communication: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/