Wavecell SMPP environment has multiple servers. To benefit from our fault tolerant, high availability platform we prefer SMPP customers to connect directly to our hostname. Based on location and traffic load your application will be automatically connected to the best server.
You should connect to Wavecell SMPP servers using SMPP version 3.4.
Below are the connection details required to connect:
|Port for SSL/TLS||2776 (TLS v1.2)|
Username and Password
Your Wavecell SubAccountId (username) will be provide by your Wavecell account manager. Due to the sensitivity and resource requirements of SMPP, you are required to have a dedicated account manager for SMPP connectivity. Please contact firstname.lastname@example.org if you have not been allocated someone directly.
You can connect to Wavecell SMPP servers using bind_receiver & bind_transmitter or bind_transceiver. Typically you are provided 1 Wavecell AccountId with multiple subAccountIds; for different routing, products or services. Wavecell SMPP platform allows a maximum of of 4 binds per subAccountId. Your bind will be rejected if your try to exceed this value.
For relaying DLR back to your platform Wavecell servers will send back deliver_sm to any bind connected with the same systemId of the originating submit_sm PDU. This includes if you are sending from multiple sites; we will send to any active bind.
Throughput is tailored to each customer’s requirement during our onboarding process. In most cases for each bind connected to Wavecell SMPP servers you will be able to submit a maximum of 50 message per second. You can check with your accout manager of specific requirements.
The following PDUs are supported by Wavecell SMPP servers:
You should send PDUs in the format as required by SMPP Protocol Specification v3.4.