Receiving Message from SMSC

chaoraksa · Post by **chaoraksa** » Wed Aug 05, 2009 1:24 am

Hi alt!

I still got same errror before invalid deliver_sm packet.

8:19:01 AM: SmppClient connected
8:19:01 AM: Binding SmppClient for SystemId: xxxx
8:19:01 AM: SmppClient bound
8:19:01 AM: Bind result : system is NowSMS with status ESME_ROK
8:19:01 AM: Received Data: 0000001c8000000900000000575ce71e4e6f77534d53000210000134
8:19:01 AM: Sending Data: 000000230000000900000000575ce71e3233363700323336376d61696c000034000000
8:19:36 AM: Received Data: 000000ce000000050000000000000002736d7363390001013835353938363130373533000001323336370040000000000100000099472d6765742075700a4f2d6f70656e20796f757220657965730a4f2d6f7574206f6620796f7572206265640a442d6461792068617320726973656e0a4d2d6d65727279206c6966650a4f2d6f6c6420647265616d732063756d20747275650a522d726973652024207368696e650a4e2d6e65772066726e64730a492d69646561206f66206c6966650a4e2d6e696365206675747572650a472d
8:19:36 AM: DeliverSm received :  Sequence : 2 SourceAddr : 85598610753 Coding : 0 MessageText : ine
N-new frnds
I-idea of life
N-nice future
G-
8:19:36 AM: Sending Data: 0000001180000005000000000000000200
8:19:38 AM: Received Data: 00000042000000050000000000000003736d736339000101383535393836313037353300000132333637004000000000010000000d474f4f44444159203420552120
8:19:38 AM: Sending Data: 0000001180000005000000080000000300
8:19:38 AM: Invalid DELIVER_SM packet

Post by **alt** » Wed Aug 05, 2009 7:28 am

What library version do you use?

chaoraksa · Post by **chaoraksa** » Wed Aug 05, 2009 8:45 am

I use ur last one.

chaoraksa · Post by **chaoraksa** » Wed Aug 05, 2009 10:01 am

I have no idea alt.

Post by **alt** » Wed Aug 05, 2009 6:16 pm

I have checked once again and found that packet
00000042000000050000000000000003736d736339000101383535393836313037353300000132333637004000000000010000000d474f4f44444159203420552120
is parsed well with last version

Please remove all instances of ALT.SMS.SmppClient.dll from your computer
and extract from last SmppClient.zip

chaoraksa · Post by **chaoraksa** » Thu Aug 06, 2009 1:48 am

I down ur new version and i do nothing just run ur sample and send test long text sms. I also debug it too but i not get this 3 items
1) msg_ref_num
2) total segments
3) sequence number

and got same log like this

Code: Select all

8:42:59 AM: SmppClient connected
8:42:59 AM: Binding SmppClient for SystemId: 2367
8:42:59 AM: SmppClient bound
8:42:59 AM: Bind result : system is NowSMS with status ESME_ROK
8:42:59 AM: Sending Data: 0000002300000009000000007f5d5d513233363700323336376d61696c000034000000
8:42:59 AM: Received Data: 0000001c80000009000000007f5d5d514e6f77534d53000210000134
8:43:35 AM: Received Data: 000000ce000000050000000000000002736d7363390001013835353938363130373533000001323336370040000000000100000099472d6765742075700a4f2d6f70656e20796f757220657965730a4f2d6f7574206f6620796f7572206265640a442d6461792068617320726973656e0a4d2d6d65727279206c6966650a4f2d6f6c6420647265616d732063756d20747275650a522d726973652024207368696e650a4e2d6e65772066726e64730a492d69646561206f66206c6966650a4e2d6e696365206675747572650a472d
8:43:35 AM: DeliverSm received :  Sequence : 2 SourceAddr : 85598610753 Coding : 0 MessageText : ine
N-new frnds
I-idea of life
N-nice future
G-
8:43:35 AM: Sending Data: 0000001180000005000000000000000200
8:43:37 AM: Received Data: 00000042000000050000000000000003736d736339000101383535393836313037353300000132333637004000000000010000000d474f4f44444159203420552120
8:43:38 AM: Sending Data: 0000001180000005000000080000000300
8:43:38 AM: Invalid DELIVER_SM packet

Does it because of my smsc?

Thanks,,
Raksa

chaoraksa · Post by **chaoraksa** » Fri Aug 07, 2009 1:52 am

Hi alt!

I implement with your library and i got the first part of Long message from my phone, where is my second part message. I can see it in the client_evReceiveData event and i got same error Invalid DELIVER_SM packet. I want all of that sms that i sent. one more thing i wonder i send text like this :

Code: Select all

G-get up 
O-open your eyes 
O-out of your bed 
D-day has risen 
M-merry life 
O-old dreams cum true 
R-rise $ shine 
N-new frnds 
I-idea of life 
N-nice future 
G-GOODDAY 4 U! "

but i got like this :

Code: Select all

i-get up 
O-open your eyes 
O-out of your bed 
D-day has risen 
M-merry life 
O-old dreams cum true 
R-rise $ shine 
N-new frnds 
I-idea of life 
N-nice future 
G

This problem i got when i use your new library.

Thanks,,
Raksa

chaoraksa · Post by **chaoraksa** » Fri Aug 07, 2009 8:23 pm

Please help answer my question

Post by **alt** » Tue Aug 11, 2009 8:28 pm

Can you still get Invalid DELIVER_SM packet?

chaoraksa · Post by **chaoraksa** » Wed Aug 12, 2009 4:25 am

yes, like the log i show u above.

Post by **alt** » Mon Aug 24, 2009 5:25 pm

first short message:

000000ce - command_length
00000005 - command_id
00000000 - command_status
00000002 - sequence_number
736d73633900 - service_type
0101 - source_addr_ton, source_addr_npi
383535393836313037353300 - source_addr
0001 - dest_addr_ton, dest_addr_npi
3233363700 - destination_addr
40 - esm_class (UDHI (user data header indicator) is on, but UDH (user data header) does not exists in short_messag field. This is a mistake from SMSC)
00 - protocol_id
00 - priority_flag
00 - schedule_delivery_time
00 - validity_period
01 - registered_delivery
00 - replace_if_present_flag
00 - data_coding
00 - sm_default_msg_id
99 - sm_length (153 bytes)

short_message:
472d6765742075700a4f
2d6f70656e20796f7572
20657965730a4f2d6f75
74206f6620796f757220
6265640a442d64617920
68617320726973656e0a
4d2d6d65727279206c69
66650a4f2d6f6c642064
7265616d732063756d20
747275650a522d726973
652024207368696e650a
4e2d6e65772066726e64
730a492d69646561206f
66206c6966650a4e2d6e
69636520667574757265
0a472d

153 bytes of short_message contains text (including new line symbol):
"G-get up
O-open your eyes
O-out of your bed
D-day has risen
M-merry life
O-old dreams cum true
R-rise $ shine
N-new frnds
I-idea of life
N-nice future
G-"

second short message:

00000042 - command_length
00000005 - command_id
00000000 - command_status
00000003 - sequence_number
736d73633900 - service_type
0101 - source_addr_ton, source_addr_npi
383535393836313037353300 - source_addr
0001 - dest_addr_ton, dest_addr_npi
3233363700 - destination_addr
40 - esm_class (UDHI is on, but again no UDH in the short_message field)
00 - protocol_id
00 - priority_flag
00 - schedule_delivery_time
00 - validity_period
01 - registered_delivery
00 - replace_if_present_flag
00 - data_coding
00 - sm_default_msg_id
0d - sm_length (13 bytes)
short_message:
474f4f44444159203420
552120

13 bytes of short_message contains text:
"GOODDAY 4 U! "

Please send this to SMSC owner and ask them why DELIVER_SM packet does not contain User Data Header.
Information
1) msg_ref_num
2) total segments
3) sequence number
which you asked from me should be in missing User Data Headers.