It's supprising how few people use sip at least those who own Razri. I found it very useful and money saving, especially when travelling.Unfortunatelly Razri uses proprietary phone.apk as a part of Motoblur and Motorola stripped off the entire Internet calling part from the application. It was the case in previous ICS and it remains in JB. Other manufacturers which opt for the similar solution use predictive way to remove android.software.sip.xml from the system and change sip value to false in framework-res.apk. But not Motorola. It obviously used more sophisticated approach. Both above mentioned files remains intact as far as the sip is concerned.
There is an application on the Google Play named Sipswitch which enable widget to enter voip credentials. In previous ICS you couldn't activate the connection. Suprisingly with JB the system accepts the credentials and communicates with the VOIP provider. And the SIP app appears as an extension of the Motorola Phone.apk. But unfortunatelly the SIP is not triggered though it is enabled. There is still the missing link remains. Is the failure result of the fact that Sipswitch is not the system application?
I'm aware that there are many SIP applications on the market. I tried most of them but with Razri they have voice issues. I have best experience with native Voip from previous phones. Does someone else plays with SIP or has otherwise useful advice how to proceed?
piskr said:
It's supprising how few people use sip at least those who own Razri. I found it very useful and money saving, especially when travelling.Unfortunatelly Razri uses proprietary phone.apk as a part of Motoblur and Motorola stripped off the entire Internet calling part from the application. It was the case in previous ICS and it remains in JB. Other manufacturers which opt for the similar solution use predictive way to remove android.software.sip.xml from the system and change sip value to false in framework-res.apk. But not Motorola. It obviously used more sophisticated approach. Both above mentioned files remains intact as far as the sip is concerned.
There is an application on the Google Play named Sipswitch which enable widget to enter voip credentials. In previous ICS you couldn't activate the connection. Suprisingly with JB the system accepts the credentials and communicates with the VOIP provider. And the SIP app appears as an extension of the Motorola Phone.apk. But unfortunatelly the SIP is not triggered though it is enabled. There is still the missing link remains. Is the failure result of the fact that Sipswitch is not the system application?
I'm aware that there are many SIP applications on the market. I tried most of them but with Razri they have voice issues. I have best experience with native Voip from previous phones. Does someone else plays with SIP or has otherwise useful advice how to proceed?
Click to expand...
Click to collapse
Nobody engaged with the SIP? OK, since I'm not a programmer I'm kindly asking developers to take a close look to the attached applications. The first is Motorola's Blur Phone.apk, the second is original ICS Phone.apk. My question is: supposed I root the phone, if I delete Blur Phone.apk and install the original one (which has SIP option included) into the system, do I solve the problem or this is not the appropriate method? Perhaps because of diferrent apk frames or something else? Or must I replace the appropriate (original) Contact.apk as well? Thanks.
Aw: [q] sip/voip
Hi, i have the same problem. I'd like to use my VoIP number with the standard phone app.
I hope that someone can help with this.
Sent from my XT890 using xda app-developers app
me too!
Hi,
I have same problem (ThL W8 phone JB4.1.2 with mt6589 cpu) great phone, but SIP capability has been crippled somehow. Its in the framework-res.apk and the other setup files are there, it seems to be in the code for phone.apk, but there is nothing visible in the menu's and the SIP tester app reports no sip or voip capability. I'd love to know what has been done and how to undo it. It seems somebody has spent quite a lot of time and effort hiding this capability and the only reason I can see is bowing to pressure from the 'airtime sellers'.
I hope someone will point us in the right direction and soon.
gmincca said:
Hi,
I have same problem (ThL W8 phone JB4.1.2 with mt6589 cpu) great phone, but SIP capability has been crippled somehow. Its in the framework-res.apk and the other setup files are there, it seems to be in the code for phone.apk, but there is nothing visible in the menu's and the SIP tester app reports no sip or voip capability. I'd love to know what has been done and how to undo it. It seems somebody has spent quite a lot of time and effort hiding this capability and the only reason I can see is bowing to pressure from the 'airtime sellers'.
I hope someone will point us in the right direction and soon.
Click to expand...
Click to collapse
Well, you missed the forum, but regarding your problem it is not quite the same as here. If the SIP tester doesn't recognize the necessary conditions for SIP, you can try this method: http://forum.xda-developers.com/showthread.php?t=1592890
Motorola as the most qualified phone company uses more sophisticated and dirty methods to screw its customers: the SIP tester does detect sip capability and all necessary files and settings are enabled. But the SIP part is simply stripped off from the core phone.apk.
If you don't dare to try the suggested method you could always use Keyyo voip which has been updated recently and works flawlessly: https://play.google.com/store/apps/...DEsImNvbS5rZXl5b21vYmlsZS5hbmRyb2lkLnZvaXAiXQ..
piskr said:
Well, you missed the forum, but regarding your problem it is not quite the same as here. If the SIP tester doesn't recognize the necessary conditions for SIP, you can try this method: http://forum.xda-developers.com/showthread.php?t=1592890
Motorola as the most qualified phone company uses more sophisticated and dirty methods to screw its customers: the SIP tester does detect sip capability and all necessary files and settings are enabled. But the SIP part is simply stripped off from the core phone.apk.
If you don't dare to try the suggested method you could always use Keyyo voip which has been updated recently and works flawlessly: https://play.google.com/store/apps/...DEsImNvbS5rZXl5b21vYmlsZS5hbmRyb2lkLnZvaXAiXQ..
Click to expand...
Click to collapse
Hi,
Thanks, but the whole point of my posting is because all of the sip information in post 1592890 is already in place, everything looks as though SIP should work, but SIP tester doesn't recognise sip or voip capability and there is nothing in the menus. As for sip/voip apps yes there are countless of them good and bad, but this capability is built into Android and I want to be able to use it as I did on my old 2.3.6 phone. I'm just completely lost as to how to get it enabled.
So thanks, but really not much help so far.
gmincca said:
Hi,
Thanks, but the whole point of my posting is because all of the sip information in post 1592890 is already in place, everything looks as though SIP should work, but SIP tester doesn't recognise sip or voip capability and there is nothing in the menus. As for sip/voip apps yes there are countless of them good and bad, but this capability is built into Android and I want to be able to use it as I did on my old 2.3.6 phone. I'm just completely lost as to how to get it enabled.
So thanks, but really not much help so far.
Click to expand...
Click to collapse
If you have both files set correct (SIP enabled in framework-res.apk and xml) than you have virtually the same problem as it is with RazrI. The core phone.apk is rebuild in the manner that the sip part is stripped off. I prefer native SIP too, regarding my previous experience is the best, but I'm afraid that the only solution in our case is to get AOSP Phone.apk (or similar with SIP as CM) and reconstruct the framework-res.apk accordingly. I'm not the programmer, I'm not sure if it could be done with this method or the whole system is to be replaced with AOSP or CM since Phone.apk is a core application cross related with a lot of other stuff.
What you can try eventually is to deploy two apps: SipSwitch Widget and Zeynalov's Call Manager (Google Play). Sip Switch Widget enables inserting your voip providers credentials and Call Manager supposed to serve as sip trigger. For me the combination wasn't work and I doubt that it would in your case since in your case sip is even not recognised as existed. But it cause no harm to give them a try.
Just use this method, works for me:
http://forum.xda-developers.com/showpost.php?p=24710862&postcount=2
Related
There is an iPhone 3G app called VOiPover3G that tricks other iPhone apps into thinking that they are on Wi-Fi even though they are on 3G/EDGE/GPRS.
Is anything like this being looked at/developed for Android phones??
Please post questions about apps in the correct subforum. This will probably get locked...
This probably is the right subforum. Apps forum is for apps that have been compiled and released. This forum is for dev including apps dev.
Anyway, what would be the point in a program like that? What programs could benefit from it?
JaboJG said:
This probably is the right subforum. Apps forum is for apps that have been compiled and released. This forum is for dev including apps dev.
Anyway, what would be the point in a program like that? What programs could benefit from it?
Click to expand...
Click to collapse
It would allow programs like sipdroid (the market version) to think it was on wifi and when we finally get something like Fring for Android that would also be able to use the data package to make voip calls, even "real" skype calls.
It is in the wrong part of the forum, but I might as well answer it...
While the iPhone doesn't allow certain services over 3G (e.g. VoIP stuff), the current Android handsets + apps don't do such a thing.
e.g. Sipdroid works fine over edge/umts/wifi (as good as those networks can support VoIP).
It's really kind of a strange question to be honest. If there isn't a problem, don't ask questions about it
JaboJG said:
This probably is the right subforum. Apps forum is for apps that have been compiled and released. This forum is for dev including apps dev.
Anyway, what would be the point in a program like that? What programs could benefit from it?
Click to expand...
Click to collapse
Not to harp on the point made by Diceman4, but it really isn't the correct sub-forum. If you look at the Stickies in the Apps/Games sub-forum, you will see that one of them is regarding request/ideas for applications.
JaboJG said:
This forum is for dev including apps dev.
Click to expand...
Click to collapse
I don't see any development going on in the first post though. This seems more like a post for the "ideas for apps" thread in app subforum. Although if the op came back with a chunk of code that needed debugging, that would be a different story.
MOD EDIT
Moved to Applications & games forum
The main reason for asking was because of problems with Tmob in the UK blocking sipdroid (port 5060) and preventing it using 3G etc.
If we had an app like VOiPover3G it may very well allow us to bypass that problem, I don't know
robiom said:
The main reason for asking was because of problems with Tmob in the UK blocking sipdroid (port 5060) and preventing it using 3G etc.
If we had an app like VOiPover3G it may very well allow us to bypass that problem, I don't know
Click to expand...
Click to collapse
Why? a better bet would be to ask the sipdroid creator to include a user configurable port setting. The point of android is that the workarounds don't need to be workarounds on the phone, but rather workrounds for interfacing with the network.
robiom said:
The main reason for asking was because of problems with Tmob in the UK blocking sipdroid (port 5060) and preventing it using 3G etc.
If we had an app like VOiPover3G it may very well allow us to bypass that problem, I don't know
Click to expand...
Click to collapse
The technique described by the op routes traffic internally from the wifi interface to the cellular interface. That will have no effect on the protocol or port used. In other words, it will only be of use if the app is hardcoded to use wifi only and you want to work around that. If the cellular carrier is blocking the data, this method will not get around that.
As for sipdroid, you can manually configure the port used.
jashsu said:
The technique described by the op routes traffic internally from the wifi interface to the cellular interface. That will have no effect on the protocol or port used. In other words, it will only be of use if the app is hardcoded to use wifi only and you want to work around that. If the cellular carrier is blocking the data, this method will not get around that.
As for sipdroid, you can manually configure the port used.
Click to expand...
Click to collapse
If you use pbxes there are a handful of different ports that will work but I haven't been able to get any to work. Saying that, up till recently I was using Gizmo5 but pbxes have blocked it's use after they (Gizmo5) allegedly stole/used sipdroid code and renamed it as if it was there own.
If any one has had success with sipdroid on 3g etc on t-mob UK please post the sip provider and the settings used.
Have you guys tried using the FULL version of sipdroid.. the one on the market didnt allow for 3g calls but this one does http://code.google.com/p/sipdroid/
turboyo said:
Have you guys tried using the FULL version of sipdroid.. the one on the market didnt allow for 3g calls but this one does http://code.google.com/p/sipdroid/
Click to expand...
Click to collapse
Been there, done that, even got the T-shirt.
The problem is T-mob in the UK are a pain in the neck and are blocking the port 5060.
As someone has already mentioned in this thread, what is needed is a user configurable port so that T-mob UK can't block.
Let's hope sipdroid developers can do something along those lines.
I don't get it... have you tried all the alternative ports listed in pbxes website?
53, 69, 80, 135, 161, 443, 500, 1433, 1701, 1812, 3389, 4500, 5061, 5900, 16999, 26999 and
36999 (recommended)
Note:
Because of the DNS entries for pbxes.org your device may be selecting port 5060 automatically. If you want to use an alternative port enter 188.40.65.148 as SIP server.
Click to expand...
Click to collapse
Both of them work as UDP or TCP.
TCP is recommended as it will help with battery life.
If none of these ports work, then It has to be that T-mobile has a Layer 7 filter in place looking for the SIP signaling traffic, and there should be no workaround possible unless you can wrap your sip traffic in a VPN. Nothing can be done to stop that, unless they filter the whole L2TP,PPTP,IPSEC or OpenVPN protocols.
I have tried most if not all of the ports specified and still no joy BUT I'll give it another go. What SIP provider do you use?
If T-mob are killing all SIP traffic how is it possible to use sipdriod over VPN?? Surely that is a major undertaking?
If it was done though, it would be the most robust and bulletproof VOIP app and would never be stopped Brilliant
I have just tried every single one of the alternative ports and every time I had a registration failure (timeout) so I guess T-mob are filtering for SIP traffic.
That leaves only the VPN route OR change providers OR change phones.
robiom said:
I have just tried every single one of the alternative ports and every time I had a registration failure (timeout) so I guess T-mob are filtering for SIP traffic.
That leaves only the VPN route OR change providers OR change phones.
Click to expand...
Click to collapse
Changing phones WILL NOT work since it isn't the phone that is causing the problem, it is the provider.
VPN should be fine, but you'll need a VPN server somewhere to connect through, i.e., your home computer.
There is nothing a carrier can do to block SIP over VPN. Everything is tunneled over the VPN connection so they can't know what goes in there.
As soon as we have a reliable VPN service (Donut seems to have PPTP or L2TP, although I'd love to see OpenVPN there) , you'll ve able to set-up your own voip and vpn server and pipe all the voice through it.
There is a couple of VoIP providers who can do that for you. One that comes to mind is callwithus.
On the connection issue with t-mobile, I suggest you try this:
If you have a DMZ linux/cygwin (altough a windows box might make it) host or a shell anywhere you can test if your provider is locking those ports, the pbxes ip or maybe even the SIP traffic.
Listen in a port using netcat:
netcat -n -l -vvvv 5060
Click to expand...
Click to collapse
Launch the Terminal Emulator in your android phone and test if you can connect to your host:
nc <your_hostname> 5060
Click to expand...
Click to collapse
Type something... if you can see the text, they have a L7 filter in place.
If you can't see anything, they are blocking the port.
Now change the listening port to 36999 for instance.
Try to connect again. It should work.
Now in Sipdroid, add your hostname, give it any username, any password, use the 36999 port and select TCP connection and keep the netcat running on your listening host.
If you see a connection in your listening host and some signalling traffic, pbxes should work for you.
If you don't, then there's a really advance L7 filter between you and the internet and they can block anything they want to.
In this case, the only solution (and there's nothing they can do unless they also block it), is to use a VPN.
Thanks guys for all your suggestions. I'll try and go through all the procedures you've suggested stickman and I'll post the results
Hi All,
I found no hint about SIP support in Gingerbread on SGS (I'm running 2.3.3). Are you also lacking the SIP feature? I read on Android website that SIP may be enabled/disabled according to provider choice (and it seems Samsung went on the safe side, and disabled it).
Do you think any custom kernel/csc/other-stuff might be used to enable it?
Thanks for the support!
Which sip/voip account do you have?
There are tons of apps that you can install and use to make your Voip calls within Android
I am testing tons of them: CSipSimple is doing good on JVK.Ginger for instance
« »
I have an iptel.org account, with custom domain name.
I would have loved to see native SIP support, as I expect it would have seamelessly integrated with the address book and the UI. But I'll give thid-party SIP clients a try, hopefully they'll suite my needs.
Is SIP battery draining in your experience?
alfredio said:
Hi All,
I found no hint about SIP support in Gingerbread on SGS (I'm running 2.3.3). Are you also lacking the SIP feature? I read on Android website that SIP may be enabled/disabled according to provider choice (and it seems Samsung went on the safe side, and disabled it).
Do you think any custom kernel/csc/other-stuff might be used to enable it?
Thanks for the support!
Click to expand...
Click to collapse
You can take a look here:
http://forum.xda-developers.com/showthread.php?t=1016583
alfredio said:
I have an iptel.org account, with custom domain name.
I would have loved to see native SIP support, as I expect it would have seamelessly integrated with the address book and the UI. But I'll give thid-party SIP clients a try, hopefully they'll suite my needs.
Is SIP battery draining in your experience?
Click to expand...
Click to collapse
Well I use Voip/Sip to place my almost free calls wherever I am in the world and in the neighbourhood of a hotspot.
I have 2 accounts with 2 Betamax/Finarea products: Justvoip and VoipDiscount,
With Sipdroid app and CSipSimple app (freem from Market) you get good integration with stock adress book and UI....
Dont know Iptel stuff
Simple question. Does the stock GB on the Bionic have the integrated SIP stack stripped from the OS or not? This is more important to me now with all the rumors of Verizon tracking / limiting rooted users. If I'm forced to use the stock OS then what other liberties did these clowns take to try to prevent me from doing things they don't want? (e.g. backing me into a corner so I still have to pay their ridiculous voice service charges)
This might be the time I decide to cancel my Verizon altogether and go with TracFone + Galaxy WiFi Player (use VoIP when in WiFi range, otherwise use backup prepaid phone). Buncha greedy jerks.
Can someone who owns the phone already check this for me? Should be able to tell by going to "Settings -> Call Settings" and looking for an "Internet Calling" configuration section. If it's not there then they likely stripped it from the OS.
Thanks!
MIA. Looks like it's been stripped.
there are better alternatives anyway - like sipdroid - i wouldnt let the lack of GB native VOIP hinder your decision. Just my thoughts
thanks guys!
to the point about external apps offering SIP support. yes, you're right, but there are numerous advantages to using the native SIP stack vs external apps like sipdroid.
a few come to mind:
* sipdroid/csipsimple has some hardware/driver issues on some phones and makes it hard to work around them at the software level.
* i've found the NAT punching/traversal these programs offer is sometimes lackluster (do they even use libjingle?) making my voip inoperable on public wifis without special port trigger setup or putting my phone in a DMZ.
* it's nice having the SIP stack integrated into OS so it's fully supported by the native dialer and other phone functions
so, i do have interest in making sure my next purchase has this feature. i'm also not sure i'm willing to sign a 2 yr commitment with a provider that limits which features i can use in the OS... that seems to be their power trip going a bit too far.
FYI -
I just got done trying the Galaxy S2 fix for this (see thread http://forum.xda-developers.com/showthread.php?t=1109962) where you add the android.software.sip.voip.xml back to the system\etc\permissions folder but it did not bring the feature back. Looks like Motorola was more effective than Samsung in their stripping of the feature.
jeffason said:
Looks like Motorola was more effective than Samsung in their stripping of the feature.
Click to expand...
Click to collapse
This feature disabled in BlurPhone. It is hardcoded as mSipSupported = 0 and no way to activate it.
i'm trying to re-enable this by editing blurphone.apk. i see in phoneapp.smali constructor this code:
Code:
.line 299
iput-boolean v1, p0, Lcom/android/phone/PhoneApp;->mIsSipSupported:Z
now, how do i change it to set the field to true instead of false? (sorry, i'm new to this)
Man I reallly hope someone has some luck with this - it's the only thing about the Bionic I have a problem with...ha
i tried changing the dalvik opcodes myself to force mIsSipSupported to true, then recompiled, resigned, and pushed to my system files but it crashes (force close) everytime it tries to access the BlurPhone.apk functionality now =(
not sure what approach should be, maybe someone has more info they can chime in with regarding modifying this .apk without it crashing
I'd love if someone figured this out I used to use CSIP SIMPLE and Google Voice Call back, which worked great, but having those running in the background was juicing my battery like no other. Hope someone can find a native SIP workaround!
I made a post/request in the developer forums @ http://forum.xda-developers.com/showthread.php?t=1322163
I'm ponying up $20 to a dev that can restore SIP support in a couple different ways on the Bionic. If this feature is valuable to you then join me by pooling in some funds for a dev to help us out!
Hope we will have a solution soon!
Hi folks,
I'm looking for someone who can either provide a guide for replacing existing BlurPhone.apk with .apks that work with the native gingerbread SIP stack OR someone who successfully hacks BlurPhone.apk so mIsSIPSupported is not hard-coded to false.
I personally will provide $20 Paypal payment to anyone who is the first to do either of these two things. I've been patiently waiting for ROM releases on this phone only to find out that all the options we currently have still utilize the stock BlurPhone app...
Anyone else who would like to offer bounties for this accomplishment please chime in here.
Thanks!
MODERATOR MESSAGE
XDA accepts no responisbility of a scam of any sort.
No offense intended to anyone, just a disclaimer.
This is actually a HUGE thing for me - so I'll toss in $20 too.
Dumb question: Would this just be standard SIP support that I remember Google talking about 12 months ago, or would this also include the ability to use Google Voice right in the OS?
Google Video Chat works ridiculously well so I can only imagine how well Google Voice calls would sound (requires less bandwidth) if it was built right into the OS. As it stands, I use GrooveIP and it is always very frustrating to the recipient of my call.
this request is specifically about the functionality disabled by motorola in blurphone.apk
bump...
anyone? anyone?
Very much needed
I will also be willing to put in money if this gets done. What was Motorola thinking taking it out?
good news...new ICS CM9 has working built-in sip ..whoot
Hi Everyone,
I understand SIP has been natively supported on Android for a while now. Is there a Google native application that I can download on my Nexus 7 tablet?
Thanks
GrooveIP
Sent from my Nexus 7 using xda premium
The native SIP client is in the Phone app, but I'm assuming that the Nexus 7 doesn't come with the Phone app?
AZImmortal said:
The native SIP client is in the Phone app, but I'm assuming that the Nexus 7 doesn't come with the Phone app?
Click to expand...
Click to collapse
Thanks for the feedback AZImmortal. You are right it doesn't come with Nexus 7. But isn't the phone app open-source? Can I not somehow get it on the nexus 7? copy and paste style But in all seriousness, I always wondered if the native dialer was customizable?
Thanks
I don't know what kind of customization you're looking for, but if you want a SIP client, you can use SIPDroid.
Groove_IP works great. All ya need is your google voice number and set it up to "chat only" and enter this info into Groove_IP. Very easy setup.
Sipdroid (with pbxes account) is a lot of work to setup but has lots more power. I have not tested Sipdroid/Pbxes on this tablet yet. :good:
If you use Google Voice, GrooveIP works incredibly well.
But you really need headphones or a bluetooth headset other wise it's a speakerphone.
Headphones?
BamAlmighty said:
If you use Google Voice, GrooveIP works incredibly well.
But you really need headphones or a bluetooth headset other wise it's a speakerphone.
Click to expand...
Click to collapse
Will an old iphone earbud set with the built in mic be functional in the N7 headphone jack?
AndroidMilos - Please don't spam for Groove IP. I don't intend to use Google Voice and your answer is not relevant.
Reason why I am after native SIP is because it's native - no bloat-ware...
Maybe this will help me:
Ref: http://forum.xda-developers.com/archive/index.php/t-1109962.html
You might want to see if any of the custom roms already have the Phone app included. If not, maybe you can ask the dev to include it and explain that it's for SIP calls. I believe that the link you referred to is for enabling SIP when the Phone app has it disabled, but since the Nexus 7 doesn't have the Phone app in the first place, I'm guessing you can't follow the thread. You should probably be able to extract it from another JB ROM and insert it, but I'm not sure how to go about doing that. You should give one of the non-native SIP clients a try before you go through too much trouble to see if it will do what you need.
SIPDroid
SIPDroid seems to work.
You can enable the phone app and the built in sip by editing the framework-res.apk file and changing "voice capable" from false to true.
This will enable the phone app however it will only allow you to add a SIP account at a density of 320.
So change the density to 320, reboot, add you SIP account, change the density again to whatever it was before and you got native sip working.
It works well on speakerphone but a little jerky with a BT headset.
If you don't know how to edit the framework-res.apk file let me know the ROM you are on and I will upload it for you.
Sent from my Galaxy Nexus using xda premium
I use sipdroid.
http://www.youtube.com/watch?v=N24HCaxoqYU
I use the Bria Softphone (by Counterpath). I actually work for a VoIP company, and we use the g729 codec, and that was the best client I could find for android that supported it. Granted it's somewhat costly. But it works very well for me.
clubtech said:
You can enable the phone app and the built in sip by editing the framework-res.apk file and changing "voice capable" from false to true.
This will enable the phone app however it will only allow you to add a SIP account at a density of 320.
So change the density to 320, reboot, add you SIP account, change the density again to whatever it was before and you got native sip working.
It works well on speakerphone but a little jerky with a BT headset.
If you don't know how to edit the framework-res.apk file let me know the ROM you are on and I will upload it for you.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
How do I edit the framework apk? Any advice would be appreciated
Sent from my Nexus 7 using Tapatalk 2
Yes, I use Bria, excellent, alos, 'VOIP by antisip' works, also has video facility, Sipbdroid works too, I have tried them all, but Bria is superior by far ..... my opinion of course!
clubtech said:
You can enable the phone app and the built in sip by editing the framework-res.apk file and changing "voice capable" from false to true.
This will enable the phone app however it will only allow you to add a SIP account at a density of 320.
So change the density to 320, reboot, add you SIP account, change the density again to whatever it was before and you got native sip working.
It works well on speakerphone but a little jerky with a BT headset.
If you don't know how to edit the framework-res.apk file let me know the ROM you are on and I will upload it for you.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hi there,
I'm on last Paranoid Rom, could you tell me how do i edit the framework-res.apk?
I love the native SIP of android, it's the best i've tried on my Nexus S.
Thks
pmauzao said:
Hi there,
I'm on last Paranoid Rom, could you tell me how do i edit the framework-res.apk?
I love the native SIP of android, it's the best i've tried on my Nexus S.
Thks
Click to expand...
Click to collapse
I realize you are looking for native, but I have to recommend CSIPsimple if you don't have any luck with native. Very good, open source and hardly even has an interface - it is very well integrated with the OS.
barryflanagan said:
I realize you are looking for native, but I have to recommend CSIPsimple if you don't have any luck with native. Very good, open source and hardly even has an interface - it is very well integrated with the OS.
Click to expand...
Click to collapse
I've tried both native and CSIPsimple im my Nexus S and the native is way much better, CSIPsimple has lot of echos and noises...
Do you know the best config for CSIPsimple?
I've been using Bria (a third party app by CounterPath) for years.
Yeah, it has some cons and costs money, but it has always worked well for me. It also supports g729 and video.
One thing to keep in mind for VoIP and phones/tablets is if you want to stay connected all the time, versus only occasionally when making calls, you need to use SIP over TCP vs UDP. Most clients/providers default to UDP since it has less overhead works fine on computers/servers/etc. Assuming you are running a VoIP server or client on a computer or phone, especially if it's on the local network, UDP would be the preferred option. The problem on battery powered devices is that it will drain them very quickly. In my testing, leaving the client connected constantly will shorten your overall battery life by about half.
However TCP is much more robust and capable of keeping sessions open through NAT (which your device will pretty much always be behind), and requires less client level activity to keep the session open (hence more deep sleep). As a result, since enabling SIP TCP on my server, I can leave the client running all the time with almost no battery impact. It's like night and day.
Many people complain about VoIP apps and battery drain, and this is a simple fix to eliminate it.