SMPP delivery report: "TrackSMPPReceipts" in SMSGW.INI

SMPP delivery report: "TrackSMPPReceipts" in SMSGW.INI SearchSearch

NowSMS Support Forums » NowSMS Support - SMS Issues » Archive through October 19, 2005 » SMPP delivery report: "TrackSMPPReceipts" in SMSGW.INI « Previous || Next »
Author Message
Roman Korobeinikov
New member
Username: Korobeinikov

Post Number: 1
Registered: 07-2005
Posted on Friday, July 29, 2005 - 09:04 am:   

Hi there!

We've got a lot of clients sending their SMS using one common "SMS user" account. Every client has it's own "source ID" (phone number). Is it possible to route inbound SMS delivery receipts so every client could retrieve his own receipts using SMPP "deliver_sm"?

I have installed the latest available trial version of the NowSMS, set up SMSC's and user accounts. Also, I edited SMSGW.INI, and added "TrackSMPPReceipts=Yes" under the [SMSGW] header. Unfortunately, only those users who are listed in "Recipient address(es) to route to this user" field, could retrieve their receipts. The receipts for other users are collecting in "SMS-IN" folder as before.

Is this parameter ("TrackSMPPReceipts") still working?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4716
Registered: 10-2002
Posted on Friday, July 29, 2005 - 05:18 pm:   

Hi Roman,

You don't mention what version you are running.

The current trial download links to v5.51. But you need to have v5.51b (or later) for this feature, which currently has a separate download link.

(See the message about v5.51b under the "What's New" section of the web site.)

If you have a version that identifies itself as v5.51b, and this is not working, there may be an issue with how the upstream SMSC is formatting its delivery reports. (It is likely that they may also be routing to an upstream SMSC, and they may not be translating message id's properly in the receipts.)

If it isn't working, and you have v5.51b (or later), then I'd like to see an SMSDEBUG.LOG and SMPPDEBUG.LOG showing a message going out with a delivery receipt requested, and the delivery receipt coming back in. Then we can determine if there is something that we can fix, or if the problem is with the upstream SMSC.

I am aware of one bug in the current "TrackSMPPReceipts=Yes" implementation. If the upstream SMSC rejects a message submission from NowSMS, NowSMS generates its own non-delivery notification. That non-delivery notification is not routed properly back to the submitter, but instead routes based upon the "Recipient address(es) to route to this user" field.

We have fixed that particular problem, but have not released it yet.

-bn
sam
Unregistered guest
Posted on Saturday, July 30, 2005 - 12:13 pm:   

Hi Bryce

Do we need to add "*" in the "Recipient address(es) to route to this user" for each and every user to get the DR back respectively?

Or does it work without defining the "Recipient address(es) to route to this user".

Thanks
Sam
Roman Korobeinikov
New member
Username: Korobeinikov

Post Number: 2
Registered: 07-2005
Posted on Monday, August 01, 2005 - 04:10 pm:   

Hi Bryce!

Thank you for your reply.

My [readme.txt] file starts from

Post v5.0 Updates to the Now SMS/MMS Gateway:
=============================================

================================
v5.51b (20050428):
================================
...


So, I've decided that my version is v5.51b or newer.

Instead of using true SMSC, I've installed SMSC-emulator (running on localhost) that receives messages from NowSMS gateway (running on localhost too) and deliver receipts. I've got that same results while using true SMSC.

All the log-files are attached as well as the [smsgw.INI] file. I would be happy if you could help me to work out my problem.

application/octet-streamcutting from SMPPDEBUG.LOG
SMPPDEBUG.LOG (8.8 k)

application/octet-streamcutting from SMSDEBUG.LOG
SMSDEBUG.LOG (1.6 k)

application/octet-streamcutting from smsgw.INI
smsgw.INI (0.6 k)


This example consists of two test messages:

1. The sender "tester1" (the recipient of the delivery report) is listed in "Recipient address(es) to route to this user" field. As you can see, the receipt is succesfully delivered to original sender.

1. The sender "tester2" (the recipient of the delivery report) isn't listed in "Recipient address(es) to route to this user" field. The receipt isn't delivered to original sender.

Will be waiting for your response. Thank you in advance.

Roman Korobeinikov
Roman Korobeinikov
New member
Username: Korobeinikov

Post Number: 3
Registered: 07-2005
Posted on Monday, August 01, 2005 - 04:29 pm:   

Hi again Bryce.

Another one question.

If there any way to set up the "message deliver priority" based on users accounts.

Example: I've got 1000 SMS in outbound queue. Some high-priority user is submitting another one SMS for delivery. I'd like this message to be placed to the head of query, so it would be delivered first.

Is there any possibility to set up the NowSMS so it could work in such a way?

Thank you!

Roman Korobeinikov
Roman Korobeinikov
New member
Username: Korobeinikov

Post Number: 4
Registered: 07-2005
Posted on Thursday, August 11, 2005 - 10:52 am:   

Bryce, where are you?

Roman Korobeinikov
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4751
Registered: 10-2002
Posted on Thursday, August 11, 2005 - 10:20 pm:   

Hi Roman,

Sorry for the delay.

The quick answer is that it appears your SMPP service provider is not returning the "receipted_message_id" parameter in their return receipts.

We could explore looking at the text of the receipt to try to parse a receipted_message_id out of the text of a message that says it is a delivery receipt.

Many SMSCs follow the format in Appendix B of the SMPP specification. However, it is important to note that the example in that appendix is defined as a "typical example", and not a standard.

We could try that. I don't like the idea of mucking with the text. (Although in the current implementation, if we do change the receipted_message_id value, we do also modify the text of the receipt to include an updated "id:" field.)

It's probably going to be at least a week (closer to two) until we can put something together to try this approach. Or maybe since you are just testing here against a simulator, you could instead use a real system which should hopefully return the "receipted_message_id" parameter in a delivery receipt.

Regarding message delivery priority ...

Well, not an exact solution. But there is another feature that is currently implemented (like TrackSMPPReceipts), but has not been documented for this release, because we were planning to hold if off for the next major release.

But I might as well mention it, because queueing can be a big problem in the current versions.

In the SMSGW.INI file, under [SMSGW], it is possible to include the following settings:

SeparateUserQueues=Yes

This setting enables the server to maintain separate outbound message queues for all users.

UserQueueThreshold=###

This setting specifies the maximum number of messages that NowSMS will try to process from any one user queue before it moves to servicing another queue. The default value is 10 (which is too low for many environments, as the queue switching does add overhead).

This doesn't give you priorities for user accounts, but what it does is stop big bulk submissions from one or more users bringing everyone else's messages to a standstill.

-bn
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4818
Registered: 10-2002
Posted on Wednesday, August 31, 2005 - 11:12 pm:   

Follow-up:

An update has been posted which will parse the receipt message id out of the message text, if the receipted_message_id is not present.

This parsing only occurs if the message type indicates that it is a receipt (which is the case in your logs above), and the receipted_message_id is not present.

Download link for update (v5.51e): http://www.nowsms.com/download/latestpatch.zip

Related threads:

http://support.nowsms.com/discus/messages/1/10862.html
http://support.nowsms.com/discus/messages/1/10806.html
http://support.nowsms.com/discus/messages/1/10825.html
Anonymous
 
Posted on Friday, September 16, 2005 - 08:56 am:   

Dear All,
I'm trying to use this delivery receipt feature but I stuck. If I specify TrackSMPPReceipts=Yes then NowSMS enter an endless loop (trying to match the receipt?) and the message stay there in the \Q directory. It happened with both the SMSC simulator (OpenLogica) and the real one.I'm using the latest (5.51h) version of NowSMS. Can anyone help me get out of this?
Thanks and BR
Levi
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4929
Registered: 10-2002
Posted on Friday, September 16, 2005 - 10:08 pm:   

Hi Levi,

There's no way that NowSMS could get into a loop trying to match a delivery receipt. If we don't have a record of the message id, it just gets routed without a message id.

Are you sure that your problem has anything to do with delivery receipts? i.e., if you don't have TrackSMPPReceipts=Yes in the SMSGW.INI file, does the same problem occur?

I just can't see any way that this setting could cause this type of problem.

So I suspect there is some other problem.

I think I would need to see a debug log to understand the message flow. It sounds like there might be some sort of circular routing defined. Or if the message is staying in the Q directory, then perhaps the SMSC connection is failing?

In any event, a debug log would help me understand, because I just don't have enough details to troubleshoot based upon your brief posting above.

To enable the debug log, use the checkboxes on the "Serial #" page of the configuration dialog. Then, I'm interested in seeing the SMSDEBUG.LOG and SMPPDEBUG.LOG files so that I can see what messages are getting routed and how they are being routed.

-bn
Mohamed Salim ALI
New member
Username: Salim

Post Number: 33
Registered: 04-2005
Posted on Monday, September 26, 2005 - 04:18 pm:   

Hi Roman & Bryce,

I am facing the same problem, but may be in opposit way. I want to send back a receipt to my mobile operator MMSC, that i have successfully receive MMS, because I am pulling MMS.
Can any one help me on that, what I can do, to enable it ?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5068
Registered: 10-2002
Posted on Wednesday, October 05, 2005 - 08:02 pm:   

What type of receipt do you want to send?

NowSMS atutomatically generates the required acknowledgment.

But what protocol are you using?

We recently had a situation where someone was connecting to an "AnnyWay" MMSC, and this MMSC does not follow the standard MM7 protocol. Instead, like Ericsson, they have defined their own implementation of MM7, and claim to support MM7 but use a non-standard variation.

I believe that Vodafone MTC Kuwait is using this particular MMSC (but there may be other mobile operators that have been duped into believing that they have bought a product that supports MM7 when it does not).

We had to add a special configuration option to NowSMS in order to define an MMSC connection that supports AnnyWay's non-standard implementation of MM7.

If this is what you are referring to, and you're not the customer that we've been dealing with separately regarding this issue, then please let me know. I don't think we've posted the update that includes this configuration option to the web site yet.

-bn
Mohamed Salim ALI
New member
Username: Salim

Post Number: 35
Registered: 04-2005
Posted on Thursday, October 06, 2005 - 01:10 pm:   

He Bryce,

Really it was me, The problem was very hight level and I got round any where to find solution on it, this why I was coming in this thread. We got many solutions from your colleague helpful Brian.
Now we are in advance way

Thanks alot Bryce.
Salim.