The certificate creator in Diafaan SMS Server does not write Subject Alternative Names (SAN) field in the certificate. SANs are used to store multiple IP addresses and DNS names in the certificate so that it can validate the server with more than one IP address or DNS name. The SAN field is usually not necessary in the certificate, you should just fill in the IP address (138.201.XX.XX) in the 'Host name (FQDN) or IP address' field of the certificate generator. But some SSL SMPP clients might require a SAN field anyway, even if the IP address is in the subject name of the certificate.
If you send me the list of IP addresses and DNS names that you need in the certificate, I can generate a certificate for you that includes the SANs. However, this is not a guarantee that the certificate will be accepted by the SMPP client. It might require a certificate that is signed by a trusted root certificate authority.
We have followed the steps and created the self-signed certificate. Below is the setting which we have applied.
In the Event log we see this error
A call to SSPI failed, see inner exception.
Customer is getting the below error. Please let us know are we doing something wrong.
[route=100529/64509,esme=138.201.XX.XX:8XXX,tls=1] Unable to connect: x509: cannot validate certificate for 138.201.XX.XXX because it doesn’t contain any IP SANs
To set up an SMPP server that supports SSL connections, you need an SSL certificate and add it to the SMPP Connector.
You can find the installation instructions for an SMPP Connector that accepts SSL connections in the online manual.
One of our customer requires a TLS 1.2 port to connect to us using the secure connection. In the SMPP Connector we can see SSL protocol TLS12 is enable but still the client is not able to connect so do we need to do any more setting.
Please let us know how we can achieve this.
Most Users Ever Online: 494
Currently Browsing this Page:
Guest Posters: 611
Newest Members:, Henk Helmantel
Administrators: Henk Helmantel: 1299