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) subscriptions, specifically allowing users to set GMLC (Gateway Mobile Location Center) numbers associated with a subscriber's IMSI (International Mobile Subscriber Identity). It is useful in telecom environments where location services need to be configured or updated for mobile subscribers.
Typical use cases include:
- Updating location center numbers for subscribers to enable or modify location-based services.
- Automating telecom subscriber management workflows involving HLR data.
- Integrating telecom backend systems with external APIs for subscriber data updates.
For example, a telecom operator could use this node to programmatically update the GMLC numbers for a batch of subscribers based on changing network configurations or regulatory requirements.
Properties
| Name | Meaning |
|---|---|
| Imsi | The IMSI (International Mobile Subscriber Identity) of the subscriber whose GMLC numbers are being set. This is a required string input. |
| Send Json | Boolean flag indicating whether to send the GMLC numbers as raw JSON (true) or via structured fields (false). |
| Json Data | When Send Json is true, this JSON input contains the full data payload for setting GMLC numbers. Must be valid JSON representing the address list and related info. |
| Address Dto List | When Send Json is false, this is a collection of structured entries specifying GMLC addresses. Each entry includes: - Address: The GMLC number/address string. - Address Type: Type classification of the address. - Address Nature: Nature/category of the address. - Numbering Plan: Numbering plan used for the address format. Multiple such entries can be provided. |
Output
The node outputs JSON data representing the response from the Summa API after attempting to set the GMLC numbers. This typically includes status information about the operation, any errors, and confirmation details.
No binary data output is indicated by the source code or properties.
Dependencies
- Requires an API key credential for authenticating with the Summa API.
- Uses an HTTP client internally to communicate with the Summa backend service.
- The node depends on the Summa API version specified in the bundled code (version referenced dynamically).
- No additional environment variables are explicitly required beyond the API credential.
Troubleshooting
- Invalid IMSI: If the IMSI is missing or malformed, the API will likely reject the request. Ensure the IMSI is correctly formatted and provided.
- Malformed JSON: When using the
Send Jsonoption, invalid JSON syntax or incorrect structure inJson Datawill cause errors. Validate JSON before sending. - Missing Required Fields: If
Send Jsonis false but no addresses are provided inAddress Dto List, the request may fail due to lack of data. - Authentication Errors: Failure to provide a valid API key credential or expired credentials will result in authentication failures.
- API Errors: The Summa API might return error messages if the GMLC numbers are invalid or if there are backend issues. Check the returned JSON for error details.
To resolve these issues:
- Double-check all required inputs.
- Validate JSON formatting.
- Confirm API credentials are correct and active.
- Review API response messages for specific error codes or descriptions.
Links and References
- Summa API Documentation (Replace with actual URL)
- Telecom standards for IMSI and GMLC numbers (e.g., 3GPP TS 23.003)
- n8n HTTP Request Node documentation for understanding underlying HTTP communication patterns