Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

This document outlines the interfaces and mechanics to connect to the Vibes Connect platform via SMPP protocol for Mobile Originated and Mobile Terminated messaging traffic.

Overview

Vibes supports sending short messages using Short Message Peer-to-Peer (SMPP) protocol version 3.4.  The Vibes Connect platform uses the standard SMPP components plus some additional optional parameter values for its product. This documentation should be read in conjunction with the specification and a familiarity with the SMPP specification is assumed. For reference, the complete protocol can be found at http://docs.nimta.com/SMPP_v3_4_Issue1_2.pdf.

Operations

Connecting to the Service

The customer will provide an ESME implementation and will establish binds to the Vibes SMSC end points. Vibes provides two active data centers for messaging capabilities, with multiple SMSCs in each data center to provide the maximum in redundancy and availability. For maximum resiliency, the customer should plan on establishing a minimum of four bind pairs (MO + MT) to take maximum advantage of the platform.

Specific host IP addresses and Ports will be assigned as part of the onboarding process, as well as System_ID and password credentials.

Bind Options & Supported Operations

The Vibes Connect platform supports Transmitter, Receiver and Transceiver binds. As part of the onboarding process, either a vpn tunnel should be established between the client and vibes or the client IP addresses need to be specified for whitelisting.

Supported Operations

Currently, the Vibes Connect platform supports the following SMPP Operations

  • bind_transmitter
  • bind_receiver
  • bind_transceiver
  • submit_sm
  • enquire_link
  • unbind
Heartbeat Keep Alives

Vibes' recommendation that the client establish an Enquire-Link at a 30 second interval to keep the connection alive.

Table of Contents

The root page CONNECTV3:@self could not be found in space Vibes Connect APIs.




  • No labels