| SMPP validity period issues |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through August 10, 2011 ⬆ |
◄ ► |
| Author | Message | |||
| Chris Frequent Contributor Username: Chrisc Post Number: 53 Registered: 12-2008 |
Hi guys We have found an issue regarding the way the validity periods are handled when sending messages through NowSMS. A large customer of ours needs this urgently as it is vital to their line of business. At the moment we can submit messages via HTTP and submit a relative validity period e.g. “validity=3D” for 3 days. However, at the SMPP level, when submitting absolute time values, the validity period is stripped off by NowSMS and no validity period is specified when the messages are forwarded to the Networks. As an example, the user sent this: Example 1: The time the message was sent: 2011-06-15 03:16:52:433 (BST) Absolute validity period: 110615022648000+ Example 2: The time message was sent: 2011-06-15 03:19:13:169 (BST) Absolute validity period: 110615022911000+ On a similar note, when we attempted to test the absolute validity period, we found out that we cannot submit messages via HTTP GET using the ValidityPeriod parameter. Would you be able to add this particular feature into the HTTP mechanism as well? It just appears to us that while you are able to specify a relative or absolute time period in the SMPP protocol, you should be able to do the same when interacting with NowSMS regardless of what interface you use. Regards Chris | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3262 Registered: 08-2008 |
Hi Chris, Unfortunately there is no support at present for absolute validity, only relative validity. (And relative validity is rounded somewhat.) I've discussed this with our engineering team and they have promised to add transparent validity period support which will support both absolute and relative formats. An update should be ready by next Wednesday. -- Des NowSMS Support | |||
| Chris Frequent Contributor Username: Chrisc Post Number: 54 Registered: 12-2008 |
Hi Des Just to confirm then, will the functionality be added for both SMPP and HTTP? Where SMPP users will be able to specify both relative and absolute values for validity period? Will this also be done for HTTP? Thanks Chris | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3263 Registered: 08-2008 |
Hi Chris, I'm not sure about HTTP. But, we can probably add an HTTP parameter that accepts this parameter in the SMPP format. It would have to be for outbound delivery to other SMPP connections only ... no attempt to convert to other formats. I'll submit this for review, but I don't see any problem with accepting the SMPP validity period setting from either an SMPP client or a new HTTP parameter. -- Des NowSMS Support | |||
| Chris Frequent Contributor Username: Chrisc Post Number: 55 Registered: 12-2008 |
Hi Des Thanks for the update  | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3276 Registered: 08-2008 |
Hi Chris, We decided that it made the most sense to support this setting via the existing HTTP "Validity=" parameter. That parameter will now support either the NowSMS ##D, ##H or ##M format ... or the native SMPP format for an absolute timestamp (such as 110615022911000+). The SMPP format validity period will only be supported when the message is transmitted outbound via an SMPP connection. Additionally, for submissions from an SMPP client, the absolute timestamp format will be handled transparently. An update is available at the following link: http://www.nowsms.com/download/nowsms20110620.zip A review of changes in this release is included in the ZIP and is also available separately at http://www.nowsms.com/download/changes.txt -- Des NowSMS Support | |||
| Rik Clews New member Username: Rikclews Post Number: 18 Registered: 08-2006 |
Thanks Des, preliminary testing has shown that to be working well. Cheers, Rik (Chris is having a well deserved holiday!) | |||
