Billing Information for SMPP connection - user_message_reference | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through February 02, 2006 ⬆ |
◄ ► |
Author | Message | |||
Steve Napp New member Username: Snapp Post Number: 2 Registered: 01-2006 |
Hi, My service provider requires me to supply a billing code in the SMPP user_message_reference parameter. I have found some reference to this parameter in a thread about another provider (mBlox): http://support.nowsms.com/discus/messages/1/9114.html However, I'm a bit thick, and there's something I'm missing. Can you explain how I can configure NowSMS to set this parameter? Thanks, Steve | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5442 Registered: 10-2002 |
Hi Steve, The user_message_reference parameter is one of the optional TLV (tag, length, value) parameters available in the SMPP protocol. Because they are optional, they are somewhat infrequently used. The SMPP specification defines user_message_reference as a message reference number assigned by the message originator. But, indeed, some SMPP service providers have decided to use this parameter to contain a billing code. Other SMPP service providers have added additional custom TLV parameters for this type of purpose. Because these parameters are often custom (and unique to a particular service provider), NowSMS requires you to configure it to tell it which of the optional SMPP TLV parameters should be supported. The thread that you referenced has a good explanation of this process, but it mBlox specific. A more generic explanation can be found in the following thread: http://support.nowsms.com/discus/messages/1/5972.html Search for "SMPPOptions" in that thread. But I'll go ahead and include the general description here:
Now, let's talk about how to use this information to configure support for the user_message_reference parameter. Edit SMSGW.INI, and add an [SMPPOptions] section like this: the following settings are intended to enable support for their premium rate parameters: [SMPPOptions] user_message_reference=204,Integer,2 (This indicates that the option parameter user_message_reference has a code of hex 204, and that it is of the type Integer, with a size of 2 bytes.) With this setting present, an additional parameter is now supported when submitting a message to NowSMS via an HTTP URL request. "&SMPPOption_user_message_reference=" allows you to set/retrieve the value of the SMPP "user_message_reference" variable. I say set/retrieve, because when this [SMPPOptions] section is present, NowSMS will also route these parameters to HTTP-based 2-way commands. If a message is received which contains values for any setting defined in this section, NowSMS will automatically append "&SMPPOption_user_message_reference=value"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. Now, suppose you need to use the same billing code / user_message_reference in every message that you submit. In addition to supporting this option via HTTP URL request, it is possible to configure default settings for any of these [SMPPOptions] 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=user_message_reference=1". (Note that you do not use the "SMPPOption=" prefix here, like you would in the URL request.) To include multiple options, separate the entries with a ";", for example, "DefaultSMPPOptions=mblox_tariff=00000;user_message_reference=14". Does that help? -bn | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5501 Registered: 10-2002 |
Here's a link to a related thread that talks about configuring the SMPPOptions settings used for mBlox: http://support.nowsms.com/discus/messages/1/9114.html |