| MessageID |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ |
◄ ► |
| Author | Message | |||
| Mathew Mathachan Frequent Contributor Username: Mathewm Post Number: 137 Registered: 04-2011 |
Hi As I understand, MessageID is a reference number returned by gateway when we submit message over HTTP. Is this reference unique? Does it get repeated? If repeated .. under what circumstance? We have an instance where it got repeated and we had some issue where status got updated on wrong records.... Appreciate your support Mathew | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 6147 Registered: 08-2008 |
Hi Mathew, The Message ID should be unique within a single gateway server, but will repeat/recycle after approximately 4 billion messages. If you need to have multiple gateways share a common message ID space, there is a MessageIDPrrefix setting that can add a server specific prefix to the ID. -- Des NowSMS Support | |||
| Mathew Mathachan Frequent Contributor Username: Mathewm Post Number: 138 Registered: 04-2011 |
Hello Des, We have only one instance of NowSMS running and we found that MessageID repeated due to some reason. We wanted to know what could be the reason? Mathew. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 6152 Registered: 08-2008 |
Hi Mathew, I am not aware of any reason. I have not seen this happen before. -- Des NowSMS Support | |||
| Mathew Mathachan Frequent Contributor Username: Mathewm Post Number: 144 Registered: 04-2011 |
Hello Des, It happened again and we were able to trace teh sequence. The customer's machine crashed and they restored an older image. So I believe the MessageID is persisted in the NowSMS directory in some file. Mathew | |||
| Mathew Mathachan Frequent Contributor Username: Mathewm Post Number: 145 Registered: 04-2011 |
Hi Would you be able to share where this is persisted so that we can try to replicate the condition? Mathew | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 6169 Registered: 08-2008 |
Hi Mathew, Yes, there is a file named UID.DAT which preserves the message ID across restarts. https://support.nowsms.com/discus/messages/1/60242.html I don’t have any details on the format of this file, but it is binary and appears to contain the last used message ID. — Des NowSMS Support | |||
| Mathew Mathachan Frequent Contributor Username: Mathewm Post Number: 146 Registered: 04-2011 |
Thank you Des. We don't need to know the format of the file.... Just where it is so that we can work around that. Mathew | |||
| Mathew Mathachan Frequent Contributor Username: Mathewm Post Number: 147 Registered: 04-2011 |
Hello Des, We were trying to recreate the duplicate message id by saving the UID file and copying it back. We were able to recreate too. However, we see that there is some concern in the delivery receipts where the mobile numbers of the same Gateway message IDs (SMSCReceiptMsgId) were not mapped correctly. Is it that we sent the duplicates with short intervals and the REC files were mapped wrongly? Mathew | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 6174 Registered: 08-2008 |
Hi Matthew, Duplicate Message IDs could cause some confusion for message ID tracking. However, the unique key in that tracking is the upstream assigned message ID, so this would cause confusion for downstream servers, not this server itself. More likely, if you are resetting/restoring an image, you are wiping out the databases which do this tracking. They are in the SMPPData directory. -- Des NowSMS Support | |||
