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 create a Calling Name Presentation for a Supplementary Service (SS) Subscription via SOAP. It is designed to manage telecommunication service subscriptions, specifically enabling or configuring the presentation of the calling name associated with a subscription.
Typical use cases include:
- Telecom operators automating the activation or update of calling name presentation services on subscriber accounts.
- Systems that need to provision or modify supplementary services programmatically in bulk or as part of a workflow.
- Integrations where calling name presentation status must be synchronized with other subscriber data.
For example, a telecom operator could use this node to activate calling name presentation for a new subscriber or update the state of an existing subscription's calling name presentation service.
Properties
| Name | Meaning |
|---|---|
| Activation State | The current activation status of the calling name presentation service. Options: NOT_ACTIVE, ACTIVE_AND_OPERATIVE |
| Id | Unique identifier for the SS subscription to be modified or created |
| Induction State | Indicates whether the service has been induced or not. Options: NOT_INDUCED, INDUCED |
| Override Category | Whether to override the default category settings. Options: FALSE, TRUE |
| Provisioning State | The provisioning status of the service. Options: NOT_PROVISIONED, PROVISIONED |
| Registration State | Registration status of the service. Options: REGISTERED, NOT_REGISTERED, ERASED, NOT_APPLICABLE |
| Supplementary Service Type | The type of supplementary service; here it is fixed as "CallingNamePresentation" |
| Hlr Subscription ID | Identifier for the Home Location Register subscription related to this SS subscription |
| Operator ID | Identifier for the operator managing the subscription |
Output
The node outputs JSON data representing the result of the SOAP request to create or update the Calling Name Presentation service for the specified SS subscription. This typically includes confirmation of the operation's success, updated subscription details, or error information if the operation failed.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential for authenticating with the Summa API.
- Depends on the Summa API endpoint accessible via HTTP(S).
- Uses internal helper classes for HTTP requests, state management, and operation resolution/execution.
- Requires proper configuration of the "summaApi" credential within n8n.
Troubleshooting
- Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect or incomplete property values (e.g., missing required fields like
idoroperatorId) may lead to API errors. - Network connectivity problems can prevent successful communication with the Summa API.
- Error messages:
- Authentication errors usually indicate invalid API keys or misconfigured credentials.
- Validation errors from the API may specify which input property is incorrect or missing.
- Timeout or connection errors suggest network issues or unreachable API endpoints.
- Resolutions:
- Verify and re-enter API credentials.
- Ensure all required properties are provided and valid.
- Check network access and firewall settings.
- Review API documentation for correct property usage.
Links and References
- Summa API Documentation (replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- General SOAP API integration best practices
Note: The above summary is based solely on static analysis of the provided source code and property definitions.