Trouble with sending long message in non-ASCII about node-smpp

[Dexus]

The best Way is to learn more about smpp Protocol so you dont Need a " Good error Message". Thats my two Cents.

Am 24.03.2014 um 09:59 schrieb Alex Yaroshevich [email protected]:

@farhadi @Dexus I'm talking about a good error message instead of strange stack trace. Thanks!

—
Reply to this email directly or view it on GitHub.

[vchatterji]

Simple Method:

Use the npm below

npm install gsm

The above module also splits the message into parts:

//We need to split the message and send it in many parts
var gsm = require('gsm');

var info = gsm("Your message string here");

//This is a unique id present in each message part
var concat_ref = this.concat_ref++; 

var part_id = 0;
info.parts.forEach(function(part) {
    part_id++;
    var udh = new Buffer(6);
    udh.write(String.fromCharCode(0x5), 0); //Length of UDF
    udh.write(String.fromCharCode(0x0), 1); //Indicator for concatenated message
    udh.write(String.fromCharCode(0x3), 2); //  Subheader Length ( 3 bytes)
    udh.write(String.fromCharCode(concat_ref), 3); //Same reference for all concatenated messages
    udh.write(String.fromCharCode(info.sms_count), 4); //Number of total messages in the concatenation
    udh.write(String.fromCharCode(part_id), 5); //Sequence number ( used by the mobile to concatenate the split messages)

    var submit_pdu = {
        source_addr:msg.from,
        destination_addr: msg.to,
        short_message: { udh:udh, message:part },
        registered_delivery:1 //If you want a delivery report
    };

    this.getSession().submit_sm(submit_pdu, function(pdu) {
        if (pdu.command_status == 0) {
            console.log("SMPP Gateway[" + this.getOptions().address + "] - SUMBIT[" + submit_pdu.source_addr + ">>>" + submit_pdu.destination_addr + "] - " + pdu.message_id);
        }
        if(callback) {
            callback(pdu);
        }
    }.bind(this));
}.bind(this));

[qfox]

We've fixed this with using message_payload, but I still don't understand stack trace.
Looks like internal bug.

[Dexus]

no, if you try to write sms longer than you must split the message by your self. and use udh to concat.

look for a sample (with shorty): https://github.com/DeineAgenturUG/shorty/blob/master/lib/sms.js

[farhadi]

This is not a bug.
short_message parameter in SMPP protocol is of type Octet String which is limited to 255 bytes.
message_payload TLV parameter was introduced in v3.4 to overcome this limitation.
However, some server implementations don't support messages longer than 160 bytes. In this case, as Dexus said, you need to split messages yourself using udh. (http://en.wikipedia.org/wiki/Concatenated_SMS)

node-smpp doesn't handle errors when using inappropriate parameters which caused this error to be thrown.

[qfox]

@farhadi @Dexus I'm talking about a good error message instead of strange stack trace. Thanks!

[PauloPhagula]

Questions: Why do String.fromCharCode for these fields? Aren't they supposed to go as hexadecimal values instead of what String.fromCharCode returns?

I ask because, for instance on my PC I get > String.fromCharCode(0xFF) //=> 'ÿ' and I don't get why we want to do this.

Thanks in advance