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 to perform various telecom-related operations. Specifically, for the Sim Swap Direct Explicit operation under the Sim Swap resource, it facilitates direct and explicit swapping of SIM cards by specifying source and target ICC IDs along with IMSI mappings. This is useful in scenarios where a telecom operator or system administrator needs to transfer subscriber identity information from one SIM card to another explicitly, such as during device upgrades, SIM replacements, or fraud prevention measures.
Practical examples:
- Migrating a subscriber's service from an old SIM card to a new one.
- Correcting SIM assignment errors by explicitly mapping IMSIs between SIMs.
- Managing bulk IMSI swaps during network maintenance or upgrades.
Properties
| Name | Meaning |
|---|---|
| From Icc Id | The ICC ID (Integrated Circuit Card Identifier) of the source SIM card to swap from. |
| To Icc Id | The ICC ID of the target SIM card to swap to. |
| Imsi Swaps | A collection of IMSI pairs defining the old IMSI values and their corresponding new IMSI values to be swapped. Each entry contains: - Old Imsi: The current IMSI on the source SIM. - New Imsi: The IMSI to assign on the target SIM. |
| Operator Name | The name of the mobile network operator managing the SIM swap operation. |
Output
The node outputs JSON data representing the result of the SIM swap operation. This typically includes confirmation of the swap status, details of the IMSI mappings applied, and any relevant metadata returned by the Summa API. The output structure depends on the API response but generally confirms success or failure of the requested swaps.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Summa API via an API key credential configured in n8n.
- The node uses an HTTP client internally to communicate with the Summa backend services.
- Proper configuration of the API credentials and network access to the Summa API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing ICC IDs or IMSI values can cause the operation to fail.
- Network connectivity problems or incorrect API credentials will prevent successful communication with the Summa API.
- Mismatched IMSI pairs or attempting to swap IMSIs not associated with the specified ICC IDs may result in errors.
Error messages:
- Authentication failures indicate invalid or expired API credentials; verify and update the API key.
- Validation errors about ICC ID or IMSI formats suggest input data does not meet expected patterns; ensure correct formatting.
- API response errors related to operator name or permissions imply that the operator name might be incorrect or the API user lacks required privileges.
Resolving these usually involves verifying input parameters, checking API credentials, and ensuring network connectivity.
Links and References
- Summa API Documentation (Replace with actual URL if available)
- Telecom standards for ICC ID and IMSI formats for reference.
- n8n documentation on creating and using API credentials.