Jump to content

Recommended Posts

Guest madmax22
Posted
This is from a newbie with 2 posts. Not that I don't appreciate your efforts, but there are too many instances of malicious apps on android, and with the increase in identify thefts & premium SMS theft, this is too risky.

To all users - USE AT YOUR OWN RISK.

1.3.7 works on blade with froyo 2.2 alpha, both incoming and outgoing use the correct speaker. excellent....

I havent tried the verison posted above.

Posted

1.6.1 beta seems to work correctly too from the brief play i had tonight. Unfortunately I can only get it to register using wifi as t-mobile seem to be blocking voip from what i can tell....

  • 4 weeks later...
Guest spicysomtam
Posted (edited)

The new 2.0.1 is broken; back to speakerphone issue . Grrr

Thanks to you folks here, I installed 1.3.7, and that works fine :P 1.5.7 is also broken. 1.6.1 is no longer available for download (bad version?). The user interface is not very nice on 1.3.7 and you cannot dial easily from the app and the dialer integration is pretty horrible in that it totally wants to take over your dialer. So I set it up so that to call over sip, I need to select a number, select messages and then select sip driod. Ok a couple of more taps, but I can easily live with this as my sip dialing is low compared to normal dialing. Shame sipdriod needs to run as a process all the time. Apparently you can also use a + after the number to select sip driod, although have not tested this.

All these voip apps have a problem with the Blade. Looks like the Audio is not setup correctly in the kernel. Its not a problem limited to this handset; alot of other handsets have the problem, including Samsungs! Personally I think someone need to provide more audio options in the settings for these apps, so you can fine tune the app for *buggy* handsets. Eg you can choose what audio channels are selected for audio output. Maybe Google can lead with some example code?

Edited by spicysomtam
Guest Just Wondering
Posted
1.6.1 beta seems to work correctly too from the brief play i had tonight. Unfortunately I can only get it to register using wifi as t-mobile seem to be blocking voip from what i can tell....

Hi , might be worth grabbing a 3 (three.co.uk) sim as they seem to allow voip with no issues , i'm on there 30 day rolling contract , 10.00 a month with 100 mobile minutes , 3000 txts , 2gb data , plus a load of 3 to 3 minutes , you can get a better deal if you sign up there 12 month contract , infact on one of the deal sites i spotted them offering i think 300 minutes and all of the other stuff for 10.00 a month...pretty good deal really , i find 3 works really well in my area.

1.61 works a treat

please keep us updated of any new versions that also work pls.

Guest Putterill
Posted
All these voip apps have a problem with the Blade. Looks like the Audio is not setup correctly in the kernel. Its not a problem limited to this handset; alot of other handsets have the problem, including Samsungs! Personally I think someone need to provide more audio options in the settings for these apps, so you can fine tune the app for *buggy* handsets. Eg you can choose what audio channels are selected for audio output. Maybe Google can lead with some example code?

One of the Hullomail devteam has posted some info in another thread which explains a similar problem and gives a possible solution:

http://android.modaco.com/content/zte-blad...e/#entry1495136

Guest GreenTurbo
Posted

First post so hi all.

My tip is http://www.acrobits.cz/index.php?id=28 it is in a beta form but free to test so worth a try..

I was looking for a generic client that I could use with my companies SIP server and this fitted the bill and seems to work very well. I was aware they did a client for the iphone but not Andriod until now.

James

Guest tanivula
Posted

Just installed the latest version of Fring from the market and set up SIP (voip) and seems to be working well so far. Sound is coming out where. I expect it to be coming from :-D

  • 4 weeks later...
Guest zurpher
Posted

I have installed SIPdroid 2.0.1 and linked to pbxes.com which I have configured with sipgate.de

Apparently, SIPdroid is registered with pbxes.com extensions - confirmed by greed dots in the taskbar - and those extensions should lead on to the sipgate.de trunk for outbound calls. However, I can't get it working properly. I followed the guides on sipdroid.org but still no luck. I always get a voice message after approximatel five seconds that I should try to call again later. I have experimented with different landline number prefixes +49511, 49511, 0049511, 0511 but none of those worked.

Does anyone has managed to establish a working connection between SIPdroid, (pbxes.com), and sipgate? I would appreciate help with trouble shooting.

ps: I also tried to enter the stun.sipgate.net sever address at SIPdroid directly but that also didn't fix the problem.

Guest isambard
Posted
I have installed SIPdroid 2.0.1 and linked to pbxes.com which I have configured with sipgate.de

Apparently, SIPdroid is registered with pbxes.com extensions - confirmed by greed dots in the taskbar - and those extensions should lead on to the sipgate.de trunk for outbound calls. However, I can't get it working properly. I followed the guides on sipdroid.org but still no luck. I always get a voice message after approximatel five seconds that I should try to call again later. I have experimented with different landline number prefixes +49511, 49511, 0049511, 0511 but none of those worked.

Does anyone has managed to establish a working connection between SIPdroid, (pbxes.com), and sipgate? I would appreciate help with trouble shooting.

ps: I also tried to enter the stun.sipgate.net sever address at SIPdroid directly but that also didn't fix the problem.

i used sipdroid with sipgate.co.uk. i had it dialling, and was able to call a landline, but didn't pick up the test call to check the line quality.

Guest zurpher
Posted
pbxes:

http://www.android-hilfe.de/58242-post72.html

See 3. for sipgate! (do everything but number 2.)

Thank you for the link. It helped me to realise that I've entered the wrong SIP server: "stun.sipgate.net" instead of "sipgate.de". Before solving this issue, I've tested sipgate for android/1.7 beta 5. However, the call quality wasn't good with an echo on the PSTN landline side.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.