SMPPReceiceMEssageCallBack | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 13, 2018 ⬆ |
◄ ► |
Author | Message | |||
Mathew Mathachan Frequent Contributor Username: Mathewm Post Number: 106 Registered: 04-2011 |
Hi We installed the new version (v2016.08.31) today and see that we get this SMPPREceiveMessageCAllBack... whcih is being forwarded to the SMSIN Callback and causing lots of issues. Do help us.. Its an urgent issue. Mathew | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5750 Registered: 08-2008 |
Hi, I don't have information to understand what is happening that is unexpected or why it is a problem. But perhaps you want to disable the SMSIN callback? The following setting can be applied in SMSGW.INI under the [SMSGW] header: SMSAccountingLimitCallbacks=PreAuth,SMSSend,SMSIn,SMSOut - If this setting is present, any accounting callback types not listed are disabled. For example, SMSAccountingLimitCallbacks=PreAuth,SMSSend enables only PreAuth and SMSSend callbacks (SMSIn and SMSOut are disabled). -- Des NowSMS Support | |||
Mathew Mathachan Frequent Contributor Username: Mathewm Post Number: 107 Registered: 04-2011 |
Hi Some more info PId=0, msgFlag=4, msg=73E59D50 201 Mathew | |||
Mathew Mathachan Frequent Contributor Username: Mathewm Post Number: 108 Registered: 04-2011 |
Hi We need SMSIN callback... as we need to process PULL messages. This is a new installation. Mathew | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5751 Registered: 08-2008 |
I still don't have information to understand: 1. what is happening that is unexpected? 2. what did you expect to happen? 3. why it is a problem? | |||
Mathew Mathachan Frequent Contributor Username: Mathewm Post Number: 109 Registered: 04-2011 |
Hi, When we send messages out.... randomly the SMSC responds with these messages that raise a SMSIN callback and junk message body. We process them and send outgoing "Invalid Message". We do process valid PULL SMSIN callbacks to service custmers.. but because of this .. customers getting Invalid message often unsolicted. Is ther a way to identify these so that we can drop them and process only others? BTW. what does msgFlags=4 indicate. Mathew | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5752 Registered: 08-2008 |
Hi Mathew, OK, that helps me understand a little better. msgFlags=4 indicates that it is a delivery report. But it also suggests that the delivery report is MISSING aa message ID. Which I'm guessing is somehow related to 73E59D50 201, but it is not encoded as a message ID. Normally, NowSMS would reformat this message text to fix it, but it does not see a message ID. Can you get a Wireshark trace so that we can better understand? As a quick fix, disable the ability to ask for delivery reports on that connection. Under the [SMPP - server:port] header for that connection in SMSGW.INI add DisableDeliveryReceipt=Yes -- Des NowSMS Support | |||
Mathew Mathachan Frequent Contributor Username: Mathewm Post Number: 110 Registered: 04-2011 |
Thanks Des for the response. Let me see if we can get a WireShark trace... The installation is in another location and getting access to this would be a little tough. Would a SMPP trace be good enough? Mathew | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5753 Registered: 08-2008 |
Hi Mathew, Yes, that's fine. Wireshark traced are easier because we don't have to manually decode them, but if that is too difficult, we can certainly get the needed info from SMPPDEBUG.LOG. Based on the info so far, I'm reasonably confident that we're seeing something non-standard in the delivery report, but if we can find a way to identify and interpret it, we will. -- Des NowSMS Support | |||
sapycola New member Username: Sapy Post Number: 1 Registered: 01-2017 |
Hi, It's possibile sent SMSPP message via Android APK? how to configurate smspp |