DELIVERY Report in UCS2

DELIVERY Report in UCS2 SearchSearch
Author Message
Alexandre
Frequent Contributor
Username: Alexd

Post Number: 102
Registered: 01-2008
Posted on Thursday, August 12, 2010 - 11:25 am:   

Have faced a small problem,SMSC sends reports on delivery in coding UCS2, and NowSMS why does not display result in SMSIN.log, there registers only here this data:

2010-08-12 14:08:35, +mobile, SMPP - SMSC:2775, DCS=8; Recip=TEST; SMSCReceiptMsgId=01532BEB4D; SMSCReceiptMsgIdOrig=5504463099255066670

I.e. completely there is no this part:
“id:IIIIIIIIII sub:SSS dlvrd:DDD submit date:YYMMDDhhmm done
date:YYMMDDhhmm stat:DDDDDDD err:E Text:.........”

Because of what it can be? The report is present in PDU, I did dump by Wireshark.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2417
Registered: 08-2008
Posted on Thursday, August 12, 2010 - 07:35 pm:   

Hi Alexandre,

Without seeing the actual message data, I do not know why this would happen.

I do however have one idea.

Try editing SMSGW.INI, and under the [SMSGW] header, add FixSMPPReceipts=No

This setting will disable some logic that reformats delivery receipts that do not start with "id:". I notice that this logic does not change the DCS if the message encoding was originally in Unicode. So you would end up with a message that could not properly be interpreted.

I'm requesting a fix for the logic of this setting to reset the DCS in this scenario. However, this may or may not be the problem you are experiencing. Try FixSMPPReceipts=No and see if the behaviour changes.

--
Des
NowSMS Support
Alexandre
Frequent Contributor
Username: Alexd

Post Number: 108
Registered: 01-2008
Posted on Friday, August 13, 2010 - 09:39 am:   

I can`t now test test param (FixSMPPReceipts),but here is screen shot from Wireshark with delivery_sm from SMSC:Screen of wireshrak
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2426
Registered: 08-2008
Posted on Friday, August 13, 2010 - 07:04 pm:   

Confirmed. The problem is related to the FixSMPPReceipts setting (default is "Yes").

If FixSMPPReceipts=No was configured, you would see the following text:

000/000/000 +7xxxxxxxxx60 2010-08-13-17:12:54

FixSMPPReceipts tries to change the text to:

id:xxxxxxxxxx etc

However, the "fix" does not expect DCS=8 which causes the replacement text to be considered invalid.

We are preparing a fix for this.

--
Des
NowSMS Support
Alexandre
Frequent Contributor
Username: Alexd

Post Number: 110
Registered: 01-2008
Posted on Monday, August 16, 2010 - 09:26 am:   

Ok.Thanks. We with impatience we will wait fix :-)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2430
Registered: 08-2008
Posted on Monday, August 16, 2010 - 09:00 pm:   

Apologies for the delay, we have had some technical problems with our discussion board software that have taken up too much time to resolve.

I've posted an update that addresses this to http://www.nowsms.com/download/nowsms20100813.zip.

--
Des
NowSMS Support
Alexandre
Frequent Contributor
Username: Alexd

Post Number: 111
Registered: 01-2008
Posted on Wednesday, August 18, 2010 - 10:13 am:   

Big thanks we will test it :-)
Alexandre
Frequent Contributor
Username: Alexd

Post Number: 117
Registered: 01-2008
Posted on Thursday, August 19, 2010 - 09:22 am:   

Now we see in SMSIN log this unreadble delivery status:

2010-08-19 12:18:59,+mobile,SMPP - SMSC:13900,Text="
@@(QGГџFp@ВЎГ©@$4@PВЈВЎ@@О ВЎГ№ ACВЎО”CГЁГё
@@Wm!@@ВЈ#Г№ВЈГІ@hГ№ВїВЈ4p@@@";Recip=TEST;SMSCReceiptMsgId=153D7 A8C7;SMSCReceiptMsgIdOrig=5507032451605532718

Something wrong ?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2450
Registered: 08-2008
Posted on Friday, August 20, 2010 - 06:52 pm:   

Do you have FixSMPPReceipts=No in the SMSGW.INI?

If not, we pass whatever garbage came in from the provider. That setting disables the logic that causes NowSMS to make sure that the text of a receipt is in the "id:xxxxxx" format.

Not all providers pass the "id:xxxxx" text string back, and in particular, some get very confused when sending back reports for binary or Unicode messages.

It doesn't sound like this particular issue is directly related to the other one, I would need to see a raw receipt to understand what the formatting issue is this time.

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2451
Registered: 08-2008
Posted on Friday, August 20, 2010 - 06:55 pm:   

There is a typo in the above reply, it should read:

Do you have FixSMPPReceipts=No in the SMSGW.INI?

If yes, we pass whatever garbage came in from the provider. That setting disables the logic that causes NowSMS to make sure that the text of a receipt is in the "id:xxxxxx" format.

Not all providers pass the "id:xxxxx" text string back, and in particular, some get very confused when sending back reports for binary or Unicode messages.

It doesn't sound like this particular issue is directly related to the other one, I would need to see a raw receipt to understand what the formatting issue is this time.


(In other words, if you are using FixSMPPReceipts=No as recommended for a temporary work-around earlier in this thread, it may be causing the problem. Do not use FixSMPPReceipts=No if you expect all receipts to have a text format of "id:xxxxx")
Alexandre
Frequent Contributor
Username: Alexd

Post Number: 119
Registered: 01-2008
Posted on Monday, August 23, 2010 - 09:46 am:   

Is problematic to use FixSMPPReceipts=No as reports on delivery can suffer from others SMSC because all logic is constructed on a format "id:xxxxxx".
Whether it is possible (FixSMPPReceipts=No) to adjust this parameter for a specific connection [SMPP - server:port] ?
In attach binary dump of delivery (unicode) packet.

By the way i check delivery sm packets from another SMSC and they all send delivery packet in forat "000/000../ but in Default encoding and all ok.
Alexandre
Frequent Contributor
Username: Alexd

Post Number: 120
Registered: 01-2008
Posted on Monday, August 23, 2010 - 09:47 am:   

Attach
application/octet-stream
delivery_binary_dump (0.2 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2456
Registered: 08-2008
Posted on Monday, August 23, 2010 - 10:51 pm:   

Ok ... so this is the same SMSC as before? That was not clear to me before. (It probably should have been clear to me as the SMSCReceiptMsgIdOrig is in the same format.)

It's difficult for us to simulate the same behaviour as this SMSC. However we did a code review, and it appears that the "fix" was not quite right. It needed to set one other attribute for the message to be encoded properly.

Try http://www.nowsms.com/download/nowsms20100823.zip.

--
Des
NowSMS Support
Alexandre
Frequent Contributor
Username: Alexd

Post Number: 121
Registered: 01-2008
Posted on Tuesday, August 24, 2010 - 10:18 am:   

Yeah thats is same SMSC as before.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2458
Registered: 08-2008
Posted on Tuesday, August 24, 2010 - 09:33 pm:   

Ok. Hopefully that update will finally address the issue.
Alexandre
Frequent Contributor
Username: Alexd

Post Number: 122
Registered: 01-2008
Posted on Wednesday, August 25, 2010 - 08:27 am:   

Yeah Thanks! It`s work!