Reliable SMS delivery depends on more than routing a message from one network to another. When subscribers are unreachable, connections fail or routes become unavailable, the SMSC needs to determine how to retry delivery, handle charging and process messages containing multiple segments.
PAiCore SMSC CT v3.3.0+cte gives telecom operators greater control over these decisions. The release focuses on three key areas: Configurable SMS Retry Profiles, Diameter ECUR Online Charging and Multipart Retry Control.
With 14 improvements and 2 bug fixes, SMSC CT v3.3 also includes enhancements to SS7 delivery reporting, CDR analysis, deployment flexibility and platform stability.
What’s New in PAiCore SMSC CT v3.3?
The three major enhancements address different stages of the SMS delivery lifecycle:
Configurable Retry Profiles define how failed messages are retried, delayed, rerouted or handled through recovery policies.
Diameter ECUR Online Charging allows charging units to be reserved before delivery and completed or released according to the delivery outcome.
Multipart Retry Control lets operators choose whether to resend all parts of a multipart SMS or only the segments that remain pending.
Configurable SMS Retry Profiles
SMS delivery failures do not always require the same response. A temporary subscriber issue, a network interruption or an unavailable destination route can call for different retry strategies.
SMSC CT v3.3 introduces Configurable Retry Profiles, enabling operators to create reusable policies for handling different delivery failures.
A Retry Profile can define:
- Multiple retry steps, each with its own number of attempts and delay
- A Maximum Due Delay to limit how long a message remains in the retry cycle
- Recovery profile chaining when the current profile is exhausted
- Alternate destination routing when a message needs to be rerouted
- Retry actions such as changing source or destination addresses, adding or removing prefixes, or adjusting message priority
Profiles can be mapped using criteria such as the origin network, destination network, protocol and error code, with additional conditions available for message fields or custom parameters.
The release also records the Retry Profile ID in the CDR, making it easier to identify which retry policy was applied to a message.
Gateway-specific error classification is available for SS7 and Diameter, including Auto Retry, No Retry and Retry Alternate Destination options.
Together, these capabilities provide more granular control over how the SMSC responds to delivery failures.
Diameter ECUR Online Charging
SMSC CT v3.3 adds support for Diameter ECUR (Event Charging with Unit Reservation) alongside the existing IEC (Immediate Event Charging) model.
With ECUR, charging units can be reserved before delivery. The charging transaction can then be completed or released based on the final delivery outcome.
The process uses:
CCR-Initial to initiate the transaction and request a reservation of units.
CCR-Termination to complete the transaction and commit or release the reservation as applicable.
ECUR also supports multipart messages and retry attempts, including reservation handling across retries. If delivery ultimately fails, the charging reservation is automatically terminated according to the charging flow.
For operators using an online charging system, this provides another way to manage charging throughout the messaging lifecycle while keeping charging aligned with delivery outcomes.
Multipart SMS Retry
Long SMS messages are commonly divided into multiple segments before transmission. When only some segments fail, the SMSC needs to determine whether to resend the entire message or only the parts that remain undelivered.
SMSC CT v3.3 introduces a Retry All Parts option at the routing-rule level.
Operators can choose:
Retry all parts — resend the complete multipart message when a retry is triggered.
Retry pending parts only — resend only the segments that have not been delivered.
This gives operators more flexibility in handling multipart traffic and can help avoid unnecessary retransmissions when only some segments require another attempt.
Additional Improvements
Beyond the three main enhancements, SMSC CT v3.3 includes several supporting improvements.
Configurable SS7 Delivery Reporting
Operators can enable or disable Report-SM-Delivery-Status (RSDS) independently for individual SS7 gateways, allowing delivery-status handling to be adapted to different network and interconnect requirements.
Improved CDR Reporting
CDR reports can now be filtered by DLR status, while DLR status is also displayed in detailed reports. Network names are read directly from the CDR, with indexing added to support faster filtering.
Flexible Deployment
The release adds support for Redis standalone mode alongside Redis Cluster mode, providing another option for labs, testing environments and smaller deployments.
HTTP Service Providers can also be configured without a DLR callback URL where one is not required.
Message Processing and Stability
The release also includes fixes for Home Routing for MT ForwardSM and SMPP client reconnection, improving message classification and helping message processing recover correctly after SMPP session rebinds.
Why SMSC CT v3.3 Matters
The latest release gives operators more control over the SMS delivery lifecycle.
Retry Profiles allow delivery policies to be adapted to different network conditions and failure scenarios.
Diameter ECUR provides a reservation-based charging option that supports retries and multipart messages.
Multipart Retry Control gives operators a choice between resending every segment or only those that remain pending.
Additional improvements to SS7 handling, CDR reporting, deployment and platform stability further strengthen the platform.
With 14 improvements and 2 bug fixes, SMSC CT v3.3 continues the development of PAiCore SMSC for telecom operators, MVNOs, SMS aggregators and messaging service providers.
Explore PAiCore SMSC CT v3.3
Want to explore the latest capabilities or review the implementation details?
Interested in open-source telecom infrastructure, standards-based messaging and flexible SMS delivery management? Explore PAiCore SMSC and discover how configurable routing, retry policies and charging integration can support your messaging environment.