Problem of duplication NowSMS message id | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 14, 2010 ⬆ |
◄ ► |
Author | Message | |||
Alexandre Frequent Contributor Username: Alexd Post Number: 126 Registered: 01-2008 |
Have faced, again, duplication NowSMS message id. It has been at various times sent 2 messages consisting of two segments, but id at them it has turned out identical: 2010-09-15 09:05:59,SAR-+mobile-7b-2-1.req,+mobile,OK -- SMPP - SMSC1:2775,SubmitUser=login;Sender=TEST;SMSCMsgId=5517002134978826294;UDH=050003 7B0201; 2010-09-15 09:05:59,SAR-+mobile-7b-2-2.req,+mobile,OK -- SMPP - SMSC1:2775,SubmitUser=login;Sender=TEST;SMSCMsgId=5517002139273990198;UDH=050003 7B0202; 2010-09-15 17:07:36,SAR-+mobile-7b-2-1.req,+mobile,OK -- SMPP - SMSC2:2775,SubmitUser=login;Sender=TEST;SMSCMsgId=933767057;UDH=0500037B0201; 2010-09-15 17:07:36,SAR-+mobile-7b-2-2.req,+mobile,OK -- SMPP - SMSC2:2775,SubmitUser=login;Sender=TEST;SMSCMsgId=933767063;UDH=0500037B0202; Because of what such could occur? Any reboots of services didn't occur. | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2509 Registered: 08-2008 |
This can be a problem because the message IDs are generated based upon whatever message ID the original submitting client put into the segmentation header. We will investigate ways to override this. -- Des NowSMS Support | |||
Alexandre Frequent Contributor Username: Alexd Post Number: 127 Registered: 01-2008 |
Ok. Thanks i`ll be waiting for update | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2522 Registered: 08-2008 |
I've uploaded an update to address this. The update modifies the naming convention for segmented long messages received from SMPP clients to match the format that is currently used for long messages from HTTP clients. Instead of SAR-+mobile-7b-2-1, the format is SAR-+mobile-xxxxxxxx-2-1 The update is at http://www.nowsms.com/download/nowsms20100921.zip. -- Des NowSMS Support |