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, named "Summa," is designed to interact with the Summa API (version indicated dynamically). It supports multiple resources and operations, including managing IMSI-related data. Specifically, for the IMSI resource with the "Set Roaming Profile" operation, the node allows users to update or assign a roaming profile to a given IMSI number. This is useful in telecommunications scenarios where subscriber identity modules (SIMs) need their roaming capabilities configured or modified remotely.
Practical examples include:
- Updating roaming profiles for subscribers when they change service plans.
- Automating roaming profile assignments during SIM provisioning.
- Managing roaming settings in bulk for network operators.
Properties
| Name | Meaning |
|---|---|
| Imsi | The IMSI (International Mobile Subscriber Identity) string identifying the subscriber. |
| Roaming Profile | The roaming profile to assign to the specified IMSI. This defines roaming permissions or settings. |
Output
The node outputs JSON data representing the result of the "Set Roaming Profile" operation on the IMSI resource. This typically includes confirmation of the update, status messages, or any relevant metadata returned by the Summa API about the roaming profile assignment.
If the node supports binary data output, it would relate to any files or attachments returned by the API, but based on the provided code and context, the primary output is structured JSON reflecting the operation's outcome.
Dependencies
- Requires an active connection to the Summa API via an API key credential.
- The node depends on internal helper classes for HTTP requests, state management, and operation resolution.
- Proper configuration of the API credentials within n8n is necessary for authentication.
- No additional external services beyond the Summa API are required.
Troubleshooting
Common Issues:
- Invalid or missing IMSI value: Ensure the IMSI string is correctly formatted and provided.
- Incorrect roaming profile name: Verify that the roaming profile exists and is valid within the Summa system.
- Authentication failures: Check that the API key credential is correctly set up and has necessary permissions.
- Network connectivity problems: Confirm that the n8n instance can reach the Summa API endpoint.
Error Messages:
- Authentication errors typically indicate invalid or expired API credentials.
- Validation errors may occur if required properties like IMSI or roaming profile are missing or malformed.
- API response errors might reflect backend issues or incorrect operation parameters; reviewing the API documentation or logs can help resolve these.
Links and References
- Summa API official documentation (refer to your organization's internal or public API docs).
- n8n documentation on creating and using API credentials.
- Telecommunications standards related to IMSI and roaming profiles for deeper understanding.