We ran into an issue because of WebSmsCom_Toolkit.inc#L129 / L335:
curl_setopt(): CURLOPT_SSL_VERIFYHOST no longer accepts the value 1, value 2 will be used instead
Support for 1 for CURLOPT_SSL_VERIFYHOST was dropped from cURL 7.28.1 onwards (20.11.2012):
https://curl.se/changes.html#7_28_1
The cURL author wrote a blog post about why:
https://daniel.haxx.se/blog/2012/10/25/libcurl-claimed-to-be-dangerous/
Thanks!