Hi JBQ, I want to extend the com.android.internal.telephony for VoIP functionality as follows:
Dialer (with alphanumerals, spl characters) -------intent/sip: ------- > PhoneApp ----> Telephony Manager ----> VoIP.java (VoIPJ) -----> VoIP.c(VoIP Daemon) ---> our custom libraries for SIP Could you please tell me whether it is possible to do this in a cleaner way. Why we want to do like this is: We think Google Android will flow the same architecture later on. We can reduce porting effort. Also there is something misleading in this: Currently, GSM and CDMA are supported by Telephony Manager. They are the media and VoIP is a technology which works over the DATA (GPRS, EDGE, Wifi, WiMax or Ethernet). Is it correct to integrate the VoIP changes into the Telephony Manager? I have seen opensource Android VoIP applications completely skip Telephony Manager (Framework Layer) and develop their applications as follows: Application ---> Service ----> Socket ----> Native C lib Application ----> Native C ---> Kernel (FW or Telephony Manager layer is skipped) Which is the best way to do this? Could you please suggest? Thank you, Ram On Nov 29 2008, 9:19 pm, Jean-Baptiste Queru <[email protected]> wrote: > Of course, if you go beyond the official SDK documentation, all bets > are off once you start to consider what might happen with newer > versions of the Android platform on the same devices, or on devices > from a different manufacturer, or using a different chipset, or using > a different protocol to communicate between the application CPU and > the baseband CPU. > > There's nothing wrong going to see what happens "under the hood", as > long as you understand that you're leaving the realm of the SDK with > its supported APIs that are meant to stay compatible across versions > and across devices, and that peeking under the hood is nothing more > than anecdotal data on implementation details about which no > compatibility is guaranteed or even implied. > > Discussions about what happens under the SDK APIs are probably better > suited for the android-platform mailing list, such that this list > remains dedicated to discussions related to developing applications on > top of the SDK APIs. > > JBQ > > > > On Sat, Nov 29, 2008 at 8:04 AM, Zigurd <[email protected]> wrote: > > > Some information on telephony internals, PhoneApp, and communications > > between PhoneApp and the RIL can be found in an upcoming book > > published by O'Reilly called Android Application Development. It is > > available on the O'Reilly "Roughcuts" site in draft form: > >http://safari.oreilly.com/9780596156220 > > > The chapter on telephony internals is mainly oriented around > > illustrating what happens within and underneath the TelephonyManager > > API, using the logging facilities. Although it is targeted to an > > application developer who needs to go beyond the documentation, it > > does provide brief explanations of the telephony internals classes and > > the implementations of those interfaces found in the sources. Maybe > > that can get you started on a full understanding of the relationship > > between the telephony UI apps, PhoneApp, and rild. It will, at least, > > walk you through the steps to observe the traffic between PhoneApp and > > rild using adb. > > > ZM > > > On Nov 28, 8:53 am, sunil <[email protected]> wrote: > >> Hi Jeff Hamilton, > >> May i know if there is any documentation available which explains > >> about the RIL layer , Telephony Manager layer and the service layer. > > >> Regards, > >> Sunil. > > >> On Nov 18, 7:35 am, "Jeff Hamilton" <[email protected]> wrote: > > >> > > Thanks for your reply. > >> > > But the TelephonyManager doesn't provide enough information for us. > >> > > We really need to get more informaiton from the RIL layer. > > >> > What information do you need from the RIL that isn't provided by the > >> > TelephonyManager APIs? > > >> > -Jeff- Hide quoted text - > > - Show quoted text - -- 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
