Closed GoogleCodeExporter closed 9 years ago
Only if udp is selected. If auto is selected in setup
It works but take a long time to connect a call.
Original comment by p...@suntec.dk
on 12 Dec 2010 at 10:41
Keep alive have been refactored entierly to ensure to lock cpu. As consequence
this should be fixed now.
Original comment by r3gis...@gmail.com
on 29 Jan 2011 at 10:46
Problems I have found
1. I encountered few times, After my calling, I press end call but the
call can't end itself.
2. The call duration starts counting even when remote party has not answered
Original comment by ronald19...@gmail.com
on 29 Jan 2011 at 10:50
Hi
I am not sure why my Samsung i9000 is sip registration problem. The
display shows sip device registered but my sip server is not showing
the device registered especially when it is using battery. In the same
scenariom I have wifi always on with skype. I can see skype online and
I am able to call back to skype.
Seems like csipsimple is having problem when running in battery.
Original comment by ronald19...@gmail.com
on 31 Jan 2011 at 9:39
Did you try to change wifi sleep policy to never. I suscpect skype to turn that
on. I do not to not drain battery. Maybe I should?
Original comment by r3gis...@gmail.com
on 31 Jan 2011 at 9:49
Actually my wifi sleep policy is set to never.
After investigation seems like it is router related problem. I cant
confirm yet. I will make for test again.
By the way, do you have any interest to implement callback into
csipsimple? After all its another service to save money on phone toll.
You filter feature is something interesting which you can add callback
dialer into it.
Upon filtered number detected or choice callback dialer, use callback dialer.
Setting includes
few choices of Callback Server number
Prefix , Suffix feature
predial wait time
pre-end call prefix and wait time
After selecting number from contacts or direct entry, store the wanted
number and dial server number. After XX sec if call not disconnected,
for call to disconnect. Wait for incoming call. Once incoming call
intercepted, wait for xx sec, dial stored number and start
conversation.
end conversation when end call button press, dont hang up call
immediately. send pre-end call prefix and xx sec hangup phone.
Procedure ends.
Original comment by ronald19...@gmail.com
on 1 Feb 2011 at 9:31
Hi
I think it is the csipsimple problem. When I restarted my router,
csipsimple is not registering to the server but if I inactive and
active the account, it is working.
I think to ensure csipsimple is always registered, can we make
registration TTL by inactive and active the account?
This way I think csipsimple will not miss the registration
regardless what condition.
Original comment by ronald19...@gmail.com
on 2 Feb 2011 at 10:19
Callback is planned. There is an open issue about webcallback but it will
package much more than just web. Also call accessing some access number etc.
That's not a priority cause obviously that's not a sip feature and would be
better (in term of software design and modularity) if done by another
opensource app.
But if no opensource app do that when I'll get time to do it, I'll implement
those advanced features.
As for your problem with keeping alive the registration.
Two things can be looked at :
*The keep alive option in csipsimple settings > network > keep alive for wifi
and for 3g.
and
* The re-registration time of the account. To edit it, transform your account
into an expert account. (Long press on it and "choose wizard"), then edit the
account and you'll find extra options to set re-registration time. For example
you can try 60s. By default it's 15 min cause on most networks and most sip
providers that's just fine with it and does not drain battery. But if your
network/sip provider requires higher values it can be tweaked here.
Original comment by r3gis...@gmail.com
on 2 Feb 2011 at 12:29
Actually I dont see webcallback is a plus. Since webcallback involve
in data, user must well use sip dialer to make call directly. After
all, data connection involve data charges. While callback dialer is
different thing. After all sip or callback or calling card is to save
phone toll.
Sip is good when using unlimited data plan. Data connection is cheaper
than direct long distance toll.
Webcallback is good only if sip is blocked by local ISP or mobile
provider. callback server number is blocked by local operator (but
this is usually not possible since callback service provider can
change callback number regularly). Or piggy back with webservice and
interface to trigger callback
Callback is good for home, mobile (when incoming call free or incoming
call + international toll is cheaper than calling directly from
mobile)
So to save phone toll, I can see only 2options is good. So callback
dialer should have higher priority than webcallback.
So far I dont find any callback app in the market nor anyone wanting
to do. I think it is not very hard to do for programmer like you. I
can see the features you have in your csipsimple is rather
professional in the technical side.
I have tested already but fails
I have tried but it does not work. I can ping my device from my PC.
Funny thing is that my phone shows registered but it does not appear
in the server.
I think I have found out the solution. I installed an app called fix
my wifi and I can see my device is in the sip server overnight. I will
continue to monitor for new few days if that is so, I think this app
'fix my wifi' can solve most wifi problems.
Original comment by ronald19...@gmail.com
on 2 Feb 2011 at 10:56
Original issue reported on code.google.com by
ronald19...@gmail.com
on 10 Dec 2010 at 2:28