I need to edit sms_emi.c field to do the ff:
1. If binfo is the right code, say 1028 (for the 1st part of the push
message), place it on the xser 0c field.
2. If binfo is some bogus code, say 1000 (for the 2nd and 3rd parts of
the push message), do not put an xser 0c field.
3. If binfo is empty (for our pull service using sms-service), set it
to 1028 and place it on the xser 0c field.
I know another solution would be to modify the application so that
everything will use smssend. But we simply don't have the time to do that.
So my (probably very newbie) question is: how do I compare sms.binfo
with "1028"? See below:
/* XSer 0c: billing identifier */
if (octstr_len(msg->sms.binfo)) {
if ((msg->sms.binfo)=="1028") /*---> what function do I need to
use to convert "1028"?*/
{
str = octstr_create("");
octstr_append_char(str, 0x0c);
octstr_append_char(str, octstr_len(msg->sms.binfo));
octstr_append(str, msg->sms.binfo);
octstr_binary_to_hex(str, 1);
octstr_append(emimsg->fields[E50_XSER], str);
octstr_destroy(str);
}
}
else
{
str = octstr_create("");
octstr_append_char(str, 12);
octstr_append_char(str, 4);
octstr_append_cstr(str, "1028");
octstr_binary_to_hex(str, 1);
octstr_append(emimsg->fields[E50_XSER], str);
octstr_destroy(str);
}
Thanks.
Johann
charging once for the a message longer than 160 char
Johann Vincent Paul de Ungria Tagle Wed, 26 Nov 2003 23:57:48 -0800
- Re: charging once for the a message lo... Johann Vincent Paul de Ungria Tagle
- Re: charging once for the a messa... Johann Vincent Paul de Ungria Tagle
- RE: charging once for the a messa... Angel Fradejas
