Possible to queue local SMS? | developer.brewmp.com Possible to queue local SMS? | developer.brewmp.com

Developer

Possible to queue local SMS?

Forums:

I've been looking at the 2.1 API guides trying to determine if it's possible to queue an SMS locally. ITAPI_SendSMS does not support this (clsID and phone) cannot both be NULL. I'm assuming if I place the local phone# in pszDst it will go to the phone, but I don't see why the phone user should incur 2 network charges. I read through some of the 3.0 docs, I can't tell if it supports this. I would like to know if 3.0 supports, only so that I know if it's possible in any scenario.

Background:

I would like to invoke the web browser and am hoping that I can do this through a locally queued SMS. The SMS would be pushed to local OpenWave browser and open an URL. The SMS queue provides an alternate channel for invoking a Browser

I (and many others) have tried to use ISHELL_BrowseURL. This will not work for many reasons. For background on BrowseURL, please read all of thread:
http://brewforums.qualcomm.com/showthread.php?t=4223&highlight=browser

Andy

Also, I've been thinking about three other alternatives, if anyone could lend advice, that would be great:
1. Capture UDP data packets sent during SMS send/recv by phone on the chance that SMS is implemented in this fashion. If so, reverse engineer these and send correctly formed UDP message locally to simulate SMS receipt. Depends if UDP can be sent locally, some posts I've read seem to say this is a problem, but I haven' t yet tested.
2. Write a program that runs outside of BREW whose sole purpose is to recv a message and invoke the (OpenWave) browser.
3. Contact OpenWave and see if they have any suggestions. I'm going to try this one shortly.

Also, I've been thinking about three other alternatives, if anyone could lend advice, that would be great:
1. Capture UDP data packets sent during SMS send/recv by phone on the chance that SMS is implemented in this fashion. If so, reverse engineer these and send correctly formed UDP message locally to simulate SMS receipt. Depends if UDP can be sent locally, some posts I've read seem to say this is a problem, but I haven' t yet tested.
2. Write a program that runs outside of BREW whose sole purpose is to recv a message and invoke the (OpenWave) browser.
3. Contact OpenWave and see if they have any suggestions. I'm going to try this one shortly.

codeedog wrote: The SMS would be pushed to local OpenWave browser and open an URL. The SMS queue provides an alternate channel for invoking a Browser
I (and many others) have tried to use ISHELL_BrowseURL. This will not work for many reasons. For background on BrowseURL, please read all of thread:
http://brewforums.qualcomm.com/showthread.php?t=4223&highlight=browser
Andy
How would the SMS "be pushed to" the browser? You're not accomplishing anything by sending an SMS that you wouldn't be able to do through sending other BREW events, unless the OEM is doing some sort of parsing of text messages before handing them over to BREW.

codeedog wrote: The SMS would be pushed to local OpenWave browser and open an URL. The SMS queue provides an alternate channel for invoking a Browser
I (and many others) have tried to use ISHELL_BrowseURL. This will not work for many reasons. For background on BrowseURL, please read all of thread:
http://brewforums.qualcomm.com/showthread.php?t=4223&highlight=browser
Andy
How would the SMS "be pushed to" the browser? You're not accomplishing anything by sending an SMS that you wouldn't be able to do through sending other BREW events, unless the OEM is doing some sort of parsing of text messages before handing them over to BREW.

Max,
Good question; perhaps I'm smoking something... This whitepaper on OpenWave's website seems to indicate that WAP Push may be implemented on top of SMS (SMS is one of its transport mechanisms).
http://odn.openwave.com/docs/wappush_tech_overview.pdf
The idea would be that the phone recognizes the SMS as a WAP Push msg and sends it to the WAP msg handler (this all occurs outside of the BREW operating environment).
Cheers,
Andy

Max,
Good question; perhaps I'm smoking something... This whitepaper on OpenWave's website seems to indicate that WAP Push may be implemented on top of SMS (SMS is one of its transport mechanisms).
http://odn.openwave.com/docs/wappush_tech_overview.pdf
The idea would be that the phone recognizes the SMS as a WAP Push msg and sends it to the WAP msg handler (this all occurs outside of the BREW operating environment).
Cheers,
Andy

Hrm...if that's what you're trying to do, ITAPI_SendSMS() isn't going to be much help. WAP push messages use a different teleservice ID than text messages. Not sure whether it would work at all, but you would need to use ISMS and set the MSGOPT_MSGTYPE as AEESMS_TYPE_WAP.

Hrm...if that's what you're trying to do, ITAPI_SendSMS() isn't going to be much help. WAP push messages use a different teleservice ID than text messages. Not sure whether it would work at all, but you would need to use ISMS and set the MSGOPT_MSGTYPE as AEESMS_TYPE_WAP.