I'm trying to understand the SIP API beyond making and receiving audio- only calls. For audio-only, everything appears to be in place for an app to make a call, or receive a call, so the user can talk and hear and all's well. The work is done with the SipAudioCall class.
But for more general-purpose SIP calling, SipSession does the work except that the documentation is very weak with respect to what is expected by the methods. For example, makeCall() takes a session description string and that's all the information available in the documentation. Is it safe to assume that a session description string must be formatted according to the Session Description Protocol (RFC 2327: http://tools.ietf.org/html/rfc2327 )? The same issue is all throughout the SipSession documentation. The onRinging() callback of SipSession.Listener provides the caller's session description. Again, is it safe to assume this is referring to an SDP-compliant string? Thanks for the help. - dave -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
