Delivery report

Delivery report SearchSearch
Author Message
medium kuriboh
New member
Username: Mediumkuriboh

Post Number: 22
Registered: 04-2008
Posted on Monday, May 10, 2010 - 12:14 am:   

I need to be able to process the delivery report like i do usually with incoming sms. Usually i rely on 2 way sms, and i send it to an asp script where i do the processing. now for the delivery, does it come the same way as smsin (because i see in smsin log file, the sms delivry receipt shown). Thanks !
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2083
Registered: 08-2008
Posted on Monday, May 10, 2010 - 04:50 pm:   

> Yes, it comes in the same way as a received message, to be processed =20 by a 2-way command. The only thing to watch out for is if the =20 original submitting user account has SMPP or SMTP enabled, the receipt =20=

gets queued for pickup by the user instead of going to a 2-way command.
medium kuriboh
New member
Username: Mediumkuriboh

Post Number: 25
Registered: 04-2008
Posted on Saturday, May 15, 2010 - 04:24 am:   

i succeeded to get the receipt message however i am facing still some problem. I read some posts here and i noticed that i need to map between the smpp assigned id for the message out from my nowsms and the delivery receiptmessageid. So basically i need to use accounting callback. I am not able to make account callback work.
i checked this link:
http://www.nowsms.com/support/bulletins/tb-nowsms-001.htm
Do i need to run nowsms as smpp server to make it work, actually i am using it as client, and without users, i am trying to test sending message by url using parameter:ReceiptRequested=1.
I even tried to run wireshark to capture the network and i noticed the nowsms is not calling the url i put in SMSGW section(SMSAccountingURL...)
Any help please
medium kuriboh
New member
Username: Mediumkuriboh

Post Number: 26
Registered: 04-2008
Posted on Monday, May 17, 2010 - 12:01 am:   

I rechecked this matter, and i noticed the following behavior:
i have 4 sessions with my provider: 2 Tx, and 2 Rx. i use 1Tx+1Rx Per Ip, one is backup for another. So connection names: Ip1R, Ip1T, Ip2R, Ip2T.
The problem happens when sms goes through Ip1T, then delivery report comes under Ip2R, then instead of having the mapped local id in the delivery sms, i get the actual SMSC identifier (the id assigned by smsc) Basically this will not help since on submit all i get is the local nowsms id.
When Ip1T and Ip1R->Ok
Ip2T and Ip2R->Ok

What could be the solution ? Thanks
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2130
Registered: 08-2008
Posted on Monday, May 17, 2010 - 06:09 pm:   

When defining the SMSC connections to NowSMS, it is necessary to use the same host name or IP address (and port).

NowSMS maintains a database of message ids for each SMSC connection. SMSC connections with the same host name/port have a shared database.

--
Des
NowSMS Support
medium kuriboh
New member
Username: Mediumkuriboh

Post Number: 27
Registered: 04-2008
Posted on Monday, May 17, 2010 - 11:26 pm:   

basically i have 2 IPs, the submit_sm could go throught one Ip and the deliv_sm could come from other IP. Is there a way to force the deliv_sm to come from the same IP ?
I checked tcpdump and actually the provider is giving me the right smscreceipt id, however like you said it tracks the mapping between client Id and server Id per IP. Any solution or workaround, or i should work on one IP ?is this a fault from the provider side to send on another smsc connection with another IP ? Thanks
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2133
Registered: 08-2008
Posted on Tuesday, May 18, 2010 - 06:24 pm:   

So the provider has two IP addresses for the same SMSC?

There is a way to configure NowSMS to use the same receipt message ID database for multiple connections. This should only be done when you are connecting to an SMSC via multiple IP addresses where you are certain that the SMSC shares a message ID space across the IP addresses (like what you describe).

To enable this, you need to edit the SMSGW.INI file.

Under the [SMPP - server:port] section header for each connection that shares the same receipt message ID namespace, add TrackSMPPReceipts=somename

"somename" can be any text that makes sense to you. NowSMS will group together receipt message ID tracking for all connections that share the same TrackSMPPReceipts value.

--
Des
NowSMS Support
medium kuriboh
New member
Username: Mediumkuriboh

Post Number: 28
Registered: 04-2008
Posted on Wednesday, May 19, 2010 - 12:34 pm:   

Good, this worked fine, now i send through first connection and it map fine the delivery through the second connection (in fact it appears now like all my delivery comes through the second connection :D

I also have a problem with a third operator (first 2 operators delivery reports are fine now)
This third operator send "strange deliv" messages, the format is something like this :
" id:01//c1f3b4d26e107077000000004629659a01e50a01/129xxxxxxxxxx sub:002 dlvrd:001 submit date:19-MAY-1012:52 done date:19-MAY-1012:52 stat:DELIVRD err:000 Text:this is a test " and the recipient address is different than the one i use to send sms. so if i send sms to my testing cellphone using the webinterface using the sender:x i am getting the delivery report using recipient address:y. i guess y is something is their side. The problem is in the end, nowsms is not able to map between the smscids and i am getting the smscid in my received message (wish makes the delivery receipt id useless). So any ideas, how i could solve this ?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2141
Registered: 08-2008
Posted on Wednesday, May 19, 2010 - 06:19 pm:   

Is this third operator also using SMPP? (I ask because the "/" characters are frequently used in UCP/EMI environments.)

When you send the message out via this other operator, in the SMSOUT-yyyymmdd.LOG file, what is reported as the "SMSMsgId=" value?

I am wondering how different this value is from the "id:01//c1f3b4d26e107077000000004629659a01e50a01/129xxxxxxxxxx" value that we are getting back in the receipt.

I'm also noticing that this message ID is extremely long ... 58 characters. The length might be a problem. I don't think it would. Although I think older versions of NowSMS could only track receipt message IDs if they were 50 characters or less. What version of NowSMS are you running?

--
Des
NowSMS Support
medium kuriboh
New member
Username: Mediumkuriboh

Post Number: 29
Registered: 04-2008
Posted on Wednesday, May 19, 2010 - 11:02 pm:   

They are using smpp, however, like you, i noticed that their ids are strange, they include the cellnumber and too much information.

Actually they are the same ids in in and out logs, i copied from out and searched in in for the pasted text, and it is the same.

Also, I tried winshark to capture the smpp traffic, it shows that the smscid in submit_sm_resp-ok and deliv. however like i mentioned before, the sender and recipient address are different.

i have nowsms 2006-2007.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2145
Registered: 08-2008
Posted on Thursday, May 20, 2010 - 05:03 pm:   

The original receipt tracking logic had a limitation of 50 characters for message IDs.

This limit was expanded to 150 characters when the receipt tracking database was upgraded to use a new database format 2008 releases.


--
Des
NowSMS Support