Related
Now that there is a solution for VoIP available I can't help but get greedy So far I used a softphone with multi provider support for this task, but now I wonder: Is it possible to use two different providers at the same time? Right now I am helping myself by switching by hotkey assigned cab files (which works pretty well btw), but what I am really looking for is using one provider for inbound calls and the others for outbound telephony. There are of course providers which can act as a proxy for others, but that solution never really worked out for me as many voip vendors seem to block these attempts (especially pointing a finger at SipGate here ). So, is there any solution for handling multiple providers?
Theoreticall, they are "Backup SIP Settings" you can provision in Windows Mobile 6. Just look at http://msdn2.microsoft.com/en-us/library/aa926605.aspx.
Having only one working VOIP provider, I haven't tried this yet.
However, the format of the XML provisioning is very similar to the one I posed in http://cleanimport.xda/index.php?posts/299950/.
You just have to replace parm name="SIPSettings" by parm name="BackupSIPSettings".
If you try it out, please report here.
Thanks.
--eluth.
The CAB installs fine, but there is no difference between installing a new provider with just "SIPSettings" and "BackupSIPSettings" I tried this with Arcor and SIPGate to test ut whether both incoming numbers would be available at the same time.
hey guys,
not sure if anyone knows the answer to this, or even if theres software available that will do this.....
i have the HD as a handset. it has wifi - we all know that.
my work has cisco VOIP system (SIP-based), that could be configured to allow traffic to our wifi network (or a new SSID setup for VOIP).
i know their is some SIP software out there, but apparently it disables bluetooth once installed - so this peice of software is no good.
HOWEVER, would i would like is when wifi is enabled and sucessfully connected and the SIP (VOIP) software sucessfully connects to the server, then all calls made are via wifi as default.
so, the questions:
- is there any software available that has the above features?
- would i need 'line2' enabled from my service provider?
think fring support sip
that would be a good test platform, but i forgot to mention that i would prefer it to be intergrated into the existing dialer, rather than a 3rd party app.
somewhat like how 'video calling' is, but obviously via a pre-configured SIP service.
the last time i looked into this voip drivers for integration stopped the GPS function working (it has been a couple of months since i last checked though), so i use either agephone (paid app) or fring (free) for SIP calls, both of which will use the contacts on your phone.
not so much the contacts, it's the fact i have to load/switch to a 3rd party app to use SIP.
the app you used that disabled GPS, could well be the one i used. i remember it disabling one of the phones' featured that i used.
veehexx said:
hey guys,
not sure if anyone knows the answer to this, or even if theres software available that will do this.....
i have the HD as a handset. it has wifi - we all know that.
my work has cisco VOIP system (SIP-based), that could be configured to allow traffic to our wifi network (or a new SSID setup for VOIP).
i know their is some SIP software out there, but apparently it disables bluetooth once installed - so this peice of software is no good.
HOWEVER, would i would like is when wifi is enabled and sucessfully connected and the SIP (VOIP) software sucessfully connects to the server, then all calls made are via wifi as default.
so, the questions:
- is there any software available that has the above features?
- would i need 'line2' enabled from my service provider?
Click to expand...
Click to collapse
X-Pro_Softphone_for_Pocket_PC_2.2.2
How does it work on Gingerbread?
Do you need a Gizmo5 / Sipgate account etc?
Anyone tested it?
Bump
Paul22000 said:
How does it work on Gingerbread?
Do you need a Gizmo5 / Sipgate account etc?
Anyone tested it?
Click to expand...
Click to collapse
I believe its just there for applications that wish to take advantage of it,
It's in Call Settings/Internet Call settings. You will need some sort of VOIP account.
Works well. You can set it to dial out using that account with various parameters, and choose to use that account to receive calls.
Works well.
DebauchedSloth said:
It's in Call Settings/Internet Call settings. You will need some sort of VOIP account.
Works well. You can set it to dial out using that account with various parameters, and choose to use that account to receive calls.
Works well.
Click to expand...
Click to collapse
nice!
can someone post a screenshot of the dept of details available?
I mean: what settings can you put in there?
ICE? STUN? secure rtp? and so on
what's the battery usage?
can you set it to register to the sip gateway only when on wifi or policies like that?
thanks
Paul22000 said:
How does it work on Gingerbread?
Do you need a Gizmo5 / Sipgate account etc?
Anyone tested it?
Click to expand...
Click to collapse
It seems to work with the new SIP that comes with Nexus S. BUT..After studying all the documentation and going thru all the screens it appears that it will only work of wifi? So, I removed all my info on that sip account on the Nexus S and installed the Sipdroid/Gizmo5/GVCall back as per your previous post on the "how to". This method gives me the option of wifi OR 3G. It appears to work . The little green led shows up on top (it does not when using the new SIP stuff on Nexus S) so everything appears to be configured correctly. I have not fully tested it but my bet is that it will work over both wifi and 3G unless of course TMobile somehow prevents this.
I actually ended up going to Best Buy last night to check out the Nexus S
The SIP stuff is in the settings, with not too many options. And yes, you have to put in an account. It does nothing unless you have your own SIP account. (What a letdown, Google.) So basically it's just an integrated SipDroid app into the OS, but with very, very few options.
Of course I didn't want to put in my own Gizmo account details into the Best Buy display phone (it didn't have internet access anyway... Best Buy Fail), so I couldn't test it. But there's an option to select when to use VoIP and I forget but the option to select "All Calls" says right next to it "Wifi only" or something.
So I'd imagine this is pretty much useless because
A) It won't allow 3G VoIP
B) For those using VoIP before, other apps (such as CSipSimple) have WAAAAY more options.
C) And in terms of networking/etc, they might even function better since they've been around longer and have been optimized/etc. (Of course, I didn't test that, but just going by CSipSimple's settings menu, there seems to be a lot of customization/options/features.)
Oh yeah, in case anyone's interested:
[Guide] Unlimited Wifi/3G VoIP Calling
How's the battery life using the integrated sip?
I've seen my battery cut by almost half for using CSipDroid and was hoping an integrated SIP, as basic as it is, wouldn't drain the battery that much.
Wonder what call & connection quality is like too??
A very limited unscientific test, but calling in to a conference call today using the built-in SIP client resulted in everybody but me hearing an echo. Using a SPA2102 on the same Internet connection resulted in a clear call with no echo. I've done a lot of tests using my Vibrant and could never get the quality acceptable for SIP calls without echo and still be able to hear the other party. The Nexus S so far has performed better, but in my opinion from limited tests still suffers the same type of issue.
Well, I did some more testing today as my previous test was just a quickie-that is with the "Sipdroid/Gizmo5/GVcallback" method. With that method I could ring to/from another phone BUT when I tested further, I could only talk/hear from one end while the other phone could hear me, I could NOT hear anything that they were saying. When using the resident SIP that comes with the Nexus S, I could hear/talk on both ends (my Nexus to another phone) over wifi of course. I don't know if this is coming off my minutes yet and will check later today to see that.
So it seems that indeed one can only "Sip" call from the Nexus S via wifi with the SIP that comes resident with the Nexus S. Of course with Sipdroid there are a lot of other settings that I have not explored and maybe it needs to be tweaked? But for now, I am gonna stick with the resident SIP in the Nexus S.
An interesting thing also is that I tried the app "Fring" on my Nexus and that did not work correctly either on my Nexus S.
Paul22000 said:
The SIP stuff is in the settings, with not too many options. And yes, you have to put in an account. It does nothing unless you have your own SIP account. (What a letdown, Google.) So basically it's just an integrated SipDroid app into the OS, but with very, very few options.
Click to expand...
Click to collapse
Thank you to everyone here for posting some really useful information about Android 2.3 and SIP. I have a sipgate account and the day I bought my Nexus S (I stood in line in cold weather in the morning to get it), shortly after I brought it back to my office, I was able to "just barely" get it to work with my sipgate account. By "just barely" I mean that I was able to place a few outgoing calls but the latency was so extreme there is no way I could use it again. Now what is quite amusing is that I also have a 2008 unlocked Nokia E71 running Symbian (which has a pretty decent built-in SIP stack in its firmware from Nokia (this is before Nokia caved to the mobile telecoms and started to remove their SIP stack from their smart phones). Well well well, I have *zero* problems with my E71 and my sipgate account (other than some latency but the latency I can pretty much live with, I just have to make sure I don't cut off the other person speaking during a conversation and wait for them to finish their point). Actually, latency is really undesirable but the point being is that the Nexus S is my first Android phone and one of the selling points is Android 2.3 built in SIP stack bundled with the unlocked no-contract Nexus S (I paid full price at Best Buy) and for all the cackling and hoopla Google has been doing on their web sites about Nexus S built-in SIP, that I can't get it to work with sipgate buy my Symbian E71 works with sipgate pretty nicely, this is egg on the face of Google and they should be admonished for their marketing faux pas on SIP / VOIP in Nexus S. It makes me wonder if Google is somehow trying to cripple the built-in SIP stack and configuration options on the Nexus S such as to possibly somehow tilt the playing field to favor Google Voice (I.e., forget VOIP on your Nexus S, just get a mobile carrier service on 3G like T-Mobile account and then maximize the heck out of our Google Voice service). Don't get me wrong, I appreciate Google Voice, but if you're going to put YouTube videos together to promote open protocols, user choice, "Pure Google" and so on, at least make your SIP stack on par with the often lately made-fun-of Symbian which has a superior SIP stack and SIP configuration UI options on the Nokia E71 compared to the Nexus S!
note to Google: don't blame sipgate, this is an Android SIP stack and configuration issue.
Question:
When you call out, what number does it show as caller ID?
Your cell number?
Google Voice number?
SIP number?
Other?
Nexus S VOIP
I was able to setup my Nexus S to work with my VOIP provider Callcentric. The built in Google Nexus S SIP stack only works on Wifi & not with 3G. You can place SIP calls on Wifi with no additional applications installed as long as you have a account with any VOIP provider who uses/allows SIP.
I used Nokia N97 & N95 for years for making & receiving SIP calls with 3G but the voice quality is usually poor on 3G networks.
Using the native Google Nexus S SIP stack on Wifi I called my parents in India, I used it for approximately 45 minutes, the call quality is not as good when compared with the call quality using Nokia N97 on Wifi networks. The volume is very low even when I turned the Nexus S Speakerphone on and set the volume to maximum. I heard echo most of the time when I was talking, the other side had no issues with echo.
The SIP stack on Nexus S needs some work and I am sure there will be more customization features added in the future. I'd not blame google on the missing 3G voip feature yet as my previous experience on 3G sip calls with Nokia weren't too great. Nokia had sip enabled phones for years and it is still not perfect when making calls on 3G network.
Finally when making calls using SIP the other party sees your SIP number. If your VOIP provider allows it, you can customize your outgoing number to display your cell phone number or any other custom number.
My phone fails registration on Callcentric. Any idea why?
auplainsman said:
I was able to setup my Nexus S to work with my VOIP provider Callcentric. The built in Google Nexus S SIP stack only works on Wifi & not with 3G. You can place SIP calls on Wifi with no additional applications installed as long as you have a account with any VOIP provider who uses/allows SIP.
I used Nokia N97 & N95 for years for making & receiving SIP calls with 3G but the voice quality is usually poor on 3G networks.
Using the native Google Nexus S SIP stack on Wifi I called my parents in India, I used it for approximately 45 minutes, the call quality is not as good when compared with the call quality using Nokia N97 on Wifi networks. The volume is very low even when I turned the Nexus S Speakerphone on and set the volume to maximum. I heard echo most of the time when I was talking, the other side had no issues with echo.
The SIP stack on Nexus S needs some work and I am sure there will be more customization features added in the future. I'd not blame google on the missing 3G voip feature yet as my previous experience on 3G sip calls with Nokia weren't too great. Nokia had sip enabled phones for years and it is still not perfect when making calls on 3G network.
Finally when making calls using SIP the other party sees your SIP number. If your VOIP provider allows it, you can customize your outgoing number to display your cell phone number or any other custom number.
Click to expand...
Click to collapse
Errors in registration may be due to multiple reasons. With the limited number of options we have for settings, my guess would be either incorrect login information or wrong transport type selection.
Here are my callcentric settings. May be these settings will help others too.
username: Your sip username* (Example: 17771234567)
*Do not include @callcentric.com as suffix. Also, this is not your regular callcentric account login name.
Password: Your sip password *Not the callcentric account login password
Server: callcentric.com
Optional Settings:
Outbound Proxy Address: callcentric.com
port number: 5060
Transport type: UDP
As most of you have probably already figured out by now the Samsung Galaxy S II, despite running Android 2.3.3, doesn’t have the native Android SIP Stack integrated.
Normally, all smartphones running Android 2.3.3 or higher come with a native SIP stack, allowing handset owners to register their SIP accounts to make and receive calls through VoIP.
Unfortunately this feature has been deliberately dropped by the Samsung cowards who obviously bowed to the pressure of greedy telecom providers (we all know how adamant these sorts of companies are about having this feature disabled).
There are various VoIP clients available on the market (both free and paid) that you can use for making VoIP calls (Sipdroid, csipsimple, etc.) but I’d definitely recommend giving the original Android SIP stack a try as it works nicely and reliably.
Here are the full step by step instructions for enabling the native SIP stack on your Galaxy S II again (I think there’s already a similar thread out there by a member named jarsiv, but I decided to create a dedicated thread describing all steps thoroughly):
- Unzip the attached file “android.software.sip.voip.zip” and add it to “system\etc\permissions\". After you’re done, reboot your phone and voila you can enjoy the benefits of the native SIP stack again
By default, the native Android SIP stack only allows for VoIP calls placed via Wifi (it seems that even the mighty G from mountain view bowed to the telecom operators), but there is a way to enable support for VoIP calls via 3G as well:
- You need to modify your framework-res.apk to enable SIP over 3G by editing the xml file "res\values\bools.xml" and setting the parameter for "config_sip_wifi_only" to false.
In order to modify your framework-res.apk you’ll need to follow the following instructions (again this is only necessary if you want to enable 3G support and not required if you only want to place VoIP calls via Wifi):
- Download the program “APK Manager” (just search the forum) and install it on your PC
- Copy your original "framework-res.apk" (via adb push or root explorer) to your PC and place your original "framework-res.apk" into the "\place-apk-here-for-modding\" folder
- Launch "script.bat"
- Press 22 to set your project and choose "framework-res.apk" as your project by pressing 1
- After setting "framework-res.apk as your project, press 9 to Decompile the apk
- Edit the xml file "res\values\bools.xml" and change the parameter for "config_sip_wifi_only" from “true” to “false”
- Recompile the apk by pressing 11
- When asked whether it is a system file, answer “yes”
- When asked "would you like to copy over any additional files...?", answer “yes”
- The script will be temporarily paused and you shouldn’t press a key now.
- Now go to the “keep” folder (located in the same folder as "script.bat")
- In the “keep” folder delete the following file:
"resources.arsc"
- Go back to the "script.bat" screen and press a key to let the program finish the job
- Your new "framework-res.apk" has been created and can be found in the "\place-apk-here-for-modding\" folder (it’s called "unsignedframework-res.apk" and doesn’t work yet).
- After unzipping the entire content of the "unsignedframework-res.apk" you should have 5 objects (3 folders and 2 files).
- Now zip these files with Winzip choosing "No compression" as zipping method
- After zipping it, rename the zip into "framework-res.apk".
- Now you can use root explorer or adb push to replace the original framework.apk with your newly created "framework-res.apk".
- Reboot your phone.
Enjoy the native SIP stack with support for both Wifi and 3G
Note: If you’re sitting behind a NAT you might not be able to receive incoming calls after a while as the keep alive packets (even when set to “always send”) sent by your android phone don’t seem to suffice to keep the connection alive. Unfortunately the keep-alive interval can’t be changed manually in Android 2.3.3 meaning this issue has nothing to do with your Galaxy S II but rather with the Android native stack.
Good luck and enjoy your VoIP calls
Nice, but native SIP is using wrong mic.
So its pretty useless right now. I recommend CSipSimple (nightly ginger builds), which works excellent, is integrated as well and let you choose a better codec.
there's already a patch in work to fix the issue with the mic.
Btw I'm also a huge fan of CSipSimple and consider it to be the best open source SIP client out there, even surpassing sipdroid in terms of functionality and variety of settings.
yep, csipsimple (nightly builds) is WAY better than sipdroid or built-in sip!
i'm a heavy sip user and tried everything.... csipsimple is the best!
thanks. I am sure this is good stuff Dialling fully numeric numbers is possible if I set call settings to always ask whether to use internet calling, but the samsung dialer doesn't allow calling sip addresses in the internet call section of a contact.
Or am I missing something?
Here it is modified mi rom KE7
requires root root explorer or similar use, route to paste system / framework
perdon por mi ingles soy español
julianico said:
Here it is modified mi rom KE7
requires root root explorer or similar use, route to paste system / framework
perdon por mi ingles soy español
Click to expand...
Click to collapse
here is same modified from
[30.05.2011][CF-Root v3.5] KE2/7 - su+bb+CWM3
I can get outbound calling to work now. inbound doesn't work at all.
update: inbound does work, just when sgsii picks-up the dialling phone continues to ring as though the phone wasn't answered (though there is echo of audio picked up by the sgsii). Maybe my dialing phone has faulty setup? i dunno.
I tried to make this trick but I don't know if it gone well.
I changed my framework-res.apk for to usa SIP under 3G but in settings I see a menu called "Use Internet Call (only WiFi)" (this in translated from italian, I don't know what is the right menu in english) with three options:
- For all calls
- Only for calls via Internet
- Ask me
Are the changes of framework-res.apk gone wrong?
thanks. I am sure this is good stuff Dialling fully numeric numbers is possible if I set call settings to always ask whether to use internet calling, but the samsung dialer doesn't allow calling sip addresses in the internet call section of a contact.
Or am I missing something?
Click to expand...
Click to collapse
For local SIP to dial you need to select allow receive calls under settings. Drains your battery like crazy though.
m_pascal said:
I tried to make this trick but I don't know if it gone well.
I changed my framework-res.apk for to usa SIP under 3G but in settings I see a menu called "Use Internet Call (only WiFi)" (this in translated from italian, I don't know what is the right menu in english) with three options:
- For all calls
- Only for calls via Internet
- Ask me
Are the changes of framework-res.apk gone wrong?
Click to expand...
Click to collapse
It seems that you encountered some kind of error while editing the framework-res.apk because obviously you're stuck on the old settings. When I first attempted to add 3G VoIP calling I couldn't set it up successfully either but when I gave it another try I could eventually get it to work.
After successfully modifying your framework-res.apk you should see the following Internet calling settings:
Option "Use Internet calling":
- For all calls when mobile network available
- Only for Internet calls
- Ask for every call
You can also use one of the frameworks uploaded by julianico or crypticc and then it should work.
@crypticc are you located behind a NAT? What are your settings? What SIP provider are you using?
There are tons of factors that could potentially cause this problem but the more info you provide the more likely we can help.
mobilegalaxy said:
As most of you have probably already figured out by now the Samsung Galaxy S II, despite running Android 2.3.3, doesn’t have the native Android SIP Stack integrated.
Normally, all smartphones running Android 2.3.3 or higher come with a native SIP stack, allowing handset owners to register their SIP accounts to make and receive calls through VoIP.
Unfortunately this feature has been deliberately dropped by the Samsung cowards who obviously bowed to the pressure of greedy telecom providers (we all know how adamant these sorts of companies are about having this feature disabled).
There are various VoIP clients available on the market (both free and paid) that you can use for making VoIP calls (Sipdroid, csipsimple, etc.) but I’d definitely recommend giving the original Android SIP stack a try as it works nicely and reliably.
Here are the full step by step instructions for enabling the native SIP stack on your Galaxy S II again (I think there’s already a similar thread out there by a member named jarsiv, but I decided to create a dedicated thread describing all steps thoroughly):
- Unzip the attached file “android.software.sip.voip.zip” and add it to “system\etc\permissions\". After you’re done, reboot your phone and voila you can enjoy the benefits of the native SIP stack again
By default, the native Android SIP stack only allows for VoIP calls placed via Wifi (it seems that even the mighty G from mountain view bowed to the telecom operators), but there is a way to enable support for VoIP calls via 3G as well:
- You need to modify your framework-res.apk to enable SIP over 3G by editing the xml file "res\values\bools.xml" and setting the parameter for "config_sip_wifi_only" to false.
In order to modify your framework-res.apk you’ll need to follow the following instructions (again this is only necessary if you want to enable 3G support and not required if you only want to place VoIP calls via Wifi):
- Download the program “APK Manager” (just search the forum) and install it on your PC
- Copy your original "framework-res.apk" (via adb push or root explorer) to your PC and place your original "framework-res.apk" into the "\place-apk-here-for-modding\" folder
- Launch "script.bat"
- Press 22 to set your project and choose "framework-res.apk" as your project by pressing 1
- After setting "framework-res.apk as your project, press 9 to Decompile the apk
- Edit the xml file "res\values\bools.xml" and change the parameter for "config_sip_wifi_only" from “true” to “false”
- Recompile the apk by pressing 11
- When asked whether it is a system file, answer “yes”
- When asked "would you like to copy over any additional files...?", answer “yes”
- The script will be temporarily paused and you shouldn’t press a key now.
- Now go to the “keep” folder (located in the same folder as "script.bat")
- In the “keep” folder delete the following file:
"resources.arsc"
- Go back to the "script.bat" screen and press a key to let the program finish the job
- Your new "framework-res.apk" has been created and can be found in the "\place-apk-here-for-modding\" folder (it’s called "unsignedframework-res.apk" and doesn’t work yet).
- After unzipping the entire content of the "unsignedframework-res.apk" you should have 5 objects (3 folders and 2 files).
- Now zip these files with Winzip choosing "No compression" as zipping method
- After zipping it, rename the zip into "framework-res.apk".
- Now you can use root explorer or adb push to replace the original framework.apk with your newly created "framework-res.apk".
- Reboot your phone.
Enjoy the native SIP stack with support for both Wifi and 3G
Note: If you’re sitting behind a NAT you might not be able to receive incoming calls after a while as the keep alive packets (even when set to “always send”) sent by your android phone don’t seem to suffice to keep the connection alive. Unfortunately the keep-alive interval can’t be changed manually in Android 2.3.3 meaning this issue has nothing to do with your Galaxy S II but rather with the Android native stack.
Good luck and enjoy your VoIP calls
Click to expand...
Click to collapse
Very nice info. Perhaps we can change the keepalive in the smali sources? Just reading this made me think of it.
pulser_g2 said:
Very nice info. Perhaps we can change the keepalive in the smali sources? Just reading this made me think of it.
Click to expand...
Click to collapse
Pulser, that's an excellent idea and maybe we can make some other changes in the smali sources as well to offer end users even more options when fine-tuning their SIP settings?
As you may have noticed, the Android native sip stack doesn't allow users to choose their desired Codec, let alone prioritize them. I think the end users should at least be able to choose between the following codes:
G.711 (A-law and μ-law) (64 Kbps for good connections (e.g. Wifi))
G.726 (32 kbps)
G.729 (8 kbps for 3 G)
Despite supporting VoIP calls for handsets located behind a NAT (or otherwise we wouldn't have the keep-alive checkbox) the android SIP settings don't allow users to specify NAT related settings such as:
- Enter Stun server
- ICE
- DNS SRV
Settings for QoS and Echo cancellation are not present either, though I haven't experienced and echo problems during my test-calls yet.
I think these are the most important settings and if we could add them people will probably stick to the native client instead of downloading alternatives from the market that often cause problems with the native dialer of the phone
mobilegalaxy said:
It seems that you encountered some kind of error while editing the framework-res.apk because obviously you're stuck on the old settings. When I first attempted to add 3G VoIP calling I couldn't set it up successfully either but when I gave it another try I could eventually get it to work.
After successfully modifying your framework-res.apk you should see the following Internet calling settings:
Option "Use Internet calling":
- For all calls when mobile network available
- Only for Internet calls
- Ask for every call
You can also use one of the frameworks uploaded by julianico or crypticc and then it should work.
@crypticc are you located behind a NAT? What are your settings? What SIP provider are you using?
There are tons of factors that could potentially cause this problem but the more info you provide the more likely we can help.
Click to expand...
Click to collapse
Hi - thanks for replying.
My sip is pbxes.org. I also setup a test sip on another network to test the call to my PC. I have finally succeeded in getting incoming working by setting pbxes.org to direct via a ekiga.net trunk and setting incoming and outbound.
However, I don't believe that or the NAT is the issue - my question is more about how to physically make the call.
What I mean is that in my dialer I literally cannot enter the sip address to dial. Even if I setup the sip: detail in the internet call placeholder in my phonebook contacts there's no call button.
sip:[email protected] for example.
I have had some success with copy-and-paste into the dialer app, and maybe the NAT thing matters a little because it is more resilient over 3g than NAT - but copy and paste is not ideal.
crypticc said:
Hi - thanks for replying.
My sip is pbxes.org. I also setup a test sip on another network to test the call to my PC. I have finally succeeded in getting incoming working by setting pbxes.org to direct via a ekiga.net trunk and setting incoming and outbound.
However, I don't believe that or the NAT is the issue - my question is more about how to physically make the call.
What I mean is that in my dialer I literally cannot enter the sip address to dial. Even if I setup the sip: detail in the internet call placeholder in my phonebook contacts there's no call button.
sip:[email protected] for example.
I have had some success with copy-and-paste into the dialer app, and maybe the NAT thing matters a little because it is more resilient over 3g than NAT - but copy and paste is not ideal.
Click to expand...
Click to collapse
You’re right, NAT is definitely not the issue here as the NAT settings don’t affect the android dialer at all. I can’t enter a sip address in my dialer either and it appears to me that this feature has been intentionally disabled to deter people from calling a SIP target. I’m looking to find a remedy for this issue though.
In the meantime you can assign a SIP uri to a contact and then copy and paste it into the dialer and then you should be able to call the desired SIP uri. Alternatively you can also download a third-party app from the market (e.g. acrobits) which allows you to enter SIP uris directly without having to rely on copy and paste.
mobilegalaxy said:
You’re right, NAT is definitely not the issue here as the NAT settings don’t affect the android dialer at all. I can’t enter a sip address in my dialer either and it appears to me that this feature has been intentionally disabled to deter people from calling a SIP target. I’m looking to find a remedy for this issue though.
In the meantime you can assign a SIP uri to a contact and then copy and paste it into the dialer and then you should be able to call the desired SIP uri. Alternatively you can also download a third-party app from the market (e.g. acrobits) which allows you to enter SIP uris directly without having to rely on copy and paste.
Click to expand...
Click to collapse
good call, will check it out. Thanks
Sent from my GT-I9100 using Tapatalk
You’re right, NAT is definitely not the issue here as the NAT settings don’t affect the android dialer at all. I can’t enter a sip address in my dialer either and it appears to me that this feature has been intentionally disabled to deter people from calling a SIP target. I’m looking to find a remedy for this issue though.
In the meantime you can assign a SIP uri to a contact and then copy and paste it into the dialer and then you should be able to call the desired SIP uri. Alternatively you can also download a third-party app from the market (e.g. acrobits) which allows you to enter SIP uris directly without having to rely on copy and paste.
Click to expand...
Click to collapse
good call, will check it out. Thanks
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Just a thought. On non samsung phone, long press menu brings up keyboard no matter what you are doing, if this could be enabled then it wouldn't matter what the phone keyboard allowed
Sent from my GT-I9100 using Tapatalk
Hey there,
for everyone who want to use the native android SIP stack,
i made an update.zip for CWM.
Important:
This Version is for WiFi only!
To activate using SIP via 3G, please follow first Post, after flashing my Native_Android_SIP.zip.
Just download the attach. and flash it with CWM.
Done!
crypticc said:
Just a thought. On non samsung phone, long press menu brings up keyboard no matter what you are doing, if this could be enabled then it wouldn't matter what the phone keyboard allowed
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I had the same thought and some VoIP clients actually support this feature. As far as I know some roms enable this feature too since many non-Samsung phones bring up a keyboard if you long press or double click the input field in the dialer app...
Also there are some dialers on the android market which might support this feature. I'm going to give some of them a try and let you know.
@BMWpokerAce thanks for the file
KE8
crypticc said:
here is same modified from
[30.05.2011][CF-Root v3.5] KE2/7 - su+bb+CWM3
Click to expand...
Click to collapse
Hi,
Great work and thanks to the OP for this.
Will the modified one for CFroot KE7 work with CFRoot KE8?
( I have Lightning 1.2 installed).
I tried to enabled the 3g/sip myself, but I don't have Windows but Linux instead.
I did attempt this myself by unzipping the framework-res.zip but the bools.xml is nowhere to be found, along with the values directory.
Any ideas for modding this on Linux? (I know, someone will suggest using WINE ).
Code:
[email protected]:~framework-res.extract/res# ls
anim drawable-en-hdpi drawable-nodpi layout-port raw-da raw-es raw-hu raw-nl raw-tr xml-land
color drawable-hdpi layout raw raw-de raw-fi raw-it raw-pl xml
drawable drawable-land-hdpi layout-land raw-cs raw-en-GB raw-fr raw-ko raw-ru xml-en
[email protected]:~framework-res.extract/res# cd values
-su: cd: values: No such file or directory
This gives nothing:
find -name bools.xml
PS. Although I see there is a point for SIP, I cannot understand why I would use it. From what I see, one has to create a SIP account somewhere with some company and pay for this. SIP is a standard, but from what I understand I have to connect with a third party server ($$s); I imagine someone has to pay for the phone number e.g There is OnSip.com, but the prices are very steep for the average residential client. Businesses can afford this, but my monthly mobile phone bill inclusive of data SMS and calls is about $20, but OnSip's cheapest is $40 yet only for a SIP account.
Or did I miss the point? Please would someone persuade me its a good idea? ( I already have Skype)
forgetmyname said:
H
PS. Although I see there is a point for SIP, I cannot understand why I would use it. From what I see, one has to create a SIP account somewhere with some company and pay for this. SIP is a standard, but from what I understand I have to connect with a third party server ($$s); I imagine someone has to pay for the phone number e.g There is OnSip.com, but the prices are very steep for the average residential client. Businesses can afford this, but my monthly mobile phone bill inclusive of data SMS and calls is about $20, but OnSip's cheapest is $40 yet only for a SIP account.
Or did I miss the point? Please would someone persuade me its a good idea? ( I already have Skype)
Click to expand...
Click to collapse
The point of SIP clients is for business users primarily, for example, I can use it to login to my SIP phone when I'm walking around the office and if someone phones me, my mobile will ring, if I want to make an internal call, I simply dial an extension.
For a personal user, it's pretty much pointless unless you're running a SIP server at home.
Hello everyone,
Is it possible, on an Android phone, to forward incoming calls (from the GSM network) to a local asterisk server (via SIP)?
I know that Android supports SIP as an extension, but that is not useful to me. Currently, the only way I've found, is to use a Bluetooth adaptor on the asterisk server. I'd prefer the SIP solution instead, if one existed.
Thank you!
Andr0ides said:
Hello everyone,
Is it possible, on an Android phone, to forward incoming calls (from the GSM network) to a local asterisk server (via SIP)?
I know that Android supports SIP as an extension, but that is not useful to me. Currently, the only way I've found, is to use a Bluetooth adaptor on the asterisk server. I'd prefer the SIP solution instead, if one existed.
Thank you!
Click to expand...
Click to collapse
I've got the same question.
"Y U dig up old thread?"
See above
So far, I've only found information, that you COULD compile Asterisk for Android. And that the RIL WOULD be difficult to handle.
Has anyone ever tried it? Did you manage to get it working or not?
No I couldn't find a way to do it. In theory, someone could create an app that redirects a call to the PBX, but nobody has done it, afaik.
What I've done instead, I've got a Grandstream VoIP phone with bluetooth support. So all my incoming mobile calls actually ring on the Grandstream. While the calls don't go through the PBX, at least I don't have to bother with the mobile phone anymore.