Ignoring receipt acknowledgement | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through July 28, 2010 ⬆ |
◄ ► |
Author | Message | |||
Chris New member Username: Chrisc Post Number: 46 Registered: 12-2008 |
Hi guys We are wondering if it is possible to ignore a message receipt if the message itself originated from a different machine. We currently have two NowSMS installations, each on its own server. With one of our binds, we have the same system_id to the same IP address. Our own source IP to the outside world is the same for both machines. So for an SMSC, the same message is routed back but is picked up by either machine. We're not entirely sure if it is the case, but it would appear that NowSMS ignores a message receipt if it didn't originate from the same machine. So we're wondering if it is possible to have this bypassed, so that any message receipt that is picked up by NowSMS is ignored regardless of where the message came from. Is this something that can be done? Thanks Regards Chris | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2278 Registered: 08-2008 |
Hi Chris, NowSMS doesn't ignore the receipt, but it doesn't know how to route it. It's going to go into the SMS-IN directory and NowSMS will attempt a couple of times to resolve the receipt message id later. However, ultimately, it is going to fail, because one server does not know about messages submitted by the other server, so it doesn't know how to translate the message ID to match it up with the original message. How to handle this? It is possible to put the message tracking database on a shared volume. However, this affects the message tracking databases for all connections. (Each connection to a different SMSC gets its own tracking database, but the all have to be on a shared volume. You can't just selectively move one.) The MessageIDTrackingDir= parameter sets this database location. See http://support.nowsms.com/discus/messages/1/51083.html Note that if you move this location for an existing server setup, it can be tricky because you have to move files from the existing SMPPDATA directory to the new directory in order to not lose any receipts. (And there is the problem that this one SMSC connection has two database files for each day, which would be difficult to combine. My advice, delete all tracking databases older than 3 days old. To merge the two connections, assign date filenames to make one of the server's files appear to be older. This way they can still be processed. This is a little difficult to explain, but if you look at the files in the SMPPDATA directory, hopefully you'll understand.) The other alternative would be to write a program that scans *.SMS files in the SMS-IN directory. Under the [SMS-IN] header, look for ModemName= values matching the SMSC in question. Copy/Move this file into the SMS-IN directory of the other server and give it a .RCT extension so that server can process it. Or, another alternative would be to use different system_id accounts on the different servers so that there is no issue. -- Des NowSMS Support |