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 HLR (Home Location Register) subscription settings, specifically allowing users to apply custom Outgoing Data Barring (ODB) configurations. It is useful in telecom environments where controlling call and data barring on subscriber lines is necessary for compliance, fraud prevention, or service customization.
A practical example would be a telecom operator applying specific barring rules to a subscriber identified by their IMSI (International Mobile Subscriber Identity), such as disabling outgoing calls while allowing incoming calls and packet-oriented services.
Properties
| Name | Meaning |
|---|---|
| Imsi | The International Mobile Subscriber Identity of the subscriber whose HLR ODB settings are modified. |
| Barring Of Outgoing Calls | The setting to enable or disable barring of outgoing calls for the subscriber. |
| Barring Of Incoming Calls | The setting to enable or disable barring of incoming calls for the subscriber. |
| Barring Of Roaming Calls | The setting to enable or disable barring of roaming calls for the subscriber. |
| Barring Of Packet Oriented Services | The setting to enable or disable barring of packet-oriented services (e.g., data services) for the subscriber. |
Each barring property expects a string value indicating the desired barring state (e.g., "enabled", "disabled" or similar, depending on the API's accepted values).
Output
The node outputs JSON data representing the result of applying the custom HLR ODB settings. This typically includes confirmation of the applied settings, status codes, or error messages returned by the Summa API.
If the operation involves binary data (not indicated here), it would represent raw responses or files related to the HLR subscription update, 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.
- The node depends on internal helper classes for HTTP requests, state management, and operation resolution.
- No additional external dependencies beyond the Summa API and its authentication.
Troubleshooting
Common Issues:
- Invalid or missing IMSI: Ensure the IMSI is correctly provided and formatted.
- Incorrect barring values: Use valid strings as per the Summa API specification for barring options.
- Authentication failures: Verify that the API key credential is correctly set up and has sufficient permissions.
- Network issues: Confirm connectivity to the Summa API endpoint.
Error Messages:
- Authentication errors usually indicate invalid or expired credentials; reconfigure the API key.
- Validation errors from the API may point to incorrect barring parameters or missing required fields.
- Timeout or network errors suggest connectivity problems; check firewall and proxy settings.
Links and References
- Summa API Documentation (Replace with actual URL)
- Telecom standards on HLR and ODB settings for further understanding of barring concepts.