I have to build a SIP application for my studies, i maked an Asterisk server, testing it with xlite and all is working. However, i wanted to test it in my Android phone(has 2.3 Gingerbread), i installed the SIPDemo app on it, adding the useful informations and nothing happens, it doesn't indicate if you are connected on the server or not. I run the application in the Android emulator and it saids "Registration failed".
Can you please help me? I really have to make this project to have my diploma.
Thank you very much.
from asterisk cli (asterisk -rvvvvvvvvvvv) you should type:
sip set debug on
and then try to register, this will let you debug the situation.
This could be an asterisk configuration problem or wrong SIP registration management on client's side.
If your registration is successful after removing password from asterisk's user then you need to check how SIP handles registration process https://www.rfc-editor.org/rfc/rfc3261#page-56 and stick to those rules with your demo.
Related
I am looking for an open source sip project to add my android application. I found IMSDroid project, downloaded the source code and build on Android ADT.
But when I install the application on my android phone, I cannot register to sip provider(sip2sip.info). I tried on both 3G and WiFi networks but Sign-in always fails. I followed the instructions at this link https://code.google.com/p/imsdroid/wiki/sip2sip_info but no success
By the way, I downloaded CSipSimple application too. I simply filled the registration settings and it worked! I mean CSipSimple application can register to sip2sip while IMSdroid cannot.
I also tried SIP stack of Android. There is a sample application using sip stack of android, called SIPDemo. I also tried this application but its registration also failed.
What is the issue about? I don't want to use CSipSimple because to me it seems more complex than IMSDroid.
I have a nodejs v0.10 server with socket.io (v0.9.16) running on Openshift, for the past 2 months it has no problem receiving data from my Android apps connecting to the server using AndroidAsync (https://github.com/koush/AndroidAsync). Suddenly after Openshift upgrade its service on 25th Feb the Android app fail to connect to the server. Every time the app tries to connect the server, the server will output an error, I run Socket.IO in debug mode and this appear (debug: destroying non-socket.io upgrade).
Funny thing is, the same server also host my web client running the same socket.io library, and it has no problem whatsoever with the web client. Can someone please point me to the right direction? I am connecting to the server with http://www.xxxxxx.com:8000/ where 8000 is the websocket port given by Openshift.
I read that "destroying non-socket.io upgrade" might due to invalid/incompatible socket.io js file, I tried to do a manual check on the socket.io file by typing this in my browser
http://www.xxxxxx.com:8000/socket.io/1/
I got this return code:
An-vI1BJofr45j9c_GmH:60:60:websocket,htmlfile,xhr-polling,jsonp-polling
PS: My Android code hasn't been changed, and so is my server code.
PPS: I have successfully connect in localhost environment and my own server. So the problem is most probably originated from Openshift, not sure what have been updated to break it.
All of a sudden it works again without any code changes. I would however recommended anyone using my approach of connecting to backend server to have a http push backup just incase any future server updates breaks it again.
Would appreciate if anyone from Openshift can help clarify this to prevent sudden death on running production apps. Thanks.
Make sure to check OpenShift Online's system status page to see if your apps have been impacted by a system outage. (fyi: we run on top of AWS)
I would definitely consider using one of OpenShift Online's paid hosting plans for production quality applications. Apps that are created using paid plans go onto a separate array of machines (more resources), and are configured to be more highly-available (no sleeping due to inactivity).
Hope this helps answer your question. Please close if so.
Has anyone made a small basic application using SIP for android? I have tried using CSipSimple app, with SIP account on antisip.com and sip2sip.com but none of them register properly, and it gives a timeout error.
I also tried those accounts with the SipDemo given with Android, and also in Linphone app. Linphone works fine with a SIP account on Linphone itself, but no other SIP accounts works.
If you want to try it out with CSipSimple, Add Account > OSTN
Account name: OSTN
Username:<yourusername>
Password:<yourpassword>
Server: ostel.co
(Register first #ostel.co)
Or you can download SipWise CE and setup your own local Sip Service Provider - you will not face errors like timeout (as long as you are not far from your wi-fi coverage)
I need to test the C2DM service. I have already implemented the service in my Android app. Before starting coding the third party server which gonna send the notifications i would like to test my app.
Is there any tool working on Windows (preferably with an UI) which allow me to enter the registration_id of my phone , the account used into C2DM and a message.
I'm looking for a jar or an exe , don't bother to propose php or any web server based script , i can't install any server or interpreter on the computer which have access to internet :'( .
Thanks
C2DM is now depricated.
Use Android GCM http://developer.android.com/guide/google/gcm/gs.html
Finally build my own command line tool based on this article . Probably faster than keep searching a ready to use tool.
I got this to work to run as the server in VB http://www.androidsnippets.com/vbnet-server-side-code-to-send-c2dm-messages
Seems to work nicely, hopefully that's the direction you were talking about.
There is a Google+ mobile application for Android. To receive all the information it must be using some API.
How I can retrieve this information from my phone and see from where this app is getting data? I'd love to access it myself and see how it works.
You are talking about "reverse engineering" a network protocol.
Full sniffing
Get a market enabled emulator: How to install Android Market App on the emulator?
Get a network sniffer: tcpdump, wireshark, ...
Start to sniff what's going over the wire
http://www.thoughtcrime.org/software/sslstrip/ - an ssl stripping proxy
Inject your ca: http://www.mcbsys.com/techblog/2010/12/android-certificates/
This should, in theory, enable you to sniff any https or plain text connection.
Already available APIs
I would not try to hijack the connection. There is already a contacts API, it's called xmpp. You should be able to use the talk integration to pull your friend list.
Future APIs
You may also want to sign up for the upcoming API.
UPDATE
It appears that the Android client uses (at least partially) XMPP. The regular client requires an open XMPP connection and you can see a "RealTimeChat" in your logcat. It looks like the connection is encrypted because you get a "TLS required" message (the client seems to go through the XMPP connection states). I'm not sure if that's used for client based posts or just for server push. You can see the open connections with the help of "netstat". The connection goes away when google plus terminates.
I'd thus expect the API to be really open once released (or rev.eng).
UPDATE 2 (06. Jul. 2011)
Hangout is build on XMPP/MUC+JINGLE (muc == multiuser chat, jingle is roughly a SIP alternative on top of XMPP). And yes, they'll release the the details of it :-)
UPDATE 3 (06. Jul. 2011)
Multiple XMPP components for gtalk/gplus have been revealed by reading the JS code. It also emphasizes that they have build a great deal of features on XMPP.
They haven't launched the API yet. If there is something you want to build on Google+, they encourage you to signup here: https://services.google.com/fb/forms/plusdevelopers/
The API hasn't been released yet. Heck, the product hasn't even been released yet. Thats like developing a video game for playstation 5.
Yes it is. Its coming "soon" read :: http://www.webpronews.com/api-coming-soon-for-google-plus-2011-07