SMPP Delivery report issue ....

SMPP Delivery report issue .... SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through November 14, 2013 » SMPP Delivery report issue .... « Previous || Next »
Author Message
Nelson Lam
New member
Username: Nelsonlam

Post Number: 2
Registered: 02-2013
Posted on Monday, August 19, 2013 - 10:37 am:   

Dear Support Team,

We are using NowSMS as SMS Gateway and the conection is as follows:

Client-SMS-GW --> (SMPP) --> NowSMS --> (SMPP) --> MobileOp


- We connect to MobileOp via SMPP as client having
Tx and Rx binding

- The Clinet-SMS-GW is just another NowSMS server
(v2012.06.28)where we send text SMS using the local web IE interface with delivery report set to "YES"

- We set the Client-SMS-GW account/password under NowSMS's (v2012.06.28) "SMS users".

- When Client-SMS-GW sends SMS, it is delivered successfully via MobileOp, BUT Client-SMS-GW does not receive the Delivery Report.

-I can see the NowSMS receive the Delivery Report send from MobileOp and store under SMS-IN directory with filename 51DACBA4.rct

- On the NowSMS server, the debug log SMSDEBUG.log shows this error: "Receipt message id =xxxxxxxx not in database for SMPP - a.b.c.d:1234"

- we have set the check box for "accept received message for this user"

Could you pls help investigate why the Client-SMS-GW cannot receive the delivery report.

Thanks.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4600
Registered: 08-2008
Posted on Monday, August 19, 2013 - 08:43 pm:   

Hi,

Are the Tx and Rx both defined as a single entry in the NowSMS SMSC list?

Assuming that is the case, in the SMSOUT logs, are you seeing an outbound reference that references that message ID?

I'm basically trying to determine where the chain is broken. The SMSOUT logs will show the message ID that was assigned by the upstream server, which should match what comes back in the receipt. That said, there are some differences we can accept with known quirks at some providers.

Any chance that the message ID contains an @ or other non-alpha symbol?

--
Des
NowSMS Support
Nelson Lam
New member
Username: Nelsonlam

Post Number: 3
Registered: 02-2013
Posted on Thursday, August 22, 2013 - 08:07 am:   

Dear Support Team

The Tx/Rx binding is under the single entry in NowSMS SMSC list (e.g. SMSC connect >> MobileOpA >> Properites >> Advanced Setting >> # Transmitter Sessions and # Receiver Sessions = 1)

In the SMSIN log, the DR received from MobileOpA is having the SMSCReceiptMsgID=SMSCReceiptMsgIDOrig.

But the DR never get deliver to my Client-SMS-GW(NowSMS server)

There is no @ or non-alpha symbol in the message id.

Thanks.

Best Regards
Nelson
sam
Frequent Contributor
Username: Samdsouza

Post Number: 166
Registered: 08-2006
Posted on Thursday, August 22, 2013 - 08:40 am:   

Nelson

Check on the following 2 points:

1. Make sure the "Process Received SMS Messages" is checked in 2 way SMS tab

2. Make sure that in the SMS users tab in the user account/s the "Accept Received Messages for this user" is checked.

In short both the above settings should be checked.

Sam
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4604
Registered: 08-2008
Posted on Thursday, August 22, 2013 - 01:28 pm:   

Hi Nelson,

I should have been more specific. I need to see more exact detailed data.

For example, what does SMSOUT log report exactly? (Complete log entry, feel free to edit out sender/recipient.)

What is the exact line from the SMSDEBUG.LOG that includes that error about the Message ID not being found?

There is likely some small detail that is different that needs to be evaluated.

Or to solve this more quickly, repeat the incident and send both the SMSDEBUG.LOG and SMPPDEBUG.LOG to nowsms@nowsms.com. Be sure to put Attention: Des in the subject line and post a reply here so that I know to look for the e-mail.

--
Des
NowSMS Support
Nelson Lam
New member
Username: Nelsonlam

Post Number: 4
Registered: 02-2013
Posted on Friday, August 23, 2013 - 03:33 am:   

Hi Des

I have posted the Debug and log to you @ nocsms@nowsms.com.
Could you please help to check.

Thanks!
Jim
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4609
Registered: 08-2008
Posted on Friday, August 23, 2013 - 02:40 pm:   

Hi Jim & Nelson,

Thanks for the logs, that makes it all very clear, but unfortunately frustrating.

Here is what is happening on the B->C link to the provider.

submit_sm_resp from provider returns message id 8016D45100000000 (as reported by SMSCMsgId= entry in SMSOUT, but I like to see the raw SMPP to confirm).

When the receipt arrives later via deliver_sm, the message indicates that it is a delivery report for message id 9229797930699849728 (this value is in the text of the receipt and in the receipted_message_id parameter).

Unfortunately, this makes it impossible to determine what message the receipt is in reference to.

There are some SMSCs that return a numeric message id in hex format for submit_sm_resp, but then use a decimal version of the message id in delivery reports. NowSMS does recognize those instances ... but in this case, I do not see any potential relationship between the two numbers.

I suspect the provider is trying to do this hex to decimal conversion but is overflowing. This is pure speculation ... but in scenarios where this is done, it is generally with an 8 byte hex id and a 10 digit decimal id. The provider is returning a 16 byte hex id and a 20 digit decimal id, so that makes me think they are trying to do the same, but when they try to do the conversion, the result is rubbish.

Anyway, that's just speculation.

The problem is that the message id in the delivery report is different from the message id that was reported back when the message was submitted.

Hopefully that is a problem that they can fix. If not, NowSMS does have a configuration setting to disable the delivery report request flag for a particular connection that returns indecipherable delivery reports.

--
Des
NowSMS Support
Nelson Lam
New member
Username: Nelsonlam

Post Number: 5
Registered: 02-2013
Posted on Tuesday, August 27, 2013 - 04:29 am:   

Hi Des,

Thank you so much for your detailed explanation.
I will contact the provider for resolving the problem.

Appreciated for your help

Thanks!
Jim
Duiker Hill
New member
Username: Nyasaking

Post Number: 2
Registered: 11-2010
Posted on Thursday, November 07, 2013 - 08:00 pm:   

I have a similar problem with the exactly the same scenerio as with Nelson Lam with the difference that the message id's in both submit_sm_response and deliver_sm are identical and yet i can't get the delivery report in the Client-SMS-GW
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4729
Registered: 08-2008
Posted on Thursday, November 07, 2013 - 08:40 pm:   

Are the message ids in SMSOUT and SMSIN logs also the same?

Also, verify the 2 configuration settings referenced by Sam earlier in this thread:



quote:


Check on the following 2 points:

1. Make sure the "Process Received SMS Messages" is checked in 2 way SMS tab

2. Make sure that in the SMS users tab in the user account/s the "Accept Received Messages for this user" is checked.

In short both the above settings should be checked.




The first setting is not obvious that it would have any effect on this scenario, but it does.

--
Des
NowSMS Support

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