InetLab

Hello Alt,

I connected the application to a particular bind but any time I send message to it, The text message is always blank and other parameters are ok. What could be responsible for this. I compared with the one that is working and the only thing that is different in the application i am moving from is ThrottleTime.
Working: "ThrottleTime"<value>0</value>
Not Working: "ThrottleTime><value>100</value

Help look into this issues please.

Please I need your response. Here is the log
8/13/2012 10:08:52 AM: Sending Data: 000000230000000900000000197bc96a6d786d616e75006d786d406e75000034000000
8/13/2012 10:08:52 AM: Received Data: 000000268000000900000000197bc96a4d6f62696c655f586365746572615f32000210000134
8/13/2012 10:08:53 AM: Received Data: 000000470000000500000000000000010001013233343830353630303032323800040933303332380000000000000000000000000e0001010006000101042400064a61696c6572
8/13/2012 10:08:53 AM: Sending Data: 0000001180000005000000000000000100
8/13/2012 10:09:03 AM: Sending Data: 000000660000000400000000197bc96d00000033303332380001013233343830353630303032323800000000003132303831353130303930333030302b000100000023536f7272792c20746861742077617320616e20696e76616c696420726571756573742e
8/13/2012 10:09:03 AM: Received Data: 000000198000000400000000197bc96d316561303838653400
8/13/2012 10:09:06 AM: Received Data: 000000cd0000000500000000000000020001013233343830353630303032323800050033303332380004000000000000000000000e0001010006000101001e000931656130383865340004270001020424007a69643a30353133383337323834207375623a30303120646c7672643a303031207375626d697420646174653a3132303831333130303920646f6e6520646174653a3132303831333130303920737461743a44454c49565244206572723a30303020746578743a536f7272792c20746861742077617320616e2069
8/13/2012 10:09:06 AM: Sending Data: 0000001180000005000000000000000200
8/13/2012 10:10:06 AM: Sending Data: 000000100000001500000000197bc970
8/13/2012 10:10:06 AM: Received Data: 000000108000001500000000197bc970
8/13/2012 10:11:06 AM: Sending Data: 000000100000001500000000197bc971
8/13/2012 10:11:06 AM: Received Data: 000000108000001500000000197bc971
8/13/2012 10:12:06 AM: Sending Data: 000000100000001500000000197bc972
8/13/2012 10:12:07 AM: Received Data: 000000108000001500000000197bc972
8/13/2012 10:13:07 AM: Sending Data: 000000100000001500000000197bc973
8/13/2012 10:13:07 AM: Received Data: 000000108000001500000000197bc973
8/13/2012 10:14:07 AM: Sending Data: 000000100000001500000000197bc974
8/13/2012 10:14:07 AM: Received Data: 000000108000001500000000197bc974
8/13/2012 10:14:41 AM: Received Data: 000000450000000500000000000000030001013233343830353630303032323800040933303332380000000000000000000000000e00010100060001010424000454657374
8/13/2012 10:14:41 AM: Sending Data: 0000001180000005000000000000000300
8/13/2012 10:14:44 AM: Sending Data: 000000660000000400000000197bc97700000033303332380001013233343830353630303032323800000000003132303831353130313434343030302b000100000023536f7272792c20746861742077617320616e20696e76616c696420726571756573742e
8/13/2012 10:14:44 AM: Received Data: 000000198000000400000000197bc977323132363363653400
8/13/2012 10:15:44 AM: Sending Data: 000000100000001500000000197bc978
8/13/2012 10:15:44 AM: Received Data: 000000108000001500000000197bc978
8/13/2012 10:16:44 AM: Sending Data: 000000100000001500000000197bc979
8/13/2012 10:16:44 AM: Received Data: 000000108000001500000000197bc979
8/13/2012 10:17:44 AM: Sending Data: 000000100000001500000000197bc97a
8/13/2012 10:17:44 AM: Received Data: 000000108000001500000000197bc97a
8/13/2012 10:18:02 AM: Received Data: 0000004d0000000500000000000000040001013233343830353630303032323800040933303332380000000000000000000000000e00010100060001010424000c4a7573742074657374696e67
8/13/2012 10:18:02 AM: Sending Data: 0000001180000005000000000000000400
8/13/2012 10:18:04 AM: Sending Data: 000000660000000400000000197bc97d00000033303332380001013233343830353630303032323800000000003132303831353130313830343030302b000100000023536f7272792c20746861742077617320616e20696e76616c696420726571756573742e
8/13/2012 10:18:04 AM: Received Data: 000000198000000400000000197bc97d323261313930653400
8/13/2012 10:18:07 AM: Received Data: 000000cd0000000500000000000000050001013233343830353630303032323800050033303332380004000000000000000000000e0001010006000101001e000932326131393065340004270001020424007a69643a30353831303133373332207375623a30303120646c7672643a303031207375626d697420646174653a3132303831333130313820646f6e6520646174653a3132303831333130313820737461743a44454c49565244206572723a30303020746578743a536f7272792c20746861742077617320616e2069
8/13/2012 10:18:07 AM: Sending Data: 0000001180000005000000000000000500

Hi majortargets,

I don't see any problem in your log.

Where did you get blank text? server side? mobile phone?
what ThrottleTime is doing for your application?
Did you try to send text in MessagePayload?

Hello Alt,
I got the blank text at the server application level i.e receiving from the SMSC.
There is no ThrottleTime in my application but I noticed it has in one application we were using before i move to Inetlab.SMPP
No, this occur at the point of receiving message from the smsc

Your immedate response will be highly appreciated please.

TThanks

In short, DeliverSm message text not in user data, but in Optional TLV parameter MessagePayload.
It is delivery receipt and you can try to get data from Receipt property.
Version 1.1 has better receipt data parsing.

Hello Alt,

Do you have a code segment I can use to get this text message using version 1.0? since 1.1 is still in beta stage.

Please I need this urgently, I need to sort it out ASAP as it is delaying a lot of things.
Thanks

string text = client.GetMessageText(data.Optional[OptionalTags.MessagePayload], data.DataCoding);

Sorry for disturbing you in need to verify following.

The code will be inside client_evDeliverSm right?
How do I test if the text is in optional parameter before executing the code?

Thanks

yes, code will be inside client_evDeliverSm
simple you can test it with code but i suggest you, when you have time for updating your code please consider to move to 1.1 version.
It has better support for delivery receipt. You can take receipt parameters from data.Receipt property.

Some SMSC sends delivery receipt without message text, only two TLV parameters for ReceiptedMessageId and MessageState.

SmppClientDemo application has example how to handle delivery receipt.

Hello Alt,

It worked. Thanks for your help.

One last issue that I have is that messages more than 160 characters are not concatenated they come in as 2 different messages.

I will try out version 1.1 ASAP.

Thanks once more

In 1.1 you can use MessageComposer class to concatenate DeliverSm messages.

In 1.0 you need to get concatenation parameters from UserDataHeader or from TLV SAR parameters (depends on SMSC), store message text from UserData short message or from TLV MessagePayload into temporary hash with key concatenation reference number + source address. And get whole message from hash when you get last message segment.