Long Message Problem

[shaan]

Hello,

I have downloaded your SMPP Client/Server demo and testing it. I am very much interested in purchasing it for a project that I am doing for my client. However, I have following questions:

a) I tried sending long message (more than 160 characters) using Payload as well as ShortMessage submit modes but the message always gets delivered as split messages (i.e. it is not delivered as concatenated text message). Is it a problem with the library or is it a limitation of trial version?

b) If we buy the source code then do we get updates of the source code as well?

Looking forward to your response ASAP.

Thanks & Regards

Shaan

[shaan]

Hi,
We noticed another problem. While using the ClientDemo if we put a internet IP address (a valid SMPP server that is running), the demo throws a exception. However, if we put the host name, it recognizes it.

Whereas if we try to connect to same SMPP app on localhost but put the hostname as 127.0.0.1 then it has no problems connecting!!!

What could be the cause of this problem?

Shaan

[alt]

Dear Shaan,

a) Trial version has full functionality. It has ony 30 days limit.
it could be SMSC side problem as well as library problem.
To eliminate library problems please post here "Sending Data:" and "Received Data:". I'll check if SubmitSm message was correct.

b) Yes, you will get updates of source code as well.
When you will need update just send email message and I will send you last source code back.

Alexey

[alt]

Please post here StackTrace of exception.
Possible you have problem with method Dns.GetHostEntry(hostName)
It can be caused by DNS settings or HOSTS file.

You can also try method
public bool Connect(IPEndPoint endPoint, bool ssl)

[shaan]

Hi,
As required by you please see below the Sending & Receiving data below:

FOR Submit Mode = ShortMessage
=======================

16:51:22: SmppClient connected
16:51:22: Binding SmppClient for SystemId: iglogix
16:51:22: SmppClient bound
16:51:22: Bind result : system is with status ESME_ROK
16:51:22: Sending Data: 0000002600000009000000004c8f1ed969676c6f676978006173646639383736000034000000
16:51:22: Received Data: 0000001180000009000000004c8f1ed900
16:51:52: Sending Data: 000000e100000004000000004c8f1eda0000004c4f47695800010139313938373330393437363700400000003130313032383034353135313030302b00000000009f0500037402015468697320697320612074657374206d657373616765207768696368206973206c6f6e676572207468616e206f6e652068756e6472656420616e642073697874792063686172637465727320746f20636865636b20636f6e636174656e61746564206d6573736167652064656c697665727920746f207468652070686f6e652e2049742073686f756c64206265207265616461626c65206173
16:51:52: Received Data: 0000002380000004000000004c8f1eda36333432333638383636303735303039323900
16:51:52: SubmitSmResp received. Status: ESME_ROK, Message Id: 634236886607500929, Sequence: 1284447962
16:51:52: Sending Data: 0000007b00000004000000004c8f1edb0000004c4f47695800010139313938373330393437363700400000003130313032383034353135313030302b000000000039050003740202206f6e652073696e676c65206d657373616765206f6e6c7920616e64206e6f74206d756c7469706c65206d657373616765732e
16:51:52: Received Data: 0000002380000004000000004c8f1edb36333432333638383636303938343038333900
16:51:52: SubmitSmResp received. Status: ESME_ROK, Message Id: 634236886609840839, Sequence: 1284447963


For SubmitMode = Payload
==================

16:56:03: SmppClient connected
16:56:03: Binding SmppClient for SystemId: iglogix
16:56:03: SmppClient bound
16:56:03: Bind result : system is with status ESME_ROK
16:56:03: Sending Data: 000000260000000900000000557d70e469676c6f676978006173646639383736000034000000
16:56:03: Received Data: 000000118000000900000000557d70e400
16:56:13: Sending Data: 000000f40000000400000000557d70e50000004c4f47695800010139313938373330393437363700000000003130313032383034353631333030302b000000000000020c00020089020f000100020e0001020426000101042400995468697320697320612074657374206d657373616765206c6f6e676572207468616e206f6e652068756e6472656420616e64207369787479206368617261637465727320746f20636865636b2074686520636f6e636174656e61746564206d6573736167652064656c69766572792e2049742073686f756c642062652064656c697665726564206173206d756c7469706c65206d6573736167
16:56:13: Received Data: 000000238000000400000000557d70e536333432333638383932323031353035313600
16:56:13: SubmitSmResp received. Status: ESME_ROK, Message Id: 634236889220150516, Sequence: 1434284261
16:56:13: Sending Data: 000000880000000400000000557d70e60000004c4f47695800010139313938373330393437363700000000003130313032383034353631333030302b000000000000020c00020089020f000101020e00010204260001010424002d657320627574207265616420617320612073696e676c65206d65737361676520696e207468652070686f6e652e
16:56:13: Received Data: 000000238000000400000000557d70e636333432333638383932323233333432373800
16:56:13: SubmitSmResp received. Status: ESME_ROK, Message Id: 634236889222334278, Sequence: 1434284262

In both the cases I received multiple SMS on my phone (read as separate messages and not concatenated)

[alt]

ShortMessage is correct, but in payload i found small bug, where SAR sequence number started from 0 instead of 1.

Please download updated version from
http://www.inetlab.ru/Downloading/Inetlab.SMPP.zip
and check payload mode again

Also please ask SMSC side what concatenated messages mode they support.
I know some SMPP server which doesn't support multi-part messages.

Also some mobile phones has problem with this. So please try to send to another phone.

[shaan]

Hi alt,

The Payload method seems to be working fine now but I have a question about "SubmitMode = ShortMessage"

It seems that the user must specifically program the client to add SAR parameters in TLV to send a concatenated SMS and the library does not do it automatically. If SAR params not added to TLV by client program then the message is simply sent as multiple messages split as single messages!

Am I right or am I missing something??

Shaan

[alt]

I'm glad that concatenated message is finally working.

If user uses methods PrepareSubmit, SubmitText or SubmitTextAsync
all required TLV paramters are added to the messages in Payload mode.

in ShortMessage mode same methods add User Data Header parameters to the message.

Possible your SMSC supports only Payload mode.

[shaan]

In my understanding of SMPP 3.4 TLV sar params are applicable for both payload as well as short message! Thats what almost all SMPP clients available in the market do. But your library is adding the message part info only in UDH!!!

The SMSC used by me supports TextMessage as well as Payload and it worked with almost all clients we tested. However, we want a commercial product rather than a open source product and hence we are testing your product.

Is it possible for you to also add the message part info to TLV sar params?

Shaan

[shaan]

By the way... SMPP 3.4 does not have any UDH part dedicated for message parts? So where are you putting them?? The specs clearly say that it has to be in the SAR params of the TLV!!

If you send me your email address, I can forward you a copy of the original SMPP 3.4 specs.

Shaan

[alt]

You are right, concatenation is provided via two methods:
- GSM User data headers
- SMPP SAR parameters

Since old ALT.SMS.SmppClient library
GSM User data headers way with text in short_message is called SubmitMode.ShortMessage, and
SMPP SAR parameters way with text in message_payload is called SubmitMode.Payload


But as far as I understood you need mode like ShortMessageSAR ?
Where text is in the short_message field and concatenation in SAR parameters?

[shazia1]

Refer to the demo application available with trial, when i send shortmessage from client, the message is properly received on the server. But when i send Payload message from client, in the server_evClientSubmitSm() event of server, data.ShortMessage is null. I am unable to verify whether my long message is received properly on the other end or not. Am I missing something??