| HEX AND DECIMAL RECEIPT ISSUE |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 16, 2015 ⬆ |
◄ ► |
| Author | Message | |||
| Srikanth M New member Username: Srikanthm Post Number: 1 Registered: 11-2014 |
Hello Support, I have a situation wherein I am connected to a mobile operator who assigns Hex receipt id's on submission and returns decimal id's in delivery receipt because of which NowSMS is unable to match and reroute receipts to submitted SMPP user. I have gone through few threads similar incidents however I am unable to find a proper solution to this. Please guide us appropriately to match the receipts and forward receipt to submitting SMPP client. Regards | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5117 Registered: 08-2008 |
Hi, Can you provide some examples of the IDs that should match? NowSMS normally handles this automatically by converting decimal to hex to look for a match. However, we have seen a few providers where there is no obvious relationship between these IDs. Do you see a pattern? -- Des NowSMS Support | |||
| Srikanth M New member Username: Srikanthm Post Number: 2 Registered: 11-2014 |
Hello Des, Thank you for responding. Below are few id's we received during submission to smsc SMSCMsgId=8272DC1800000023 SMSCMsgId=8272DC5700000070 SMSCMsgId=8272DC5900000022 and below are corresponding id's received in delivery report for same mobile numbers however the reports are not forwarded back to the submitting smpp client id:9399817367912972323 sub:001 dlvrd:001 submit date:1411241120 done date:1411241120 stat:DELIVRD err:255 text:Round";SMSCRouteName=XX;Recip=XXXXX;SMSCReceiptMsgId=9399817367912972323;SM SCReceiptMsgIdOrig=9399817367912972323 id:9399817638495912048 sub:001 dlvrd:001 submit date:1411241121 done date:1411241121 stat:DELIVRD err:255 text:Round";SMSCRouteName=XX;Recip=XXXXX;SMSCReceiptMsgId=9399817638495912048;SM SCReceiptMsgIdOrig=9399817638495912048 id:9399817647085846562 sub:001 dlvrd:001 submit date:1411241121 done date:1411241121 stat:DELIVRD err:255 text:Dear";SMSCRouteName=XX;Recip=XXXXX;SMSCReceiptMsgId=9399817647085846562;SMS CReceiptMsgIdOrig=9399817647085846562 Looking forward for your reply Regards. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5118 Registered: 08-2008 |
Hi, That is good news, as those values can be converted, they are just very large (require unsigned 64-bit integer values). We have seen a few similar cases in the past with extremely large values, but no valid calculation available to do the conversion. So your case is good news because the values can be converted. We've posted an updated version of NowSMS that should be able to handle this conversion. The EXE in the ZIP is a full install to update an existing installation. http://www.nowsms.com/download/nowsms20141122.zip -- Des NowSMS Support | |||
| Srikanth M New member Username: Srikanthm Post Number: 3 Registered: 11-2014 |
Hi Des, Thank you for the update. I have updated the software however its still the same situation I don't see any reports getting forwarded to submitted smpp client. Please advise Regards. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5119 Registered: 08-2008 |
Hi, I ran some tests, and it looks like that install was missing an update to one of the DLLs. Try this one instead: http://www.nowsms.com/download/nowsms20141122a.zip -- Des NowSMS Support | |||
| Srikanth M New member Username: Srikanthm Post Number: 4 Registered: 11-2014 |
Hello Des, The issue is still not resolved. Even though now I can see the assigned id's to client are matching up the smsc assigned id's as per the smsin log file the reports are still not getting forwarded to the submitting smpp client. Please look into this asap Thanks Regards. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5121 Registered: 08-2008 |
Hi Srikanth, Go into "SMS Users", and for any accounts being used by these SMPP clients, make sure that "Accept received messages" is enabled. Without that setting, no messages (including delivery reports) will ever get queued for the client. Also make sure the client is bound as a transceiver (or has at least one receiver bind), as delivery reports will not be routed to a client over a sender bind. -- Des NowSMS Support | |||
