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 (version indicated in the node description) to perform various operations on multiple resources. Specifically, for the resource HLR Subscription and operation Get ODB, it retrieves the Operator Determined Barring (ODB) information associated with a given IMSI (International Mobile Subscriber Identity). This is useful in telecom scenarios where you need to check call barring or restrictions applied to a subscriber's profile.
Practical examples include:
- Querying whether a subscriber identified by an IMSI has any active call barring settings.
- Integrating telecom backend systems to automate subscriber status checks.
- Supporting customer service workflows that require real-time subscriber restriction data.
Properties
| Name | Meaning |
|---|---|
| Imsi | The International Mobile Subscriber Identity string used to identify the subscriber whose ODB information is being requested. This property is required. |
Output
The node outputs JSON data containing the ODB details for the specified IMSI. The exact structure depends on the Summa API response but typically includes fields describing the barring status, types of barring applied, and related metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential to authenticate with the Summa API.
- Uses an HTTP client internally to send requests to the Summa backend.
- The node depends on the Summa API service being available and reachable.
- Proper configuration of the API credentials within n8n is necessary.
Troubleshooting
- Missing or invalid IMSI: Since IMSI is required, ensure it is provided and correctly formatted; otherwise, the API call will fail.
- Authentication errors: If the API key credential is missing, invalid, or expired, the node will not be able to connect to the Summa API.
- Network issues: Connectivity problems to the Summa API endpoint can cause request failures.
- API errors: The Summa API might return errors if the IMSI does not exist or if the requested ODB data is unavailable.
To resolve these:
- Verify the IMSI input value.
- Check and update the API authentication credentials.
- Ensure network connectivity to the Summa API.
- Review error messages returned by the node for specific API error codes.
Links and References
- Summa API Documentation (Replace with actual URL)
- n8n HTTP Request Node documentation for understanding underlying HTTP calls: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/