...
SMS settings allows for the configuration of SMS. These are general settings of how will Trivore Identity Service try to send SMS messages.
Core settings
Setting | Description | Default value |
|---|---|---|
Enable SMS sending via REST API | Enables/disables SMS sending via REST API. This is a system wide setting. | True (checked) |
Gateway resiliency enabled | Enables/disables SMS resubmit through a secondary | False (unchecked) |
Queued messages | If there are any queued messages in the system, pressing the Flush queue button will attempt to send out any unsent messages | N/A |
Proxy | A proxy can be enabled for SMS sending. This is for all SMS related outgoing traffic. | False (unchecked) |
Proxy host | Proxy host name or IP address | localhost |
Proxy port | Proxy port number | 8080 |
Maximum number of messages per hour | Message limit for a single mobile number in a single hour. This counter is reset every hour | Unlimited |
Maximum number of messages per day | Message limit for a single mobile number in a single day. This counter is reset every day | Unlimited |
Number patterns
Number patterns can be used to define mobile numbers (via regular expression) that are not recognised by system. This may be needed when numbering plans are changed or to define numbers that are not supported for other reasons, such as machine-to-machine numbers (M2M).
The system has some default number patterns built-in but custom number patterns can also be defined here. Number patterns require for the region to be defined which will contain the country calling code for the region. A pattern can then be defined using Regular expression patterns.
Kannel compatibility
Kannel compatibility can be enabled to support older SMS clients that may use Kannel to communicate. Although this option can be be used it is highly preferred to use the REST API to send SMS messages.