• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Native SIP client vs. 3rd Party SIP client

D

dylane

Well-Known Member
I want to use my Android phone with my work SIP phone provider, so that I can make and receive work calls on my phone. Android has apparently included a native SIP stack as part of the phone application since 2.3. It looks like U.S. carriers typically remove this feature, but I think you can get it back if you root.

There are also 3rd party clients like Bria that are for sale in the market with additional features.

I like the idea of the native client, partly because it is free, but also because it seems like it will be better integrated into the phone. My current phone (Nokia N900) has integrated SIP support (along with a bunch of other protocols like Skype and GTalk) and it works really well and is always running. I'm assuming that the native SIP stack in Android would be functionally similar, but I would appreciate any thoughts from anyone who has experience either with the native client or with a 3rd party client on Android.

Thanks,
Dylan
 
dylane said:
I want to use my Android phone with my work SIP phone provider, so that I can make and receive work calls on my phone. Android has apparently included a native SIP stack as part of the phone application since 2.3. It looks like U.S. carriers typically remove this feature, but I think you can get it back if you root.

There are also 3rd party clients like Bria that are for sale in the market with additional features.

I like the idea of the native client, partly because it is free, but also because it seems like it will be better integrated into the phone. My current phone (Nokia N900) has integrated SIP support (along with a bunch of other protocols like Skype and GTalk) and it works really well and is always running. I'm assuming that the native SIP stack in Android would be functionally similar, but I would appreciate any thoughts from anyone who has experience either with the native client or with a 3rd party client on Android.

Thanks,
Dylan
Click to expand...

I use the native stack with Sipgate which works well for my level of use (receiving calls only when at home).
To start receiving calls I have to toggle it on. There is some battery drain associated with keeping the connection to Sipgate live as you would expect.
 
CodeMonkey said:
I use the native stack with Sipgate which works well for my level of use (receiving calls only when at home).
To start receiving calls I have to toggle it on. There is some battery drain associated with keeping the connection to Sipgate live as you would expect.
Click to expand...

Thanks. Not familiar with Sipgate, but I was hoping for minimal battery life difference while keeping the connection on all the time, which is what I was hoping the native stack would allow.

I'm not clear on what is going on in the backend with the connection the SIP provider, but adding both Skype and SIP credentials to the native phone app in my N900 didn't have a noticeable effect on battery life, and there is no need to enable or disable the connection ever (not even sure if there is a way to do this other than deleting the account)
 
dylane said:
Thanks. Not familiar with Sipgate, but I was hoping for minimal battery life difference while keeping the connection on all the time, which is what I was hoping the native stack would allow.

I'm not clear on what is going on in the backend with the connection the SIP provider, but adding both Skype and SIP credentials to the native phone app in my N900 didn't have a noticeable effect on battery life, and there is no need to enable or disable the connection ever (not even sure if there is a way to do this other than deleting the account)
Click to expand...

It's not so much enabling / disabling the connection, more (as I understand it) toggling a keep-alive state that improves reliability.
 
You must log in or register to reply here.
Back
Top Bottom