| SMPP Option type length |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through August 22, 2012 ⬆ |
◄ ► |
| Author | Message | |||
| Jimmy Cherian |
Dear Sir, Our operator is requesting for SMPP option with type as integer and len as 4, but when we put the len as 4 we are getting malformed error. But len=2 is working fine, is this a limitation on NOWSMS? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3682 Registered: 08-2008 |
Hi Jimmy, That does seem to be a bug. We did not consider the possibility for a 4 byte integer in a TLV parameter. (All of the TLV examples in the spec are 1 or 2 bytes, but a 4 byte integer is also allowed by the spec.) We will correct this in a future update, but you should be able to work-around this temporarily by using the HexString data type. For example: [SMPPOptions] some_parameter=4000,HexString [SMPP - server:port] DefaultSMPPOptions=some_parameter=00000000 or &SMPPOption_some_parameter=00000000 When using the HexString type, NowSMS interprets this parameter as a string of binary data to be included in the TLV parameter. For a 4 byte integer, this would be an 8 digit hex number. For example: 000000FF = 255 decimal 10000000 = 268435456 decimal NowSMS bases the parameter length on the length of the hex string, so be sure to pad with zeroes to keep the length as 4 (4 bytes = 8 digits). If this work-around will not be sufficient for you, please let me know. We will be working on an update to properly support this value type as an integer, but I do not know if this work can be scheduled until after the holidays. -- Des NowSMS Support | |||
