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 IMSI (International Mobile Subscriber Identity) records. Specifically, the "Add IMSI" operation allows users to add a new IMSI entry with detailed configuration templates and profiles. This is useful in telecommunications environments where managing subscriber identities and their associated network templates and roaming profiles is essential.
Practical examples include:
- Adding a new subscriber's IMSI to the system with specific LTE, WLAN, HLR, and IMS templates.
- Configuring roaming profiles and enhanced coverage settings for a subscriber.
- Automating IMSI provisioning workflows in telecom backend systems.
Properties
| Name | Meaning |
|---|---|
| Icc Id | The Integrated Circuit Card Identifier (ICCID) of the SIM card associated with the IMSI. |
| Imsi | The International Mobile Subscriber Identity to be added. |
| Hlr Template | The Home Location Register template to apply for this IMSI. |
| Lte Template | The LTE network template to apply for this IMSI. |
| Wlan Template | The WLAN network template to apply for this IMSI. |
| Roaming Profile | The roaming profile name to assign to this IMSI. |
| Delta Roaming Profile Name | The delta roaming profile name used for incremental roaming updates. |
| Map Screening Name | The MAP (Mobile Application Part) screening name associated with this IMSI. |
| Ims Template | The IMS (IP Multimedia Subsystem) template to apply for this IMSI. |
| Enhanced Coverage | The enhanced coverage setting to apply for this IMSI. |
All properties are required for the "Add IMSI" operation.
Output
The node outputs JSON data representing the result of the IMSI addition operation. This typically includes confirmation details such as the IMSI added, status messages, and any relevant metadata returned by the Summa API.
If the operation supports binary data output (not indicated here), it would represent related files or attachments, but this node primarily deals with JSON responses.
Dependencies
- Requires an active connection to the Summa API via an API key credential configured in n8n.
- Uses internal helper classes for HTTP requests, state management, and resource-operation resolution.
- No additional external dependencies beyond the Summa API and its authentication.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Providing incomplete or incorrect property values (e.g., invalid ICCID or IMSI format) may result in API errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors: Verify that the API key credential is correctly set up and has necessary permissions.
- Validation errors from the API: Check that all required fields are provided and conform to expected formats.
- Timeout or network errors: Ensure stable internet connection and that the Summa API endpoint is reachable.
Links and References
- Summa API Documentation (replace with actual URL if available)
- Telecommunications standards for IMSI and ICCID formatting.
- n8n documentation on creating custom nodes and using credentials.