Delivery reports aren't sent back to SMPP client ?

Delivery reports aren't sent back to SMPP client ? SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through February 09, 2012 » Delivery reports aren't sent back to SMPP client ? « Previous || Next »
Author Message
Andrej Silin
New member
Username: Asilin

Post Number: 1
Registered: 11-2011
Posted on Monday, November 28, 2011 - 01:55 pm:   

Hi,

I'm using NowSMS/MMS Gateway evaluation version 2011.07.05 and I'm planing to integrate a SMS Gateway to my infrastructure and I won't be able to do that until I solve the problem.

The crucial point is the delivery reports that aren't sent back to my SMPP client. Here is my setup:

[My Kannel] <--> [NowSMS] <--> [SMPP Provider]

I'm am able to send messages and I get delivery reports from my 'SMPP Provider' (located in SMSIN log file). However these reports aren't sent from 'NowSMS' back to 'My Kannel': why ?

Please help.
Andrej Silin
New member
Username: Asilin

Post Number: 2
Registered: 11-2011
Posted on Monday, November 28, 2011 - 02:48 pm:   

Well I found some answers here :

http://support.nowsms.com/discus/messages/1/9540.html

However I have another big issue : only one of two delivery reports are forwarded back to kannel.

- Status ACK is forwarder perfectly from 'SMPP Provider' to 'My kannel'.

- Status DELIVERED, which comes 1 to 5 seconds later is never forwarded to 'My kannel' client. Why ?

Please help.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3621
Registered: 08-2008
Posted on Monday, November 28, 2011 - 03:30 pm:   

Hi Andrej,

The information in that thread is a little outdated ... the setting mentioned is no longer required and is enabled by default.

The most common issue that can cause delivery receipts to not be routed properly today is if the SMPP client account (defined in "SMS Users") does not have "Accept received messages for this user" checked. That setting must be checked for delivery receipts to be routed to that user account.

That said, I'm a little confused about your references to status "ACK" and "DELIVERED". I'm assuming that your provider is providing an interim/enroute delivery receipt when it processes the message, and then forwarding a separate delivery receipt later.

If you are getting the interim/enroute receipt, but not the separate delivered receipt, then it is likely that your provider is not properly tracking message IDs when they route delivery receipts from upstream providers.

Before reaching any conclusions, can you please provide me with details from the SMSOUT-yyyymmdd.LOG and SMSIN-yyyymmdd.LOG files, so I can see the message ID information recorded when the message is sent out, and the message ID information that is recorded when the receipts are received.

--
Des
NowSMS Support
Andrej Silin
New member
Username: Asilin

Post Number: 3
Registered: 11-2011
Posted on Tuesday, November 29, 2011 - 07:30 am:   

After some SMPP research it would seem that I'm not asking for intermediate delivery report (meaning the way it works is fine, I suppose): please, correct me if I'm wrong. Anyway, here are the logs.

(Sorry, but the time between my Windows running NowSMS and Linux server running kannel might be a little out of synch).


SMSIN (Server) :

2011-11-28 17:04:18,33611XXXXXX,SMPP - smpp.realserver.com:3333,Text="id:4ECFE497 sub:001 dlvrd:001 submit date:1111281604 done date:1111281604 stat:ACKED err:003 text: @";SMSCRouteName=RealSrv;Recip=33611YYYYYY;SMSCReceiptMsgId=4ECFE497;SMSCReceipt MsgIdOrig=1495570966

2011-11-28 17:04:21,33611XXXXXX,SMPP - smpp.realserver.com:3333,Text="id:4ECFE497 sub:001 dlvrd:001 submit date:1111281604 done date:1111281604 stat:DELIVRD err:004 text: @";SMSCRouteName=RealSrv;Recip=33611YYYYYY;SMSCReceiptMsgId=4ECFE497;SMSCReceipt MsgIdOrig=1495570966


SMSOUT (Server) :

2011-11-28 17:04:18,4ECFE498.req,,33611YYYYYY,OK -- LocalUser:testKannel,SubmitUser=SMPP - smpp.realserver.com:3333;Sender=33611XXXXXX;Text="id:4ECFE497 sub:001 dlvrd:001 submit date:1111281604 done date:1111281604 stat:ACKED err:003 text: @"

2011-11-28 17:04:21,4ECFE49A.req,,33611YYYYYY,OK -- LocalUser:testKannel,SubmitUser=SMPP - smpp.realserver.com:3333;Sender=33611XXXXXX;Text="id:4ECFE497 sub:001 dlvrd:001 submit date:1111281604 done date:1111281604 stat:DELIVRD err:004 text: @"


'My kannel' (Client) :

2011-11-28 17:04:17 Sent SMS [SMSC:NowSMS] [SVC:MyKannel] [ACT:] [BINF:] [FID:1322247319] [from:33611YYYYYY] [to:33611XXXXXX] [flags:-1:0:-1:-1:11] [msg:9:Bonjour !] [udh:0:]

2011-11-28 17:04:17 Receive DLR [SMSC:NowSMS] [SVC:MyKannel] [ACT:] [BINF:] [FID:1322247319] [from:33611YYYYYY] [to:33611XXXXXX] [flags:-1:-1:-1:-1:8] [msg:4:ACK/] [udh:0:]

2011-11-28 17:04:18 Receive DLR [SMSC:NowSMS] [SVC:MyKannel] [ACT:] [BINF:] [FID:1322247319] [from:33611YYYYYY] [to:33611XXXXXX] [flags:-1:-1:-1:-1:1] [msg:102:id:4ECFE497 sub:001 dlvrd:001 submit date:1111281604 done date:1111281604 stat:ACKED err:003 text: .] [udh:0:
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3628
Registered: 08-2008
Posted on Tuesday, November 29, 2011 - 01:20 pm:   

It is strange that you are getting two delivery receipts, but the policy of the upstream server may be to generate an interim receipt whether or not one is requested.

What is odd is that your client is only receiving one of these delivery reports. The NowSMS logs suggest that it is routing both of the delivery reports to your client.

So from a NowSMS perspective, it looks like everything is working ok. Two delivery reports are received, and both are routed back to the submitting client.

Perhaps the client considers the second delivery report to be a duplicate (since it refers to the same message ID) and is ignoring it.

I suppose it is also possible that there could be some other sort of communication problem.

If you enable the SMSDEBUG.LOG in NowSMS, this will also enable an SMPPDEBUG.LOG that logs all SMPP packets sent and received. This would show us for certain whether or not both receipts are being transmitted to the client, as I think they are.

Or, another alternative is to use Wireshark to intercept the traffic. This can be useful as it decodes the SMPP packets, so you can better see the activity yourself ... whereas SMPPDEBUG.LOG just shows the activity in a hex dump format.

--
Des
NowSMS Support

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