Android-ready JAIN-SIP库？ [英] Android-ready JAIN-SIP library?
问题描述
Greets！
我正在开发（尝试开发）Android的VoIP SIP应用程序，经过两周与mjsip，pjsip和sdk的库之间的争吵，我已经选择了JAIN-SIP。从理论上讲，这些库看起来很棒。无需学习任何Android本机代码，大量文档（但还不够，因为我在这里）等等。
I am developing (trying to develop) a VoIP SIP application for Android, and after two weeks of bickering with mjsip, pjsip and the sdk's libraries, I have settled on JAIN-SIP. The libraries look great, in theory. No need to learn any android native code, lots of documentation (yet not enough, since I'm here), etc.
我的第一次尝试是使用Android SDK的SIP libs（是的，我知道它们基于JSIP），并且在SipManager.open（）拒绝打开与服务器通信的配置文件后失败，没有例外或任何类型的输出来帮助我诊断问题。 （如果您有潜在的解决方案，请查看此处）使用mjsip和pjsip我决定按照计划，花费太多时间来弄清楚本机代码，所以JAIN似乎是完美的解决方案......或者是它？
My first attempt was using the Android SDK's SIP libs (yes, I know they're based on JSIP), and it failed after the SipManager.open() refused to open the profile for communication with the server, with no exceptions or any sort of output to help me diagnose the issue. (If you have a potential solution please look here) After dicking around with mjsip and pjsip I decided that, being on a schedule, it would take too much time to figure out the native code, so JAIN seemed like the perfect solution... or is it?
问题是 - JAIN SIP库在包装中使用的名称与java的核心库相同，因此导致dalvik出现dex问题。但是，确定一个ant make all-android解决方案将sip堆栈源构建为为android准备的单个.jar。的 WRONG 即可。只有gov.nist包被重构，留下javax包，就像之前一样，导致dalvik dex问题。但是等等！ - theres JarJar，一个重新打包jar并重构包的工具，解决了dex冲突。的 WRONG 即可。使用JarJar重新打包还会重命名对堆栈所需的实际javax.net包的引用以进行加密等等，从而导致异常和崩溃以及各种问题。所以我昨天花了大部分时间手工重构javax库，这导致
Problem is- the JAIN SIP libraries use the same name, in the packaging, as java's core libraries, therefore causing a dex issue with dalvik. But ok- theres an "ant make all-android" solution to build the sip stack source into a single .jar prepared for android. WRONG. Only the "gov.nist" packages get refactored, leaving the "javax" packages as they were before, causing the same dalvik dex problems. But wait!- theres JarJar, a tool that repackages your jar and refactors the packages, resolving the dex conflict. WRONG. Repackaging using JarJar also renames the references to the actual javax.net packages that the stack requires for encryption and whatnot, causing exceptions and crashes and all sorts of issues. So I spent the majority of yesterday refactoring the javax libraries by hand, which led to
...Caused by: java.lang.Error: Unresolved compilation problem:
所以这是我的问题......
So here are my questions...
- 有没有人遇到任何准备好Android的jain-sip库真的开箱即用，无需重命名，重新包装和重构？
- 也许我的JarJar规则错了？有人可以为我提供重命名所有包和对javax.sip和javax.sdp的引用的规则，但不javax.net？
- 是否还有其他任何用于Android的SIP库（不需要任何NDK或本机代码知识）？
- 为什么这在2014年仍然如此痛苦？
- Has anyone come across any android-ready jain-sip libraries that really work out of the box, without the need to rename,repackage, and refactor?
- Maybe my JarJar rules are wrong? Can someone provide me with rules to rename all the packages and references to "javax.sip" and "javax.sdp", but NOT "javax.net"?
- Are there any other SIP libs for android (that dont require any knowledge of the NDK or native code)?
- Why is this still such a pain in the back in 2014?
PS在向我指向谷歌页面或其他stackoverflow问题之前，请考虑我已经坚持了两个星期，除了尝试解决问题之外别无其他 - 我可以向您保证，互联网已经彻底搜索并且解决方案要么不申请，要么不工作。
P.S. Before pointing me to a google page or other stackoverflow questions, consider that I've been stuck on this for two weeks now, doing nothing else but trying to solve the issue- I can assure you, the internet has been thoroughly searched and the solutions either don't apply or don't work.
编辑2016年5月 - 接受的答案现在已过期，请参阅下面的joelpatrol回复解。 HERE
Edit May 2016 - The accepted answer is now out of date, refer to thejoelpatrol's response below for the newer solution. HERE
推荐答案
接受的答案已过期。官方版本现在包含适用于Android的版本，从主页链接： https://jsip.java.net/
The accepted answer is out of date. The official builds now include a version suitable for Android, linked from the homepage: https://jsip.java.net/
我现在正在使用它们，可以确认它们正常工作。
I'm using them now and can confirm that they work fine.
这篇关于Android-ready JAIN-SIP库？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
