On 08/08/2006 17:44, gigolo wrote:
Oh.. that hurts. Thank you for the replies. I don't we will go to MO (depends
on the service). The only solution I see is using the dlr-url which will
take time to send the remaining msgs (if more than 160chars) because will
still have to wait for the response of the smsc if user have load or not. If
yes, then we will send the remaining msg for free since the first one is
already billed. Would there still be any chance of fixing the problem any
other way?
you can always send the the billing message separably from the content,
if your content is textual, and over 160 chars.
you might send something like: [You have been billed X money, your
content will arrive shortly]
I also believe that it is possible (at least the specs speak of this) to
event send the billing message with a kind of signal low flag, which
could be empty, meaning that it will not alert the user of its
reception. I am not sure if this is possible for a normal SMS, but if
you are doing wap push or OTA stuff then it is.
hope this helps, and also since i will most likely be having this issue
soon, let me know of the best solution.
--
Kyriacos Sakkas
Development Team
Netsmart
Tel: + 357 22 452565
Fax: + 357 22 452566
Email: [EMAIL PROTECTED]
http://www.netsmart.com.cy
Taking Business to a New Level!
** Confidentiality Notice: The information contained in this email
message may be privileged, confidential and protected from disclosure.
If you are not the intended recipient, any dissemination, distribution,
or copying of this email message is strictly prohibited.
If you think that you have received this email message in error, please
email the sender at [EMAIL PROTECTED] **
