SMPP Implementation Testing
Test SMPP compliance and performance of clients and servers.Customer support Compliance Cost reduction
Short Message Peer-to-Peer (SMPP) implementation testing shows the level of conformance to the protocol when sending and receive SMS messages between applications and mobiles. The implementation's level of performance is also determined.
SMS applications (clients) and SMSCs/SMS gateways (servers) can be tested using this service. Automated and manual testing is used with servers and clients. Some services are only available to those with a Pro account from Melrose Labs.
SMSC / SMS Gateway Testing (SMPP Server)
Testing shows the conformance of an SMSC or SMS Gateway to the SMPP protocol support and its performance, e.g. rate of SMS processing. SMPP account credentials are used to connect to the SMPP server of the SMSC or SMS Gateway and perform testing.
SMPP test available:
- Bind Type and Version Support (SMPP v3.3, v3.4, v5.0) [example]
- SMS submission rate
- Delivery receipt support and reception rate
- Attribute testing (e.g. validity period adherence)
- SMPP load testing (simultaneous binds, SMS load)
- SMPP operation support
Non-conformance with the SMPP protocol, connection attempt reliability and response timings are also reported.
The SMSC/SMS Gateway Bind Type and Version Support test is publicly available on this page. All other SMPP implementation testing requires a Pro account from Melrose Labs.
SMS Application Testing (SMPP Client)
Our SMSC Simulator can be used to manually or automatically test your SMS application. Testing includes submission rates, the behaviour of the application when errors are encountered, SMPP operation support, connection reliability testing and delivery receipt handling.
SMSC / SMS Gateway Testing
SMS Application Testing
Melrose Labs SMPP Testing PICS
SMPP Client and Server Testing - Abbreviated SMPP Protocol Implementation Conformance Statement
|PDU-OUTBIND||Is the outbind PDU supported?||NO|
|PDU-BIND-TRANSMITTER||Is the bind transmitter PDU supported?||YES|
|PDU-BIND-RECEIVER||Is the bind receiver PDU supported?||YES|
|PDU-BIND-TRANSCEIVER||Is the bind transceiver PDU supported?||YES|
|PDU-UNBIND||Is the unbind PDU supported?||YES|
|PDU-ESME-GENERIC-NACK||Is the generic_nack PDU initiated by the EMSE supported?||YES|
|PDU-SMSC-GENERIC-NACK||Is the generic_nack PDU initiated by the SMSC supported?||YES|
|PDU-SUBMIT-SM||Is the submit_sm PDU supported?||YES|
|PDU-SUBMIT-MULTI||Is the submit_multi PDU supported?||NO|
|PDU-DELIVER-SM||Is the deliver_sm PDU supported?||YES|
|PDU-ESME-DATA||Is the data_sm PDU initiated by the EMSE supported?||NO|
|PDU-SMSC-DATA||Is the data_sm PDU initiated by the SMSC supported?||NO|
|PDU-QUERY||Is the query_sm PDU supported?||NO|
|PDU-CANCEL||Is the cancel_sm PDU supported?||NO|
|PDU-REPLACE||Is the replace_sm PDU supported?||NO|
|PDU-ESME-ENQUIRE-LINK||Is the enquire_link PDU initiated by the EMSE supported?||YES|
|PDU-SMSC-ENQUIRE-LINK||Is the enquire_link PDU initiated by the SMSC supported?||YES|
|PDU-ALERT||Is the alert_notification PDU supported?||NO|
- SMSC / SMS Gateway testing - simulate SMS application (ESME)
- SMS application testing - simulate SMSC / SMS gateway