| Message priority for internal queue |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| PM |
Gentlemen! We are considering the question of using your software package "NOWSMS" as part of our notification service (we send SMS messages to the SMS center of our provider thorough UCP protocol). Unfortunately, our provider limited the number of messages per minute that we can send through it's SMS center. In cases where we send out large numbers of messages the limitation introduced by our provider results in that NOWSMS caches messages and sets up an internal message queue from which messages are send according to the "first in - first out" rule.This happens also in cases where we use two-way mode to exchange SMS messages with the SMS center - outbound reply messages (which as supposed to be sent back without delay) join the same internal message queue. The problem is that it is impossible to assign message a priority so that messages with higher priorities waiting in the internal queue were sent first. As a result in situations where we have large outbound SMS traffic, high-priority outbound messages, especially those related to two-way exchange, wait in line with low priority messages. As correct handling of message priority is essential to us, I would like to know whether you consider implementing in future versions of NOWSMS such feature as control of priorities of messages waiting in the internal queue. As I said, this is especially important in case of outbound messages sent as reply to inbound messages, i.e. in two-way exchange. Regards, PM | |||
| Bryce Norwood - NowSMS Support |
Hi PM, I don't have any good solutions for you here ... this is something that we should look at for a future release. Is it possible for you to have two SMSC connections (maybe even to the same SMSC)? What I'm thinking here is that it is possible to submit a message with a "Sender Address" specified, which indicates that the message should be routed only by a particular SMSC connection. You could submit high priority messages with this sender address specified, and they would be queued through a separate SMSC connection. This might be the quickest way to solve your problem. I posted some more information about how this works at: Selecting Outgoing MMSC -bn | |||
