Regarding Kannel SMSBOX response with http code 502 bad gateway.

[Manas Mohanty]

Hi All,

We are using kannel-1.4.4 as sms gateway.  To send messages to kannel we
are using kannel http url as we are using smsbox and bearerbox.

As we are using multiple kannel (smsbox and bearerbox), we are using AWS
ALB (load balancer) in between our application and smsbox.

We build kannel debian package and install the binary files in AWS opsworks
infra on Ubuntu 14.04.

The issue we are facing is, in a span of around one month of running fine
one of smsbox used to not  accepting the message and response with http
code 502 bad gateway.  But bearerbox is used to working fine as we are
getting DLRs from SMSCs.
We need to restart that kannel to bring the kannel working properly.

The issue comes repeating to all the kannel instances in span of one month
of working fine.

Does anyone facing this issue. If yes how do they fix this issue?
Please suggest what could be the possible reason/solution for this issue ?

How to Set Data coding scheme to Latin1 (ISO-8859-1)

[Manas Mohanty]

Hi,
Our upstream carrier wants us to send message with text encoding in
Latin1(ISO-8859-1).
Please help me to set DCS set to Latin1 (ISO-8859-1) in kannel.

SET data_coding as 1 in submit_sm

[Manas Mohanty]

Hi,
I am using kannel sms gateway 1.4.4
One of the SMSC is supporting charset ASCII with DCS = 0x01.

How to send a message with  charset ASCII with DCS = 0x01 in kannel.


Regards,
Manas

Re: UTF-8 Unicode SMS Scrambled

[Manas Mohanty]

Insert the msgdata field in binary instead of hex.


On Wed, Apr 19, 2017 at 7:43 PM, Amelye Chatila  wrote:

> Hi,
>
>
> Any reply on this,
>
>
> Regards,
>
> Amelye
>
>
> On Tue, Apr 11, 2017 at 4:15 PM, Amelye Chatila  wrote:
>
>> Hi all,
>>
>>
>> Not able to send unicode message, receiving scrambled content. This issue
>> is on production and I was able to reproduce on testing environment
>>
>> *INSERT Statement:*
>>
>> INSERT INTO `kannel`.`send_sms` (`sql_id`, `momt`, `sender`, `receiver`,
>> `udhdata`, `msgdata`, `time`, `smsc_id`, `service`, `account`, `id`,
>> `sms_type`, `mclass`, `mwi`, `coding`, `compress`, `validity`, `deferred`,
>> `dlr_mask`, `dlr_url`, `pid`, `alt_dcs`, `rpi`, `charset`, `boxc_id`,
>> `binfo`, `meta_data`) VALUES
>> (92553, NULL, 'TEST', '255765154235 <0765%20154%20235>', NULL,
>> '%D9%85%D8%B1%D8%AD%D8%A8%D8%A7+%D9%83%D9%8A%D9%81+%D8%AD%D8%A7%D9%84%D9%83',
>> NULL, 'smppone', NULL, 'smppone', NULL, NULL, NULL, NULL, 2, NULL, NULL,
>> NULL, 31, 'b6981681-13c8-11e7-82b6-06cba1bf0ce7', NULL, NULL, NULL,
>> 'utf-8', 'sqlbox', NULL, NULL);
>>
>>
>>
>> *Content on msgdata Column: *(this what get inserted on this column and
>> I think the issue starts here)
>>
>> 254439253835254438254231254438254144254438254138254438254137
>> 2B2544392538332544392538412544392538312B25443825414425443825
>> 4137254439253834254439253833
>>
>> *Environment:* Kannel SMS Gateway-1.5.0 installed on CentOS Linux 7 (
>> Core ) with mysql  Ver 15.1 Distrib 5.5.52-MariaDB
>>
>>
>>
>> *Content on msgdata Column: *(On different environment and Kannel
>> Version) This get sent fine . . .
>>
>> %06E%061%06-%06(%06'%00+%06C%06J%06A%00+%06-%06'%06D%06C
>>
>> *Environment:* Kannel SMS Gateway-1.5.0 installed on Ubuntu 15.04 (
>> vivid ) with mysql  Ver 14.14 Distrib 5.6.28
>>
>>
>>
>> Thanks In Advance
>>
>> Amelye
>>
>
>

Re: '@' missing in MO message.

[Manas Mohanty]

Hi,

Thanks for the quick response.
How to use your suggestions. Is there any configuration parameter to set
that in kannel.
I am bit confuse as the issue comes for only incoming (MO) message. That to
for the SMSC which is sending delivery_sm with data_code = 1 i,e ASCII.
I can not set alt-charset =ASCII for this SMSC because MT (outgoing)
message will be encoded to ASCII where as we want to use GSM 3.38 (default)
charset for MT messages.

Thanks,
Manas.

On Wed, Apr 12, 2017 at 11:40 AM, Web Services <coinhost...@gmail.com>
wrote:

> Hi,
>
> use url decode value (ie for @ is %40)
>
> thnx
>
> On Tue, Apr 11, 2017 at 6:25 PM, Manas Mohanty <mohanty.ran...@gmail.com>
> wrote:
>
>> We kannel is replacing '@' with empty in MO message.
>> In kannel bearerbox log delivery_sm data_coding is set to 1.
>> How to configure kannel to get '@' correctly in application end.
>>
>> Regards,
>> Manas
>>
>
>

'@' missing in MO message.

[Manas Mohanty]

We kannel is replacing '@' with empty in MO message.
In kannel bearerbox log delivery_sm data_coding is set to 1.
How to configure kannel to get '@' correctly in application end.

Regards,
Manas

Re: Help regarding sending pound '£' symbol through kannel

[Manas Mohanty]

Thanks Davor.
 I will try what you suggested.

On Thu, Feb 23, 2017 at 4:16 PM, Davor Spasoski <davor.spaso...@onevip.mk>
wrote:

> P.S.
>
>
>
> Best way to check the default SMSC encoding is to send %00 with coding=0
>  and check if you get @ or ¡ on your handset. If you get the ¡, then for
> sure GSM 03.38 is not the default SMSC alphabet (as far as the SMPP
> communication is concerned).
>
>
>
> BR,
>
>
>
> *Davor Spasoski*
>
> *From:* Davor Spasoski
> *Sent:* 22 February 2017 15:03
> *To:* 'Manas Mohanty' <mohanty.ran...@gmail.com>; users@kannel.org
> *Subject:* RE: Help regarding sending pound '£' symbol through kannel
>
>
>
> Hi,
>
>
>
> In my understanding, you could send the @ and £ using GSM 7-bit alphabet
> only if the default SMSC encoding is set to GSM or you have set alt-dcs in
> kannel whics sets DCS=241 and should indicate the SMSC to use the 7-bit GSM
> alphabet.
>
>
>
> But you should also consider this document  http://www.linkas.it/docs/
> kannel/Characters,%20Kannel%20&%20MT%20SMS.docx which explains that after
> version 1.4.2 kannel has switched to internal use of utf-8. So bascially
> you should use utf-8 to submit to kannel and kannel will translate to GSM
> alphabet if alt-dces i set to true. This might have evolved with the
> vesrions and I would appreciate if someone sched light to this topic.
>
>
>
> I think you should do some tests with various parameters and draw your own
> conclusions, but first check the default smsc alphabet. This is the
> alphabet used for SMPP, it’s usually ASCII and *is not the same thing as
> the default GSM alphabet.*
>
>
>
> *Davor Spasoski*
>
> *From:* users [mailto:users-boun...@kannel.org <users-boun...@kannel.org>]
> *On Behalf Of *Manas Mohanty
> *Sent:* 22 February 2017 14:34
> *To:* users@kannel.org
> *Subject:* Help regarding sending pound '£' symbol through kannel
>
>
>
> Hi,
>
> I am trying to send pound '£' symbol through kannel using
> charset=utf8=0 but getting '@£' on the handset.
>
> But when I set coding=2, message properly '£' landed on the handset. But
> doing this I am wasting half of the sms capacity as pound symbol is defined
> in the default 7bit GSM 03.38.
>
> Please suggest how to send the message so that I can manage to send it in
> default 7bit GSM 03.38.
>
> Thanks
>
> Manas
>
>
>
>
>
> --
>
> Disclaimer: one.Vip DOO Skopje
> This e-mail (including any attachments) is confidential and may be
> protected by legal privilege. If you are not the intended recipient, you
> should not copy it, re-transmit it, use it or disclose its contents, but
> should return it to the sender immediately and delete your copy from your
> system. Any unauthorized use or dissemination of this message in whole or
> in part is strictly prohibited. Please note that e-mails are susceptible to
> change. one.Vip DOO Skopje shall not be liable for the improper or
> incomplete transmission of the information contained in this communication
> nor for any delay in its receipt or damage to your system.
> Please, do not print this e-mail unless it is necessary! Think about
> saving the environment!
>
> Напомена: оне.Вип ДОО Скопје
> Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да
> биде заштитена со правни привилегии. Доколку не сте лицето на кое таа му е
> наменета пораката, не треба да ја копирате, дистрибуирате или да ја
> откривате нејзината содржина, туку веднаш да ја препратите до испраќачот и
> да ја избришете оригиналната порака и сите нејзини копии од Вашиот
> компјутерски систем. Секое неовластено користење на оваа порака во целост
> или делови од истата е строго забрането. Ве молиме да забележите дека
> електронските пораки се подложни на промени. оне.Вип ДОО Скопје не презема
> одговорност за несоодветно или нецелосно пренесување на информациите
> содржани во оваа комуникација, ниту пак за било какво задоцнување на
> приемот или оштетувања на вашиот систем.
> Ве молиме не ја печатете оваа порака освен ако не е неопходно! Зачувајте
> ја природата!
>

Help regarding sending pound '£' symbol through kannel

[Manas Mohanty]

Hi,

I am trying to send pound '£' symbol through kannel using
charset=utf8=0 but getting '@£' on the handset.
But when I set coding=2, message properly '£' landed on the handset. But
doing this I am wasting half of the sms capacity as pound symbol is defined
in the default 7bit GSM 03.38.

Please suggest how to send the message so that I can manage to send it in
default 7bit GSM 03.38.

Thanks
Manas

Re: Issue in sending long sms emojis

[Manas Mohanty]

Hi,

Did not get any response till now.

On Fri, Dec 16, 2016 at 11:32 AM, Manas Mohanty <mohanty.ran...@gmail.com>
wrote:

> Any suggestion on this. I am waiting for the response.
>
> On Wed, Dec 14, 2016 at 11:42 AM, Manas Mohanty <mohanty.ran...@gmail.com>
> wrote:
>
>> Thanks Jeff for the update.
>>
>> Anybody else facing this issue and solved it by any means.
>>
>> Thanks
>> Manas
>>
>> On Tue, Dec 13, 2016 at 6:27 PM, Jeff Thorn <j...@thorntechnologies.com>
>> wrote:
>>
>>> We have noticed the same issue. My guess is that since emojis are multi
>>> byte characters the message is getting split mid emoji. For the time being,
>>> we have a policy not to put an emoji character around the 36 character
>>> position.
>>>
>>> On Dec 13, 2016 1:21 AM, "Manas Mohanty" <mohanty.ran...@gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I am sending emojis through kannel-1.4.4.
>>>>
>>>> Upto 35 emojis i,e without splitting the sms its delivered to the
>>>> handset without any issue.
>>>>
>>>> But if I send 36 emojis i,s more than one sms split 35 emojis and extra
>>>> ?? is getting delivered to handset. If I send 37 emojis, 36 and extra ?? is
>>>> getting delivered.
>>>>
>>>> So I think one character is getting split with long message(emojis) .
>>>>
>>>> Please suggest how I can send more that 35 emojis without any issue.
>>>>
>>>> Thanks,
>>>> Manas
>>>>
>>>>
>>>>
>>
>

Re: Issue in sending long sms emojis

[Manas Mohanty]

Any suggestion on this. I am waiting for the response.

On Wed, Dec 14, 2016 at 11:42 AM, Manas Mohanty <mohanty.ran...@gmail.com>
wrote:

> Thanks Jeff for the update.
>
> Anybody else facing this issue and solved it by any means.
>
> Thanks
> Manas
>
> On Tue, Dec 13, 2016 at 6:27 PM, Jeff Thorn <j...@thorntechnologies.com>
> wrote:
>
>> We have noticed the same issue. My guess is that since emojis are multi
>> byte characters the message is getting split mid emoji. For the time being,
>> we have a policy not to put an emoji character around the 36 character
>> position.
>>
>> On Dec 13, 2016 1:21 AM, "Manas Mohanty" <mohanty.ran...@gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I am sending emojis through kannel-1.4.4.
>>>
>>> Upto 35 emojis i,e without splitting the sms its delivered to the
>>> handset without any issue.
>>>
>>> But if I send 36 emojis i,s more than one sms split 35 emojis and extra
>>> ?? is getting delivered to handset. If I send 37 emojis, 36 and extra ?? is
>>> getting delivered.
>>>
>>> So I think one character is getting split with long message(emojis) .
>>>
>>> Please suggest how I can send more that 35 emojis without any issue.
>>>
>>> Thanks,
>>> Manas
>>>
>>>
>>>
>

Re: Issue in sending long sms emojis

[Manas Mohanty]

Thanks Jeff for the update.

Anybody else facing this issue and solved it by any means.

Thanks
Manas

On Tue, Dec 13, 2016 at 6:27 PM, Jeff Thorn <j...@thorntechnologies.com>
wrote:

> We have noticed the same issue. My guess is that since emojis are multi
> byte characters the message is getting split mid emoji. For the time being,
> we have a policy not to put an emoji character around the 36 character
> position.
>
> On Dec 13, 2016 1:21 AM, "Manas Mohanty" <mohanty.ran...@gmail.com> wrote:
>
>> Hi,
>>
>> I am sending emojis through kannel-1.4.4.
>>
>> Upto 35 emojis i,e without splitting the sms its delivered to the handset
>> without any issue.
>>
>> But if I send 36 emojis i,s more than one sms split 35 emojis and extra
>> ?? is getting delivered to handset. If I send 37 emojis, 36 and extra ?? is
>> getting delivered.
>>
>> So I think one character is getting split with long message(emojis) .
>>
>> Please suggest how I can send more that 35 emojis without any issue.
>>
>> Thanks,
>> Manas
>>
>>
>>

Issue in sending long sms emojis

[Manas Mohanty]

Hi,

I am sending emojis through kannel-1.4.4.

Upto 35 emojis i,e without splitting the sms its delivered to the handset
without any issue.

But if I send 36 emojis i,s more than one sms split 35 emojis and extra ??
is getting delivered to handset. If I send 37 emojis, 36 and extra ?? is
getting delivered.

So I think one character is getting split with long message(emojis) .

Please suggest how I can send more that 35 emojis without any issue.

Thanks,
Manas

TLS support in kannel

[Manas Mohanty]

Hi,
Does kannel support TLS for smsc bind. If yes, how to do that.

Regards,
Manas

Re: Queuing Messages

[Manas Mohanty]

Hi,

We are also facing this issue. No clue how to resolve this. Only solution
is to restart but restart loss messages in queue. We are using
gateway-1.4.4.

On Thu, May 19, 2016 at 4:32 PM, Amelye Chatila  wrote:

> Hello,
>
> Messages get queued, we found that it is because of an I/O Error below
>
> smsc-one.log
>
> 2016-05-18 08:23:53 [6095] [41] ERROR: SMPP[smsc-one]: I/O error or other
> error. Re-connecting.
> 2016-05-18 08:23:53 [6095] [41] ERROR: SMPP[smsc-one]: Couldn't connect to
> SMS center (retrying in 10 seconds).
>
> bearerbox.log
>
> 2016-05-18 08:25:10 [6095] [10] DEBUG: Routing failed, re-queued.
> 2016-05-18 08:25:10 [6095] [10] DEBUG: Routing failed, re-queued.
>
> Routing failed means can not find the smsc but the smsc is up. The only
> solution we have so far is to restart.
>
> The issue why the queue is not emptied when the bind is up again? Is this
> I/O Error a connection error to SMSC?
>
> Thank you!
>

Re: Kannel Make issue on Debian Jessie

[Manas Mohanty]

Install bison-2.5.1 .. don't install it from apt-get install. Delete
existing kannel dir .. untar it fresh.
./configure
make install


On Thu, Dec 3, 2015 at 7:57 PM, Richard Ng  wrote:

> There was an issue with my bison install..a valid PATH was missing.
>
> I added the path and now this issue is fixed.
>
> Thanks
>
> -Original Message-
> From: users [mailto:users-boun...@kannel.org] On Behalf Of Milan P. Stanic
> Sent: Thursday, November 26, 2015 9:23 AM
> To: users@kannel.org
> Subject: Re: Kannel Make issue on Debian Jessie
>
> On Thu, 2015-11-26 at 07:33, Richard Ng wrote:
> > I'm trying to install kannel 1.4.4 on Debian Jessie and running into
> > the following error:
> >
> > gcc -std=gnu99 -D_REENTRANT=1 -I. -Igw -g -O2 -D_XOPEN_SOURCE=600
> > -D_BSD_SOURCE -D_LARGE_FILES= -I/usr/include/libxml2
> > -I/usr/include/openssl -I/usr/include/mysql -o wmlscript/wslexer.o -c
> > wmlscript/wslexer.c
> >
> > wmlscript/wslexer.c:221:32: error: unknown type name 'YYLTYPE'
> >
> > int ws_yy_lex(YYSTYPE *yylval, YYLTYPE *yylloc, void *context)
> >
> > Makefile:231: recipe for target 'wmlscript/wslexer.o' failed
> >
> > make: *** [wmlscript/wslexer.o] Error 1
> >
> > anyone have an idea how to fix this?
>
> Do you have installed all needed development packages for Kannel?
> Bison/Flex?
>
>
>
>

Need Opensmppbox help for dlr route

[Manas Mohanty]

Hi,

I am using opensmppbox.
I have noticed certain thing that in the case of multiple Rx or TRx session
while submitting dlr opensmppbox is sending dlr to particularly one (first)
session in all_boxes queue in find_receiver_box function

for (cnt = 0; cnt < gwlist_len(all_boxes); cnt++) {
thisbox = (Boxc *)gwlist_get(all_boxes, cnt);
if ((thisbox->login_type == SMPP_LOGIN_RECEIVER ||
thisbox->login_type == SMPP_LOGIN_TRANSCEIVER) &&
(octstr_compare(thisbox->boxc_id, box->boxc_id) == 0) && thisbox->alive) {
return thisbox;
}
}

Is there any way and is anyone tried to make round robin manner or
something like random pick of esme, so that all esmes will distribute the
load ??


Regards,
Manas

Make failed for kannel 1.4.4

[Manas Mohanty]

Hi,

I am trying to install kannel gateway 1.4.4 on Debian jessie and getting
below error while make.

In file included from wmlscript/wslexer.c:72:0:
y.tab.h:262:5: error: conflicting types for ‘ws_yy_parse’
In file included from wmlscript/wslexer.c:70:0:
wmlscript/wsint.h:296:5: note: previous declaration of ‘ws_yy_parse’ was
here
 int ws_yy_parse(void *context);
 ^
Makefile:231: recipe for target 'wmlscript/wslexer.o' failed
make: *** [wmlscript/wslexer.o] Error 1

I have installed bison but no luck.

Please suggest me what can be the issue.

Regards,
Manas

Unicode long message spliting in 140 charactors

[Manas Mohanty]

Hi All,


I am using kannel sms gateway 1.4.3 .
When sending unicode long message using smsbox url in kannel bearerbox log
it showing each part sm_length = 140. i,e kannel spliting unicode long
message in 140 characters instead of 70.

I have tried with 1.5.0 also but result is same.

kannel url with  coding=2 -

http://xxx.xxx.xx.x:8080/sendsms?username=tester=foobar=%2B17542059075=23=%E0%A4%AE%E0%A4%B9%E0%A4%BE%E0%A4%B0%E0%A4%BE%E0%A4%B7%E0%A5%8D%E0%A4%9F%E0%A5%8D%E0%A4%B0%20%E0%A4%95%E0%A5%87%20%E0%A4%B0%E0%A4%BE%E0%A4%9C%E0%A4%B8%E0%A5%8D%E0%A4%B5%20%E0%A4%AE%E0%A4%82%E0%A4%A4%E0%A5%8D%E0%A4%B0%E0%A5%80%E0%A4%AE%E0%A4%B9%E0%A4%BE%E0%A4%B0%E0%A4%BE%E0%A4%B7%E0%A5%8D%E0%A4%9F%E0%A5%8D%E0%A4%B0%20%E0%A4%95%E0%A5%87%20%E0%A4%B0%E0%A4%BE%E0%A4%9C%E0%A4%B8%E0%A5%8D%E0%A4%B5%20%E0%A4%AE%E0%A4%82%E0%A4%A4%E0%A5%8D%E0%A4%B0%E0%A5%80%E0%A4%AE%E0%A4%B9%E0%A4%BE%E0%A4%B0%E0%A4%BE%E0%A4%B7%E0%A5%8D%E0%A4%9F%E0%A5%8D%E0%A4%B0%20%E0%A4%95%E0%A5%87%20%E0%A4%B0%E0%A4%BE%E0%A4%9C%E0%A4%B8%E0%A5%8D%E0%A4%B5%20%E0%A4%AE%E0%A4%82%E0%A4%A4%E0%A5%8D%E0%A4%B0%E0%A5%80=access2=2=91xx=http://requestb.in/1h5qnmi1=callsiprtc9

kannel bearerbox log -

2015-09-08 08:09:06 [19419] [8] DEBUG: boxc_receiver: sms received
2015-09-08 08:09:06 [19419] [8] DEBUG: new split_parts created 0x2550990
2015-09-08 08:09:06 [19419] [8] DEBUG: send_msg: sending msg to box:
<127.0.0.1>
2015-09-08 08:09:06 [19419] [6] DEBUG: SMPP[access2]: Sending PDU:
2015-09-08 08:09:06 [19419] [6] DEBUG: SMPP PDU 0x25449b0 dump:
2015-09-08 08:09:06 [19419] [6] DEBUG:   type_name: submit_sm
2015-09-08 08:09:06 [19419] [6] DEBUG:   command_id: 4 = 0x0004
2015-09-08 08:09:06 [19419] [6] DEBUG:   command_status: 0 = 0x
2015-09-08 08:09:06 [19419] [6] DEBUG:   sequence_number: 2 = 0x0002
2015-09-08 08:09:06 [19419] [6] DEBUG:   service_type: NULL
2015-09-08 08:09:06 [19419] [6] DEBUG:   source_addr_ton: 1 = 0x0001
2015-09-08 08:09:06 [19419] [6] DEBUG:   source_addr_npi: 1 = 0x0001
2015-09-08 08:09:06 [19419] [6] DEBUG:   source_addr: "17542059075"
2015-09-08 08:09:06 [19419] [6] DEBUG:   dest_addr_ton: 2 = 0x0002
2015-09-08 08:09:06 [19419] [6] DEBUG:   dest_addr_npi: 1 = 0x0001
2015-09-08 08:09:06 [19419] [6] DEBUG:   destination_addr: "91x74740"
2015-09-08 08:09:06 [19419] [6] DEBUG:   esm_class: 67 = 0x0043
2015-09-08 08:09:06 [19419] [6] DEBUG:   protocol_id: 0 = 0x
2015-09-08 08:09:06 [19419] [6] DEBUG:   priority_flag: 0 = 0x
2015-09-08 08:09:06 [19419] [6] DEBUG:   schedule_delivery_time: NULL
2015-09-08 08:09:06 [19419] [6] DEBUG:   validity_period: NULL
2015-09-08 08:09:06 [19419] [6] DEBUG:   registered_delivery: 1 = 0x0001
2015-09-08 08:09:06 [19419] [6] DEBUG:   replace_if_present_flag: 0 =
0x
2015-09-08 08:09:06 [19419] [6] DEBUG:   data_coding: 8 = 0x0008
2015-09-08 08:09:06 [19419] [6] DEBUG:   sm_default_msg_id: 0 = 0x
2015-09-08 08:09:06 [19419] [6] DEBUG:   sm_length: 140 = 0x008c
2015-09-08 08:09:06 [19419] [6] DEBUG:   short_message:
2015-09-08 08:09:06 [19419] [6] DEBUG:Octet string at 0x254f950:
2015-09-08 08:09:06 [19419] [6] DEBUG:  len:  140
2015-09-08 08:09:06 [19419] [6] DEBUG:  size: 1024
2015-09-08 08:09:06 [19419] [6] DEBUG:  immutable: 0
2015-09-08 08:09:06 [19419] [6] DEBUG:  data: 05 00 03 00 02 01 e0 a4
ae e0 a4 b9 e0 a4 be e0   
2015-09-08 08:09:06 [19419] [6] DEBUG:  data: a4 b0 e0 a4 be e0 a4 b7
e0 a5 8d e0 a4 9f e0 a5   
2015-09-08 08:09:06 [19419] [6] DEBUG:  data: 8d e0 a4 b0 20 e0 a4 95
e0 a5 87 20 e0 a4 b0 e0    .. 
2015-09-08 08:09:06 [19419] [6] DEBUG:  data: a4 be e0 a4 9c e0 a4 b8
e0 a5 8d e0 a4 b5 20 e0   .. .
2015-09-08 08:09:06 [19419] [6] DEBUG:  data: a4 ae e0 a4 82 e0 a4 a4
e0 a5 8d e0 a4 b0 e0 a5   
2015-09-08 08:09:06 [19419] [6] DEBUG:  data: 80 e0 a4 ae e0 a4 b9 e0
a4 be e0 a4 b0 e0 a4 be   
2015-09-08 08:09:06 [19419] [6] DEBUG:  data: e0 a4 b7 e0 a5 8d e0 a4
9f e0 a5 8d e0 a4 b0 20   ...
2015-09-08 08:09:06 [19419] [6] DEBUG:  data: e0 a4 95 e0 a5 87 20 e0
a4 b0 e0 a4 be e0 a4 9c   .. .
2015-09-08 08:09:06 [19419] [6] DEBUG:  data: e0 a4 b8 e0 a5 8d e0 a4
b5 20 e0 a4   . ..
2015-09-08 08:09:06 [19419] [6] DEBUG:Octet string dump ends.
2015-09-08 08:09:06 [19419] [6] DEBUG:   more_messages_to_send: 1 =
0x0001
2015-09-08 08:09:06 [19419] [6] DEBUG: SMPP PDU dump ends.
2015-09-08 08:09:06 [19419] [6] DEBUG: SMPP[access2]: Sending PDU:
2015-09-08 08:09:06 [19419] [6] DEBUG: SMPP PDU 0x25449b0 dump:
2015-09-08 08:09:06 [19419] [6] DEBUG:   type_name: submit_sm
2015-09-08 08:09:06 [19419] [6] DEBUG:   command_id: 4 = 0x0004
2015-09-08 08:09:06 [19419] [6] DEBUG:   command_status: 0 = 0x
2015-09-08 08:09:06 [19419] [6] DEBUG:   sequence_number: 3 = 0x0003
2015-09-08 08:09:06 [19419] [6] DEBUG:   service_type: NULL