On 2021-02-15 13:56, Antony Stone wrote:
On Monday 15 February 2021 at 13:44:40, Dave wrote:
Thanks for the quick reply, Antony.
>> I've installed Kannel as bundled package through apt
>
> Which repository did you use?
# apt search kannel
Sorting... Done
Full Text Search... Done
kannel/focal,now 1.4.5-3ubuntu2 amd64 [installed]
Okay, that's certainly up to date, then - you have the latest kannel
release.
# ldd /usr/sbin/smsbox
libssl.so.1.1 => /lib/x86_64-linux-gnu/libssl.so.1.1
(0x00007fcedd7c4000)
libcrypto.so.1.1 => /lib/x86_64-linux-gnu/libcrypto.so.1.1
(0x00007fcedd2f8000)
# ldd /usr/sbin/bearerbox
libssl.so.1.1 => /lib/x86_64-linux-gnu/libssl.so.1.1
(0x00007f84b91bf000)
libk5crypto.so.3 => /lib/x86_64-linux-gnu/libk5crypto.so.3
(0x00007f84b7e8c000)
The output from above is from the 20.04 LTS server.
Hm, well that disproves my theory, then :(
Here's an example of an SMSC definition from my kannel.conf for a
connection
which works with SSL. Does that look different from what you're using?
# SMSCs
group = smsc
smsc = smpp
smsc-id = Vaxbane
system-type = "SMSC"
host = 198.51.100.82
port = 2778
smsc-username = Grumbleweed@Vaxbane
smsc-password = S3cur3P455w0rd
connection-timeout = 60
use-ssl = true
I know - it's strange. I have a similar version as you:
group = smsc
smsc = smpp
smsc-id = first-smsc, second-smsc
allowed-smsc-id = first-smsc
preferred-smsc-id = first-smsc
host = <ip address>
port = 2775
transceiver-mode = true
smsc-username = <username>
smsc-password = <password>
system-type = "CMT"
throughput = 10
use-ssl = true
It's an exact copy of a productive SMSC connection. I also tried to set
the option
ssl-client-certkey-file = "/etc/kannel/server.pem"
But that did not change anything. If I comment out the use-ssl option I
do get a connection.
Thank you, Dave.
