| Unable to match Deliver Receipts |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 13, 2018 ⬆ |
◄ ► |
| Author | Message | |||
| Stoner2008 New member Username: Stoner2008 Post Number: 18 Registered: 05-2013 |
Hello, We have discovered that some message receipts returned from NowSMS contains the message id from the SMPP provider rather than the message id that NowSMS provided us when the message was submitted via HTTP. After investigating those unmatched receipts, we realised that the parameters, SMSCReceiptMsgId and SMSCReceiptMsgIdOrig have the same values. here an example: OUT LOG: 2018-04-03 10:03:30,5AC377E5.req,192.xxx.xxx.xxx,21xxxxxxx(msisdn),OK -- SMPP - 192.xxx.xxx.xxx#ShortCode:portNumber,Sender=ShortCode;SMSCMsgId=34a27f40;Text="e xcellent! XXXXXX XXXXXX amitié XXXXX! Découvrez XXXXXXXX text!" In Log: 2018-04-03 10:03:37,21XXXXXX (msisdn),Text,34a27f40 2,ShortCode,SMSCReceiptMsgId=34a27f40 when we submit this text, nowSMS assign this value : 5AC377E5.req and we can't get SMSCMsgId in our Databse.when we get the DLR, nowsms should assign the value of: SMSCReceiptMsgId to 5AC377E5.req but we find the SMSCMsgId instead. here is the 2way-command http://localhost:xxxx/NowSMS/dlr.jsp?msisdn=@@SENDER@@&receipient=@@RECIP@@&text =@@FULLSMS@@&smsid=@@RECEIPTMESSAGEID@@ it's a critical problem.can you check, please! Thank you | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5904 Registered: 08-2008 |
Hi, Tell me more about your SMPP configuration. Do you have multiple SMSC connections defined to the same provider (i.e., multiple entries in the NowSMS SMSC list)? Basically, NowSMS assumes each SMSC connection has its own set of message IDs, so a DLR arriving on a different connection is not recognized. There are 2 ways to overcome this: 1.) Instead of multiple SMSC connections, use 1 connections with multiple sessions enabled under advanced settings. 2.) Use the TrackSMPPReceipts setting for all SMSC connections that share the same message ID space, described here: https://www.nowsms.com/smpp-receipt-message-id-tracking-over-multiple-connection s You might also find this past discussion helpful: https://support.nowsms.com/discus/messages/1/73565.html ... as it discusses a configuration with similar issues. -- Des NowSMS Support | |||
