Unable to send concatenated message

Unable to send concatenated message SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through November 14, 2013 » Unable to send concatenated message « Previous || Next »
Author Message
Mohamed Anis
New member
Username: Mohamedanis

Post Number: 1
Registered: 02-2013
Posted on Tuesday, November 12, 2013 - 07:43 am:   

Dears,

I tried to send long message but almost failed, single message successfully sent and "SMSC Character Set" putted as “iso-8859-1 (Latin)”

please advise.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4737
Registered: 08-2008
Posted on Tuesday, November 12, 2013 - 03:32 pm:   

Hi,

For SMPP connections, there are different encodings expected by different providers ... because the SMPP standard is not specific enough.

What you need to do is try some different options under "Advanced Settings" for the SMPP connection in NowSMS, in order to determine which format works best with your provider.

Here are the different combinations that you should try:

1.) Use WDP Adaptation - NOT checked
Encode long text messages with 7-bit packing - NOT checked
Use TLV parameters - NOT checked

2.) Use WDP Adaptation - NOT checked
Encode long text messages with 7-bit packing - checked
Use TLV parameters - NOT checked

3.) Use WDP Adaptation - NOT checked
Encode long text messages with 7-bit packing - NOT checked
Use TLV parameters - checked

4.) Use WDP Adaptation - checked
Encode long text messages with 7-bit packing - NOT checked
Use TLV parameters - NOT checked

Unless your SMPP provider has problems handling long messages, one of the above should work.

For testing each combination of settings, you must press Ok/Ok/Apply in order to save the setting in NowSMS. Then either restart the service with the changed settings, or wait about 60 seconds, before trying another message.

I have listed the different combinations in the order of which is the most likely to work. (1 is most likely, 2 is next most likely, etc.)

If you are still experiencing problems, please explain what happens in the different scenarios.

--
Des
NowSMS Support
Mohamed Anis
New member
Username: Mohamedanis

Post Number: 2
Registered: 02-2013
Posted on Wednesday, November 13, 2013 - 08:42 am:   

HI,

I test 4 steps and below log for all
1-
[SMS]
SubmittedBy=127.0.0.1
Data=E8E8F41C949E83C2207A794E07B5CBF379F85C06351474747A0E4ACF416110BD3CA783DAE5F 93C7C2E831A0A3A3A3D07A5E7A030885E9ED341EDF27C1E3E97410D051D9D9E83D2735018442FCFE 9A076793E0F9FCBA086828E4ECF41E939280CA297E77450BB3C9F87CF6550434147A7E7A0F41C140 6D1CB733AA85D9ECFC3E732A8A1A0A3D3
UDH=0500039F0201
Binary=1
PhoneNumber=01003746656
LastRetryTime=20131113105635
LastErrorInfo=ERROR: Timeout waiting for response from server or lost connection -- SMPP - 192.168.0.61:2775




2-
[SMS]
SubmittedBy=127.0.0.1
Data=E8E8F41C949E83C2207A794E07B5CBF379F85C06351474747A0E4ACF416110BD3CA783DAE5F 93C7C2E831A0A3A3A3D07A5E7A030885E9ED341EDF27C1E3E97410D051D9D9E83D2735018442FCFE 9A076793E0F9FCBA086828E4ECF41E939280CA297E77450BB3C9F87CF6550434147A7E7A0F41C140 6D1CB733AA85D9ECFC3E732A8A1A0A3D3
UDH=0500039F0201
Binary=1
PhoneNumber=01003746656
LastRetryTime=20131113110923
LastErrorInfo=ERROR: Timeout waiting for response from server or lost connection -- SMPP - 192.168.0.61:2775

3-
[SMS]
SubmittedBy=127.0.0.1
Data=E8E8F41C949E83C2207A794E07B5CBF379F85C06351474747A0E4ACF416110BD3CA783DAE5F 93C7C2E831A0A3A3A3D07A5E7A030885E9ED341EDF27C1E3E97410D051D9D9E83D2735018442FCFE 9A076793E0F9FCBA086828E4ECF41E939280CA297E77450BB3C9F87CF6550434147A7E7A0F41C140 6D1CB733AA85D9ECFC3E732A8A1A0A3D3
UDH=0500039F0201
Binary=1
PhoneNumber=01003746656
[ErrorDetail]
RetryCount=2
LastRetryTime=20131113113009
LastErrorInfo=ERROR: submit_sm or submit_multi failed - ESME_RSUBMITFAIL (0x45) -- SMPP - 192.168.0.61:2775


4-
[SMS]
SubmittedBy=127.0.0.1
Data=E8E8F41C949E83C2207A794E07B5CBF379F85C06351474747A0E4ACF416110BD3CA783DAE5F 93C7C2E831A0A3A3A3D07A5E7A030885E9ED341EDF27C1E3E97410D051D9D9E83D2735018442FCFE 9A076793E0F9FCBA086828E4ECF41E939280CA297E77450BB3C9F87CF6550434147A7E7A0F41C140 6D1CB733AA85D9ECFC3E732A8A1A0A3D3
UDH=0500030C0201
Binary=1
PhoneNumber=01003746656
[ErrorDetail]
RetryCount=2
LastRetryTime=20131113113159
LastErrorInfo=ERROR: submit_sm or submit_multi failed - ESME_RSUBMITFAIL (0x45) -- SMPP - 192.168.0.61:2775


but when I sent single SMS log as below
[SMS]
SubmittedBy=127.0.0.1
Data=fgdfgdf
PhoneNumber=01003746656



I noted that when I sent single message data sent with normal chars but in case of sent long SMS data will sent as encryption.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4738
Registered: 08-2008
Posted on Wednesday, November 13, 2013 - 02:52 pm:   

Hi,

The binary format for the REQ files in the Q directory is normal and expected.

It does not necessarily reflect the format that is used for the actual message transmission.

If you would like too see the actual format used for the SMPP transaction, you can enable the SMSDEBUG.LOG and view the SMPPDEBUG.LOG. Or for a decoded view, capture the traffic with WireShark.

For the options I described above ...

#1 - Uses text format for transmitting the message, with esm_class set to indicate that the message data starts with user data header.

#2 - Uses the over the air 7-bit packed binary format that you see in the Q files, also with esm_class set to indicate that the message data starts with user data header.

#3 - Uses text format for transmitting the message, with TLV parameters used to specify segmentation information instead of user data header.

#4 - Transmits the entire long message in text format in a single transaction using the message_payload format.

The underlying issue is that for a long message that needs to be split to be sent out, segmentation headers are included with each message segment. These headers are used by the receiver to put the message back together, so that it again looks like a single long message on the receiving side.

There are only two ways to encode these segmentation headers ... either via user data header (UDH) which is how it gets encoded over the air, or via TLV parameters that are defined in the SMPP specification.

At this point I see 2 options ...

a.) Find out from the SMPP provider why the messages are not being accepted and/or ask what format is to be used for sending long messages. (The above four encoding methods are the only methods we have seen, but perhaps there are others.)

b.) We add an option in NowSMS to not include segmentation headers ...this would mean that the receiving client would see separate messages instead of a single long message.

--
Des
NowSMS Support
Mohamed Anis
New member
Username: Mohamedanis

Post Number: 3
Registered: 02-2013
Posted on Thursday, November 14, 2013 - 06:52 am:   

Dears,

Long message sent successfully by option 1 and Enable SMPP Async Mode "checked"

Thanks,
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4741
Registered: 08-2008
Posted on Thursday, November 14, 2013 - 03:04 pm:   

Thank you for that feedback ... it is VERY interesting that async mode was required.

We've never seen that before, but I would theorize that the SMSC you are connecting with does not acknowledge acceptance of a multipart message until all segments are transmitted.

Thanks for sharing that feedback as it may help someone in the future who is interfacing with a similar service.

--
Des
NowSMS Support

Login Login / Register Logout Logout Search Last 30 Days Topics Topics