| Author |
Message |
Ivan
Unregistered guest
| | Posted on Monday, October 04, 2004 - 01:44 pm: | |
Dears,
it seems that the PPG on the NowMMS is not setting the expiry time on the SMSes sent to the SMSC, while the expiry time is set in the PAP request. Is it a bug or is this feature just not implemented? (or am I not reading the traces correctly)
Cheers,
Ivan |
Anonymous
| | Posted on Thursday, October 07, 2004 - 12:52 pm: | |
Hello,
When Now.Sms sends a multi segment mms notification does the timestamp on each segment of the notification have the same value?
How do other smsc's behave with respect to setting timestamps of individual segments in a notification? Does the standard give any recommendations?
Thanks. |
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce
Post Number: 3553
Registered: 10-2002
| | Posted on Tuesday, October 12, 2004 - 09:41 pm: | |
Hi Ivan,
Support for an expiry time is not implemented. We may consider implementing it for selected SMSC interfaces in the future, but at present I can confirm that we do not generate an expiry time. (We have limited support for it when sending regular SMS through a GSM modem, but have not implemented it via any of the other SMSC interfaces.)
Regarding the multi-segment MMS notification message, there are indeed timestamps contained within an SMS message, but those are all set by the SMSC ... they can't be set at the application level. I would expect a different timestamp in each segment, at least there is no requirement that they be the same. Generally the sender address must be the same.
-bn |
|
Search
Last
