SMPP using mBlox

SMPP using mBlox SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through October 19, 2005 » SMPP using mBlox « Previous || Next »
Author Message
Yosi Oren
New member
Username: Nabulaer

Post Number: 6
Registered: 12-2004
Posted on Monday, April 04, 2005 - 01:12 pm:   

Hi,
mBlox want me to add aditional paramter to the smpp connection/send so they will be able to bill the PSMS MT receiver.
for Example :
mblox_operator, id = 0x1402
According to the SMPP v3.4 specification, the range 0x1400 – 0x3FF are reserved for vendor specific use.

These fields are essential for many PSMS implementations.





Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4306
Registered: 10-2002
Posted on Sunday, April 10, 2005 - 12:07 pm:   

Hi,

I believe you contacted us directly on this issue, and we implemented a version that allows additional SMPP parameters to be supported.

I'm just posting this as a follow-up for others to see. These capabilities will be included in the next update to NowSMS. But in the meantime, if you are facing similar issues, then please e-mail nowsms@now.co.uk, and reference this discussion thread.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4434
Registered: 10-2002
Posted on Thursday, April 28, 2005 - 07:54 pm:   

Follow-up: This is included in the v5.51b update. More information is available at http://www.nowsms.com/whatsnew.htm.
Derek Barber
Unregistered guest
Posted on Thursday, May 05, 2005 - 04:42 pm:   

I am trying to get NowSMS working with MBlox and I have installed this latest update (5.51b). I am using an SMPP account. Unfortunately I am having a problem sending messages to Mblox even when I use the correct Operator ID and Tariff - I get an error back from MBlox when I try to send a message.

I currently have a trouble ticket open with MBlox but they aren't very helpful. Has anyone been able to successfully get their MBlox account working with NowSMS? If so, can anyone provide some assistance?

Many thanks.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4479
Registered: 10-2002
Posted on Friday, May 06, 2005 - 06:18 pm:   

Hi Derek,

I know we traded some e-mail on this ... I just wanted to update others on it.

It appears that mBlox wants the mblox_operator and mblox_tariff fields each to be 5 characters long.

-bn
Hussam Dahbour
New member
Username: Hussam83

Post Number: 1
Registered: 08-2005
Posted on Saturday, August 06, 2005 - 08:20 am:   

I found a post about tariff and operator, what about mBlox_sessionid and mBlox_ProfileID, how I can send them?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4872
Registered: 10-2002
Posted on Friday, September 09, 2005 - 06:44 pm:   

Hi Hussam,

I believe that you had indicated to me via e-mail that you had resolved these issues by modifying the [SMPPOptions] section of SMSGW.INI, where you were able to add these parameters in the same manner as mblox_operator and mblox_tariff were added in our example.

However, I wanted to follow-up with others to explain details of mBlox specific requirements for premium rate SMS.

We have posted another update, currently known as v5.51g. This update expands upon some of the support for mBlox specific requirements that we have added in past releases. v5.51g (or a later version) can be downloaded from http://www.nowsms.com/download/latestpatch.zip. This is an update patch that is designed to update any existing v5.51(x) installation.

The following changes have been applied to simplify life for people connecting to mBlox:

* SMS Gateway/SMPP: Updated information on mBlox recommendations. To enable support for specifying premium rate SMS parameters when connecting to mBlox over SMPP, edit SMSGW.INI, and add the following section:

[SMPPOptions]
mblox_operator=1402,String,5
mblox_tariff=1403,String,5
mblox_sessionid=1404,String,45
user_message_reference=204,Integer,2

When these settings are present, additional parameters are supported when submitting a message to NowSMS via an HTTP URL request. "&SMPPOption_mblox_operator=" will specify a value for the destination operator. "&SMPPOption_mblox_tariff=" will specify a value for the premium rate tariff associated with the message. "&SMPPOption_mblox_sessionid=" is required for some premium rate SMS operator implemtnations. For additional information on any of these parameters, please refer to the mBlox SMPP Gateway Version 3.0 Manual.

"&SMPPOption_user_message_reference=" is a generic option that allows you to set/retrieve the value of the SMPP "user_message_reference" variable. An mBlox FAQ suggests that it is possible to use this option to specify a billing reference.

Please note that mBlox support will often suggest that you use a value of "0" for the mblox_tariff initially. However, customers have reported to us that mBlox appears to require a 5 digit code for this field, and that "00000" should be used instead of "0".

When these SMSGW.INI file settings are present, NowSMS will also route these parameters to HTTP-based 2-way commands. If a message is received which contains values for either of these settings, NowSMS will automatically append "&SMPPOption_mblox_operator=value" and/or "&SMPPOption_mblox_tariff=" to the 2-way URL. It is not necessary to add any variables to the 2-way command template, as these values will be appended automatically if present in a received message.

In addition to supporting these options via HTTP URL request, it is possible to configure default settings for any of these options for each outbound SMPP connection. To define default settings, manually edit the SMSGW.INI, and in the section header for an SMPP connection (e.g., [SMPP - ip.address:port]), add a "DefaultSMPPOptions=" setting, where the value of this setting can contain any of the "SMPPOptions" settings. For example, "DefaultSMPPOptions=mblox_tariff=00000". To include multiple options, separate the entries with a ";", for example, "DefaultSMPPOptions=mblox_tariff=00000;user_message_reference=1".

* SMPP: By default, a source_addr_ton (source address type of number) value of 3 will be used for any messages where the sender address is numeric, and of length less than or equal to 5 digits. To disable this behaviour, manually edit SMSGW.INI, and under the [SMSGW] section, add MaxSMPPShortCodeLen=0. (Note: If the sender address contains alpha characters, source_addr_ton will be 5 by default. If the sender address starts with a "+", then source_addr_ton will be set 1 by default. In all other cases, the default value for source_addr_ton will be 0.)

(Note: mBlox will reject messages sent from your shortcode if the source TON is not set to 3. While NowSMS has always allowed this value to be set manually in the configuration, not having this value set to 3 has been the most common problem that we have seen for customers attempting to connect NowSMS to mBlox ... so we hope this change will help simplify these connections.)

* 2-way SMS: Allow the SMPP "service_type" value associated with a message to be passed to a 2-way command by adding support for the following variable: @@SERVICETYPE@@.


-bn

Login Login / Register Logout Logout Search Last 30 Days Topics Topics