| WAP push delivery too long |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through June 21, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| saimike New member Username: Saimike Post Number: 4 Registered: 02-2007 |
I've recently been testing WAP push, and it takes way too long for delivery (a few hours!) at times. Is there a way to prioritize how messages are inserted into the queue? For example, "super users" messages gets put at the front of the queue, or WAP push messages are put at the front of the queue, etc. On a related note, is it possible to view on the nowsms server, what times messages are sent? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6982 Registered: 10-2002 |
Hi, You can view the times that NowSMS actually dispatched the message to the SMSC by examining the SMSOUT-yyyymmdd.LOG. I'd encourage you to take a look at that ... because unless you are sending out a lot of bulk broadcasts, NowSMS does not single out "WAP Push" messages to be sent out with lower priority. If you are sending out a lot of bulk broadcasts, I would encourage you to enable "Separate outbound message queues for each user" on the "SMS Users" page. Send out the bulk broadcasts using a different user account (e.g., "SMS Users" account) than your more messages with a more timely requirement. When separate outbound message queues are enabled, NowSMS won't let large bulk broadcasts from a few user accounts get in the way of normal message sending from other accounts. In your case, I'd suspect that the issue is not in NowSMS ... but if you're using a GSM modem, we have noticed in the UK that at least one of the operators (I think it was O2) seems to occasionally experience extreme delays in delivering binary SMS messages, including WAP push, when they are sent via a GSM modem. -bn | |||
| saimike New member Username: Saimike Post Number: 5 Registered: 02-2007 |
Bryce, would it be possible to put in a feature request which would tell the user either: 1) Where in the message queue his SMS/MMS/WAP-push etc is? or 2) Estimated time for the message to be sent (based on its place in the message queue etc)? This can be a useful tool for the enduser to determine if the excessive delay was due to the backlog, or to the network. It would also allow me, the administrator, to determine when I should upgrade my license. Appreciate your feedback on this. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7006 Registered: 10-2002 |
Hi, We are making some improvements in the area of statistic information (and user access to their own logs) for the next major release update. However, at this point, there is nothing planned for indicating to a user whether or not a message that they sent is still queued locally. Maybe that is something that can be incorporated into the next round of major updates ... or maybe not ... I have added notes about this into the development plans for the next major release ... but I don't know what is practical in the next release. I do know that estimated time is not practical to provide because there are too many variables. Regarding administrator information ... we are working to improve this for the next major release ... but at present, I would recommend enabling the e-mail alerts, and putting in an alert for when the queue size exceeds some value that would be considered very large in your environment. -bn | |||
