IoT Developer Blog | emnify (3)

All Categories SMPP

AWS

Ultimate guide to update IoT Firmware with EMnify and Serverless on AWS

29.04.2021 In the world of IoT device management, going Serverless takes care of most of the hassle of doing it yourself. How would you feel if your application could tell your tracking device to update when it would be the cheapest to do so? How about telling your device to send data less frequently when it is connected to a network with expensive data rates? I will show you how to do exactly that. In this post, I will explain how to manage your devices using the EMnify Data Streamer, AWS Kinesis and AWS Lambda.

Feature image for Create+an+IoT+Gateway+with+EMnify%2C+Raspberry+Pi+and+Sixfab

Create an IoT Gateway with EMnify, Raspberry Pi and Sixfab

25.03.2021 – IoT Connectivity

While there are several ways to connect your IoT devices, cellular connectivity is by far the favorite choice for mobile applications. Although when you are in the prototyping phase of your IoT application, mobile connectivity can get a little tricky with choosing the modem, the connectivity provider, the configuration required, etc.

How to use Rest-API via Postman

03.02.2021 – EMnify API

You can use Postman as a powerful tool for testing and running EMnify’s Rest-API and perform operations in bulk.

EMnify now supports configurable DNS settings for IoT device groups

10.12.2020 –

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.

The best API experience with our new EMnify API documentation

04.12.2020 – Blog

Cellular IoT - API First At EMnify, we develop our cellular IoT platform features using an 'API-first' approach. This means that we design and implement our APIs before any other functionality and consider our API as one of the most important components of our platform. Most other features and applications we develop, such as our GUI management platform, are all built around our APIs.

Enhanced Security for A2P SMS using SMPP with TLS

04.12.2020 –

EMnify now offers SMPP over secure SSL/TLS as an enhanced security feature for Application-to-Peer (A2P) SMS.

Image for Webinar%3A+Email+%2F+Slack+notifications+from+the+EMnify+Data+Streamer

Webinar: Email / Slack notifications from the EMnify Data Streamer

04.12.2020 – AWS

Stream Platform Events to S3 CSV Read & Routing Lambda Add an Email Notification Lambda Subscriber Add a Slack Integration Lambda Subscriber Cleaning Up and Adding Filtering Hints In the EMnify User Interface (EUI), events provide details on the connectivity status of devices using EMnify SIMs. The Event Data Streamer provides a single interface for streaming platform events to application servers or other developer tools. In this tutorial, we will configure a basic but flexible notification service using the following AWS tools:

SMPP Integration Guide

04.12.2020 – SMPP

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.

How to send and receive SMS via the API?

04.12.2020 – Blog

To submit SMS directly from your application to an endpoint using our API, the following API call needs to be made: POST https://cdn.emnify.net/api/v1/endpoint/{endpointId}/sms Required Headers: Content-Type: application/json Authorization: Bearer {auth_token} JSON Body: { "source_address": "12345", "payload": "This is the message text!" } To receive SMS on your application server from the device you will need to first set up a Callback URL in the Service profile assigned to that endpoint: Set the API URL on the "SMS" tab - select "RestAPI" on the drop-down menu for “Interface” Select the “configuration icon” next to “RestAPI”, input a purpose (name of your choosing) and the URL You can also set up a "Secret" (optional) The EMnify system will then send the MO SMS as a JSON payload if the destination address of the SMS is an invalid MSISDN (8 digits or less). A2P / P2P Routing Our system distinguishes A2P SMS (application-to-person) from P2P SMS (person-to-person) based on the length of the source (MO SMS) or the destination (MT SMS) address. If there are 8 digits or less (i.e. an invalid MSISDN), an SMS will be considered A2P. If there are 9 digits or more, an SMS will be processed as MSISDN and will be considered P2P. To dispatch SMS MO to your application (A2P) and at the same time have P2P SMS enabled, the destination number (dest_address) must be limited to 8 digits or less. A detailed description of the SMS API you can find in our API Documentation.

‹

1 2 3 4

›

High Growth Companies

Small Businesses

Enterprises