Related
Well, very strange: Since a couple of days everytime I open up the keyboard menu I found myself with a list of probalby a hundred selection entries. Not only Keyboard etc, but also strange names like:
ATI Audio Decider DMO Class
Active SSCE engibe Object...
CE Shell...
(you get the idea)
I opened up sipchange.exe and found the same entries.
Seems my registry got corrupted. Everything else works. Could someone send me an export of the standard registry entries for the SIPs?
Would be very appreciated, thank you.
More on this issue ....
Ok, after reading some of the Wiki I found out, that I find all Input methods in
HKEY_CLASSES_ROOT\CLSID\
Well, and I could put them on "hide" by setting the IsSIPInputMethod to "0".
since I found like 150 entries in CLSID - I would like to know if it is safe to completely delete the CLSID entries that are not corresponding to my standard inputs or if I have to manually set all IsSIPInputMethod to "0". Inother words: Do I need the other CLSID entries for anything else?
I would now really really appreciate if someone could send me his part of the registry below "HKEY_CLASSES_ROOT\CLSID\" from a Hermes.
Could Paypal help anyone for his effort? I would suggest SKTools since it can export a registry. I only need the part mentioned above.
Regards,
Apple*
And again...
Well, it seems the entries have to stay there. Just looked at an old backup registry.
Well, anyone knows a registry editor that can easily "search & replace" entries?
Regards,
Apple*
All done ...
No idea which application tampered with my registry - but I managed to put all the values back to normal:
I did a Export with the Registry-AddIn from Resco Explorer 2005, then I exported this to a PC, edited the file with an Texteditor and copied it back to the device. Resco Explorer did import the .reg file without problems.
Didnt know Resco Explorer had an import function as well :
Well done you did it with no help from anyone. I would have helped out but site was so slow until now that I was not able to do much for anybody recently - sorry.
Cheers
Mike
Is anyone using a 3 uk simcard in a hermes tytn or spvm3100. Im having problems connecting to msn and skype via gprs. I was wondering if anyone could post their 3 uk settings especially the phone band settings. I used to be able to connect to skype and msn but ever since I temperd with the settings it refuses to connect. It connects onto the 3g network to surf the net though. They both also connect using wifi. Help please!!!
Telco Settings - Wiki?
Well, there are more and more posts about GPRS/MMS settings in these forums. Could anyxone open up a Wiki for WM5/WM6 settings?
I could gladly provide german T-Mobile and Vodafone settings.
Mike, thanks for the offer. I suspect Beemer NullKeyboard in getting all my CLSID registry entries registered as SIP. So a big "caveat" to all readers using this software.
Hello everyone!
Situation: I have several VoIP provider (sipgate, 1und1...) My problem is I can only setup a single provider in my phone with built-in WM6 VoIP client.
Solution attempt: I set up an account with pbxes.org. There I added my SIP providers and an extension with username and password. Now I tried to set this up using the Sip Config Tool V2.0.1. Here are the settings:
Sip Server: pbxes.org Port: 5060
(tried others like sip.pbxes.org(com) and the IP)
username: username-extension_number
password: password
That's it. It's not working. The Today Internet-Calling-plugin tells me "searching....", but never to "selected"
I also tried using x-lite on my desktop pc. With the same settings I successfully registered and I was able to use pbxes just as it is supposed to be.
When using sipgate directly with WM6 it works, but not with pbxes.
I am kind of running out of ideas. So any help is really appreciated.
Thanks in advance,
Stefan
Tried several times as well on my S620.
Now, two days ago got a S710 and was curious to test VOIP on it.
Very first time I tried I was thinking everything was fine, at least nearly.
The Today plugin showed "Searching" (like with providers it works with)
The icon for Internet Phone showed up.
Unfortunately it "semi worked" only that time, any other tests I tried the Today Plugin didn't even get into "Searching".
The bad thing is that it did work once, like meaning it could work. Now PBXES status shows as Registered but it isn't actually. The other bad thing is that I tried to post in their forum for help but didn't receive much info back.
Bad luck, but I'll try and try again. Maybe newer files one of these days and our probs would be solved.
Ka.
Subscribe message
I ever check the message from sip server, I found that windows mobile voip client not only send register message, but also try to send subscribe message, I guess that it is reason that some sip server only may work as registra, and not handle correctly subscribe. it seems the reason the client always display "searching", I will try to modify sip server to support subscribe message in the future.
try fring
try using fring...
it supports multiple sip accounts.. and actually register u not just subscribe you.
You are right, Fring or any other 3rd party app connecting to a SIP server can work maybe better than the "builtin" SIP functionality but personally would prefer being able to use a solution where I dial like usual and calls get automatically router to VOIP, not having to switch to a separate app.
This is why I'd rather like the builtin sip stack to work on its own with any SIP provider. I tested it with PBXES but doesn't work. I'm currently renting a VPS with Asterisk (Trixbox) installed and it does connect. Only prob is that even if it manages to register, seems MS VOIP implementation is still not really compatible or suitable for the use I wish to have.
Ka.
This is an old thread but this is the same problem I have on my HTC HD2 (Leo).
Installed sip drivers and voip config cabs and configured it with my account through pbxes and it is not working.
Can someone help?
Android (Moto droid, HTC Hero) I had no problem with pbxes and sipdroid...
I have been seeing various posts on people struggling to make BBConnect work on HTC Touch Pro 2 a.k.a Rhodium and thought I would put down a step by step guide from various posts put down through this forum So rejoice all you HTC Touch Pro 2 owners like me BB Connect is finally working and so is Multiple APN's. I have BB Connect Enterprise and GPRS connecting simultaneously and its showing up on the notifications manager.
This step by step solution is thanks to Cornholio, Absahnen & NRGZ8(The Master Chef who cooks wonderful ROms across devices)
So Here Goes
Step I: GET YOURSELF A NEW ROM:
Trying to install Blackberry Connect is very buggy on most of the stock ROMS and will keep on failing. So go and get yourself the latest NRGZ8 ROM for Rhodium I am using Build 21877 27th Nov Standard Manila 2.1. The ROM is anyway faster with almost no bugs and free of Junk that you see on standard ROMS
download the ROM from this link:
http://hotfile.com/list/93322/b5a2687
Step2: CHANGE AKU SETTINGS
This change is needed to make BB Connect work on WinMo 6.5 ROMS.
Using a registry editor go to HKLM/System/Versions
There you will see the aku key usually on any WinMo 6.5 ROM its .5.xx.xx change the aku value to .1.6.0(.1.6.3 didnt work, the connection was getting dropped)
Step 3: FOOLING YOUR BB CONNECT SOFTWARE TO THINK YOUR DEVICE IS A RAPHAEL
The Rhodium is not yet supported by RIM and looks like they have withdrawn support for further devices. Therefore you need the BB connect to believe that your Touch Pro 2 is a Touch Pro i.e. Your Rhodium is a Raphael. To do this you have to make registry changes you can use any registry editor I used Resco Registry Editor which loads when you load Resco Explore on your device To do this follow the steps below very carefully, using the registry editor
Instructions:
------------
- Uninstall any BB Connect software if you loaded.
- Attached find a rar file which contains SetModelID.exe. Unzip it and copy it over to the \windows\ folder of your device.
- Using any registry editor of your choice navigate to HKLM\init Create a new String Value with the name "Launch130" and a value of "SetModelID.exe" (without the quotes)
If Launch130 already exists, choose a number greater than 130, it doesn't really matter, just make sure it is higher than the other entries so it get started after everything else.
This makes sure the exe isnt started after every softreset.
- Do a softreset
- The program changes your model-id from "HTC-Rhodium" to "HTC-Raphael" in memory
- Install Blackberry Connect like you usually do (My tests where successfull with version 4.0.0.106)
- After installation and the auto-reset through BBC open the BBC settings and go to the Info-Tab. Under device-name there should now be HTC-Raphael.
- If you're using BES configure your device using enterprise activation or the BB Connect desktop app
STEP 4: ENABLING MULTIPLE APN'S
This will allow you simultaneously have an active BBConnect and a GPRS connection active at the same time
Go to:
HKLM\Software\OEM\RIL\OperatorContexts
There you will find several numbers. E.g. 26202 for Vodafone in Germany.
The number is a combination of MCC / MNC so 262 02. You might find you operator in this list:
http://surfio.de/info/mcc_mnc/mcc_mnc_liste_6.html
or do a google search for your specific operators MCC/MNC nos
Create the two DWord Value Entries below if they arent there:
GPRSContextNumber = 3
UMTSContextNumber = 3
Just set the Contexts value to 3 and delete the NetworkContexts entry. It will be created from the source above with the value 3.
And voila you will have multiple connections running simultaneously you can get your BB Mails as well as see Youtube videos over GPRS. I managed to do this over a frustrating 48 hour period and I thought will share this for anyone seeking an answer.
Cheers and enjoy
Man! The guide looks great! but it makes my brain hurt!!! Arggg!!!
(Hardly understand some part of the guide.)
: )
Heres my step by step, plus all the software and a cab called black berry that someone else kindly put together for me that does all the registry steps (and makes the multiple APN switch for TMOB US). (BTW this has worked on EVERY ROM I have used, 6.1, 6.5, 6.53, sense 2.1 and 2.5):
['black berry cab' does all these]:
Copy SetModelID.exe into windows
HKLM\init: Create a new string: Launch130 with value: SetModelID.exe
HKLM\system\versions\aku - change to .1.6.3 [which works for me]
HKLM\Software\OEM\RIL\OperatorContexts\...
Create new ones or edit your relevant operators GPRS and UMTS to 3
[for US find them in http://en.wikipedia.org/wiki/List_of_mobile_network_codes_in_the_United_States]
HKLM\Comm\Cellular\RIL\
set the Contexts value to 3
Delete the NetworkContexts entry
Soft Reset
Install BB Settings CAB
(I always create a shortcut in programs from 'BB Settings' in Program Files/Blackberry - its a quick way to run this file later)
Either: Using BB connect desktop for WM 'configure wireless handset' (see below)
Or: get new key generated by your company's tech support and enter them into BB Settings on your device
(Activesync blackberry connect desktop setup can be found at http://sems.org/content/download/bbc4/bb_desktop_4.0.0.22.zip. I use this becuase YOU CAN GENERATE YOUR OWN KEY and configure your handset again and again which means you dont have to bug tech support every time you burn a new ROM, which I do every few days!)
for some reason I cant upload the blackberry connect cab, so here is the link http://sems.org/content/download/bbc4/bbconnect_wm6_professional_bb.4.0.0.106.cab
black berry cab is attached.
what150 said:
Man! The guide looks great! but it makes my brain hurt!!! Arggg!!!
(Hardly understand some part of the guide.)
: )
Click to expand...
Click to collapse
Well what can I say Mr What 150 was trying to help. The step by step guid is written keeping noobs in mind so that you dont get back Q's on How to do this? and How to do that? and help ppl besides just those in the US who cant use the cab posted here anyways and dont know how to write complicated XML codes.
Thanks a lot patcat!!!
I had my rhodium working with BB connect but no multiple APNs... had to manually suspend BB service and enable GPRS everytime I needed anything from the internet. Those days are gone now!!!
Now, have you ever wondered why is it that BB Messenger, being a Java application, can not be ported to WM and run on our TP2s? I mean, we have our BB data plans, a PIN# and are connected to the Blackberry service.. what else do we need for BB Messenger to work?
Roberto Gonzalez said:
Thanks a lot patcat!!!
I had my rhodium working with BB connect but no multiple APNs... had to manually suspend BB service and enable GPRS everytime I needed anything from the internet. Those days are gone now!!!
Now, have you ever wondered why is it that BB Messenger, being a Java application, can not be ported to WM and run on our TP2s? I mean, we have our BB data plans, a PIN# and are connected to the Blackberry service.. what else do we need for BB Messenger to work?
Click to expand...
Click to collapse
You are welcome Roberto. I havent yet come across any cab for BB messenger. There has been talk of a BB application suite to run on WinMo but I havent seen any beta's also of that floating around. If you do come across any BB Messenger cab do post it here or PM me the cab.
Most reliable method
Here is what I do...I think it is the most reliable method....and I have used it with just about every ROM out there and it works...everytime...It looks like a lot of steps but it is very easy and after the first ROM flash you will know what do do for any others...I actually learned this from this site and MUCH smarter people than me...so thanks to all those who helped get Blackberry Connect working. Without this site I might still have an 8525 because I need blackberry connect...!
Installing Blackberry connect...this has to happen in this order...
1. Download a ROM
2. Edit the ROM using the information from here, it looks complicated but takes less than a minute essentially you use the program you download to change any reference to Rhodium to Raphael using a search: http://www.silentservices.de/HexEdit-ROM-for-BBC.html
3. Flash the edited ROM.
4. Install the CAB file I attached it will change the AKU for you...I actually put it in my UC script so it automatically installs before Blackberry Connect...
5. Install Blackberry Connect version 4.0.0.106
Allowing Multiple APN's (This can happen at ANY time)
Follow step four in the original guide or if you are AT&T all you have to do is use a registry editor and go to HKLM\Software\OEM\RIL\Operator Contexts\310410 and change UMTSContextNumber to 2. If you use 2 then you don't have to worry about anything else like deleting the Network Contexts entry....
BBC
Works excellently on my TP2 with .106 cab on Vodafone India network at Delhi.
Good work bro, well sorted out steps
PIN Pending
Hu there, Thanks for all your help, The device has changed into Raphael but I still get PIN pending? how can I have Blackberry Service if there is no pin? help please
Patcat007
You are the got damn man!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
PIN Penidng No Connection
Hello,
I have done as per above steps but I am still getting Pin Pending. I am using HTC touch Pro 2 with Win Mo 6.5. In BlackBerry Connect About Device Type is HTC-Raphael.
Please help me what to do how can I resolve thie issue.
Address book, Sending pictures via Email not available
Hi,
I've got everything working thanks to you guys.
When composing a new Email, the address book is not being used (no Auto completion or suggestion).
I would take a picture from the camera but the option to send via Email is greyed out with the account setup via BB.
No HTML Email viewing.
Is it designed to work like that with BB Connect?
PIN Issue
foolyfaltoo said:
Hello,
I have done as per above steps but I am still getting Pin Pending. I am using HTC touch Pro 2 with Win Mo 6.5. In BlackBerry Connect About Device Type is HTC-Raphael.
Please help me what to do how can I resolve thie issue.
Click to expand...
Click to collapse
PIN is provided by GSM service provider. These step enable the BBC software to accept your handset model as compatible for BB services. Its not a hack for working BB without BB activation. Get the BB services activated from GSM operator and u shall have a PIN also.
HTCSOCAL said:
Hi,
I've got everything working thanks to you guys.
I added what I know...it does seem since Blackberry connect is an older program everything ends up like a work around...
When composing a new Email, the address book is not being used (no Auto completion or suggestion).
It won't auto complete. If you click the menu and use the "check Names" feature it will first look in your address book and then if you hit Lookup it will look in the global address book. A little more cumbersome but it works.
I would take a picture from the camera but the option to send via Email is greyed out with the account setup via BB.
I have not been able to send photos from the camera in the last several Roms...so I think it is the newer Album that doesn't allow it. You can still send it by attaching it when creating an email, but yes this is a little cumbersome as well...
I only have one email account setup on my device which i
No HTML Email viewing.
Yes that is correct...
Is it designed to work like that with BB Connect?
Click to expand...
Click to collapse
Hope this helps...
mumboender said:
Hope this helps...
Click to expand...
Click to collapse
I also had seen those issues with my HTC HD on WM 6.1.
Another one is clicking an URL in the Email body gives me an error (The parameter is incorrect).
Thanks for the tips.
HTCSOCAL said:
I also had seen those issues with my HTC HD on WM 6.1.
Another one is clicking an URL in the Email body gives me an error (The parameter is incorrect).
Thanks for the tips.
Click to expand...
Click to collapse
Yeah, I have not been able to click on a URL since my days with an HTC 8525....
Working with Valkyrie 5.2 ROM and BB Enterprise I'm using
Thanks
NO PIN
dineshh said:
PIN is provided by GSM service provider. These step enable the BBC software to accept your handset model as compatible for BB services. Its not a hack for working BB without BB activation. Get the BB services activated from GSM operator and u shall have a PIN also.
Click to expand...
Click to collapse
hi there, i have the same problem of not having a pin on my tp2, my carrier says the pin is on the device here is a copy and paste of my carrier web iste when i tried to activate the service
"To find your PIN perform one of the following actions:
* In the BlackBerry device options or settings, click Status.
* Look for the PIN and IMEI information on the outside of the box that your BlackBerry device or BlackBerry-enabled device came in.
* Turn the BlackBerry device off and remove the battery. Look for the sticker on the BlackBerry device with the PIN information where the battery is usually located."
Nice tutorial, patcat007. On my TP2 with a 6.5 ROM my BB Connect work. Anyway, when I change the AKU to .1.6.3, something happens with graphics in my dialer like in the picture attached. Anyone could help to correct this? Thank's!
NEW IMPROVED CABS : POST 3
A very Special Thanks to tucahara, Schap, Jaap de Wolf, Dridder
Note : For HTC devices only, please read 2nd post -below-for non HTC devices.
- 3G, WLan, GPRS Capable
- GPS Works
- Recent Drivers
- Updated Registry
- All Major Codec compatible[ a-law, u-law, GSM ask provider to enable ]
- Integrated with Phone and address Book
- VOIP and Carrier sellectable on today screen
- SIP Tool [ Start Menu WM6.5 or Start Menu-Programes Wm6.1 ]
- Dial Plan Tool [ Start Menu WM6.5 or Start Menu-Programes Wm6.1 ]
- NAT Enabled
- Echo Canceller
- For WM6.1 and WM6.5
- Tested and working on my HD, HD2, Omnia II, Glofiish M700, Touch Pro2[Rhodium], BlueAngel[PDA2K], Xperia X2
- No sound from earpiece ( Please install cab from previous thread but that is only for HTC devices )
INSTALL ON FRESH OS and PLEASE POST YOUR RESULTS GOOD OR BAD. Thanks
THERE IS NOTHING WRONG WITH THESE CABS, SO PLEASE DO NOT COMPLAIN ABOUT CABS. IF THESE CABS WONT WORK, PLEASE READ DIFFERENT POSTS IN XDA AND FIND OUT WHY. MOST COMMON REASON IS DEVICE OR OS NOT SUPPORTRD MEANING DEVICE DOESNT HAVE FILES NEEDED FOR THESE CABS TO WORK.
These cabs are tested, working with different providers-devices and are not for noobs, if you have come across this before, you will find out, these cabs are the best among them.
Outdated Cabs HERE
For non HTC devices, do the following
- Install one of the cabs post 3 matching your OS.
- Fill all required information in setup voip.
- When you try to save you will get a error
- Close it and Run your GPS program.
- Your GPS with get a lock in few minutes as normal.
- Once you find out your GPS program can see satellites, close it.
- Copy and paste dnsapi.dll into your windows folder
- Restart your device and you will have your gps and voip/sip working
- Make sure to fill information in setupvoip again
New improved cabs
New improved cabs with changed dll. Note : Only for HTC devices. For other non HTC devices, please refer post 2 along with these cabs for optimum results.
Reserved for future2
Reserved for future3
Reserved for future4
Calls hang up immediately after being answered
Voip calls hang up immediately after being answered. No matter which direction.
(Using Omnia 2, WM 6.5)
Any ideas?
nickdo said:
Voip calls hang up immediately after being answered. No matter which direction.
(Using Omnia 2, WM 6.5)
Any ideas?
Click to expand...
Click to collapse
Samsung WM6.5 drivers not compatible with dlls. Please look at outdated cabs link above and go to last page for omnia solution. It works fine on my omnia with Wm6.1. I have tried on WM6.5 on Omnia with same results as yours.
So the only possible solution for Omnia 2 is to downgrade to WM 6.1?
nickdo said:
So the only possible solution for Omnia 2 is to downgrade to WM 6.1?
Click to expand...
Click to collapse
you are right
Hi dhillonbros,
thanks for your new cabs. But now I am even not able to setup my SIP configurartion with Windows Mobile 6.1 on my Omnia II (as you know it is exactly the same ROM you have).
When trying to save the settings I always get the error message you can see in my attachments. What is going wrong here?
At least storing the settings worked for me with the latest outdated cab for WM 6.1. Do you think you can provide a fix?
That is not right. I have an Omnia 2 i8000 windows mobile 6.5 and I am able to use voip on my phone.It works great )!
1. Don't forget to follow the instructions from .txt file
2. I instaled portgo m
3. AutoAudioRoute V2.0
4. Copy paste dll in windows folder.
My PDA is i8000NXXJJ1
jukefox said:
Hi dhillonbros,
thanks for your new cabs. But now I am even not able to setup my SIP configurartion with Windows Mobile 6.1 on my Omnia II (as you know it is exactly the same ROM you have).
When trying to save the settings I always get the error message you can see in my attachments. What is going wrong here?
At least storing the settings worked for me with the latest outdated cab for WM 6.1. Do you think you can provide a fix?
Click to expand...
Click to collapse
Add this file in your windows folder. Thanks
Attached: dnsapi.dll
bbuhas said:
that is not right. I have an omnia 2 i8000 windows mobile 6.5 and i am able to use voip on my phone.it works great )!
1. Don't forget to follow the instructions from .txt file
2. I instaled portgo m
3. Autoaudioroute v2.0
4. Copy paste dll in windows folder.
My pda is i8000nxxjj1
Click to expand...
Click to collapse
----------------------------------------------------------
this is not the integrated solution sir. Thanks for time.
----------------------------------------------------------
dhillonbros said:
Add this file in your windows folder. Thanks
Attached: dnsapi.dll
Click to expand...
Click to collapse
OK. Thanks a lot. Settings could have been applied now. But the error after submitting a call is still the same that I had before with the previous cab version.
See the message from the attached screenshot. I tried calling numbers like +491231234 as well as 00491231234 and 01231234 but the error is always the same.
What to do now?
jukefox said:
OK. Thanks a lot. Settings could have been applied now. But the error after submitting a call is still the same that I had before with the previous cab version.
See the message from the attached screenshot. I tried calling numbers like +491231234 as well as 00491231234 and 01231234 but the error is always the same.
What to do now?
Click to expand...
Click to collapse
There is nothing wrong with these cabs by looking on your images. either there is a problem with your local network or its your internet provider who doesnt supports or block voip packets. you only need one codec out of three, your phone wil self configure with provided codec. Can you untick SIP ALG service in both modem and router you may be using. If its not that then change your provider to voipvoip.com(US based). Let me know your results
dhillonbros said:
There is nothing wrong with these cabs by looking on your images. either there is a problem with your local network or its your internet provider who doesnt supports or block voip packets. you only need one codec out of three, your phone wil self configure with provided codec. Can you untick SIP ALG service in both modem and router you may be using. If its not that then change your provider to voipvoip.com(US based). Let me know your results
Click to expand...
Click to collapse
My phone works great with other not integrated solutions like PortSIP or AGEphone Mobile, so my network is fine. And there should not be a problem with the codecs as well as PortSIP (I don't of the codecs AGEphone uses) uses G711U, G711A and GSM as well (I know of them because theses codecs are configurable over the GUI).
I use AVM FRITZ!Box 7390 as modem / router with its own SIP registrar. That means my Omnia II is configured to use my FRITZ!Box as a SIP server whereas my FIRTZ!Box is connected to my VoIP service provider (the popular German internet provider 1&1) and redirects the VoIP packets to them. It is totally transparent to the SIP client therefore no STUN / ALG (I never heard about ALG before) is used between the SIP client and my FRITZ!Box.
I am not willing to create an account at voipvoip.com because I definitely want to use the phone numbers I got from my ISP but I may provide you credentials for testing purposes to use a phone number from my ISP if you like.
PortSIP runs with the codec G711U as well as G711A with my provider 1&1. GSM does not work.
Moreover I tested a different VoIP configuration on my Omnia II against pbxes.org as an alternative to my routers SIP registrar with the same result.
I still assume a problem with the cabs. I really want to invite you to try to reproduce my problem by connecting against pbxes.org either by creating an own totally free account with registration to a SIP provider of your choice (I may help you with the configuration at pbxes) or by running against my own account at pbxes.org with a number of my ISP.
Please let me know whether you are interested then I will PM you the settings you need for temporary usage. Of course I will donate for your help.
jukefox said:
PortSIP runs with the codec G711U as well as G711A with my provider 1&1. GSM does not work.
Moreover I tested a different VoIP configuration on my Omnia II against pbxes.org as an alternative to my routers SIP registrar with the same result.
I still assume a problem with the cabs. I really want to invite you to try to reproduce my problem by connecting against pbxes.org either by creating an own totally free account with registration to a SIP provider of your choice (I may help you with the configuration at pbxes) or by running against my own account at pbxes.org with a number of my ISP.
Please let me know whether you are interested then I will PM you the settings you need for temporary usage. Of course I will donate for your help.
Click to expand...
Click to collapse
Thanks for testing it out. On my omnia ii it is working with no problem with great voice clarity. I have changed few setting and tweaked for a-law. My provider is 2talk.co.nz. I still believe there must be some setting which needs enabling in your modem/router. can you bypass your routing by using differnt modem/router without server. Thanks
dhillonbros said:
Thanks for testing it out. On my omnia ii it is working with no problem with great voice clarity. I have changed few setting and tweaked for a-law. My provider is 2talk.co.nz. I still believe there must be some setting which needs enabling in your modem/router. can you bypass your routing by using differnt modem/router without server. Thanks
Click to expand...
Click to collapse
Hello again,
I already bypassed my router by configuring my pbxes.org account, didn't I? Anyway I now switched my router with integrated telephony services support by an older FRITZ!Box 3130 without telephony services to exclude any conflicts with reserved ports or somewhat else. And you know it: Same result.
Last but not least I tried a connection over 3G by activating that option within the configuration. But I failed already with selecting the service. The search action did not succeed.
I'm running out of ideas. What now? Shall I setup an account for you? I really wanna see whether you are able to reproduce my problem or not.
Thanks a lot.
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.