Objective
Several key details are essential when connecting to the Vonage SMPP server to send SMS using the SMPP protocol. These include the correct host, port, and credentials. Additionally, understanding platform availability is crucial for ensuring smooth operations. Below is a summary based on Vonage’s documentation.
Applies To
- SMPP
- Login Credentials
- Connectivity
Procedure
To enable your account for SMPP, Submit a Support request including your API Key and the email address on the account.
To connect to Vonage’s SMPP server, users need to know the host and port configurations and the connection options:
SMPP Host/Endpoint:
Vonage SMPP hosts are available in 3 zones: AP, EU, and US.
Customers can connect to the relevant hosts or endpoints based on their server's location and choose one solution below.
We offer 2 options for each SMPP zone (AP, EU, US) connectivity:
Option 1:
If customers have the capability of simultaneous connections to different SMPP servers, they can connect to one of these pairs:
- smpp-ap-1.vonage.com and smpp-ap-2.vonage.com (for customers in APAC region)
- smpp-eu-1.vonage.com and smpp-eu-2.vonage.com (for customers in EMEA region)
- smpp-us-1.vonage.com and smpp-us-2.vonage.com (for customers in US region)
Option 2:
If customers do not have the capability of simultaneous connections to different SMPP servers, they can connect to one of these single endpoints:
- smpp-ap.vonage.com (for customers in APAC region)
- smpp-eu.vonage.com (for customers in EMEA region)
- smpp-us.vonage.com (for customers in US region)
We suggest customers choose Option 1 and establish simultaneous binds to both SMPP endpoints at all times.
SMPP Port:
-
8000
Standard (Non-Encrypted) -
8008
TLS/SSL encrypted
Default Throughput:
- 30 sms/sec
Default Maximum Connections:
- 2 connections max (it can be one TR and one RX, or two TRX)
Enquire Link Frequency:
- 30 seconds
These ports correspond to standard and encrypted connections, with TLS/SSL offering enhanced security for message transmission.
Finding SMPP Credentials
To access Vonage’s SMPP service, you need specific credentials, including your SMPP username (System_ID), SMPP password, and account-specific host/port details. These credentials are provided when you create a Vonage API account.
You can find your SMPP credentials by logging into your Vonage Dashboard and navigating to the API settings. There, you will find your API Key and API Secret, which you should use for your SMPP binding.
- SMPP System_ID = API Key
- SMPP Password = API Secret
Note: The default Vonage API secret is 16 characters. If your SMPP system follows the SMPP standard of 8 characters maximum, please shorten your API secret to a maximum of 8 characters. You can change the API secret in your Vonage API account dashboard under the menu Settings
SMPP Platform Availability
Vonage offers reliable SMPP services, but like any service, there may be occasional downtime due to maintenance or unforeseen issues. Customers can monitor the platform’s status via the Vonage Status Page, which provides real-time updates on platform availability. Users can access this information to ensure they know of any disruptions and plan their messaging accordingly.
The SMPP platform typically runs smoothly and has high uptime. However, in rare cases of scheduled maintenance or unscheduled downtime, timely updates are posted to the status page to keep users informed.
- Users connecting to a single endpoint
smpp-xx.vonage.com
: The user's SMPP server would need to queue SMS MT requests until the connection is re-established. Additionally, users' SMPP implementation is expected to automatically re-initiate bind attempts if their binds go down so that they can successfully reconnect once the Vonage server is again available. - Users connecting to dual-endpoints
smpp-xx-1.vonage.com
andsmpp-xx-2.vonage.com
will always have at least one cluster server up and running during the maintenance operations and, therefore, will always be able to route their traffic via the existing binds to one of the servers from the cluster. This is one of the reasons why users set to connect to dual endpoints must always maintain simultaneous binds to both SMPP servers.
Articles in this section
- How do I send concatenated messages via SMPP?
- “Window of time” to submit a multipart SMS over SMPP
- TLS certificates for SMPP nexmo.com
- TLS certificates for SMPP vonage.com
- Why are SMPP concatenated messages not delivered?
- How to Read a Vonage SMPP Delivery Receipt
- Why are my SMS messages displayed as jumbled text?
- Does Vonage need to add my originating IP address to an allow list?
- What field contains the message ID in SMPP?
- How can I receive the network ID on a delivery receipt in SMPP?