Related
Hi
I am new to this form.
I had a look at the tsril.zip example as it seems from this forum that to make/receive a data call the ril is the only option. Unfortunately the documentation for ril is nonexistent and I want to ask if someone has done an example of a client/server data call, data transfer between to XDA's.
Thanks in advance.
Anton
It all depends on what type of data you want to transfer. I have never used RIL so I don't know the advantages of it, over the normal programming interface. I say normal, not thinking there is anything wrong with RIL but the little I do know is that RIL is operating system level and is normally hidden from the application programmer. There must be times when RIL must be used if Microsoft forgot functions in the normal APIs.
However I would say that for a data link between 2 devices then RAS seems the way forward. One device would be the Server and the other the Client. I have only ever programmed RAS from the client side, making a Telnet link to an already running server.
I just had a look at the help on Embedded Visual C++ 3.0 and under 'Creating a TCP Stream Socket Application' it explains the server side and then links to the client side. Have a read there.
RAS is not an option as it is a server consept, which I think does not even exist as a service on the desktop windows os let alone on a Pocket PC.
What I am looking for is something similar that you would be able to do with a landline modem or a gsm modem connected to a serial port of a pc (even a usb modem) which is to send AT commands to make/accept a call and then to make use of the serial port as if it is an io stream. This is possible on windows, linux using either c#, c++ or java. I can even do this with an embedded gsm module like the siemens TC45 java module.
What I can not understand is why Microsoft and the XDA suppliers (I am using a Qtex running Pocket PC 2002) is making it so difficult to make/answer a data call and let you run your own protocol over the connected stream.
RAS (Remote Access Services) is built into all Windows Operating Systems, including Windows CE. Did you look up the help example I pointed to ? What you do with RAS on an application level is for you to code but the connection itself is handled by the operating system.
As to making a connection similer to a modem and using AT commands. Then no you can't use AT commands directly, but you don't need to. To get that type of connection you need to use TAPI. Once Tapi has made a DATA_MODEM type connection, you use the TAPI callback connect event to then ask for a file handle that you can use with the normal WriteFile and ReadFile commands.
I already have something on this forum about that see:-
http://forum.xda-developers.com/viewtopic.php?p=7857&highlight=#7857
The problem is not so much making the data call but it is accepting/answering the data call that I can not get working on the XDA
Not sure if this is your problem, but in Australia they have a seperate "data" phone number for the same SIM. If yo call one number you get voice, if you call another number you get data on the same sim. Not sure if this may be effecting you.
I just looked into all this ras stuff a bit deeper, and yes I think I may of been talking rubbish. Although RAS does exist in PPC2002, it can't see any functions that allow the device to answer the line. I can see that PPC2003 has a Ras Server and RasIOControl that looks like the answer there.
Also looking into Tapi, I can't see how you answer a data call using that.
So I now understand your problem. It seems PPC is made as a client device.
Is GPRS the answer ? With that the link is always present and then you can use the built in Ras functions on seperate devices. Since you only pay for data actually sent then would it matter if the network link was always present ?
I have only worked out Tapi and Ras from the client side so I have never had this problem, but I agree it is an interesting one. I will have a bow out of this thread for a bit and see if anybody else knows how to Answer a Call.
Thanks for trying.
GPRS is also not the answer as you need a server in between that both XDA's can connect too and use as a router as the XDA's do not get fixed IP adresses but actually a NAT adres from the APN so you can not connect directly between the two.
Now that's an interesting thought, how about using some free web space to act as a pigion hole for your data ?
Believer: A seperate number? How do you know this, and what would the number be?
I can actually make two XDA connecting to each other using TCP. The trick is that I have one client always connect to a server to register it IP address with an ID. Then the caller send a query to the server to look up the callee's IP address.
In this way, accept() and connect() work fine.
I am using AT&T network and not sure about if other networks behave the same.
I wrote two application using TAPI. One is ModemDial and the other is ModemWatch, if I make a voice call the ModemDial dials the number successfully and ModemWatch reports that an incoming call exist. But when I change the behavior of call to DATAMODEM, the ModemWatch couldn't track any incoming call.
Is there any one, had some experience with pick a call for DataModem?
Best regards,
A. Riazi
riazi said:
I wrote two application using TAPI. One is ModemDial and the other is ModemWatch, if I make a voice call the ModemDial dials the number successfully and ModemWatch reports that an incoming call exist. But when I change the behavior of call to DATAMODEM, the ModemWatch couldn't track any incoming call.
Is there any one, had some experience with pick a call for DataModem?
Best regards,
A. Riazi
Click to expand...
Click to collapse
In your ModemWatch application make sure you are calling lineOpen with dwPrivileges (the 7th parameter, 1 based) equal to LINECALLPRIVILEGE_OWNER and dwMediaModes (the 8th parameter) equal to LINEMEDIAMODE_DATAMODEM.
If you're able to answer a voice call successfully, making these changes to the ModemWatch application should allow you to answer a data call.
There's a need in mobile PC/GSM device which allows to put a software filter on voice which is transmitted via GSM network when talking.
Can it be done on XDA2 and if not which models will you suggest?
The filtering needs to be done on digital signal not packed to GSM packets, in both directions, during the talk - in realtime.
Thanks in advance.
Re: XDA2:Is there some software handler possible on GSM voic
This is impossible on XDA1,2,3 and Anextek SP230. Probably this is a limitation of PocketPC 2003 (even SE) OS. Wait for a device with a PPC 2005, maybe it would support this.
sure
it IS possible.
but you must delete default Phone application and services. and then you can run your own implementation of phone features with filter or anything other inside the voice channels.
please note: default Phone is invoked by several services, you have to lock all these ways.
Hi,
Anyone knows any free VOIP softphone for O2 Exec which allows to configure to use third-party SIP providers (e.g. sipdiscount, sipgate etc.) ?
Thanks!
SV
use skype
Sorry, I meant to configure with SIP protocol.
sjphone, works fine
With SJPhone, at the moment, when calling, you have to use loud speakers or headset not the phone speaker. Is it right?
Thanks!
That happens with any phone edition device.. Apps don't have access to the other speakers...
Re Sip
I have tried many. However most free products are generic to a provider,
Successful products are:
Xten lite from xten Networks
SJ Phone this is the best and is easily configured to multiple profiles.
It intergrates nicely with our office Sip server too,
Regards
DW
Re Sip
I have tried many. However most free products are generic to a provider,
Successful products are:
Xten lite from xten Networks
SJ Phone this is the best and is easily configured to multiple profiles.
It intergrates nicely with our office Sip server too,
Regards
DW
svkhtn said:
Sorry, I meant to configure with SIP protocol.
Click to expand...
Click to collapse
May I know what is SIP protocol?
Is it different with Skype protocol? Is SIP protocol is a standard one?
Thx.
Regards,
Arto.
Artosoft said:
May I know what is SIP protocol?
Is it different with Skype protocol? Is SIP protocol is a standard one?
Click to expand...
Click to collapse
SIP is a standard - most VOIP application and hardware uses it.
I meen: SIP RFC 3261
Skype is a own protocol and only skype clients can connect each other using skype soft phone or by skype gateway.
I guess that the source is not public.
I use AGEphone.
http://www.ageet.com/us/
It is not Free.
But, maybe best.
Files are light, but works very well.
the sound is very clear.
We can use SIPdiscount, VoipBuster, VoipStunt, StanaPhone, SIPphone, Free World DialUp, Agilephone, etc all at the same time.
I installed SJPhone and could get connected. I could dial my cell phone number and it will ring my cell phone.
But there is no sound whatsoever in my Universal/JJ.
Can anybody help me? Did I miss something? I tried to plug in my headset but no luck as well.
Thanks.
Also, may I know which version of SJPhone you guys use?
Can you send the link for the download? I can only find the one for 2003SE and 2003, nothing for WM5.
Since I didn't see a follow-up post by anyone, I'd like to say that the SJPhone for Windows 2003 SE works with the universal *only in portrait mode*.
Has anyone [other than shamilsh] tried the ageet soft phone suggested in this thread?
Does Skype work over GPRS or just 3G?
Regards.
Just for text messages, skype is ok with GRPS - but for voice you need 3G oder WLAN.
Hi
Any sip cliente for wm5 that have G.729 (8 kbps) or G.723 (5.3 & 6.3 kbps codecs ?
sj phone only 711 or their own gsm....
Owl said:
Just for text messages, skype is ok with GRPS - but for voice you need 3G oder WLAN.
Click to expand...
Click to collapse
Is that need 3G as in would be slow, or need as in can't do it...
Just that GPRS is free for the T-Mobile plan I'm using, but think I have to pay for 3G (Relax + Web & Walk thing)
are there any programs that allow routing of the sound to phone speakers instead of main speakers?
Guys....just use sj phone with sip service from voipbuster.com and forget the rest.... and now you are talking....FREE and with free local rate call back number also...now...that ROCKS :twisted:
BR
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
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.