| SMPP TLV Custom Params Send/Recieve |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 16, 2008 ⬆ |
◄ ► |
| Author | Message | |||
| Shawn Lewis |
I have a SMPP interconnection with MXTELECOM. When receiving traffic from them, embedded in the message is a TLV Value: # Operator code ID: 0x3010 Name: Operator code Direction: MX -> Customer Length: Variable Value: String (not null terminated). I need to get this value, it is Not being written to the text file in the SMS-IN directory, how can I enable that? And then the reverse, when sending a message to MXTELECOM, based on the carrier to which I am sending to, I must include a specific TLV for the carrier to which they are to route it. This is done by me using a custom TLV field USERNAME. This value changes depending on the carrier the message must be routed too. # MT Username ID: 0x3000 Name: MT Username Direction: Customer -> MX Length: Variable Value: String (not null terminated) Thanks for any pointers here on what to do..... Shawn | |||
| Shawn Lewis New member Username: Smlcaerus Post Number: 2 Registered: 08-2006 |
Here is an update, so I saw a post where somebody put [SMPPOPTIONS], and some other values. This allowed incoming messages to now include: SMPPOptions=SMPPOption_operator=CINGULARUS Now my question is, when we receive an inbound message, we HTTP POST that over to our webservice. How do I post this new field so that when defined in 2-Way messaging? The reverse is true as well, when we want to send outbound messages, our applications HTTP POST to NOWSMS, and we will need to include this custom USERNAME field (defined in 1st post above) as part of the post, and have it embedded in the SMPP message as well. Thanks | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 150 Registered: 08-2008 |
Hi Shawn, This post that talks about the TLV parameters for mBlox: http://blog.nowsms.com/2008/10/mblox-and-nowsms.html It's a good starting point for configuring TLV parameters for other services. It sounds like you need to add the following to SMSGW.INI: To enable the additional mBlox parameters in NowSMS, it is necessary to manually edit the SMSGW.INI file and and add the following section: [SMPPOptions] mx_operator=3010,String mx_customer=3000,String (Based on your second post, it looks like you added this first one as just "operator", which is also fine. I just put the mx_ prefix as a reminder that it was specific to MX Telecom.) Since you're seeing the mx_operator parameter showing up in the ran SMS-IN file, that should indicate that it is configured properly. When a configure TLV parameter setting is present in a received message, NowSMS will automatically the parameter to the 2-way URL. in this example, you'd get "&SMPPOption_mx_operator=CINGULARUS" appended 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. On the outbound side, you can add "&SMPPOption_mx_customer=MYCODE" for individual HTTP requests to set this value for a particular message. In many cases, it may be desirable to define default values for this parameter, instead of having to specify it in each HTTP URL submission. To define default values for these parameters, 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=mx_customer=MYCODE". To include multiple options, separate the entries with a ";", for example, "DefaultSMPPOptions=mx_customer=MYCODE;mx_operator=CINGULARUS". (I realise that in this particular case, you would not send the mx_operator setting to the provider, but I use this as an example of how you specify default values for multiple parameters.) -- Des NowSMS Support | |||
