Five Frequently Asked SMPP Questions Answered

Even though SMPP is a widely-used protocol to send SMS messages, even the most experienced users sometimes need a question answered. Here are 5 common questions answered…

What 3^rd party SMPP clients can be used for Windows and Linux respectively?

While a number of 3^rd party applications exist for both Windows and Linux to establish an SMPP connection, there are a few that seem to be more popular than others, which is of course not to say that the latter lack in any way.

Windows users can install applications like NowSMS and Linux users Kannel. Take note that the applications specified here may not be free of charge and, in both cases, require a connection to a SMS service provider. Additionally, be sure to brush up on your SMPP knowledge by going through the SMPP Specification Version 2.4.3.

Can SMPP be used to send messages to roaming handsets?

First off, let’s reach consensus on that which is understood under roaming in this case:

Roaming, when using a handheld mobile device, is when the owner of said devices retains the same number, even when not in his local country, region or coverage area. Mobile providers often have roaming partners in other regions or countries that allow calls and data to be put through to the handheld mobile device in question in said foreign region or country.

That being said, to answer the question as comprehensively possible, we need to look at message routing, too. Simply put, message routing determines the route to a specific operator, based on cost. These routes are, in part, planned using a Home Location Register (HLR) that contains information regarding the location of the destination mobile’s operator. As such, using SMPP or any other application programming interface for that matter to send messages to roaming profiles could result in non-delivery because of the geographic location of the mobile handset versus it’s location in the HLR. Savvy?

How do you set the sender ID with SMPP?

Set your ton=0 and npi=0 (or ‘unknown’). It’s that simple – the source address will automatically be detected. But, note that your sender ID has to be registered before it can be used and also keep in mind that not all networks support alphanumeric sender IDs. Check out the coverage page for more information.

How do I get two-way messaging working in SMPP?

Well it’s pretty simple: you have to apply for a two-way messaging SMPP service. If you’ve got that enabled, then you have to make sure that your application programming interface (API) connection has a pre-configured mobile originated (MO) number set up.

What does “ESME already in bound state” mean?

Hmmm, where do we begin to answer this? The very simple explanation is that you’ve already got a virtual SMPP connection established to your SMS service provider. But it could also be a little more complex than this:

SMPP version 3.3 required one virtual connection (SMPP session) to send messages, and another to receive messages. Some version 3.3’s and all versions above support the BIND_TRANSCEIVER field, which means that only one SMPP session is required to both send and receive. So, to solve the problem, you’ll first have to find out whether you are employing the BIND_TRANSCEIVER field and then check whether your system actually allows more than one connection – it could be that you are using the more traditional version 3.3, and that your system allows only one SMPP session to be established.

And that’s it for today! If you’ve got some questions you’d like answered, let us know below. Alternatively, learn more on the SMPP page.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.