SMPP Integration Guide
emnify customers can exchange SMS with their endpoints through 4 different interfaces: the Portal, the RestAPI, Zapier and/or through a SMPP bind towards the emnify SMSC. This guide explains the SMPP setup.
EMnify now supports configurable DNS settings for IoT device groups
At EMnify, a security-first approach is the foundation of the development of our platform features. This is reflected in our solutions which enable TLS on A2P SMS, the integration of your IoT devices with your VPC via Cloud Connect, and multiple software and physical measures undertaken to prevent SIM misuse. The addition of configurable DNS settings for device groups allows for end-to-end control of the networking settings of your devices. Aside from providing further options for using alternative public DNS services, device fleets can now be restricted to use private DNS services which do not expose DNS query logs or internal server IPs, and may be configured to drop internet access for hardened security-first IoT infrastructure.
API Blog Series Part 3: SMS over API
In the last edition of the EMnify API Blog Series, we explored how to configure protocols to automatically initiate and configure your IoT & M2M devices or services. We gave examples of automated API calls, and technical information on how to implement automated process in your own application. In Part 3 of the Blog Series, we will continue on the technical track, covering how to send and receive application-to-peer (A2P) SMS messages over API.