Android 2.3 using external JAIN-SIP (J-SIP) Stack | Classpath

Question

I am trying to use the JAIN-SIP (J-SIP) library on Android 2.3.3. (Http://jsip.java.net/) Therefore, I used a very simple application for SIP applications, which comes with SIP-Stack. This example works great on Android devices <= Android 2.2.

The problem is that Android 2.3.3 brings SIP-Strack with its system libraries, which is a slightly modified version of the JAIN-SIP stack. Thus, on Android 2.3.3 devices, the internal SIP stack is loaded (due to the same package / library names) instead of the JAIN-SIP that comes with the APK, and the application crashes with exceptions “function not found” (due to the fact that some features do not exist in this internal Android 2.3.3 SIP-Stack).

What I don't know is how I can “assign” my JAIN-SIP stack that comes with the APK and ignore the SIP-Stack system for Android.

One solution uses an internal SIP-Stack directyl, which is very discouraged because no one knows if it has changed in future versions of Android.

Another solution that occurred to me was to change the package names of the "my" JAIN-SIP stack, which do not mix with the internal SIP stack.

The uses-library declaration in manifest.xml does not work, because it is used only for internal SDK-libs / SDK add-ons.

Any ideas?

Answer 1

We are considering shipping banks that will allow you to embed JSIP Stack in any Android device, renaming all javax classes using the post-conversion tool and publishing the jar along with regular jsip banks. See https://groups.google.com/d/topic/mobicents-public/UD7ZTX74Yrk/discussion

Jean

Answer 2

I applied my proposed solution and renamed the JSIP stack packages using the Eclipse refactoring function and got the JSIp stack working on the emulator and Android 2.3.3 device. In the samples and in the class "SipStackImpl.java" there are lines of the package-path that need to be renamed (find / replace) manually to new new package paths.

I tested it with the shootist and shootme samples from the JSIP stack.

He also worked on Android 2.2 in the emulator.

If someone can come up with a better solution, I would approve of it.