What you can do, is to write a light weight client, that gives the user a choice..either send the sms using your android app, or send the sms over the operator's network.
Based on the user's input, you can take necessary action. Unconditional interception of all outgoing SMS messages, i think is not right and I dont know what the implications might be. Hence the SMS client route seems legal and hassle free to me. On Jun 12, 5:33 pm, aayush bhatnagar <[email protected]> wrote: > Outgoing calls cannot be equated with this. > 1. Dial codes (also known as feature codes in telecom) usually prefix the > actual phone number when entered by the user. Complex digit analysis takes > place at the GSM MSC which then routes the call to the IN platform (that > provides value added services like the one you describe...calling card > numbers, 1800 toll free numbers etc). Thus, there is a dependency on the > network side to understand and consume these feature codes. > > Free/low cost VoIP calls might need to traverse a wireless soft switch of > the cellular operator, which needs to have the intelligence (SLAs) to route > it to your target low cost network. Otherwise, the call will be rejected. > > No operator will let you use *his access technology* (air interface) or data > network to route calls to a free network without his knowledge so that the > user can dodge his otherwise legitimate revenue generating voice call. > > If he allows you, then he will charge you some money ( for providing a POI > (Point Of Interconnect)) to the target network. > * > * > 2. Coming to SMS.. > > There is no provision in the GSM standard to redirect SMS messages from the > Mobile Station. For achieving redirection, or intelligent routing of your > SMS messages, you need to write a SMS gateway that proxies all your SMS > messages through the 'least cost route', as you describe below. For doing > this, you need to either use a feature code that your SMS gateway > understands ( like the one given > here:http://www.smsitaly.com/eng/smsredirect.asp) or you invoke the SMSC of > the > operator by invoking a web service/API like the one given here: > (http://www.betavine.net/bvportal/resources/api/betavine) > > In both cases, a SMS gateway is required. > > Hope this helps.. > > > > > > On Fri, Jun 12, 2009 at 12:43 PM, Seer <[email protected]> wrote: > > > It is not just about notification but the ability to cancel or modify > > as well. > > > To give you a bit of background a similar feature already exists for > > outgoing calls. It allows you to intercept the outgoing call and auto > > insert say a calling card number and dial codes for outgoing calls or > > maybe you would use it to block outgoing calls to set numbers. In my > > case i use it to reroute calls that would cost me through free numbers > > provided by a voip provider so that for all my calls i pay voip rates > > on my mobile even though i make the call over the mobile network. > > > A similar case is with sms for me. My mobile provider will charge me > > between 25cents and $1.50 for sms's depending on the destination but i > > use a website to send the same sms for 5 cents. Having this > > functionality allows developers to write applications to intercept all > > outgoing sms and manipulate or redirect them over other delivery > > methods that can save users a lot of money. Currently the only way to > > do this is to write your own sms client. the most famous example of > > this on Android is Chomp sms. Most developers would prefer to let the > > users use what ever sms client they want and not have to reinvent the > > wheel just to catch outgoing sms. > > > There are many more cases on why this would be useful but that is my > > particular case. > > > Chris > > > On Jun 12, 4:35 pm, aayush <[email protected]> wrote: > > > Interesting feature request. > > > What is the use case for such a requirement? I am asking for my > > > understanding. Why do you need to be notified when the sms or email is > > > sent out? > > > > On Jun 12, 5:18 am, Seer <[email protected]> wrote: > > > > > Guys there is a issue raised for this now. Please add your votes to > > > > it so that hopefully it will be implemented. > > > > >http://code.google.com/p/android/issues/detail?id=2261 > > > > > Hopefully it will be implemented so we can capture outgoing sms in the > > > > next release of android. > > > > > Chris > > > > > On Apr 21, 11:28 pm, Gulfam <[email protected]> wrote: > > > > > > Hi all, > > > > > > Any updates about interception of out going SMS???????????? > > > > > > Gulfam > > > > > > On Apr 5, 4:53 am, Seer <[email protected]> wrote: > > > > > > > I have been trying to catch outgoing sms and i can tell you it is > > > > > > currently impossible. No one on here or the platform knows a way to > > do > > > > > > it and from the people i have spoken to most have did not seem to > > even > > > > > > think people may want to do so. Hopefully it is a feature added in > > > > > > the future. > > > > > > > On Feb 5, 3:00 pm, Dietrich Ayala <[email protected]> wrote: > > > > > > > > i figured out how to listen foroutgoingcalls. however, i can't > > find > > > > > > > any docs or code samples for making a Receiver that > > catchesoutgoing > > > > > > > sms or email. > > > > > > > > is that possible? > > > > > > > > thanks! > > > > > > > > -dietrich > > -- > aayush > ---------------------------------------------------- > "Cleverly disguised as a responsible adult" --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
